How to write a video editing brief that prevents extra rounds

Most projects that reach round five did not get there because the editor was slow. They got there because nobody wrote down what the video was supposed to do, so round one became a conversation that belonged before the first import.

A brief also makes bids comparable. Two editors working from the same page come back within range of each other. Two working from 'need a launch video, footage is in the shared drive' do not, because one priced a straight cutdown and the other priced graphics, color, and a mix. That gap is not a difference in rate but in what each thought the job was.

Writing one does not require a producer title. A shared document, kept current, does the work, and it sits inside the wider sequence in the end to end hiring process. The parts people skip are the ones that matter: exact specs, where the footage lives, and who has the final word.

What a vague brief actually costs

The cost lands in three places, and rounds are the first. A quote usually includes two. When the first cut is a guess, round one goes to agreeing on structure, round two to the notes you actually had, and the polish that was supposed to be included slides into round three. Everything past that is billed by the hour.

Guessing time is the second cost, and it is invisible to you. An editor handed 90 minutes of footage and no structure watches all of it, builds a selects reel, and invents a story before cutting a frame. Six lines of beat sheet removes most of that.

Late scope is the third. Captions were assumed. A vertical version was assumed. Someone wanted the logo animated. None of it was in the quote, so the invoice grows and the date slips. What that work costs is covered in what hiring an editor costs. The reason it happens is nearly always the brief.

The sections a working brief needs

A brief is not a creative document. It is a specification with a small amount of taste attached. Keep it to one or two pages, and ask the editor to fill in any technical field you cannot. If the job depends on an existing After Effects template or a Resolve color pass, say so and filter a shortlist by software first.

• Purpose, in one line. What the video should make someone do.
• Audience and placement. Who watches, and on which screen.
• Deliverables with exact specs. Runtime, aspect ratio, codec, frame rate, loudness target, captions.
• Footage inventory and location. Hours, cameras, codec, audio, and a link with access granted.
• Structure or beat sheet. Six lines, or at least the first five seconds and the last shot.
• Tone, with references described. Two or three, each with what you want from it.
• Music, color, and graphics. Who supplies the track, and whether a grade is in scope.
• Brand rules. Logo files, fonts, hex codes, safe areas, and any required legal line.
• Revision policy. How many rounds are included and what counts as one.
• Milestones, not one deadline. Assembly, picture lock, and final master, each dated.
• Delivery method. Where the master lands and how files are named.

A worked example brief you can copy

Below is a brief for an invented product, Meridian Sort: a 90 second launch film. Swap in your details and the shape holds for most short form work.

Project and purpose

• Project name: Meridian Sort launch film
• Purpose: Convince a warehouse operations manager who has never heard of us to book a 15 minute demo.
• Primary placement: Paid social, plus the hero slot on the product page.
• Secondary placement: Looping on a trade show screen with no sound.
• Audience: Operations managers at midsize distributors, skeptical of software, watching on a phone with the sound off.

Deliverables

• D1: 90 second master, 16:9, 1920x1080, H.264 MP4, 23.976 fps, around -14 LUFS integrated, with an .srt caption file alongside.
• D2: 30 second cutdown, 9:16, 1080x1920, same codec and frame rate, captions burned in, top 250 and bottom 350 pixels clear of text, leaving 1320 usable.
• D3: 6 second bumper, 1:1, no audio, burned in captions, for the booth loop.
• D4: ProRes 422 HQ master of D1 for archive, at final only.
• File naming: meridian-launch_v03_16x9_2026-09-18.mp4, incrementing once per delivered round.

Footage and assets

• Volume: 4 hours of A camera and 2 hours of B camera, 4K at roughly 200 Mbps. That is about 90 GB per hour, so 540 GB, plus 40 minutes of ProRes screen capture. Call it 600 GB.
• Cameras: Sony FX3 as A camera, 4K, 23.976, S-Log3. FX30 as B camera, matched settings.
• Audio: Two lavalier tracks to a separate field recorder, synced by timecode. Room tone at each location.
• Screen recordings: 1440p ProRes, cursor highlighting off, clean enough to replace on screen text in After Effects.
• Where it lives: Shared drive, access granted before kickoff. At 100 Mbps that pull runs past 13 hours, so budget a day before anyone expects a cut.
• Not shot: No close ups of the handheld scanner. We can shoot them on September 10, four days before picture lock.

Structure

1. 10:00 to 0:05. Cold open on a missorted pallet and a manager checking a clipboard. No logo, no music sting.
2. 20:05 to 0:25. The problem in an operator's own words, cut from interview. Two speakers maximum.
3. 30:25 to 0:55. Product in use, screen recording intercut with floor footage. Has to read with the sound off.
4. 40:55 to 1:15. One operator on the outcome. Lower third appears on the second sentence, not the first.
5. 51:15 to 1:30. Outcome line on screen, logo, end card held four seconds.

