Editorial decisions
How to edit a panel discussion into a short two-viewpoint summary
Build a short panel video around one question, two supported viewpoints and an honest conclusion. Includes an argument map and worked selection example.
A panel recording often contains several useful answers to the same question. Cutting only the most forceful answer can hide the qualification that made the conversation valuable. Including every contribution can leave viewers unsure what the discussion was about.
A two-viewpoint summary gives an in-house marketing or events team another option: one clear question, two relevant positions and an honest account of where they meet or remain different. The aim is to help a specific audience understand a decision, using the event footage the team already has.
Start with the relationship between the ideas. The number of speakers and the duration of the clip come later.
01
Choose a question the recording actually answers
Write the intended viewer and their decision at the top of your brief. For example, a marketing operations lead deciding how to introduce a new reporting process needs a different summary from an executive interested in the event's overall theme.
Find the question in the recording, including any clarification the moderator added. Then watch each candidate response with the surrounding exchange. A comment made in response to a later question should not appear to answer the opening question unless that relationship remains accurate.
If the useful contributions concern different problems, make separate clips. Sharing a broad topic does not make two statements opposing viewpoints.
02
Build an argument map before a timeline
Use this five-part structure to record what the footage supports:
- Question: The specific issue the viewer needs to understand.
- Viewpoint A: One speaker's answer and the reason or evidence supporting it.
- Viewpoint B: A distinct answer, condition or emphasis that matters to the same issue.
- Qualification: The boundary, exception or assumption needed to interpret either answer.
- Resolution or unresolved point: What the discussion established, or what it left open.
For each part, record the source file, speaker and verified in/out points. Add a plain-language summary for planning, but keep it separate from the speaker's actual words. Never turn that summary into an attributed quotation.
Write the relationship between A and B in one sentence. They may disagree about a recommendation, agree on the goal but differ on sequencing, or describe different operating conditions. This sentence is the test of whether the edit has a coherent centre.
03
A hypothetical worked example
Imagine a panel about introducing a new reporting process. One participant favours agreeing a common measurement definition before a pilot. Another favours testing with one team to discover which definitions cause confusion.
These are hypothetical inputs, not quotations from a real event. The useful distinction is sequencing. A faithful summary would show why each participant favours their sequence, then retain any discussion of when that sequence is appropriate.
Suppose both participants acknowledge that teams eventually need shared definitions. Calling the clip “Why experts disagree on standardisation” could overstate the difference. A more accurate editorial angle would be choosing whether to standardise before or after a pilot.
If the panel never settled that choice, the ending should leave it open. A moderator's later thank-you is not evidence of consensus. Nor should an editor write a conclusion and place it in a speaker's mouth.
04
Decide what cannot be cut
For that hypothetical reporting panel, the short version could follow this sequence. These are editorial summaries of invented inputs, not speaker quotations or verified source passages.
| Keep in the summary | Why it matters |
|---|---|
| The question of when to agree measurement definitions | Establishes the actual decision, rather than a broad discussion of reporting |
| The case for defining measures before a pilot | Gives the first position its reasoning, not just its conclusion |
| The case for learning from a pilot before finalising definitions | Makes the second approach distinct and intelligible |
| Both participants' acceptance that shared definitions are eventually needed | Prevents a disagreement about sequence becoming a false disagreement about the goal |
| The fact that no single sequence was agreed | Preserves the discussion's unresolved ending |
In a real edit, check the selected passages and their source locations before arranging them. The useful question at each cut is what a viewer could wrongly infer from what has disappeared. A personal preference can start to sound like a general recommendation; a proposed approach can start to sound like a tested result.
If the sequence is too long for the intended slot, narrow the question. Remove secondary examples before removing the reasoning that distinguishes the positions.
05
Preserve the relationship between speakers
A short summary does not need equal speaking time. It needs enough of each relevant position to represent it accurately. One answer may require an example; another may be clear in a single sentence. Padding a weak or irrelevant contribution to create symmetry introduces false balance rather than fairness.
Check the joins carefully. A reaction shot taken from another moment can make a speaker appear to dismiss a comment they never heard. Applause may belong to the session ending, not the argument preceding it in the new edit. A cut that removes “in our case” can broaden a narrow observation.
The Associated Press standards for audio and video offer a useful reference for preserving meaning when improving or shortening recorded material.
When rearranging passages, compare the finished sequence with the original discussion. Ask whether each participant would recognise the position attributed to them, including its conditions. That is a useful editorial check, not a substitute for checking the actual source.
06
Confirm the reuse context
Before distribution, check the arrangements covering the event recording and the intended use of individual contributions. Keep a record of any speaker approval process, agreed attribution, restricted passages or channel limitations. Confirm with the responsible event or legal contact where those arrangements are unclear.
Payment for filming is not, by itself, your team's complete reuse checklist. A partner-branded panel, a customer contribution and a public keynote may have different approval arrangements. This is a practical production check, not a legal conclusion about any particular recording.
Give the reviewer the proposed title and accompanying post as well as the video. A careful edit can still be misrepresented by a headline claiming a dispute or consensus that did not occur.
07
Where Anjin Media fits
Anjin Media can build a source-grounded edit from a written brief, with a plan identifying the selected passages and their source timecodes. Use your argument map to specify the question, the two positions and the qualification that must remain. Anjin Media documentation
A composition accepts one to four ready source groups. Plan review is available before rendering when auto_render is left off; auto-render is an opt-in alternative. Creating a composition
The person reviewing the edit still needs to judge whether the joins and ending faithfully represent the conversation. Keep the argument map alongside the approved file so later campaign edits do not quietly discard the conditions that made the summary fair.
For the wider process of deciding which recordings deserve new campaign assets, see the B2B video content repurposing system.
If the panel includes essential slides, use the webinar framing decision tree before choosing a vertical output.
08
Common questions
What if the moderator's question is too long to include?
Use a concise, clearly editorial introduction in the accompanying text or your editing workflow, rather than presenting new wording as the moderator's speech. Check that the shorter framing preserves the scope and conditions of the original question.
Can I include a speaker who later corrected their answer?
Use the corrected position and enough context to make it understandable. Do not retain an earlier, punchier statement as their final view. If the correction changes the whole argument, reconsider the proposed summary.
What if an audience member's question is inaudible?
Do not guess its wording. Look for a moderator's accurate restatement or another clearly supported introduction. If neither exists, choose a passage that establishes its own context, or leave that exchange out.
About this field note
Written by Anjin Media's editorial team from hands-on work with long-form video, cut plans and searchable archives. Product details are checked against the documented platform behaviour before publication.
