The call sheet is not a table

Description and use

Backlot implements the call sheet as a filtered view of assignments instead of a separate table, simplifying code and keeping data current.

Problem

Film sets need a call sheet that lists who is where and when, but the traditional call sheet is often out‑of‑date and duplicated.

Outcome

By treating the call sheet as a filtered view of assignments rather than a separate table, Backlot reduces code complexity, ensures real‑time accuracy, and enforces fine‑grained access control.

Workflow

• Create Assignment at "offered" state with owner_username set to person_email
• Crew portal fetches all assignments via client.getObjects('assignment') and sorts by call time
• Server policy filters assignments where owner_username equals the logged‑in user
• Crew member confirms or declines via UI, updating the state
• Office can confirm via workflow that emails and SMS are sent, with error handling and compensation

Evidence

Backlot is an open-source film production scheduling app that has five tables and none of them is the call sheet.

Source

The row is created by the line producer. It belongs to the cinematographer.

Source

The call sheet is not a table. It is a row filter with a name.

Source

The office creates the assignment at offered. An event binding on @create:backlot:assignment runs a workflow that emails the person.

Source