The Nightly Call Sheet Workflow: From Locked Plan to Confirmed Crew

The call sheet isn't a document task. It's a communication workflow that happens to end in a document, and most of the pain people blame on formatting actually comes from doing the steps in the wrong order: building before the plan is locked, sending before it's approved, or treating "sent" as if it meant "read".

This is the sequence, and who owns each part of it.

Who owns what

The 1st AD owns the plan. They rarely type the sheet, but if tomorrow's priorities, call times, safety concerns and pace aren't clear before it goes out, the crew feels that confusion at call time.

The 2nd AD or production coordinator owns the document: translating the plan into something every department can act on, distributing it, and knowing who has confirmed. On a small commercial, wedding or content shoot the same person does both, and the sequence doesn't change.

Step 1: lock the plan, then build

Review the next day with the director, DP, production manager and any department heads who need to be there. Confirm the first setup, scene order, company moves, required cast, special equipment, effects, access restrictions and realistic meal and wrap targets.

The rule that saves the most time: don't use the call sheet to solve an unresolved schedule problem. Resolve it, then publish the decision. Chasing changes into a half-built sheet costs more than waiting for a locked plan did. On a small shoot this is a ten-minute call, not a production meeting, but it still has to happen before you start formatting.

Anything genuinely still open goes on the sheet as a clearly marked pending note, not buried in a text thread.

Step 2: build backward from the first setup

Set general crew call from the time the team must be ready to work, not from when the location opens. Then add earlier calls only where prep genuinely requires them.

Build department by department rather than from scattered messages, because working from memory is how somebody gets missed: production, camera, sound, art, HMU, wardrobe, talent, client, agency, assistants, drivers. For each person set a clear role and individual call time, and check the phone and email before sending.

• Location name, full address, parking or load-in point, access instructions
• Individual call times made obvious, so nobody assumes general call applies to them
• Key decision-makers and the best day-of contact number
• Weather, safety, hospital, transport and client details where they affect the day
• Notes that say what changed, who it affects, and when it matters

Step 3: approval, scaled to the shoot

On a larger production the sheet may pass through the 2nd AD, 1st AD, production office, UPM, producer, director and department heads. On a small one it's the coordinator and the director. Either way, keep the review to three questions: what changed, what needs checking, and who gives final approval.

Send the draft as a live link rather than an attachment, so the approver is always looking at the current version. Otherwise a note changes and you're re-exporting and re-sending a PDF just to get a second opinion.

Step 4: distribute, and aim for confirmed reads

Get it out no later than twelve hours before call. The target isn't sent emails, it's confirmed reads, and those are different things. A PDF sitting in an inbox tells you nothing about whether the sound recordist saw the revised load-in time.

This is the step Easy Call Sheets exists for: send by email or SMS, crew confirm or decline in one tap without creating an account, and a live view shows who's in, who declined and who hasn't opened it. Automated reminders chase the non-responders so you're not texting people at midnight. Pull the crew from a contact book or a saved template rather than retyping them, and the weather fills itself in from the location.

Step 5: revise without version chaos

Plans move. A gate code changes, call shifts thirty minutes, weather turns, a client adds a parking instruction. The fix is not another renamed PDF with FINAL in the filename.

• Change only what needs to change
• Resend to the people it affects
• Make the current link the single source of truth
• Keep a PDF export available for printing and offline backup

And don't patch a bad call sheet with five follow-up texts. One clean revision beats a thread of corrections, because everyone ends up reading a different subset of a thread.

The exception is a critical call-time change. Don't rely on a passive update for that one. Contact the affected people directly and get a response, then let the revised sheet be the record.

Keep it lean

Indie and small-crew sheets work best when they're focused. Too much noise and people miss the details that matter, which is the opposite of the point. A fifty-page studio document is solving a different problem than a one-page sheet for a six-person crew.

The test

A call sheet is working when nobody has to ask where to be, when to arrive, who to contact, or whether the version they're holding is current. If getting there still takes manual formatting, a PDF export, reminder texts and a separate list of who replied, the workflow is doing by hand what it shouldn't have to.