A minute-by-minute event-day timeline that solves itself. Move one moment and every call time, buffer, and golden-hour window recalculates — instead of hand-typing every row in a spreadsheet that breaks the moment plans change.
The depth you need, none of the noise you don't.
Times are never typed — they are solved from sequence, duration, buffers, and travel. Anchor a block to a fixed time, a key moment, or let it float from its neighbours. Change one thing and the day reflows around it.
Anchor portraits to sunset or sunrise and ClientCasa computes the exact window from the venue's coordinates. Set the location once with address autocomplete; the timeline keeps photos in the light.
Drag a key-moment line to push the ceremony later, drag an edge to resize a block's duration, or use "Shift day" to bump everything ±N minutes. Every downstream time follows.
Ask Coach to review the timeline for conflicts, tight gaps, and portraits scheduled outside golden hour — then apply its one-click fixes. "Set up this day" tailors a starting timeline to your event type.
Keep a reusable vendor rolodex, assign call time, coverage, and meals per event day, and generate a call sheet scoped to each vendor. "Add vendors from booked services" suggests vendors from the client's accepted quote.
Publish a read-only portal where clients comment and approve. Approval freezes a versioned snapshot, so the timeline they signed off on stays the timeline of record.
A full-screen, offline-ready day-of view with a NOW / NEXT hero and Start, Done, and Skip controls. "Running 12 min behind" reflows the rest of the day; it syncs when you reconnect.
Export the master timeline or a single vendor's slice as a PDF or .ics. Per-audience visibility builds Master, Client, Venue, Shot list, and Wedding party views from one source.
Read and write event days, timeline items, and vendor assignments over the v1 API with OAuth or API-key scopes. Webhooks fire on event_day_published, timeline_item_completed, and more.
See how your industry uses this feature day-to-day.
A spreadsheet stores times. ClientCasa derives them. Every block's wall-clock time is computed from its place in the sequence, its duration, buffers, and travel — anchored to a fixed time, a named key moment like the ceremony, or golden hour. Push the ceremony 30 minutes later and the prep, portraits, and reception all move with it. In a spreadsheet you re-type every cell below the change.
Set the venue location with address autocomplete, then anchor a block — usually portraits — to sunset or sunrise. ClientCasa computes the exact golden-hour window from the venue's coordinates and keeps that block in the light even if the rest of the day shifts. The Audit will flag portraits that drift outside the window.
Yes. The Run Day view is offline-ready. It shows a NOW / NEXT hero with Start, Done, and Skip, tracks how far behind you are running and reflows the remaining timeline, and syncs back when you reconnect. It uses a single-device lease so two people don't fight over the same day.
Clients get a read-only portal where they can comment and approve — approving locks a versioned snapshot. Each vendor gets a scoped share link and call sheet showing their call time, coverage, and the parts of the day relevant to them, dimmed to context. You publish from one master timeline, so the views never drift out of sync.
Yes. The public v1 API exposes event days, timeline items, vendor assignments, and the vendor rolodex with OAuth or API-key scopes. Webhooks fire on events like event_day_published and timeline_item_completed, so integrations and automations can react in real time.
