Make a shot-list notebook that separates ideas from required coverage

Make the check

1. Write the deliverable first. List what the finished piece must communicate. Turn those requirements into a short must-have section before adding visual experiments.
2. Give shots identifiers. Use a simple code beside subject, framing note and status. Keep the same code in production notes or filenames when useful.
3. Keep technical questions visible. Write unresolved equipment or location questions separately. Do not let an attractive idea conceal an unanswered practical constraint.
4. Close the loop after recording. Mark what was captured, what changed and what still needs follow-up. Keep the notes with the source files so they remain useful during editing.

A worked example

A page can contain M01–M05 for required coverage and E01–E03 for experiments. If time runs short, that distinction makes the trade-off visible. These are example identifiers, not a professional production standard or a claim that the workflow improves completion rates.

What to watch out for

• Do not record private client information in a casually shared notebook photo.
• A shot list does not replace location permission, releases or safety planning.
• Avoid choosing equipment before you know the required shot.

Separate required coverage from experiments

Put the client-approved or project-required shots in one list and optional ideas in another. For each required shot, record location, subject and any dependency such as a prop or a specific lens. A packing note should refer back to that list rather than listing every item you own. Leave space for what was actually captured. The notebook organizes coverage; it does not establish permission to photograph, location access or the safety of a setup.

Sources and evidence

• Hardcover Notebook – Leuchtturm1917.us (read November 7, 2026)

Common checks

Published November 7, 2026. Sources last read November 7, 2026. Send a correction.