Camera report template
The camera report is the map post-production navigates by — written on set, in the only moment the knowledge exists.
What this is about
Metadata records what the camera did; the report records what the humans meant. ISO and lens live in the file, but which take the director liked, why take four broke off, which clip is a false start — that knowledge evaporates by wrap unless someone writes it down against card and clip IDs. An editor with circled takes opens the good material first; one without watches everything at least once. Multiply that difference across a multi-day shoot and the little sheet outperforms most gear upgrades.
A template is the starting point, not the goal: once it has been filled in by hand twice, it is worth asking whether the document should come out of the plan instead.
What runs differently here
Where this differs from the general case:
- Card and roll identifiers that stay unique across the whole production, because A003 meaning two different cards ruins the archive
- Per clip: scene, take, lens, filter and frame rate, so post can reconstruct any setup without calling the DP
- A circled-take column marking the takes worth opening first — the single highest-value field on the sheet
- A notes column for the human layer: false starts, focus buzzes, the plane in the background, print this one
Step by step
This order gets you there fastest:
- Set the ID scheme before day one — camera letter, roll number, date — and never reuse a combination.
- Open a fresh report per card at the moment the card enters the camera, not retroactively at lunch.
- Log every clip with scene, take and lens while the slate is still in view; ten seconds now beats ten minutes later.
- Circle takes immediately when the director reacts, and write down the reaction in three words.
- Hand the report to the DIT together with the card, so footage and knowledge travel as one package.
- At wrap, check reports against the media log for orphan cards — a card without a report is a riddle, a report without a card is an alarm.
Common pitfalls
What most often goes wrong in practice:
- Reconstructing the day's reports at wrap from collective memory, which is fiction with a form
- Card IDs recycled mid-production, so two clips answer to the same name
- No circled takes, leaving the editor to relive every minute of the shoot in real time
With TillyGen
Shot IDs from TillyGen's plan give the report its reference system: what was logged on set maps back to the planned shot, so coverage gaps show up while reshooting is still cheap.
Change one constraint and the consequences travel through the whole plan: affected shots are flagged, the call sheet is regenerated, and nobody keeps working from yesterday's version.
Frequently asked
Cameras record metadata — is a written report still worth it?
Yes, because intent is not metadata. The file knows the ISO; it does not know the director said use this one. Circled takes and human notes are the part no sensor captures.
Who fills in the camera report?
Classically the camera assistant, on small crews whoever stands closest to the slate — decided before the day starts. A report with a rotating, unnamed author is how gaps begin.
How long does it take to get started with TillyGen?
A first project takes under an hour to set up. There is no configuration phase in which templates and fields have to be defined before the tool produces anything.
Can the results be exported?
Yes — as PDF for the crew, CSV for downstream systems and through the API for anything automated. The plan stays the source; the exports are views of it.