An organiser's note saying “use the answer at 11.20” may be clear on event day and almost useless in the edit. The programme ran late, one recording started after the room opened and another restarted during a break. Commission a practical map between event notes and recorded material before the team disperses.
The map does not need to turn the organiser into a technical operator. It needs to identify the session, the relevant recording and a reliable way to locate the moment. Agree the reference method with production so editorial notes are usable in the material the editor will actually receive.
Decide what deserves a logged reference
Log moments that change the editorial task: a corrected statement, a requested omission, an unusually useful explanation or a segment requiring content-owner review. Logging every sentence can consume attention without improving the commission. Prioritise information the editor could not safely infer from the recording alone.
Separate observations from instructions. “Speaker corrects project date” describes an event. “Remove earlier date and retain correction” is an editorial proposal that may need approval. If both appear in the same note, identify who authorised the action rather than making the logger's interpretation look final.
Include the session identity even when the running order seems obvious. A panel can move rooms or a speaker can appear in more than one session. The more the programme changes, the less useful an assumed chronological folder order becomes.
Establish the reference at capture
Ask production how a note will be tied to a source file. It may use an agreed recording reference, a logged marker or a recognisable spoken phrase alongside the session name. The technical team should choose a method suited to its workflow. The buyer should test that the method can be followed by the eventual editor.
Where recording restarts or source names change, record the transition. Do not assume elapsed event time and elapsed file time remain equivalent. A small handover note at the time can prevent a later search through several similar files.
The note owner should also record uncertainty. “Approximate location near the second audience question” is more honest than a precise-looking reference copied from an unrelated clock. The editor can then use it as a search aid rather than treat it as a verified cue.
Test the handover with one real note
At a hypothetical industry forum, an organiser flags a useful answer using the scheduled session time. The editor receives three recording segments and cannot find it quickly. A better handover identifies the actual panel, the second recording segment and the opening words of the question. The note becomes traceable without requiring an elaborate logging system.
Before the event ends, ask someone other than the logger to locate one marked passage using the proposed package. If they cannot, improve the reference while the people and programme details are still available.
Keep the map with the source identity
Deliver the log alongside the recording register, not as an isolated message in a personal chat. Distinguish raw observations, requested changes and approved changes. The organiser should nominate an owner for unresolved notes.
This small commissioning item reduces editorial guesswork and preserves important decisions from the event day. Its value is the traceable connection between what someone noticed and what the editor can verify, rather than the apparent precision of a long spreadsheet.
Discuss suitability
Contact Live Images to discuss the proposed recording, audience and delivery requirements. Discuss suitability, scope and availability for the proposed brief.
Editorial note
Original commissioning guidance prepared with AI assistance. Hypothetical examples are invented, not Live Images projects. This unpublished resource makes no service, legal or performance guarantee.