Updated: September 10, 2026
The stage where projects quietly go wrong
Video projects rarely fail during the shoot. They fail during approval, in the weeks between a first cut and a final delivery, when feedback arrives from more people than anyone planned for, contradicting each other, in an order nobody controls.
The symptoms are recognisable. A cut goes out for review and comes back with notes from four people who have not spoken to each other. A change made for one stakeholder is reversed by another. A senior person who was not involved at any earlier stage sees the film for the first time at round three and asks for a different approach. And the delivery date, which everyone agreed to, quietly slips by three weeks while nobody is quite responsible.
All of this is preventable, and the prevention happens before production rather than during review.
Map the approvers before you start
The single most useful exercise is to write down, before any filming, who will have a view on the finished film and what kind of view it is. People fall into a small number of categories.
- The decision maker. One person who can say yes and make it stick. There should be exactly one.
- The project owner. The person managing day to day, consolidating feedback and holding the timeline.
- Required reviewers. People whose sign-off is genuinely necessary, such as legal, compliance or brand.
- Consulted contributors. People whose input is valuable but not binding, such as a subject expert.
- Informed parties. People who should see it before it goes public but are not reviewing it.
The trouble starts when the last two categories behave like the first. A colleague asked for their thoughts will give them, and if nobody has explained that their input is advisory, they reasonably expect it to be acted on.
Get the senior view early, not late
The most expensive feedback is a senior stakeholder seeing the project for the first time at the final cut. At that point every option is costly: reshooting, restructuring or delivering something the decision maker is not behind.
The fix is to involve them at the points where their input is cheap. Show them the creative brief and the treatment. Show them a script. If they are unavailable for those, at minimum have the project owner confirm the direction with them in writing before production starts.
Where a senior person genuinely cannot engage early, say so explicitly at the outset and agree what happens if they object later. That conversation is uncomfortable and it is far less uncomfortable than the alternative. The upstream work is covered in how to write a creative brief for your Miami video project.
Structure the review stages
| Stage | What is being approved | What is not open |
|---|---|---|
| Brief and treatment | direction, tone, audience, message | nothing yet |
| Script | wording, structure, claims | the agreed direction |
| Rough cut | structure, pacing, which content is used | the script, the direction |
| Fine cut | timing detail, graphics, text | structure and content selection |
| Final | errors and factual accuracy only | everything creative |
Making these boundaries explicit is what keeps a project moving. When a note arrives at the fine cut asking to restructure the opening, the answer is not no, it is that this reopens a decision made at rough cut and here is what that costs in time and money. That is a conversation about trade-offs rather than a conflict.
State the boundaries on the review link itself, not only in a document nobody reopens. One line saying what stage this is and what feedback is useful now changes the responses you get.
Consolidate feedback through one person
Feedback should reach the production company as one list from one person, not as messages from five people over ten days. This is the single most effective process change available and it costs nothing.
The project owner collects everything, resolves contradictions internally, and sends a single consolidated set of notes. Where two stakeholders disagree, that is resolved on the client side before the note goes out, not by asking the editor to arbitrate.
This also protects the revision count. A round should be one consolidated set of notes, and a stream of individual comments over two weeks is several rounds pretending to be one. How rounds are defined commercially is covered in understanding revision rounds in your video contract.
Writing feedback that can be acted on
Useful notes share a few characteristics, and they are easy to adopt.
- Reference timecode. At 0:47 rather than near the beginning.
- Describe the problem, not only the solution. This section feels slow is more useful than cut four seconds, because an editor may have a better fix.
- Separate must from prefer. A factual error and a stylistic preference need different treatment.
- Be specific about wording. If text must change, supply the exact replacement.
- Avoid contradicting earlier approvals silently. If you are reopening something, say so.
- Do not send notes on someone else's behalf. Second-hand feedback loses the reasoning.
A review tool that attaches comments to timecode helps considerably, but the discipline matters more than the software.
Set deadlines for feedback, not only for delivery
Timelines usually specify when the production company delivers and say nothing about when the client responds. That asymmetry is where most slippage lives.
Write both. Feedback on the rough cut by this date, on the fine cut by this one, with the delivery date conditional on those. Then, when feedback is late, the effect on delivery is a stated consequence rather than a negotiation.
Add a default for silence. If no feedback arrives by the deadline, the cut is treated as approved, or the delivery date moves by the number of days the feedback was late. Either rule is fine; having no rule is what allows a project to drift indefinitely.
Legal and compliance review
Where a project needs review by legal, compliance or a regulated function, plan it as a stage with its own duration rather than assuming it happens alongside everything else. These reviews often take longer than creative ones and they operate on their own schedule.
Give reviewers the script rather than waiting for a cut, since a claim that has to be removed at fine cut may have been the reason a scene was shot. And ask specifically what they need to see: some functions review only the words, others need the finished film with graphics in place.
Approvals across languages and regions
Where a Miami project delivers English and Spanish versions, or serves offices in more than one country, the approval map gets a second dimension. The temptation is to approve the primary version and treat the others as translation, which works until a regional reviewer objects to something that was settled weeks earlier.
The workable approach is to bring the regional or language reviewer in at script stage, so their input shapes the original rather than arriving as a correction to a finished film. Then treat each language version as needing its own final approval for accuracy, but not reopening creative decisions already made. Say that explicitly, because otherwise a second reviewer will reasonably assume everything is still open.
When approval stalls
Occasionally a project simply stops moving because a decision cannot be reached. The useful responses are practical rather than procedural.
Name the specific decision that is blocking things, in one sentence, and put it to the decision maker on its own rather than inside a long update. Offer two options rather than asking an open question. Say what each costs in time and money. And state what happens if no decision is made, since a deadline concentrates attention in a way that a request does not.
Where the stall is caused by genuine disagreement about direction, that is a brief problem rather than an edit problem, and continuing to iterate the cut will not resolve it. The related commercial dynamic is discussed in change orders and scope creep in Miami video production.
How we run approvals
We ask who the single decision maker is before we start, and we ask whether anyone senior will see the film for the first time at the end, because that answer changes how we structure the early stages. Each cut goes out with a note saying what stage it is and what feedback is useful at that point.
We ask for consolidated notes from one person with timecode, and we write feedback deadlines into the timeline alongside our own delivery dates. Where a note reopens an earlier decision, we say so and explain the cost rather than absorbing it silently. More on working with production companies is on our blog, background on the about page, and you can reach us through the contact page.
The short version
Map the approvers before production and identify one decision maker, distinguishing required reviewers from people merely being consulted. Get senior input at brief and script stage, where it is cheap. Define what each review stage is approving and what is closed, and state it on the review link. Consolidate all feedback through one person into one list. Write notes with timecode, describing the problem rather than only the fix, and separating must from prefer. Put feedback deadlines in the timeline alongside delivery dates, with a stated consequence for silence. Plan legal review as its own stage with its own duration.