A useful decision log records what was tried, what changed and which file supports the conclusion. It does not need to narrate every minute of a session or make the final result seem inevitable. A small studio can preserve enough context to explain its choices without turning private coordination into public content.
This article proposes a lightweight record. The project, files and decisions are fictional and do not document a Fanatia shoot. Any real log should be adapted to the team's workflow and kept separate from sensitive participation records.
Record the decision while it is still recognizable
After a production, it is easy to remember the chosen image and forget the alternatives. A short note made around the decision can preserve the difference between an original intention and something discovered during work.
For a fictional portrait with a dark jacket and a chair, the starting idea is to compare the garment's shape in a seated and a standing frame. During the exercise, the hand becomes more important than expected. The log should show that change rather than later claiming the whole series was always about the hand.
Use stable file identifiers so the note can be checked. «The better photo» is not enough when several versions look similar or a crop changes later.
Three decisions in a completed example
| Decision | Evidence described in the fictional record | Chosen action | Remaining uncertainty |
|---|---|---|---|
| Give the hand more room | Frame A cuts the fingertips; B keeps the gesture visible | Continue from B's framing | Confirm the final crop preserves it |
| Reduce the number of standing views | C and D repeat the same relation to the chair | Keep C in the working selection | Revisit if the sequence's theme changes |
| End with the jacket on the chair | E returns to the garment without the participant | Test E as the closing frame | The order is an editorial proposal, not capture chronology |
The log contains a reason for each action and a question that remains open. It does not use uncertainty as a defect to hide. Those open points become tasks for selection and review.
Distinguish observation from explanation
«The fingertips are outside the frame» is an observation you can verify in the file. «The participant wanted to disappear from the picture» would be an interpretation of another person's experience and is not supported by that observation.
Similarly, «we preferred C over D for this sequence» does not mean D is technically or artistically worthless. It means one version was selected for a stated purpose. Keep the language close to the actual decision rather than ranking every unused frame.
If the team disagrees, record the options without inventing consensus. A later editor can see that the ending was debated and understand what each alternative would change.
Let the log survive a new edit
Suppose the closing image E is removed during final selection. Do not delete the old note and pretend that the idea never existed. Add the new decision: «E was tested as an ending but removed because the final sequence stays with the participant». Identify the version of the sequence concerned.
This is not an invitation to publish every draft. It is a way to keep the production record coherent when a project changes. The public note can remain concise while the internal history stays accurate.
A log that distinguishes versions also helps prevent a caption written for an old order from following the new selection unnoticed.
Derive a public note without exposing the file room
From the fictional log, a restrained note might say: «The final selection concentrates on the hand's relation to the jacket. We reduced repeated standing views and kept enough room around the gesture for it to remain legible. The published order follows that visual relation rather than the order of capture».
A real studio should only publish such a note when it matches its records and approved material. There is no need to attach private conversations, identity information or every unused photograph to support the explanation.
Keep the record small enough to use
A practical entry needs a date or stage, file references, the decision, its reason and an unresolved question when one exists. More fields are useful only when someone actually uses them. A form too cumbersome to complete will not preserve the choices it was designed to record.
The log succeeds when another authorized team member can understand why a frame was chosen and what still requires checking. It turns the process into traceable decisions without polishing away uncertainty or inventing an artist's story after the photographs are already finished.