The daily production report: the production's daily record of truth

Planned versus actual

The call sheet states a plan; the daily production report states what happened. Crew call, first shot, meal breaks, wrap — each logged as an actual time beside the planned one. The gap between the two columns is the report's entire value: a day that ran to plan reads as quiet, and a day that didn't reads as a specific number of lost hours attached to specific reasons.

By the second week of a shoot, nobody remembers what happened on day three. Memory is a terrible filing system for a business where every hour has a price — the DPR is the filing system.

What the report carries

A complete DPR carries the day's progress and the day's exceptions. Progress: scenes completed, setups, pages shot against pages scheduled — the measure of whether the schedule is holding. Exceptions: delays with reasons, overtime, meal-penalty exposure, and every incident on set, including the minor ones.

The incident log matters more than its daily size suggests. Injuries, near misses and property damage recorded the same day, with times and actions taken, are what an insurance claim is built from months later — and the same discipline is what protects a production when a dispute arises about hours or breaks. A report that was never written cannot defend anyone.

• •Actual times against planned: crew call, first shot, meals, wrap.
• •Progress: scenes, setups, pages shot versus pages scheduled.
• •Exceptions: delays with reasons, overtime, penalty exposure.
• •Incidents: injuries, near misses, damage — logged the same day, every time.

Who reads it

Internally, the report feeds the chain upward: the line producer reads it for schedule and cost trajectory, and the accountant reads it for the labor the day generated. Post-production reads it for what was actually shot, because the editor's coverage expectations come from the scenes and takes the report says were completed.

Externally, the DPR is a deliverable. Studios expect it daily, completion bond companies read it to confirm the production is tracking against its schedule and budget, and insurers read the incident record when a claim arrives. A production that files clean, complete reports daily is treated as a production that is being managed; one that reconstructs its days at wrap is treated as a risk.

The report only exists if the day was recorded

The failure mode of DPRs is not bad writing — it's reconstruction. Times guessed after the fact, delays remembered approximately, incidents left off because the day was long: each one converts the report from a record into an estimate. The report's accuracy is decided on set, at the moment each event happens.

That's why day-of logging and end-of-day reporting belong to the same system: the events, delays, incidents and progress are captured while the day runs, and the report is composed from what was captured rather than compiled from memory.

How Clarice handles this

Clarice runs the day and the report as one record. The production day sheet tracks planned and actual times for the day's events, keeps the delay log with minutes and reasons, tracks per-performer and per-crew-member in and out times with turnaround and meal-window flags from the project's union rule pack, and holds the incident and progress logs as they happen.

The DPR composes from that day sheet in one step — no retyping — and the wrap times it records flow through to timecards and cost reporting, so schedule, payroll and the daily record agree on what the day was.