How to Write a Shooting Report

A strong shooting report is not just a formality. It is the operational memory of your set day. If your report is incomplete or inconsistent, production loses time, editors lose context, and post teams inherit confusion.

Start with a clear hierarchy: project → day → scene → shot → take. Each take should include camera/file reference, duration, mode flags (DAY/NIGHT, INT/EXT, SYNC/MOS), and notes. The point is not to write more, but to write in a consistent structure.

Keep statuses standardized across the whole team. If one person writes “good,” another writes “print,” and a third writes “ok,” downstream filtering becomes messy. Use one naming system and keep it stable through all days of the project.

Capture information in real time instead of reconstructing it after wrap. Delayed rewrite is where most mistakes happen: wrong file number, missing note, lost status, or mixed continuity comments.

At the end of the day, export in a format production can use immediately. CSV and XLSX remain practical because coordinators and post teams can review and merge them quickly.