Tone and references

• Reference A: A workwear brand's factory film. What we want: unhurried pacing, ambient sound under the music, no posed smiles.
• Reference B: A software launch video. What we want: the way a screen recording is cropped so one feature stays readable on a phone.
• Reference C: Our own video from last year. What we want: the title card typography, nothing else.

Music, color, graphics, and brand

• Music: We supply the licensed track. Do not source your own. If the cut wants a different feel, say so before picture lock.
• Color: A camera is S-Log3, so a grade is in scope. Match B camera to A. The supplied LUT is a starting point, not the final look.
• Graphics: Lower thirds and end card from the existing After Effects template, project file provided. One new animated number card is in scope, anything past that is a change order.
• Brand: Logo as SVG and AI. Primary color #1F4A6B. Headline font is licensed, and the license covers vendors.
• Legal: The disclaimer line holds on screen at least three seconds wherever a performance claim is made.

Process, rounds, and dates

• Rounds: Two included. A round is one consolidated set of timecoded notes in a single document.
• Assembly due Tuesday September 8. Structure and story only. No color, no graphics, no mix. Temp music is fine.
• Notes on the assembly due Thursday September 10.
• Picture lock Monday September 14. Structure frozen, changes after this are billed hourly.
• Final master Friday September 18, by end of business.
• Approver: One named person has final say. Others comment, that person resolves conflicts before notes go out.
• Delivery: Upload to the shared drive plus a review link. Project archive within one week of final.
• Budget: Flat fee for the scope above, half at kickoff, half on delivery. Extra rounds quoted separately.

Staged dates do the quiet work. An assembly deadline gives everyone a cheap place to argue about structure, and a lock date lets the editor start passes that are expensive to undo. Check them against a calendar: a deadline landing on a Sunday is one nobody meets.

Run this checklist before you send

Read it as the editor would, hunting for anything you would have to ask before opening a timeline. Questions left in the document become delays. Questions asked after the quote become scope.

• The purpose line names an action, not a subject.
• Every deliverable has runtime, aspect ratio, codec, frame rate, and captions decided.
• The footage link is in the document, access granted, nothing still on a card.
• There is a beat sheet, or a first five seconds and a last shot.
• Each reference says what you want from it.
• Music is supplied or budgeted, and the brief says which.
• The revision policy defines a round and how many are included.
• Assembly and picture lock have dates, and one person is named as approver.
• The brief says where the master goes and how files are named.

Vetting the person you send it to is a separate job with its own tells, laid out in the warning signs worth screening for. The brief only removes ambiguity from the work.

Feedback that does not cause chaos

A good brief can still be undone at round two. The failure mode is six people typing in one channel, notes that say 'the middle feels long', and two of them disagreeing without knowing it.

Use timecodes. 'At 0:34 the cut lands before he finishes the word' is actionable. 'The middle feels long' is a reaction, and the editor will guess which forty seconds you meant. Review tools stamp comments to a frame. In a document, write the timecode yourself.

A note an editor can act on has a timecode, a verb, and a reason. Everything else is a conversation you have not had.

Consolidate. One list per round, because the editor cannot start until notes stop arriving, and a note contradicting an earlier one in the same round burns an hour.

Separate wrong from different. Mark each note as a fix or a preference. 'The client name is misspelled' is a fix. 'I would have used the wider shot' is a preference, and preferences need an arbiter. The approver settles those before the list goes out.

Be precise about approval. 'Approved' on an assembly means the structure is locked. If it is not, write 'approved for pacing, still deciding on the opening'. Ambiguous approval is how a locked structure reopens at round three.

Brief mistakes that look reasonable

None of these look like mistakes at the time. They look like thoroughness.

• Sending forty reference videos. More references do not add clarity, they average it out. Three, each with a note on what you want, beats forty.
• 'Make it pop'. Also 'punchier' and 'needs more energy'. Translate those into shorter shots at the top, a brighter grade, a music swap, or tighter framing.
• Adding stakeholders at round three. Anyone seeing it for the first time reacts to structure. Get every reviewer into the assembly, even for two minutes.
• Leaving frame rate to fate. Mixed 23.976 and 29.97 in one timeline creates stutter that someone notices at final and blames on the edit.

Write the purpose line today

Open a blank document and write the purpose line for the project on your desk. If it will not fit in one sentence, the project is not ready to brief, and the next step is a conversation with whoever owns it.

Then fill the deliverables in with real numbers, paste the footage link with access granted, and date the assembly and the lock. Send it unchanged to everyone you are considering, whether they came from a referral or a directory listing. The one who asks about the loudness target or the missing scanner close ups is showing you how they will behave in week three.