Video editor brief template: 20 mandatory points
What to tell the editor before the work starts: the delivery format required by the platform, references, acceptance criteria and the number of rounds of changes.
A video editor brief template is a compact working document that saves more time than any adjustment during the work. It has 20 mandatory points: what we are editing, for which platform, how many rounds of changes are included in the work and what counts as a finished result. Below is a list you can move into your own brief and fill in over one evening.
The mandatory points of the brief
The points follow the order of reading: first what we do, then what we finish with. The order does not matter — what matters is that no point is left empty. An empty point in the brief comes back to you as a change that nobody put in the estimate.
20 points to fill in before the work starts
- The goal of the video and the running time: for which platform and to what length we are cutting.
- The delivery platforms: YouTube, VK, Reels, TikTok — or one specific platform.
- The format of the raw files: what to send if the shooting is already finished.
- The frame rate of the timeline: in which timeline we assemble and what we calculate for.
- The delivery resolution and the bitrate for each platform.
- The container and the video codec of the finished file.
- Sound: codec, sampling rate, bitrate, number of tracks.
- The colour space for SDR.
- The intermediate project file and its container — so that the archive opens.
- The tempo of the track and the cut points: on which counts we cut.
- What to say on screen: subtitles, titles, captions.
- What we do not do in this order: effects, retouching, animation — separately.
- References: links with timecodes, not “something similar”.
- Who reviews the draft and when: one person, one deadline for the answer.
- How many rounds of changes are included in the work.
- What counts as an additional round and what it costs.
- The acceptance criterion: what counts as a finished video.
- The payment schedule.
- What we deliver: the final file, the project sources, the archive.
- The delivery deadline and what we do if it moves.
References and acceptance criteria
A reference is not “something similar” but a specific video with a timecode. That is how you explain what exactly you are looking at: a transition, the rhythm of the edit in the first part, the work with colour. A vague link turns into a round of changes: the editor guesses and shows you something else.
What we fix as an acceptance criterion
- The finished video: the edit is assembled, the sound is mixed, the colours are approved, the subtitles are proofread.
- One person responsible on the client side and one deadline for the answer on the draft.
- How to count the client's silence: what counts as approved if there is no answer.
- Where the final file lives and in which format we hand over the project archive.
Revisions: how many and how
The norm in our work is 2-3 rounds: the rough cut, the refinement, the final polish. A round beyond that is separate work, 3 000 — 10 000 ₽ depending on the volume. If the document does not state the number of rounds, the argument will not be about quality but about the invoice.
The payment schedule is fixed in advance as well: 50% before the start and 50% after the final approval. These two figures are the most common cause of misunderstanding at the start: without them the first “I will just have a look” turns into a negotiation about the price and not about the picture.
Delivery format and raw files
The delivery format is taken not from taste but from the requirements of the platform. YouTube states it directly, and it is the most verifiable document of all: an MP4 container with the moov atom at the beginning of the file (Fast Start), the H.264 High Profile video codec with progressive scan and CABAC, and AAC-LC sound with a sampling rate of 48 kHz.
| Delivery parameter | Value required by the platform |
|---|---|
| Container | MP4 with the moov atom at the beginning of the file (Fast Start) |
| Video codec | H.264 High Profile, progressive scan, CABAC |
| Audio codec and sampling rate | AAC-LC, 48 kHz |
| Audio bitrate for stereo | 384 kbit/s |
| Video bitrate for 1080p | 8 Mbit/s |
| Video bitrate for 2160p | 35-45 Mbit/s |
| Typical frame rates for delivery | 24, 25, 30, 48, 50, 60 fps |
| Colour space for SDR | BT.709 |
A separate line is the frame rate of the timeline. Our working timeline is 25 fps, and it decides whether the cuts land on the beat. On a synthetic 120 BPM track, 30 hits out of 60 land on a frame border: cutting is possible every other hit, but not on every hit. On a 128 BPM track it does not work that way — only 2 hits out of 64 reach the border, and the hits drift further and further away from the grid.
The intermediate file is a line in the brief as well, and here are the specifics: we write ProRes into a .mov and not into a .mp4 — in a .mp4 this codec is not written, and the editor gets a file of zero size. On the test signal ProRes 422 came out at 51.53 Mbit/s, and the proxy version ProRes 422 Proxy at 19.34 Mbit/s. This is the lower bound: on real footage the bitrate is higher, and the space for the project is planned by the target bitrates, not by our measurements on a test pattern.
The template works when every point can be answered with “yes” or “no”. One unfilled point is a future change, and a future change costs money. Move the list into your own brief and send it to the editor before the start, not after the first draft.
Frequently asked questions
Do you need a detailed brief for a short video?
For a short cut in a single vertical version a short list is enough: the platform, the running time, the frame rate, the codec with the bitrate, what to say on screen and the acceptance criterion. The shorter the video, the more expensive every omitted point: reworking the delivery format and the acceptance happens only after the file has already gone out.
What to do if the client changes the requirements?
Change the list, not the edit: put the change down as a separate point and recalculate the estimate. If the requirement changes the concept itself, that is a new project and not a round of changes. It is worth fixing this in the document in advance: how many rounds are included in the work, what counts as additional and at what price.
Read next
Need this done as a project?
We take on projects like this — with the same settings we walk through in this piece.