RCRAIN CITY
PRODUCTION NOTES

Clear thinking for small productions.

About the publication ↗
Post-production

Log Demonstration Footage by What the Viewer Can See

Describe usable actions and visible differences between takes so an editor can find the right moment without replaying every clip.

Several files can contain the same demonstration while offering very different material to an editor. In one take the hand covers the control. Another shows it clearly but ends before the action settles. A useful log describes those differences. “Good take” alone does not explain what is good or whether the clip serves the particular sequence being cut.

Agree on the logging format with the editor before making a large document. They may already have a bin structure or a way to attach notes. A small table is enough for a short production if it points unambiguously to the delivered media. Keep camera filenames intact unless the agreed workflow specifically calls for a coordinated rename.

Give each note a reliable address

Record the file or clip identifier and the time reference the editor will see. State whether a time is measured from the beginning of the clip or comes from another reference. Mixing these systems makes otherwise accurate notes difficult to use. Test one entry together: can the editor reach the exact moment without asking what you meant?

Describe the action in ordinary language. “Blue lever reaches the lower stop; label stays visible” identifies a useful event. Avoid a long account of what the crew hoped to achieve. The log should help someone choose from recorded material, so distinguish an intended shot from an action that is actually present and readable.

Note type A useful example
Action The lid opens fully and stays in view.
Difference This take keeps the front label facing the camera.
Limitation A hand obscures the control during the final movement.
Sound A chair scrape overlaps the spoken product name.

Keep preference separate from evidence

You can flag a preferred take, but explain the reason and retain the alternatives. The person making the selection may value continuity over the liveliest performance. A concrete note lets the editor reconsider your preference when the surrounding sequence changes. “Clean view of the fastening” is still useful after a different opening shot has been chosen.

Mark technical questions for the appropriate person rather than diagnosing unfamiliar problems. If a detail looks soft in a small preview, record the observation and request a proper check of the original. Do not discard material because a compressed review copy makes it difficult to judge. Keep evaluation notes connected to the version you watched.

For a long demonstration, divide the action into meaningful stages. Name the setup, the operation and the visible result, using the same terms as the approved brief. Several references within one clip may be more useful than a single overall rating. Include a quiet beginning or ending when it gives the editor a clean place to enter or leave the action.

Hand over a map, not another obstacle

Remove repeated descriptions and unexplained abbreviations before sharing the log. Sort it in a way that follows the media organization or the planned sequence, and say which you used. If several people logged footage, reconcile their terms for the same object. A control described as a latch in one place and a tab elsewhere can create needless confusion.

Deliver the log with the media reference information and keep a dated copy. If a file is later replaced, update the affected entry and tell the editor. A reliable log makes the first review easier while preserving the editor’s freedom to discover a better sequence in the footage.