A call sheet template will carry you through day one. Not day two.

A call sheet does not inform, it summons. It is the document of record for each person's call time, for the rendezvous point and for the order of the day's scenes. Its job is to make a day executable without anyone having to phone the production office to check a detail — and that is the only standard by which a template should be judged. A missing section does not produce a less attractive document, it produces one phone call at six in the morning and then ten more. This is why call sheet structure is remarkably stable across productions, from a two-day short to a feature: it is not a presentation choice, it is the list of questions a crew asks before leaving home.

The first thing you notice filling in a template is how little of it is actually writing. Nearly everything is copied from documents that already exist. Unit call and estimated wrap come from the shooting schedule; the location, interior or exterior, day or night, and the background count come from the screenplay breakdown; cast calls come from crossing the two. Only production notes are genuine authorship. The table below sets out the full structure and marks, for each section, whether it is typed or copied — that column, more than the list itself, explains why writing call sheets by hand is such tiring work.

The header looks decorative and never is. It carries the project title, the day number against the total — "day 7 of 23" situates a delay better than a date does — the date, the production company and, above all, the numbers that are answered on the day. Three are enough and all three must be there: production office, 1st AD and the location or unit manager. The classic failure is reusing the header of a downloaded template without replacing the contacts with the ones on duty: on a production where the location team rotates, the number printed last week reaches someone who is no longer on the unit. A call sheet is read on a phone, standing up, in the dark. The contacts belong at the top, not in an appendix.

This is the section a call sheet commits to most, and the one templates get wrong most often, because they usually offer a single "call time" field. A shooting day has several. There is the unit call for crew, cast calls staggered by makeup and wardrobe, a separate background call, first shot, the meal break and estimated wrap. Collapsing unit call into first shot brings cast in an hour early or crew an hour late, and nobody notices until the morning. A template with one time column forces you to invent a reading convention that only you know; pick one that separates calls by group explicitly, and state on the sheet which time is the crew call.

The scene list is not script order: it is shooting order, decided by the schedule to group locations, effects and cast availability. Each line carries the scene number, interior or exterior, day or night, the set, a one-line synopsis, the characters present, the background count and — depending on the production — the page count in eighths. That last figure deserves attention: it is the only number that lets you say at wrap whether the day did what it promised. A template that omits it produces perfectly legible sheets and makes progress tracking impossible. You know which scenes remain; you never know how many days they represent.

Three lists, three different logics. Cast are called individually, with a per-day status — working, hold, travel, rest — and that grid by role and by day is what contracts and payroll are built from. Background artists are called as a group, with their own time and wardrobe instructions. Crew are called by department, and the head count only varies occasionally: an extra grip for a dolly day, a second sparks for a night. The common failing of generic templates is melting all three into one list of names. You then lose the most useful piece of information on the page — the reason each person is there that day — and the 1st AD reconstructs it from memory.

These are the fields no template fills for you, and that nobody chases until the morning they are absent. The exact rendezvous address, which is not always the set address. Parking: where unit vehicles go, where everyone else goes, and under what permit. The unit base, dressing rooms and catering. Meal time, place and head count. Sunrise and sunset, which govern an exterior day far more reliably than the forecast does. The safety notes specific to the location, and the address of the nearest hospital. Finally the advance schedule — one line on what shoots tomorrow — which stops the crew from organising their lives around a rumour.

A template will accept any call time you type, including one that leaves too little rest after a late wrap. Yet turnaround — the gap between wrap and the next day's call — is the single most structuring constraint on a schedule, and the one that triggers penalty payments and fatigue arguments in equal measure. The point here is methodological rather than legal: the rule is verified between the estimated wrap of one day and the call of the next, which means between two call sheets, never inside one. A standalone document cannot check it by construction. If you work from a template, run that check separately on the schedule before you distribute anything, and remember that minimum rest periods are set by local labour law and by whichever union or collective agreement applies to your production.

On a shoot, a call sheet is almost never written once. A location moves, weather flips two days, an actor's availability shifts: tomorrow's sheet changes, and sometimes next week's too. The risk is not presenting the document badly, it is a grip arriving at the time printed on the previous version. That is where a template reaches its limit, and it is not a question of how good the template is: a file attached to an email has no way to update itself, and a crew of forty has no way to tell which of three attachments is current. The only remedy, template in hand, is procedural — number the versions, stamp the time of issue, and reissue the whole document rather than sending a correction.

Three ways of producing call sheets coexist, and they do not differ in output — all three print something legible. They differ in what happens after a change. A Word template is free and flexible, but every schedule change is retyped by hand. A spreadsheet adds arithmetic and dropdowns, at the cost of a layout that breaks the first time you export to PDF. Generating from the shooting schedule removes the retyping entirely, because the scheduled day and the call sheet are the same object seen from two sides. Disclosure: Soldum publishes one of the solutions described here, and this page.

There is no universal threshold, but there is a symptom. As long as you are writing one call sheet a day on a three-day shoot, the template wins: it costs nothing and you control it. The switch happens when you catch yourself copying the same fact for the third time — once into the breakdown, once into the schedule, once onto the sheet — or when you spend longer confirming that the crew is reading the right version than preparing the day itself. In Soldum the call sheet is not a separate module: it is the output of a day in the shooting schedule, which is itself derived from the AI breakdown of the screenplay. You do not make call sheets, you approve the schedule and they exist; every change produces a new time-stamped version, and the link already sent to the crew always shows the latest one.

Worth ending here, because it is what gets lost in the move to a tool: a call sheet template encodes real craft knowledge. The order of the sections is not arbitrary, nor is the separation of calls by group, and putting the contacts at the top of page one comes from dozens of shoots where they were somewhere else. Good software does not replace that structure, it adopts it and stops asking you to retype it. It is also why an incomplete document does not become complete by being generated: if the breakdown does not know a scene's location, or casting does not say which actor plays which sequence, the sheet comes out hollow whatever produces it. The question to ask a template and a tool is the same one: where do the fields come from.