Animation production schedule template for a 60 to 90 second piece
A 75 second animation takes about ten weeks in a small studio when the client approves on time. Below is the week-by-week plan, the approval gates where work stops until the client signs off, and the payment that falls due at each one.
The short answer
Plan ten weeks for a 60 to 90 second explainer or 3D product animation made by a team of 2 to 5. Two weeks for brief, script and styleframes, one for the animatic, three for blocking and animation, two for lighting and rendering, one for compositing and sound, and one for delivery and slack. Put a client approval gate after the script, the styleframes, the animatic, the animation pass and the final. Invoice a payment at the signed quote and at three of those gates.
The template below is for a piece with one client and one named approver. Change the weeks, keep the gates. For a general timeline on any creative job, see the creative project timeline template. For 3D scheduling with render maths, see how to schedule a CGI project.
Assumptions
This schedule fits a 75 second piece, 1920 by 1080, 25 fps, one character or product hero, one environment and a voiceover. That is 1,875 frames. If your piece is a 3D product film with no character, blocking and animation are shorter and rendering takes the weight. If it is 2D motion graphics, rendering shrinks and comp grows.
The schedule assumes the client reviews within two working days and gives one consolidated list of notes per round. If they take a week, the whole plan moves by a week per gate. Write that in the quote.
The week-by-week plan
| Week | Stage | What happens | Gate at end |
|---|---|---|---|
| 1 | Brief and script | Kickoff call, written brief, script draft with timings | Script approved |
| 2 | Styleframes | 3 to 4 styleframes: look, colour, type, one hero frame | Styleframes approved |
| 3 | Animatic | Storyboard cut to the voiceover, rough timing, temp music | Animatic approved |
| 4 | Blocking | Camera and key poses in rough, assets finished | Internal check |
| 5 | Animation | Full animation on all shots, playblast | Animation approved |
| 6 | Animation fixes | Round of notes on the playblast, timing locked | Picture lock |
| 7 | Lighting | Lighting and materials on every shot, test frames | Internal check |
| 8 | Rendering | Final frames on the farm or local machines | Internal check |
| 9 | Compositing and sound | Comp, grade, type, final mix | Final approved |
| 10 | Delivery | Master file, social cuts, source package, final invoice | Delivered |
The gates are the point. At each one, the studio stops work on the next stage until the client signs off in writing. An email reply saying "approved" is enough.
Why the gates sit where they do
Every gate closes a decision that is expensive to reopen.
- Script. Changing a sentence after the voiceover is recorded costs a new recording session.
- Styleframes. A new look after week 3 means rebuilding assets and re-lighting every shot.
- Animatic. This fixes timing and camera. Changing a shot length after animation starts means animating it again.
- Animation pass. Picture lock. After this, only fixes. A note that adds a shot is a change, not a revision.
- Final. Colour, type and sound. Small fixes only.
If you sign off nothing until the end, the client reviews the whole film once, sees something they did not expect, and asks for week 3 to be redone in week 9. The revision clause and the revision policy template cover how to write this into the contract.
Review rounds per gate
Write the rounds in the quote, per gate. A common set for this kind of piece:
| Gate | Rounds included |
|---|---|
| Script | 2 |
| Styleframes | 2 |
| Animatic | 2 |
| Animation pass | 1 |
| Final | 1, small fixes only |
Each round is one consolidated list from one named person. Put two working days for the client to review in the schedule. Those days belong to the client. If they use 6, the delivery date moves by 4.
Render time in the plan
Rendering is the stage that surprises small studios, because it looks like waiting. Do the maths in week 1. At 4 minutes per frame, 1,875 frames is 7,500 minutes, or 125 machine hours. On one workstation that is more than five days of nonstop rendering. Across five machines it is 25 hours, so one working day.
Then add a buffer for the re-render. Plan for at least one full re-render of the problem shots. Every frame count and time per frame in your schedule should come from a test frame, not from hope.
The milestone payment schedule
Tie each payment to an approval gate. The client controls when the invoice falls due by approving. A schedule that works for a 10 week job:
| Payment | Share | Falls due on |
|---|---|---|
| Deposit | 30% | Signed quote, before work starts |
| Second | 30% | Animatic approved (end of week 3) |
| Third | 30% | Animation pass approved (end of week 5) |
| Balance | 10% | Final approved, before master files are released |
On a 12,000 EUR job that is 3,600 EUR at signing, 3,600 EUR at the animatic, 3,600 EUR at the animation pass and 1,200 EUR on the final. Money comes in before the expensive weeks. The studio is not lending the client three months of salaries.
Hold the full-resolution master and source files until the balance is paid. Send a watermarked or low-resolution preview for final approval.
Two lines go in the quote. If a gate is not signed off within 10 working days after delivery, its invoice is due anyway. If an invoice is overdue, work pauses. Both are in the milestone payments guide, with other splits. For the price of the whole job, see how to price animation per second.
Freelancers in the schedule
A 75 second piece in a small studio often has a freelance voiceover, a sound designer and sometimes a rigger or a lighter. Put each in the table as their own row with their own deadline. Voiceover recorded before the animatic. Sound mix in week 9. A rigger delivers by the end of week 3, so blocking can start in week 4. Their delay is your delay, so give them a date, not "next week".
Common mistakes
- No gate after the animatic. The client sees timing for the first time at animation.
- Approvals by phone. Write it down the same day.
- Payments by date, not by gate. A late client then costs you.
- Render time guessed, not tested.
- Social cuts treated as free. Put the formats in the quote.
How to adapt it
Shorter piece, 30 seconds: compress to six weeks, keep the same gates. Longer piece, 3 minutes: split into sequences, run the gates per sequence and move to monthly invoices. Hard launch date: work backwards from it and count the client's review days first. If the plan does not fit, cut scope before you cut the gates.
Doing this in OIO
In OIO, each stage is a ticket on the client's project, with a due date and a checklist. The timeline view shows the ten weeks. The client views the project for free, with no seat, and their notes go on the ticket per round. Freelancers get a link to their own ticket with no account. Each payment is an invoice from the same project, in the client's currency. OIO does not detect that an invoice was paid. You mark it paid yourself.
Questions
How long does a 60 to 90 second animation take to produce?
About ten weeks for a small studio when the client approves within two working days. Late approvals add days gate by gate.
What should an animation production schedule include?
The stages from brief to delivery, a deadline per stage, client review days, approval gates, render time from a test frame and the freelancers' dates.
What is a typical milestone payment schedule for animation?
A 30, 30, 30, 10 split is common: signed quote, approved animatic, approved animation pass, approved final. Tie each payment to the approval, not to a date.
When should the client approve during an animation project?
After the script, the styleframes, the animatic, the animation pass and the final. Each of those decisions is expensive to reopen once the next stage starts.