Tell the editor what the cut must achieve.
“Make it engaging” leaves the editor to work out what the video is saying. Start the brief with the audience’s question and the answer this cut needs to give. Then identify the source passages, what can go and which qualifications need to stay.
The assignment: shorten “Which mistake should a map make?” into a spoken explanation of the area-versus-navigation tradeoff. Preserve the opening choice, the useful property of standard Mercator, the return to area comparison and the final decision. The geographic-extent explanation remains available in the full source and accompanying transcript.
This is an original teaching exercise with synthesized demonstration narration. It is not Rishwajeet’s voice, a real interview or a released client film. The source file and cut below exist so you can inspect the handoff against actual media.
Give every instruction a stable source.
Name the recording and version before writing timecodes. Use source time for locating material and sequence time for where it lands in the proposed edit. A timestamp without that distinction can send an editor to the wrong sentence. For multiple cameras or separate sound, specify the synchronized timeline and its frame rate before anyone cuts.
This exercise uses elapsed audio time in minutes:seconds.milliseconds. The editable JSON also carries exact PCM frame offsets at 22,050 Hz. These audio sample positions are not video-frame timecode. A real video handoff should state the actual timeline format, including frame rate and any drop-frame convention.
Download the full source audio (WAV) · Download the timecoded transcript (TXT) · Download the cut sheet (JSON)
The full source runs 01:44.772. The transcript retains every segment and the scientific scope notes. Each selection below points to that file.
Make the proposed cut reconstructable.
The cut keeps four of the six source segments. It removes the general flat-map constraint and the paragraph about geographic extent to concentrate on one comparison. Those omissions narrow what the short edit explains; they do not license a broader claim about every map.
| Selection and purpose | Source in → out | Edit in → out |
|---|---|---|
| A01 — Put the viewer inside a choice | 00:00.000 → 00:14.648 | 00:00.000 → 00:14.648 |
| A03 — Make the apparent flaw useful | 00:33.342 → 00:55.918 | 00:15.148 → 00:37.724 |
| A04 — Return to the first job | 00:56.918 → 01:11.432 | 00:38.224 → 00:52.738 |
| A06 — Resolve the opening choice | 01:28.645 → 01:44.772 | 00:53.238 → 01:09.365 |
There is a half-second gap between selections. The resulting narration is 01:09.365 long; this is an audio assembly for inspecting the structure, with no finished visual treatment or music.
Download the example edit (MP3). Its spoken text is A01, A03, A04 and A06 in the transcript.
For an interview, quote the actual words and preserve the surrounding answer. Reordering two genuine sentences can still manufacture a connection the guest never made. The editor needs enough context to spot that, plus an explicit instruction to flag uncertainty before a context-changing cut is approved.
Describe the work a visual has to do.
“Add B-roll” specifies an asset category. It does not tell the editor what the viewer needs to understand. Tie visual directions to the passage they support, with separate notes for required facts and creative choices.
| Passage | Useful direction |
|---|---|
| A01: two jobs | Present the classroom area comparison and the constant-bearing route as distinct tasks. Give the viewer time to read each. The exact graphic style is open. |
| A03: Mercator tradeoff | Show a checked standard Mercator diagram with the constant-bearing line and area distortion explained separately. Never label the line “shortest route.” Do not use a random online-map screenshot as equivalent evidence. |
| A04: area comparison | Use a properly labelled equal-area example for the comparison. Keep geographic extent and labels comparable; do not casually stretch an image to fit a frame. |
| A06: decision | Return to task, geographic area and protected property. The final visual should help the viewer apply the question, not introduce another fact. |
These are proposed visual instructions, not assets included in the download. The editor should flag the missing map artwork before finishing. Agree who commissions or sources it, who checks its accuracy, and whether its usage terms allow the intended release.
Separate story approval from finishing.
Review the first assembly for the argument, omissions and meaning of each cut. Review a later cut for pacing, graphic comprehension and the way sound and picture work together. Then check the approved export, captions, names, source credits and delivery settings. Keep the sequence proportional to the job: a small edit can combine stages when the reviewer can still make a clear decision.
Consolidate comments into one decision list with an owner. “The opening feels slow” is a useful observation but an incomplete instruction. A stronger note identifies the location, the problem and the intended result: “At sequence 00:00, keep both jobs; remove the repeated setup before the comparison so the choice arrives once.” The exact change should follow the material rather than a universal rule to cut faster.
Name who can approve story changes and who can approve the release. A polished export does not answer whether the argument was accepted. Frame.io’s approval guidance also emphasizes defining the review process and keeping feedback clear.
Plan accessibility at the brief stage. Decide who owns captions, a transcript and any necessary description of visual information; check that on-screen labels can actually be read in the intended format. W3C’s media planning guidance explains why these requirements belong before production, when choices are easier to make. A caption file alone is not proof that every accessibility need has been met.
Use the blank brief on a real project.
The editable editor brief template includes the decision, source inventory, cut instructions, visual requirements, sound, accessibility, review ownership and deliverables. Fill it with actual filenames and agreed settings. Remove fields that do not help the editor make a decision.
For a YouTube long-form film, include the opening promise and where it gets paid off. For a podcast, preserve the guest’s meaning and the relationship between questions and answers. For a short, specify the standalone question and the context a new viewer lacks. For an educational film, make the evidence and diagram checks easy to locate.
Finish the brief by naming unresolved choices. A missing graphic, an unverified quote or an undecided aspect ratio should be visible before edit time is spent on it. The handoff is ready when the editor can start with confidence, identify the real constraints and propose improvements without guessing what the piece is for.
Questions about the method.
What should a video editor brief include?
Audience, intended outcome, stable source files, the story or argument, proposed cuts, visual and sound requirements, factual and rights limitations, accessibility needs, reviewers and exact agreed deliverables.
Are the example timecodes real?
Yes. They are measured from the supplied synthesized source audio, with source and edit positions shown separately. They use elapsed audio time and PCM sample offsets, not video-frame timecode.
Should the editor follow every proposed cut exactly?
Treat the proposed cut as an inspectable starting point. The editor should propose improvements and flag missing context, assets or factual issues; identify which changes need story approval.
Tell us what you want to make.
Tell us about the channel or idea, the team you have and where you need help. We’ll discuss the scope on a 30-minute call.
Book a 30-minute call rishwajeet@machinehouse.media