Built from the booking
Crew calls are created against the people confirmed on the show, so nobody is on the sheet who was never booked and nobody booked is missing from it.
Build the call from the show record rather than a document, send it to the people actually booked, and change it once when the schedule moves.
Call sheets are usually built in a document, exported, and sent as an attachment. That works exactly until something moves, which on a live job is most of the time.
Then there are two versions in circulation, the person who most needs the change is the one who did not see it, and somebody spends the morning of the show confirming by phone what the sheet already said.
The fix is not a better template. It is building the call from the show record, so the sheet is a view of current information rather than a snapshot of what was true on Tuesday.
Real screens from the current Flightcase build.


Most call sheet pain is version pain. These are the parts that remove it.
Crew calls are created against the people confirmed on the show, so nobody is on the sheet who was never booked and nobody booked is missing from it.
Roles and call times sit on the individual. A rigger at seven and an operator at eleven get their own time rather than the earliest one on the sheet.
Crew confirm or decline through a link. Silence is visible as silence, which is the state worth chasing and the one a PDF cannot show you.
Move a schedule item on the show and the call reflects it. There is no second document to reissue and no question about which version is live.
The sheet is a view of the show, so each step tightens the same record.
Confirm crew onto the show with their roles. Availability and booking stay separate states.
Add the call: times, roles, venue detail, access notes and the files crew need.
Crew get a link rather than an attachment, and respond against the call itself.
Schedule moves are made once on the show. Everyone is reading the same current call.
Go deeper on the workflows behind the platform.
We will rebuild it from a show record and show what the second and third versions would have cost you.
Essential storage is required for security, forms, sessions, and core product behavior. Optional analytics and advertising storage follow your choice below. They are on by default outside the EEA, UK and Switzerland, and off until you allow them within those regions.