Day-Of Schedule Changes: A 1st AD's Protocol for Call Sheet Revisions

Schedule changes are normal. Version chaos is not.

Every 1st AD has lived this morning: the location rep calls at 6:15 AM with bad news, the talent is stuck in traffic, or a thunderstorm just moved your exterior to next week. The day is going to change. That is not the problem. The problem is what happens to information in the next twenty minutes, when half the crew has the old call sheet, three people have texted three different corrections, and the gaffer is already at the wrong parking lot. Changes are normal in production. Inconsistent information is a choice, and it is almost always the expensive one.

Rule zero: one person owns the revision

Before the protocol, you need the person. On every shoot, designate exactly one person who publishes call sheet revisions. Usually that is the 1st AD or the production coordinator. Everyone else routes changes to that person, including department heads, the producer, and the client. No department sends its own correction email. No PA texts a new call time to the group chat. One publisher, one source of truth. If you take nothing else from this article, take that.

The five-step day-of revision protocol

Step 1: Confirm the change with the decision-makers. Before you touch the document, confirm that the producer, the 1st AD, and the affected department heads agree on the change. A rumored change that gets published and retracted an hour later does more damage than a late confirmed change. Get the yes, then move.

Step 2: Revise the master document, not the message. Open the actual call sheet and change the actual call sheet. Do not describe the change in the email body while leaving the attachment stale. The revised document becomes the new source of truth, and every crew member must be able to open it and see the current plan in one place.

Step 3: Label the revision where nobody can miss it. Number every version and stamp it with a time: REV 2, issued 7:10 AM. Put it in the header, large. A crew member glancing at the top of the page should know within two seconds whether the sheet in their hand is current. When two versions float around a set, the unlabeled one always wins the argument.

Step 4: Say what changed in one line. Lead the redistribution with a single plain sentence: Sc. 14 moved to Day 4, crew call now 6:30 AM. Parking moved to the north lot. Company move after lunch canceled. Nobody reads a paragraph of context at 6 AM. One line, at the top, in bold. The full revised document does the rest of the talking.

Step 5: Redistribute through one channel and confirm the affected. Send the whole revised PDF through the same main distribution channel every time, never scattered across email, text, and a group chat. Then actively confirm receipt from the people the change touches: drivers if parking moved, the 2nd AD and talent if call times shifted, the location manager if the address changed. Passive sends lose people. Targeted confirmations catch them.

Announce it out loud on set

Digital accuracy still matters on shoot day, but the fastest distribution channel is a human voice. When a change lands during the day, the 1st AD or production lead announces it verbally: to the whole unit for schedule changes, to the affected department for logistics changes. Then update any printed copies that are practical to replace. If your production runs hard-copy call sheets at base camp, the revision does not count until the printed stack matches the digital one. A crew member who never opens email but reads the pinned sheet is still on the old plan, and that is on you.

Four things to never do

• Never send text-only changes. A text that says call time moved, without the revised document attached, creates two versions of the truth. Always the full document.
• Never split channels. The moment the change lives in email for crew and texts for cast, you have guaranteed that somebody is working from the wrong one.
• Never leave placeholders. A revision published with TBD still in the parking line is worse than a ten-minute delay while you confirm the real answer.
• Never assume a sent revision is a read revision. For anything that touches call times, location, transportation, or safety, get an explicit confirmation from the affected people.

Track who confirmed, not just who was sent to

The distribution list tells you who received the revision. It tells you nothing about who read it. For day-of changes, the confirmation list is the document that matters: drivers confirmed the new lot, talent confirmed the new call time, the medic confirmed the new hospital route. Live digital confirmation tracking is the difference between assuming the day is aligned and knowing it. That is exactly why Easy Call Sheets was built: publish the revision once, distribute in one click, and see in real time who has confirmed and who still needs a nudge.

After wrap: freeze the final version

When the day ends, lock the last revision as the record: final issued version, time-stamped, filed with the production paperwork. If the shoot spans multiple days, tomorrow's sheet starts from the final frozen version, not from a draft with today's scribbles half-applied. Disputes about call times, meal penalties, and overtime are settled by the frozen record, so make the record boring, complete, and unambiguous.

Day-of changes will never stop happening. Weather shifts, talent runs late, locations change their minds. Your job is not to prevent change, it is to keep the information about it moving through one channel, from one owner, with a visible version number and a one-line summary, until every affected person has confirmed. Do that, and the change becomes a footnote. Skip it, and the change becomes the story of the day. Build tomorrow's call sheet the easy way with Easy Call Sheets, and put the night-before spreadsheet grind behind you for good.