# AI Video Project Timeline: The 7-Day Run, Stage by Stage

This ai video project timeline guide turns a delivery window into a plan: seven stages, five approval gates and a day-by-day view of the 7-day run from an approved brief. It also shows which delays genuinely move a launch date, and which ones never do.

## Why publish a timeline at all

A turnaround figure without stages is an anxiety generator. If nothing is expected until delivery day, every silent afternoon looks like a problem, and the client ends up chasing status instead of planning around it. Publishing the stages inverts that: each day has an expected artefact and an expected approver, so a delayed signature is visible the moment it happens rather than a week later.

The model below is deliberately unglamorous. It requires a written brief, one archive of assets, two early signatures, one consolidated feedback form and a final acceptance. That is the whole surface area of the client's time, and stating it upfront is what makes a seven-day window believable rather than decorative. The studio-side hand-offs are documented in the [AI video project timeline guide article](https://carlosvideo18.shop/blog/ai-video-project-timeline-guide), which carries the same schedule in long form with briefing templates.

## The seven stages of the project

**Intake.** The request lands with the outcome, the deadline and the budget owner. Intake decides one thing: is this a scoped project or still an idea? Ideas get a short discovery exchange before any date is promised.

**Brief.** Audience, platform, length, single message, call to action, assets, brand rules and the named approver per stage. From this point on, disputes are settled by reading the brief rather than re-litigating the request.

**Style frames.** Stills that fix palette, typography, character look, environment and camera language. Approving the look here costs minutes; discovering a problem with it in motion costs a regeneration, because a look problem cannot be graded away.

**Generation.** The locked frames drive the full pass. This is a quiet stage for the client by design, since input arriving mid-generation forces the stage before it to restart.

**Editorial review.** Rough cuts go out with one consolidated feedback form and a stated response window. Consolidation is what makes the schedule hold; notes arriving in drips reset the clock on every scene the clips share.

**Revisions.** Included revision rounds are applied across the set. One decision fixes every cut that shares the affected scene, which is why a single well-written response beats five short ones.

**Delivery.** Masters export in each agreed aspect ratio, captions where specified, project files at the top tier. Specs were confirmed at kick-off, so delivery is a hand-over rather than a negotiation.

## The seven-day run, day by day

* **Day 1, intake confirmation and brief lock.** Objectives, lengths, formats, asset pack and approval owners confirmed in writing. Nothing generates before this signature exists.
* **Day 2, script and storyboard.** Scenes broken out with timing and direction, so the brand approves words before images exist.
* **Day 3, style frames.** The look is produced from the brand book and returned for one approve-or-amend decision.
* **Day 4, generation pass one.** The full set renders against the locked frames. No client action is scheduled.
* **Day 5, editorial review.** Rough cuts arrive with a single consolidated feedback form and a named response window.
* **Day 6, revisions.** Notes are applied across the set, followed by a short confirmation pass that closes the round.
* **Day 7, final export and delivery.** Masters, aspect ratios and captions ship together in the agreed hand-over format.

If a stage is still open at the end of its day, the delay is reported that afternoon with a reissued estimate. Silent slippage is the failure mode this schedule is built to prevent.

## Approval gates and who signs them

| Gate | Artefact | Signer | Unlocks |
| --- | --- | --- | --- |
| G1 Brief lock | Written brief plus asset pack | Sponsor or marketing lead | Script work begins |
| G2 Script approval | Script and storyboard | Marketing lead | Generation planning |
| G3 Style approval | Style frames | Brand guardian | Full generation pass |
| G4 Review close | Rough cuts plus feedback form | Channel owner | Revision round starts |
| G5 Final acceptance | Master set in all agreed formats | Sponsor | Delivery declared complete |

Two operating rules keep the gates quick. One named person signs each gate, never a committee, and every signature carries a response window. A gate that misses its window is escalated to the sponsor the same afternoon instead of waiting for the next business day.

## What makes a schedule slip

**Late feedback.** Notes landing after the response window push revisions into the export window. The countermeasure is structural rather than polite: one form, one deadline, one responder, escalation if the window closes empty.

**An unclear brief.** When the message or the platform is left open, the studio guesses, and a guess rejected at review costs an entire stage. Rewriting the brief mid-run is the specific mechanism that turns seven days into eleven.

**Missing brand assets.** Fonts, logos, product imagery or screen recordings that arrive after generation begins restart the style stage. One archive delivered before day one closes removes the risk entirely.

**Scope added mid-run.** A new aspect ratio requested on day six is a change request, not a revision. Booking it as a follow-on run keeps the current delivery date intact and avoids charging the revision round with unplanned work.

## Risk register and mitigations

| Risk | Early signal | Mitigation | Owner |
| --- | --- | --- | --- |
| Feedback window missed | No response by midday of the review day | Escalate to sponsor and issue a same-day estimate | Channel owner |
| Brief changes after lock | New message or platform raised after day 2 | Log as a change request for the next run | Marketing lead |
| Asset pack incomplete | Fonts or logos absent at kick-off | Require one archive before day one closes | Brand guardian |
| Style rejected in motion | Amends requested on the rough cut | Re-approve still frames before regenerating | Brand guardian |
| Approver unavailable | Gate unanswered for half a day | Deputy named in the brief at kick-off | Sponsor |
| Scope added mid-run | Extra format requested on day six | Book a follow-on cycle, keep the delivery date | Sponsor |

## Planning backwards, and paying for the run

Take the launch date, subtract one day for internal circulation and one delivery day. What remains is the brief-lock deadline. If that date has already passed, the honest options are a smaller first batch or a revised launch date, not optimism. Budget questions belong in the same conversation: our [AI video production budget guide](https://carlosvideo18.shop/blog/ai-video-production-budget-guide) shows how a per-clip quote maps to a quarter, and the current tiers sit on the [pricing page](https://carlosvideo18.shop/pricing). A single 10 to 15 second clip starts at $94, 30 to 60 second or multi-scene work is $150, and a 60 plus second clip or a full package runs $250.

## FAQ

### How long does an AI video project take end to end?

Seven days from an approved brief, revisions included. The clock starts once the brief, asset pack and brand book are confirmed, not when the enquiry first arrives.

### What approval gates sit inside the 7-day run?

Five gates: brief lock, script approval, style approval, review close and final acceptance. Each has one named signer and a stated response window.

### What is included in the seven-day run?

Brief handling, script and storyboard, style frames, generation, editorial review, included revision rounds, and final export in every agreed aspect ratio.

### What can push the schedule off track?

Late feedback, an unclear brief and missing brand assets, in that order. A scope addition mid-run is a new item rather than a revision and belongs in the next cycle.

### What does the client actually do during the run?

Sign the brief and style gates, return one consolidated feedback form on the review day, and accept the final set. Generation days need no client input.

### How do you plan backwards from a fixed launch date?

Subtract one day for internal circulation and one delivery day from the launch date; the result is the brief-lock deadline. If that date has passed, shrink the first batch or move the launch.

## Lock the brief, hold the date

Write the brief, gather the asset pack, name an approver for each gate, and the seven-day window becomes a plan instead of a hope: [Order a custom AI video](https://www.CarlosVideo18.shop/order).