Your conference runs for a day, and the enquiry asks for “event coverage”. One stakeholder expects a promotional film showing why the occasion mattered. Another expects colleagues who missed a presentation to be able to follow the entire discussion afterwards.
Those are different purchases. A highlights film selects moments to communicate a story. A session recording preserves an agreed presentation or discussion as a usable account. Decide which obligation the supplier must meet before a crew plan is built around the event timetable.
Choose the value required after the event
For a highlights commission, identify what someone should understand about the occasion: its subject, the people involved, the experience or a specific message. The production can select relevant moments rather than preserve every contribution. Its acceptance test concerns the finished account, not whether every agenda item appears.
For a session recording, identify who needs the content and why. A viewer may want to revisit a complete explanation, hear a panel's differing perspectives or access a presentation they missed. Selected atmospheric images and a few strong sentences will not necessarily serve that need.
Neither option is simply the longer or shorter version of the other. Nor does choosing a recording answer whether it must be broadcast live. This decision concerns what must survive the event as an agreed deliverable.
Name the sessions rather than requesting everything
Mark the programme with the exact presentations, panels or other segments that require a complete account. Give each an identifier, room and expected time window. Distinguish confirmed requirements from optional coverage and unresolved requests.
Then define the boundary of each recording. Does it include the host's introduction, the presentation itself and audience questions? Are breaks and housekeeping outside the intended output? What should happen if an unexpected discussion becomes part of the session?
“Full event recording” is too imprecise when the programme contains simultaneous activities. The brief needs to say which account matters, not leave the crew to infer what the organisation might want later.
For highlights, name the story priorities separately. Those could require contributions or activity outside the rooms being recorded. Do not assume that everything useful for the promotional film will occur in front of a session camera.
Expose competing capture obligations
Australian producer Dream Engine's event-video guidance distinguishes presentation recording from highlights work elsewhere at an event, and asks buyers to identify simultaneous sessions. It also addresses slides and audience questions. These are useful examples of different coverage requirements, not a recommendation of a particular crew arrangement or supplier.
Put overlapping requirements beside each other. If a complete panel account is essential while an interview is proposed elsewhere, ask the supplier how both would be covered. An additional requirement may need more resources, a changed interview time or a reduced priority list.
Do not prescribe a universal number of cameras. The supplier should assess the actual rooms, programme, sound, presentation material and agreed outputs. What matters commercially is whether the proposal explains how it will meet the named obligations, including any exclusions.
Preserve the content that makes a session understandable
A speaker may refer to a chart, demonstrate an object or answer a question that is barely audible from the stage. A continuous picture of that speaker is not necessarily a complete explanation for the later viewer.
Identify these dependencies before filming. Ask who supplies the authorised presentation files and which version will actually be used. Explain whether audience questions belong in the required account and ask production and the event's audio-visual team to assess the arrangements.
Keep permission and release decisions visible for speakers, presentation material and audience contributions. Attendance at the event does not establish every later use. Unresolved material may require a narrower release, an agreed edit or a held recording; it should not become an unnoticed gap in something described as complete.
Build an event coverage-obligation map
Complete one row for each materially different commitment.
| Field | Buyer decision |
|---|---|
| Programme reference | Named session or activity, room and expected window |
| Finished use | Complete session account, selected highlights or both |
| Required boundary | What must be retained, and what is expressly excluded? |
| Supporting content | Slides, demonstrations, questions or other context required |
| Concurrent demand | Which other commitment occurs during the same window? |
| Production response | Supplier's proposed coverage and unresolved dependencies |
| Change authority | Who can reprioritise if the programme changes? |
| Acceptance evidence | How the buyer will check the agreed coverage and finished output |
Have the event owner and supplier reconcile conflicts before treating the map as confirmed. A longer wish list does not create additional coverage capacity.
Hypothetical example: a keynote and a separate reception
A fictional industry forum wants its keynote available to registered delegates afterwards. Marketing also wants an invitation film for the following year's event, including participant comments from a reception elsewhere in the venue.
The keynote runs into the reception period. The first proposal refers only to one general filming window. The map reveals two obligations that overlap: preserve the agreed keynote account and collect selected reception contributions.
The buyer asks the supplier to assess a combined plan. It could involve separately resourced coverage, moving the planned interviews or reducing the promotional requirement. The buyer does not assume missing keynote passages can be reconstructed from reception footage. This example is invented and suggests no standard crew, price or guaranteed solution.
Agree what successful delivery will contain
For session recordings, check the named sessions against the agreed boundaries, the inclusion of necessary supporting material and any disclosed omissions. Clarify which edits are permitted without changing the account. Do not silently label an abridged or interrupted version complete.
For highlights, check the selected story, accurate context and agreed promotional outputs. If both deliverables are purchased, accept them separately rather than treating an attractive highlight as proof that session coverage is complete.
Live Images currently presents construction project-film services, not a confirmed conference-recording package. Ask about suitability if considering an enquiry, and obtain explicit confirmation of any event-production provider and scope. Bring the coverage map so the purchase is defined by what must be usable afterwards—not merely by how long someone attends with a camera.
Prepared with AI assistance for Live Images. Planning guidance is general; suitability and production scope must be agreed for your project.