Shooting Schedule: How to Build One That Survives the Shoot Day

A shooting schedule rarely fails because someone planned too little. It fails because the plan lives in a spreadsheet nobody opens once the day starts — fifteen tabs deep, with Tuesday's version still circulating, and nothing legible on a phone.

This article covers how to structure a schedule that survives contact with reality: what each block has to carry, how to place buffers that do not evaporate by mid-morning, and where the line runs between the shooting schedule and the call sheet.

A shooting schedule and a call sheet are different documents

The terms get used interchangeably, but they answer different questions — and confusing them is the first reason plans become unreadable.

	Shooting schedule	Call sheet
Span	the whole production	exactly one shoot day
Audience	production, director, client	the crew turning up tomorrow
Contents	all shoot days, locations, time frames	call times, addresses, running order, contacts
Question it answers	"when do we shoot what?"	"where am I, when, and what happens there?"

The schedule is the overview. The call sheet is one day pulled out of it, plus everything the set actually needs: meeting point, parking, contacts, weather. On a one-person shoot they collapse into the same document. From two units upwards you want them separate, or the camera unit reads information meant for someone else.

The block is the right unit of planning

Most schedules are lists of clock times. That works exactly until something slips — and then not a single row is accurate any more.

Planning in blocks is far more robust. A block is one self-contained unit with one setup: an interview, a B-roll run, a product detail. Each block carries the same five facts:

1. What is being shot — the title, plus the shot-list reference if there is one
2. How long it takes — the duration, not just the start time
3. Who is on it — the team or unit, not every individual
4. Where — the location, with travel and meeting point
5. What with — the gear this particular block needs

The payoff shows up at the first delay: when blocks carry durations instead of fixed clock times, everything after them moves automatically. A list of clock times has to be retyped row by row in the same situation — usually while the crew stands around waiting.

Turnaround is its own block

The most common planning mistake: strike, relight and travel never appear in the schedule. They happen anyway — unplanned, and at the expense of the next block.

Lighting an interview rarely takes under 30 minutes. Moving locations inside a city costs the travel time plus load-out and load-in, so realistically double the drive itself. Entering those as blocks produces a schedule that shows less shooting time but actually holds.

Buffers that genuinely save the day

Why the spreadsheet stops working on set

For the planning phase, a spreadsheet is perfectly fine. On the shoot day it breaks for three reasons:

• Versions. The moment the plan is sent as a file, it exists in several states. "Is this the current version?" costs more time on set than the change itself did.
• Legibility on a phone. Nobody opens a laptop on set. A fifteen-column table on a six-inch screen is not a working document.
• Too much information per person. The camera unit needs its next two blocks, not the master plan with every team on it. Every row that is not theirs is a row their own can hide behind.

Then there is the client, who wants to know when things happen but has no business seeing every internal note and every turnaround gap. In a shared spreadsheet, those are the same document.

One plan, seen by crew and client at once

That is what production planning in Exportlab is built for: one plan, as many shoot days as you need, and everyone sees the slice that concerns them.

The planning side covers six areas that usually live in separate files:

• Schedule & timetable — blocks with time, duration, team and location. Move one and everything after it moves with it.
• Teams & crew — who is on which block. Crew join by invitation link, with no forced account.
• Content & scripts — every block knows what is being shot, with the shot list and script alongside it.
• Locations & map — all locations on one map, coloured by unit, with travel and parking.
• Equipment & checklist — what has to come along, tickable per block.
• Stakeholders & client — the client gets a link and sees only what has been released.

On the day itself the app takes over. It shows the block running now and the one after it, for exactly the person looking at it, without scrolling past other units. There is a checklist for on-site, and the day stays readable offline — which in underground car parks and rural venues is the difference that matters.

The scale is open-ended: from one person alone with ten blocks from setup to wrap, up to four shoot days with three units across eight locations. You do not have to use all six areas — one day, one block, done, works just as well.

For context: production planning is currently in beta and enabled per workspace.

From the schedule to delivery

A shooting schedule does not end at wrap. The material has to be reviewed, cut, approved and handed over — and for most productions that takes longer than the shoot itself.

When the plan and the delivery sit in the same project, the handover stops being a break in the process: footage lands where the block was planned, video feedback hangs off the same project, and the client watches progress on a status page instead of asking. For collecting frame-accurate feedback rather than emailed timecodes, the comparison of video review tools goes deeper.

FAQ: Shooting schedules

Conclusion

Building a shooting schedule that holds is less about the tool than about the unit of planning: blocks with durations instead of a list of clock times, turnaround as its own block, buffers where the delay actually occurs, and critical content early in the day.

The second half is distribution. A plan everyone sees at the same time, where each person gets only their own slice, removes exactly the questions that otherwise land between two blocks. Production planning shows what that looks like in practice — and if you want to keep the client informed after the shoot without letting them into the plan, a status page does that job.