1st AD software: the breakdown, the schedule and the call sheet in one chain

The breakdown, the schedule and the call sheet describe the same film at three scales: what it needs, when it is shot, and who is called tomorrow. Treating them as three independent documents is not a method failure, it is a consequence of the tools — a spreadsheet has no way of knowing that one of its breakdown rows belongs to a scene the stripboard just moved to day 14. Once the underlying data is shared, the question stops being how to keep three files in agreement and becomes which of them recalculates.

Breaking down a feature by hand is several days of annotated reading, and those are rarely the last days you spend on it: the next draft arrives, and nobody redoes the annotations line by line. What happens instead is that you re-enter what you noticed and let the rest drift — which is how a prop cut from the script stays in the budget and a location added in act three is noticed by nobody. In Soldum, importing the script produces the breakdown scene by scene for you to correct and complete, and a new draft is compared against the previous one so that what moved is shown to you rather than hunted for.

A shooting schedule is not a list of scenes dropped into boxes. It is a solution to a set of constraints that contradict each other. Group by location to avoid company moves, but respect the window that location is available. Group an actor's scenes to cut their work days, but work around the days they are not free. Put exteriors early to keep a weather contingency, but do not run two nights straight into a day call. Those trade-offs stay yours — no tool knows the film. What software can do is hold the constraints current and tell you which ones a given arrangement breaks, instead of letting them surface on the floor.

The next day's call sheet is the last document in the chain, and it is the one most often rebuilt from a duplicated template. Yet every field on it already exists somewhere: the day's scenes, the locations, the cast called, the times. Retyping it means accepting that it can contradict the schedule — and nobody sees that contradiction until a department turns up at the wrong hour. In Soldum the call sheet is generated from the scheduled day and distributed as a personal link: no account for the crew to create, one tap to confirm attendance, a chase aimed only at those who have not answered, and group sending by email and WhatsApp. When the day changes, the version behind the link changes.

It takes five minutes and no commitment, so run it during a trial instead of comparing feature lists. Move one shooting day forward by two days, then count what you have to reopen. In a split chain: the stripboard, the work days of the cast involved, the location and equipment holds, the call sheets already sent, and the matching budget lines. In an integrated chain those all read the same date field, so they recalculate, and the clashes the move creates surface before you commit to it. What is left is a judgement call — accept what it displaces or not — rather than an afternoon of copying.

Prep happens in front of a screen. The shooting day does not. Between the first call and wrap, the first AD holds the rhythm, calls the roll, tracks what is left to shoot and warns production when the gap stops being recoverable. Software has no business in that loop except to disappear from it. The only useful thing is that what was agreed in the morning is readable by everyone, and that whatever was not shot today lands in the right place in tomorrow's schedule. The rest — the eye on the floor, the decision to drop a setup to save the end of the day — is the job, and stays the job.

Three families of tool share the work of assistant directors, and feature count is not what separates them. Spreadsheets and a call sheet template cost nothing, start immediately, and remain a sensible choice on a three-day shoot; their limit is that no column knows a scene changed day. Dedicated scheduling tools order strips well and output call sheets, but they start from a breakdown you enter yourself, and they stop before the budget. An integrated chain connects the script, the days and the money in one database, which is where the retyping actually disappears. Disclosure: Soldum publishes one of the solutions described here.

Worth a paragraph if your production touches France, and skippable otherwise. Working hours and turnaround there are set by the industry-wide collective agreement rather than by a generic setting; crew are hired on the fixed-term contracts specific to French freelance film workers, which makes work days a contractual figure and not just a count; and the schedule you build turns, on the production manager's desk, into budget lines in the category structure used by the CNC, the national film agency. Soldum treats those frameworks as the starting point rather than as an export to rebuild — so an added day produces a figure production can read. On a shoot that never goes near France, those parts simply go unused.

Worth saying before you open an account, because it is the promise scheduling tools keep least well. It does not build the schedule for you: it proposes a grouping, and you correct it knowing what each change displaces. It knows nothing about the rhythm of the film, what the director wants in the can first, or how tired a unit is in week three. It does not choose between a weather contingency and an actor's day — it shows the clash and waits for your call. AI suggestions go through an approval queue that shows their impact before anything is applied. What it removes is the retyping, and the drift between documents that retyping always creates.