The anatomy of a call sheet

What goes on a call sheet, why each line is there, and the one failure that ruins an otherwise perfect one: nobody having it.

Adam Murray6 August 20269 min read
On this page

It's 6:40am. The gaffer is at the wrong entrance, the client's product hasn't arrived, and someone is calling you because you're the only person whose number they have.

Every one of those is a call sheet problem. Not a talent problem, not a planning problem: a document problem, and the document is one page long.

What a call sheet actually is

It's the operational summary of a single shoot day. Not the creative plan, not the schedule for the whole project: one day, everything a person needs to show up correctly and know what happens next.

Its real function is removing you as the single point of failure. A shoot day has too many moving parts to hold in a group chat, and when something goes wrong early, the call sheet is what people look at instead of phoning you. If everyone on set has to ask you where the toilets are, you're not directing, you're doing reception.

The header

Production name, client, date, day n of n, general call time, estimated wrap.

Two of these are load-bearing.

Day n of n matters because on multi-day shoots people genuinely lose track, and the sheet for day two circulating on day three causes real chaos.

Estimated wrap matters because it's a commitment. It's what crew plan their evening around, what determines whether you're heading into overtime, and, if you routinely wrap three hours late, it's the number that quietly tells good crew not to work with you again. Put a realistic one on the sheet, not an optimistic one.

Location

Address, and this is worth being pedantic about: as text, not as a map screenshot or an embedded pin.

Somebody is going to paste it into their phone at 5am. A picture of a map is useless for that. A pin dropped in one messaging app doesn't survive being forwarded to another. Plain text, copyable, with the suburb and the postcode.

Then the things that aren't obvious from an address:

  • Parking. Where, whether it's paid, and whether a truck fits.
  • Which entrance. The loading dock is rarely the front door.
  • Access. Codes, buzzer numbers, who has the key, and what happens if that person is late.
  • Where to put gear. Whether there's a room, or whether everything lives in the corridor.

If you're shooting at more than one location, each gets its own block, and the schedule says when the move happens.

Who, and when

A table: name, role, call time, phone number.

Three rules that sound obvious and are routinely broken.

Individual call times, not one general time. Nobody benefits from the editor standing around for four hours because everyone got the same 7am. Stagger by when people are actually needed. It's the single biggest cost saving available on most small shoots.

Live phone numbers. Not internal Slack handles. Not "contact via the producer". At 6:40am the producer is driving.

Include the client. Whoever is attending from the brand goes on the sheet, with a call time, like everyone else. If they're arriving at 11 to see the hero shot, say so. Otherwise they'll arrive at 8 and watch you rig for three hours, which helps nobody.

The schedule

Time, what's happening, who's needed, where.

Keep it in shooting order, which is not edit order and not story order. The controlling constraint is how often you move the camera and relight, so group by setup, not by narrative. A shot list built in edit order gets reordered here. See shot lists that work for why you build it one way and shoot it another.

Two things belong in this table that people leave out:

  • Setup and rig time. It's real, it's often the largest single block, and leaving it off makes the day look achievable when it isn't.
  • Lunch. With a time. A crew that doesn't know when they're eating gets slower in a way nobody names.

Build in slack. A schedule with no gaps is a schedule that fails at 9:15 and never recovers.

The details that aren't obvious

A short block at the bottom for everything that has no other home:

  • Nearest hospital, with the address. You will almost certainly not need it. It costs one line.
  • Weather, and the contingency. "If it rains we move the exterior to Thursday" is a decision better made now than at 6am in the rain.
  • Lunch arrangements: provided, or people fend for themselves. Say which.
  • Dress code or safety requirements, if the location has them.
  • Who to call for what. One name for creative questions, one for logistics.

The failure that ruins good call sheets

Here it is, and it's almost always this one:

So:

Send it the night before. Not the morning of. People plan their travel the night before, and some of them will be on a train with no signal at 6am.

Send it in something that opens on a phone. A PDF is fine. A link that requires a login is not. A document in a shared drive that isn't shared with the freelancers is the classic version of this failure.

Send it to everyone, including the client and any third party at the location.

Send an update if something changes, with the change called out at the top. A silently-revised document is worse than no revision, because half the crew is working from the old one and doesn't know it.

What doesn't belong

Call sheets bloat, and a bloated one gets skimmed instead of read.

Leave out the creative rationale, the full brief, the mood board, the strategy, and the shot list. The creative brief covers the first four; the shot list is its own document, attached separately, because the people who need it are a subset of the people who need the call sheet.

One page if you can. Two if the day is genuinely complex. If it's running to four, something that isn't a call sheet has crept in.

For smaller shoots

If it's you, a camera, and one person on the other side of it, you don't need a formal call sheet. You do still need three things in writing to whoever else is involved: where, when, and how long. Most one-person-crew problems are one of those three going unstated.

The threshold where a real call sheet starts paying for itself is roughly the third person, or the first person you haven't worked with before.

Where Acumin fits

Call sheets, shot lists and branded hand-off packs generate from the brief in production docs, so the brief becomes the shoot without anyone retyping the address. Rosters carry over between shoots, which removes the most common source of wrong phone numbers: copying them from the last job by hand.

None of that is the point of this article. The document above works in any tool, including a text file, as long as everyone has it by the night before.

How to use this tomorrow

Take your next shoot and write the call sheet now, before anything else is settled. You'll immediately find three things you haven't decided: usually the access arrangement, the client's arrival time, and what happens if it rains.

Deciding those now is the whole value. The document is just where the decisions live.


Related: Shot lists that work is the document that goes alongside this one. How to hire a videographer covers what to agree before you get anywhere near a shoot day.

Free document pack

Call sheet + shot list pack

One document, three parts: a call sheet and a shot list that survive contact with a shoot day, and the hand-off checklist that goes to the client the night before.

The method is all in this article and always will be; the download just saves you building it.

Send me the call sheet + shot list pack

Written by
Adam Murray
Founder, Acumin

Adam builds Acumin. He spends his days on the same two problems this library is about: working out what a piece of content is actually worth, and getting a brief through production without it turning into something else.

Want this done on your own channel?

Acumin reads your public content and your category and hands back what to make next. Every call comes with its confidence and the evidence it rests on. The first Snapshot is free.