“Sent” isn’t “seen”: three call-sheet delivery states
Disclosure: I’m Joey, a Dallas DP, and I built CallSheet: Crew Calls.
When a call sheet changes, I think there are three different questions:
Was it delivered?
Was the current sheet viewed?
Did the recipient explicitly confirm it?
Those are useful operational states, but they are not proof that someone understood the change or will arrive on time. A critical call-time or location change still deserves a direct phone or text follow-up.
I would keep a plain PDF/email workflow when the crew is small, changes are rare, and one person can close the loop manually.
Recipient-specific tracking starts to earn its keep when the sheet changes late, different people are affected, or the coordinator needs one place to see who opened the current information and whether they confirmed it.
That is the distinction I built into CallSheet: each recipient gets a private link to the current call sheet without needing the app or an account, and the sender can track delivery, views, and confirmations. It is a workflow aid, not a substitute for production judgment.
Because I built it, weigh that recommendation accordingly. What does your team count as “confirmed” now: email sent, a read receipt, or an explicit acknowledgment?
