A production schedule needs to account for active work and the dependencies between reviews. A producer may finish a storyboard while waiting for a test account, but cannot verify the recorded workflow without access. A delivery date becomes useful when the proposal states those assumptions and assigns the decisions to named people.
At 20cuts, we confirm the schedule with the project scope after reviewing the request. A preview gives the customer a concrete direction to assess before committing to full production. A launch date belongs in the initial request so the proposed work can account for it.
Identify what production needs before it can proceed
The fictional error-triage product Sift needs a video showing an engineer resolving a group and inspecting the next matching occurrence. The producer needs a test workspace, a reproducible fixture, and the documented reopening behavior. Brand files alone cannot answer whether the group reopens automatically.
The customer assigns a product expert to verify that behavior and a reviewer to consolidate feedback. Those roles can belong to the same person, but the schedule needs their availability. An unresolved product question can affect every later scene that depicts the rule.
The brief template records the intended audience, required example, and publication destination. It also identifies excluded topics so a review does not quietly expand the film into a product tour.
Plan around reviewable artifacts
| Stage | Artifact the customer can inspect | What must be settled before later work |
|---|---|---|
| Product verification | Recorded fixture and source notes | The shown rule and values are accurate. |
| Concept and sequence | Scene list with starting and resulting states | The example answers the intended question. |
| Visual development | Still frames and a representative motion test | The screens are accurate and readable. |
| Narration and audio | A read matched to the reviewed visuals, then a recorded take | Spoken claims match visible actions. |
| Final production | Encoded cut with captions and agreed variants | Timing, readability, and delivery files pass review. |
These stages describe dependencies, not fixed durations. A familiar interface might need little reconstruction, while a complex screen or an unresolved story may require more iteration. The producer estimates the work for the specific scope.
For Sift, the still review can catch an occurrence count that changes when the engineer clicks Resolve. That correction should happen before the wrong count appears in several animated scenes. The motion review can then check whether the later occurrence clearly causes reopening.
Separate work time from waiting time
An illustrative plan might reserve two review windows with a full business day for the customer to consolidate each response. Those windows are planning choices, not a promise that the production fits a certain number of days. They become meaningful only after the producer confirms availability and estimates the work between them.
If the customer returns notes after the agreed window, the producer checks the revised schedule rather than assuming the original delivery date still holds. The effect may depend on other booked work or external recording availability, so a delay does not always translate into the same number of days at the end.
The schedule also needs an owner for conflicts. Two reviewers asking for different explanations cannot both determine the next cut. Consolidated notes let the producer act on an approved direction.
Account for changes after visual review
A narration change can require a new take, different scene timing, and updated captions. A new product workflow can require additional research and rebuilt scenes. The agreement should distinguish those changes so the customer understands the effect on scope before authorizing more work.
Keeping editable sources and versioned review cuts helps the producer preserve approved material. It does not eliminate the need to inspect the revised render, particularly when a change affects the action that a spoken phrase describes.
Reduce scope when the deadline requires it
A shorter Sift cut could explain reopening without teaching assignment or alert configuration. That leaves a complete example with fewer dependencies. Dropping the result state or removing the product review would make the remaining demonstration harder to trust.
Alternate layouts can also require separate work. If the main film must launch first, the proposal can place a vertical version later, provided the customer agrees to that delivery schedule.
The final review uses the actual encoded files and checks every agreed destination. The confirmed schedule should leave time to correct an unreadable caption or inaccurate status before publication. A project request can include the deadline and the deliverables that must be ready for it.