Call sheet software

Every tool in this category does two things: it helps you author a shoot-day document, and it gets that document to the people who need it. Authoring is the visible half and the easy one. A spreadsheet authors a perfectly good call sheet.

Distribution is where the category earns its keep, and it is the half that a template cannot do at all. Getting each person their own current copy, knowing who has read it, and revising without starting the whole conversation again are the problems software is actually for.

First, where can you build? Most of this category is browser-based, which assumes a laptop and a connection. If you build call sheets on location, that assumption breaks at exactly the wrong time.

Second, what do recipients have to do? Any tool that requires crew to install an app or hold an account has added a step to thirty people's day to save one person some effort. Crew turnover makes this worse every job.

Third, can you see who confirmed? Delivery is not receipt and receipt is not acknowledgement. The useful signal is who actually opened it and said yes.

Fourth, what happens on a revision? This is the question that separates the category, and it is the one least often asked before buying.

Almost every evaluation is done on the first send, which every tool handles. The day changes afterwards, and that is where the differences become expensive.

The default behaviour in most workflows is to resend everything to everyone. That asks the whole crew to re-read the document to discover that nothing changed for them, it competes with the version they already saved, and it quietly destroys the confirmations you had already collected. Do that twice in an evening and nobody believes the next one either.

The alternative is to work out who the change actually affects and tell those people, while everyone else keeps the version they already confirmed. It is a small difference in software and a large one at 10pm.

The larger platforms bundle script breakdown, scheduling, shot lists, budgets, and call sheets, on the argument that connected stages beat separate tools. That is a real advantage for a production office where several people work inside the software all week.

It is a poor trade when the stages do not exist. On commercial, branded, documentary, and photo work there is often no screenplay to break down and no schedule upstream of the call sheet: there is a client conversation, a location, and a crew booked over text. A connected pipeline with nothing to connect is a large empty structure you pay for and maintain.

The honest test is how many people will be working inside the tool, and how many of its stages you will actually run.

CallSheet is built for the person who personally owns the call sheet. It runs on iPhone and iPad, and the whole build works with no account and no network: the editor, the reusable Crew Directory, Sun Path, and PDF export. An account is needed only when you send.

Recipients get a private link and the current PDF, open it in any browser on any device, and confirm on the link itself. When something changes, the revision starts with the affected recipients already selected, and you review that list before anything goes out.

The boundaries are as important as the features. There is no script breakdown, no shot list, no storyboard, and no production accounting. If you need those, you need a suite, and this is the wrong tool.