Where is each person on each day?

Daysync currently models people as app users with permissions. There's no concept of a touring party member as a schedulable entity, so our artists, TM, FOH, guitar tech and photographer only exist as text typed into item notes.

That means Daysync can't answer a basic question: where is this person on this date?

It matters most when the party splits. On a DJ tour with heavy flying, crew are routinely in two or three cities at once — while tonight's show loads in, part of the crew has already flown ahead to start tomorrow's advance. Daysync assumes one linear tour: one day, one city, one venue. Reality is several concurrent threads through the same tour.

What we'd need:

• Party members as records — name, role, contact — not just app users
• Assign a person or sub-group to a day, venue, travel leg and accommodation stay
• Per-person itinerary view: pick a name, see their movements end to end
• Per-day roster view: pick a date, see who's in which city
• Reusable sub-groups ("advance crew", "artist party", "audio") so we're not assigning eight people to every item

The test: can Daysync tell me who's in Berlin on Wednesday and who's already in London?

Knock-on benefit — this unlocks a proper rooming list export, which is per-person by nature (each guest with their own check-in, check-out, ETA and ETD) and currently impossible because check-in/out sits on the stay, not the guest. It also needs to handle a party split across two hotels on the same night, which is normal, not unusual.