A shooting schedule template gives you the columns. It will not make the calls.

A shooting schedule is not a decorative calendar: it is the production's commitment to a number of days. Everything expensive follows from it — cast is paid in days worked, equipment is rented by the week, crew is booked by the day. It is also read by very different people: the producer looks for a volume, the 1st AD for an order of work, the location department for addresses, the line producer for a cost. That is why its structure varies so little from one production to the next, from a weekend short to a feature: the columns are not a presentation choice, they are the questions each of those jobs comes to the document to ask. This is the one thing a template is genuinely good for — making sure you do not omit a column whose absence you would only discover at budgeting time.

Fill in a template and you notice quickly that most columns are not written, they are copied. Scene number, location, interior or exterior, day or night, characters present, background count and technical requirements are already in the screenplay breakdown. Page count comes from the script. What is a genuine decision fits in three columns: which shoot day a scene lands on, its rank within that day, and the times that follow. The table below sets out the full structure and marks, for each column, whether it is decided or copied — that distinction, more than the list itself, explains both why the data entry is slow and why it is automatable.

A shooting schedule template circulates in three shapes, and they are not rivals — they serve three moments. The stripboard, one strip per scene moved around a board, is the historical form and still the best one for the trade-off phase: you try a grouping, undo it, try another, without retyping anything. The spreadsheet is the working form: it totals, sorts, filters and travels by email. The calendar is the distribution form, and it is what cast and vendors actually read, since none of them need the eighty-line grid. The common mistake is keeping only one of the three and rebuilding the others on demand — usually under time pressure, and usually without remembering which version was the live one.

This is the one place where a template is empty by construction. Assigning scenes to days means holding together constraints that pull in opposite directions: group every scene at one location so you never build it twice, but without stretching an actor's availability across three weeks; shoot night exteriors consecutively so the unit is not flipping its body clock, but leave weather cover; stay inside a workable day, commonly eight to ten hours of actual shooting. Every trade-off displaces another, and that is what makes the exercise slow by hand — the cost is not the typing, it is redoing the reasoning on every attempt. A template gives you the grid to record the answer in, never the method to reach it; our guide covers the method and the grouping rules in full.

A complete schedule reads in two directions. The first, scene by scene, is the main grid. The second, cast member by cast member, crosses roles against shoot days: who works, who is on hold, who is finished, who travels. That second grid — the day out of days — is what contracts are written from, what day counts are drawn from, and what reveals that a supporting actor is being carried for three weeks to shoot five days. Most free templates omit it, and that omission is the expensive one: it is invisible when you read the schedule and perfectly visible on the cost report. If you are building your own template, put it in from the start. Roles down the side, shoot days across the top, a status in each cell, is enough to expose the recalls you are paying for by accident.

A spreadsheet never objects. It will accept a fourteen-hour day, a next-day call that leaves no real turnaround after a late wrap, two locations sixty miles apart on the same morning, or an actor scheduled on a date they flagged as unavailable. These are the costly errors precisely because they do not surface at the desk — they surface on the day, when it is too late to reorganise. Turnaround deserves a separate note, because it is structurally invisible in a template: it is measured between one day's estimated wrap and the next day's call, so between two rows that never look at each other. Minimum rest and maximum working hours are set by local labour law and by whichever union agreement covers the production, and both vary by territory. The point here is methodological rather than legal: a static document cannot perform that check, so it has to be done separately — and redone after every change.

Filling in a shooting schedule the first time is slow, but it is a cost you pay once and accept willingly. The real cost arrives afterwards, and it never stops. A location drops out, an actor's availability shifts, weather forces two days to swap, the director adds a scene: the day breakdown has to be redone, and the result pushed everywhere it had been copied — the distribution calendar, the day out of days, the day count in the budget, the call sheets already drafted. On a spreadsheet none of that propagates. Each re-entry is a chance to miss a line, and nobody notices until the day in question. That is the genuine difference between a template and a production chain: not the quality of the first document, but the price of the second.

Three ways of holding a shooting schedule coexist, and they are not told apart by their output — all three produce a readable document — but by what happens on the first change. A spreadsheet template costs nothing and you control it completely, but every field in it was retyped from the breakdown and will have to be retyped again. Dedicated scheduling software removes part of that re-entry, depending on whether it can import an existing breakdown at all. Generating from the breakdown removes the question: the schedule stops being a document you maintain and becomes a computed view of the scenes, which recalculates when they change. Disclosure: Soldum publishes one of the solutions described here, and this page is published by its maker.

There is no universal threshold, but there is a reliable symptom: the moment you type the same fact for the third time. Once in the breakdown, once in the schedule, once on the call sheet — and a fourth time in the budget, when the day count has to be carried across. As long as your shoot runs three days and nothing moves, the template wins: it is free, immediate, and there is nothing to learn. The switch happens when the schedule becomes a living document. In Soldum the shooting schedule is not a file you maintain: it is derived from the AI breakdown of your script, with location grouping, cast availability and travel time, and it recalculates on every change. Call sheets are its daily view, and the day count feeds the budget directly — script to schedule to budget, in one tool rather than three.

Worth saying at the end, because it is what gets lost in the move to software: a shooting schedule template encodes real craft knowledge. The order of the columns is not arbitrary, nor is the line between what comes from the breakdown and what is a scheduling call, and the presence of a day out of days comes from productions where its absence cost real money in cast holds. Good software does not replace that structure — it adopts it and stops asking you to retype it. Which is also why an incomplete document does not become complete by being generated: if the breakdown does not know a scene's location, or which characters are in it, the schedule will come out hollow whatever produced it. The question to ask a template and a piece of software is the same one: where do the columns come from.