How to brief a video editor—without a week of back-and-forth.

Start with a decision, not an effect

Before choosing transitions, write one sentence: “After watching, this person should understand this idea and take this action.” Name the viewer rather than writing “everyone.” If you cannot finish the sentence, decide the message before commissioning a batch of clips.

For an interview, choose a passage that makes sense without the interviewer’s question. For a product demo, identify the visible action that supports the promise. If the footage does not show the feature or substantiate the claim, mark it as a missing input. An editor should not have to invent product behavior to connect the shots.

This guide covers supplied-footage handoffs. Filming, voiceover and publishing are separate production decisions. For the service itself, see Famekite’s short-form video editing.

Package footage so someone else can use it

• Source: supply original recordings where possible. Keep untouched source files separate from reference exports.
• Names: use filenames that identify the recording and version, such as founder-interview-take02. Do not rename source files halfway through an edit.
• Selection: give in/out timecodes and explain why each passage matters. State whether these are required selections or suggestions.
• Brand: include approved logo files, colors, fonts and a caption reference. Confirm that fonts and other supplied assets may be shared and used.
• Audio: label separate microphone tracks. Flag noise, missing audio or words that need checking rather than promising they can always be repaired.
• Access: share through an agreed private channel. Test access before the deadline; do not put customer data or unrestricted asset links in a public enquiry.

A reference should identify a decision: “Use the restrained captions, not the fast cuts.” Otherwise the editor may copy the part you dislike. References communicate direction; they do not grant permission to reuse someone else’s footage, music or design.

Worked example: turn a vague request into an edit handoff

Illustrative production example. The business, filenames and timecodes below are invented for teaching; they are not a client project or a claim of results.

Vague: “Make this interview into a punchy Reel.”

Useful: “Create one short explaining how a studio owner checks a booking request before confirming it. Keep the speaker’s warning about availability. End with an invitation to view the booking process, not an invented discount.”

Specify the desired runtime as a working constraint, not permission to cut important context. If the story cannot fit clearly, request a revised approach before finishing captions and graphics. That saves reworking polished sections that should never have been there.

Repurpose a podcast or webinar into shorts without losing the point

Start with self-contained ideas, not a quota of clips. A useful short makes a point, includes enough context to understand it and ends without requiring the rest of the episode. A long source recording does not guarantee a large batch of good shorts.

Hypothetical source-selection exercise—not a client result or a promised output count.

For each candidate, record source filename, start/end timecodes, central idea, missing context and approval owner. Then agree which candidates deserve an edit. The selection list is not a guaranteed clip count: some passages may need more context or unsuitable material may be rejected.

Once selected, name each base edit and its alternate openings or exports separately. One podcast passage with two opening versions is not necessarily two different stories. Use the editing quote comparison to agree source-review work, versions and revision boundaries before production.

Count clips, versions and exports separately

A new idea, a new opening and a resized export are different units of work. List them separately so the quote and the handoff describe the same project.

• Base edit: one agreed story using the selected source material.
• Hook variation: a different opening, with the rest kept consistent where practical.
• Placement export: a version reviewed for its destination, framing and interface overlays.
• Caption deliverable: burned-in captions, a separate subtitle file, or both, as agreed.

Review Reels, TikTok and Shorts in their intended placements. Do not assume that a caption position, music permission or interface-safe area transfers unchanged. Verify current platform requirements when producing the exports; a generic format label is not an approval checklist.

Give feedback the editor can act on

Use the review export’s timecodes, not source timecodes, when reviewing a finished draft. Identify the version and consolidate comments through one owner.

Separate corrections from changed direction. Fixing a misspelling is different from replacing the audience, message or source material. Agree revision rounds and how additional work is approved before production starts.

Approve the deliverable, then assign publishing

Watch the final export on a phone with sound on and off. Check caption accuracy, readable text, uncropped product details, audio continuity and the last frame. Open each delivered file rather than assuming differently named exports contain the intended versions.

Record who approved the copy, product claims and asset permissions. Name the person who uploads the video and verifies the live post. Approval of an edit does not automatically approve every music licence or grant permission to publish it on another account.

The Editor Handoff worksheet in our six-tool pack helps organize these decisions; downloading the pack requires basic details and email verification. The instruction on this page is readable without signing up. Bring the source inventory and open questions to a scoped editing enquiry; do not invent answers to make a brief look complete.

Before you brief us