Call Sheet Revisions Without the Chaos: A 1st AD's Field Protocol

Revisions are where call sheets go to die. The original sheet is beautiful, timed to the minute, printed at 9 PM. Then the location manager moves the company move up an hour, the DP adds a pickup, and talent's pickup time changes. By 11 PM you have three versions floating around and half the crew reading the wrong one. If you have ever stood on set at 6 AM wondering why the art department showed up for the old schedule, you know exactly what I am talking about.

Why revisions fail

Revisions rarely fail because of bad information. They fail because of unclear distribution. Most 1st ADs know how to update a spreadsheet. Far fewer have a system for making sure the update actually replaces the old information in every crew member's head. The crew does not read the sheet three times. They read it once, screenshot it, and move on. Every revision you send after that first read is competing with a version that is already living in their phone.

The second failure point is version confusion. A sheet named CallSheet_Final.pdf followed by CallSheet_Final_v2.pdf followed by CallSheet_Final_REVISED.pdf is an invitation for someone to show up at the wrong call time. If your file naming cannot be read at a glance in a crowded notification tray, it is not doing its job.

The one-writer rule

Assign exactly one person who publishes revisions. On most sets that is the 2nd AD or the production coordinator. Everyone else can suggest changes, flag errors, and request updates, but only one person touches the master document and hits send. The moment two people are issuing versions, you have parallel truth, and parallel truth always ends with someone at the wrong address.

This person should also be the only one who decides what counts as a revision. A location note that changes parking does not need the same fanfare as a call time change. Establish three tiers in prep so your writer can move fast under pressure.

The three-tier revision system

Not every change deserves a blast to 60 people. Tier your revisions and communicate accordingly:

• Tier 1, cosmetic: typos, name spellings, contact corrections. Fix silently and note it in the next version. Nobody needs a text at midnight about a corrected surname.
• Tier 2, departmental: a prop changes, a department gets an extra hand. Message that department directly with the updated section. Do not redistribute the whole sheet.
• Tier 3, structural: call times, locations, company moves, scenes dropped or added, weather contingency triggered. This is a full redistribution with a clear revision marker and a read-back request.

Most revision chaos comes from treating Tier 1 and Tier 2 changes like Tier 3. You train the crew to ignore your messages by sending them too often. When the Tier 3 blast finally comes, it drowns in the noise of the six cosmetic updates that preceded it.

Naming and marking, non-negotiable

Every revised sheet carries the same three markers, every time. First, the version number in the header: v1, v2, v3, never Final or Revised without a number. Second, a one-line revision summary at the top of the sheet: Revised 10:42 PM: talent call moved to 7:00 AM, location B parking note added. Third, a timestamp on the filename itself so it sorts correctly in every file app: 1026_CallSheet_v3.pdf.

The revision summary is the most underused tool in production. Crew members will not diff two documents side by side. They will read the two-line summary and know whether they are affected. Write it for the person scanning it on a phone in bed.

Distribution that actually lands

Send the revised sheet to the same channels as the original, and say which version you are replacing. A short message works: Updated call sheet v3 attached, replaces v2. New call time for all: 6:30 AM. Everything else unchanged. Pin it in the crew group chat so late joiners find the current version first, not the old one buried under 40 messages.

For structural changes, get a read-back. A read receipt is not confirmation. Ask departments to reply with the new call time in their own words. It takes one minute and catches the people who skimmed. The ones who reply are the ones who actually registered the change.

Rule of thumb: if a change could make someone show up at the wrong place or time, it requires an explicit confirmation, not just a delivered message.

What to do about the night before

Set a revision cutoff time in prep, and tell the producer and director what it is. A common one: no structural changes after 10 PM except safety issues and weather. A cutoff does two things. It forces decisions to happen earlier in the evening when everyone is still at a desk, and it gives you a clean way to push back on the 11:30 PM request to add a scene without being the bad guy. The policy is the bad guy, which is the entire point of having one.

When a late change does clear the bar, keep the blast tight and human. Nobody resents a well-handled late revision. They resent finding out about it at the location.

The morning-of check

On set, confirm the version number out loud at the safety meeting. We are on v3, call time 6:30, company move at noon. Ten seconds, and anyone holding v2 finds out before the day is lost. Your 2nd AD should also keep one printed copy of the current version taped to the production table and replace it on every revision. Paper does not sync, so the physical copy is the source of truth for anyone who asks.

Where the system breaks down

Be honest with yourself about the weakest link in your process. It is almost always one of three things: the spreadsheet template is fragile and formulas break under edits, the distribution list is stale and two people never got the update, or confirmations are tracked in a group chat and nobody can find them. Fix the distribution list before every show. Rebuild the template when it starts breaking. And stop tracking confirmations in a chat thread.

The difference between a smooth revision and a chaotic one is rarely the change itself. It is whether the crew trusts that the sheet they are holding is the current one. Build that trust with clear versioning, disciplined distribution, and a cutoff time, and revisions become a non-event instead of a fire drill.

Modern call sheet tools remove most of this manual work. Easy Call Sheets versions every revision automatically, distributes the current sheet in one click, and tracks live digital confirmations from cast and crew, so the 11 PM reprint scramble becomes a thing of the past.