Why video production runs late and how to recover the schedule
Identify missing inputs, decisions, and approvals that block a video, protect the schedule, and recover a delayed project.
The team behind Polimake. We explore the intersection of technology, creativity, and automation.
An agency must deliver a product video on the 28th. The shoot is booked for the 10th, but final packaging will not arrive until the 12th, legal has not approved the main claim, and nobody has confirmed which client stakeholder can sign off.
The project is already late even though delivery is weeks away.
Delays do not begin when editing misses a date. They begin when blocked work enters production as if it were ready.
Use an intake gate
Before confirming a shoot or edit, require an approved brief, defined deliverables, closed script, checked client material, known rights, a feedback owner, final approver, review milestones, budget, and scope.
When something is missing, the state is not “in production.” It is “waiting for source material” or “waiting for decision”, with an owner and date.
Separate three types of delay
A resource is missing
Product, logo, translation, music, location, or participant has not arrived.
Action: record what is missing, its owner and deadline, and which work can proceed without it.
A decision is missing
Two claims remain, nobody chooses a script, or several stakeholders give incompatible instructions.
Action: send a closed question to the decision-maker. Do not request general feedback; ask them to choose A or B by a named time.
Scope has changed
After approving a horizontal video, the client requests six vertical cutdowns and another language.
Action: calculate work, price, and a new date. Do not hide the extension inside the original schedule.
Protect the critical path
Not every delay moves delivery. Waiting for a font may not prevent selecting footage. Waiting for the location prevents shooting.
Identify blocking dependencies:
Approved script → Shoot → Ingest → Approved rough cut → Finishing → Delivery
When one critical date changes, update dependent milestones immediately. Do not preserve a fictional final date until the last week.
A recovery example
Situation:
- Planned delivery: Friday 28.
- Packaging available: Wednesday 12, two days after the shoot.
- Legal claim decision: Thursday 13.
- Campaign launch: 28.
Honest options:
- Move the shoot to the 14th, deliver the master on the 28th, and supply adaptations the following week.
- Shoot non-packaging material on the 10th and product on the 14th, paying for a second unit.
- Use old packaging and limit shots if client and legal approve.
- Preserve every deliverable and move publication.
“Work faster” is not a plan. Present the cost, risk, and consequence of each option so the client can choose what to protect.
Review in layers
Each round answers one question:
- Script: are message, facts, and CTA correct?
- Rough cut: do structure, selection, and duration work?
- Fine cut: are graphics, sound, color, and subtitles correct?
- Final QC: do files, names, and formats match delivery?
Do not grade color while structure is open. Do not let final QC reopen the concept without recording a scope change.
Make waiting visible
Track production time, waiting for material, waiting for feedback, revision time, and work repeated because of late decisions.
When a video takes 18 days but spends 9 waiting for the client, hiring another editor will not fix the bottleneck.
Use the video brief as the intake gate, the complete production workflow for milestones, and the client communication guide to consolidate decisions.
A reliable schedule does not promise that nothing will change. It explains what happens when it does.