Video production workflow: from brief to delivery

Map the workflow around seven handoffs

Pre-production, production and post-production describe the broad phases. For day-to-day coordination, split them into seven handoffs: approved brief, shoot-ready plan, completed capture, accepted media package, reviewable edit, approved master and delivered archive. The sequence below is a practical editorial framework, not a mandatory industry standard. Combine roles on a small project, but keep the decisions visible.

A workflow differs from a schedule. The schedule gives dates; the workflow explains what must exist before the next task can succeed. An editor can have an available afternoon and still be blocked by missing sound files. A review slot is useless if nobody can decide which conflicting comment takes priority. Record dependencies as explicitly as deadlines.

• Brief: producer owns scope; project sponsor approves the audience, message and deliverables.
• Plan: producer coordinates access, contributors, shot requirements and recording dates.
• Capture: director and crew deliver usable picture, sound and coverage notes.
• Media handoff: media owner transfers verified files; editor confirms usability.
• Edit: editor builds the agreed story; producer checks readiness for review.
• Approval: one decision-maker signs off the exact version after specialist checks.
• Delivery: producer verifies the package; publishing owner accepts it and records the release.

1. Approve a brief that can guide decisions

Start with the viewer, their question, the promised answer and the action the video should enable. Define the evidence available to support the message. If those choices are unresolved, settle the content strategy before turning the request into a production job.

List the actual outputs: for example, a two-minute website explanation, one short vertical edit, a clean master and caption files. Add languages, destinations, access constraints, budget boundaries and review responsibilities. Duration alone does not describe the workload; animation, customer approvals and alternate languages can introduce separate dependencies.

Name one person who resolves feedback and one owner for factual accuracy. Agree which changes fit the original scope and which require a revised cost or date. The brief passes when the sponsor approves these decisions in writing and the production team can describe the same outcome. Our creative brief guide explains how to turn subjective preferences into observable review criteria.

2. Turn the brief into a shoot-ready plan

Develop a script, interview outline or sequence of story beats, then connect each essential claim to something the crew can record. Confirm the people, locations, objects and permissions required. Identify anything difficult to recreate, such as a customer visit or a live demonstration, and give it priority.

Work backwards from the edit. Plan the opening, explanation, evidence and ending, including clean sound and useful transitions. Specify alternate framing before filming if a vertical version must preserve a product detail or demonstration. The pre-production planning guide goes deeper into converting an idea into a practical shot plan.

Include accessibility at this stage. W3C recommends planning relevant captions, descriptions, transcripts and player support as part of the project. Decide who prepares these assets and whether essential visual information should also be explained aloud. Last-minute captioning cannot repair a demonstration whose meaning is unavailable to someone who cannot see it.

• Confirm contributor and location availability, equipment, sound conditions and contingency choices.
• Have the editor inspect the proposed formats and identify missing coverage before the shoot.
• Approve the script or story beats and confirm who may approve a necessary change on the day.

3. Capture the material and verify coverage

On the production day, track usable coverage against the planned story. A recorded clip is not automatically a usable clip. Check intelligible sound, focus, demonstrations, factual wording and complete answers while contributors are available. Mark preferred takes and any caveat, such as a screen that contains information which must be removed.

Give one person responsibility for comparing completed shots with essential story beats before wrap. If the schedule slips, protect the evidence and the ending before optional atmosphere. Record room tone and the supporting actions needed to join the explanation honestly. Keep original media protected until the agreed copies have been verified.

The exit condition is a coverage record that tells the next person what exists, what is missing and which workaround was approved. If a critical demonstration failed, report it immediately. Do not label the stage complete and leave the editor to discover the gap after the location has closed.

4. Hand over an editing package, not just a drive

Transfer camera originals, separate audio, graphics, the approved brief, script or transcript, shot notes and usage information together. Keep folder names predictable and preserve camera folder structures where the format requires them. Tell the editor which files are originals, working copies or proxies, and where the verified backup lives.

Adobe describes proxies as lightweight copies used for editing while the originals remain available for finishing. They can help on demanding footage, but they do not replace the source media. Test that proxies reconnect to the correct originals before committing the project to that workflow.

Ask the receiving editor to open representative picture and audio files, confirm synchronisation and flag missing assets before accepting the handoff. A checksum comparison can verify that copied files match their source; playback checks answer a different question, whether the recorded material is usable. Include both checks in the agreed transfer process when the project warrants them.

Use a short acceptance message: package received, sample files opened, audio checked, missing items listed, next deadline confirmed. This turns a silent file upload into a completed transfer of responsibility.

5. Separate story review from finishing

The first reviewable edit should establish the argument, sequence and evidence. Label temporary music, graphics or colour so reviewers understand what they are evaluating. Ask whether the video fulfils its promise before asking for detailed styling feedback. An expensive polish pass on the wrong story creates work that must be discarded.

Collect comments against one numbered version, preferably with time references. The producer consolidates duplicates and resolves contradictions before sending instructions to the editor. Separate factual corrections, required scope changes and preferences. When a new request changes an approved decision, record its effect on time and deliverables.

Approve the sequence before detailed sound, colour and graphics finishing. This approval is often called picture lock: the team agrees that shot order and timing are settled. Corrections remain possible, but the people responsible should understand which downstream work must be repeated.

For recurring social batches, the short-form video workflow is a more compact companion. A one-off business film needs the same clarity with extra attention to contributors, evidence and final delivery responsibilities.

6. Check the master, versions and delivery package

Make a delivery matrix with one row per output and columns for aspect ratio, resolution, language, captions, audio, destination, filename and approval status. Choose settings from the agreed destination requirements. Adobe's export guidance supports selecting a format and preset, checking settings and exporting the sequence; a successful export still needs a separate content check.

Watch every final version from beginning to end. Check spelling, names, claim accuracy, missing frames, sound transitions, caption timing, graphic placement and the intended ending. Open caption files in the actual player when possible. Confirm that vertical reframing has not cropped a demonstration and that no temporary watermark or offline-media screen remains.

Deliver the approved masters, distribution versions, captions and any agreed project files with a readable index. Record relevant licences, contributor permissions, expiry restrictions and backup ownership. The publishing owner should acknowledge the exact files received. Keep an archive that another editor can reopen instead of relying on a filename containing the word final.

7. Close the project with a useful review

Review the workflow as well as the finished video. Record where work waited, which information arrived late and which approval reopened a decision. Separate hands-on editing time from waiting time so a slow turnaround is not automatically blamed on craft.

Then assign one change to the next project: earlier product review, a transfer checklist, a clearer version name or a protected captioning slot. For audience results, use the video measurement guide to connect behaviour to a change in the next production. Closing the loop makes the workflow more useful each time it runs.