Film Post-Production Time Estimator

Turn footage, edit pace, and note cycles into a film post-production timeline

Film post-production has two separate clocks: the time it takes to cut the footage and the time it spends waiting on notes. This calculator combines both so you can turn editorial workload into a timeline that is useful in real production meetings. Enter the amount of source material, how quickly the team can process it, how many formal review rounds you expect, and how long each response usually takes. The result is a planning estimate in weeks, which makes it easier to compare against release dates, client promises, and the next booking on the calendar.

The estimate is deliberately practical rather than cinematic. It does not pretend to know whether your project is a short branded piece, a documentary, or a feature film. What it does give you is a transparent baseline that shows how much of the schedule comes from active editing and how much comes from the pause between revisions. If the number already overshoots your deadline, you can react early by staffing up, reducing review layers, or narrowing the delivery scope. If the number looks comfortable, you can still add buffers for sound, color, VFX, captions, clearance, or any approval step outside the edit room.

What each input means in a film post-production schedule

Each input on this film post-production estimator corresponds to a real editorial choice, not a generic spreadsheet placeholder.

Footage Hours is the amount of source material the editor must meaningfully work through. That is not the same thing as final runtime. A 90-minute film can easily involve dozens of hours of takes, alternate performances, pickups, B-roll, interview selects, or multicam angles. If you are planning early, enter your best estimate of the usable source footage that still needs to be watched, sorted, and cut into shape. If an assistant editor will dramatically reduce the load before the lead editor starts making creative decisions, use the hours that truly reflect the editor's working pool rather than every minute the camera captured.

Editing Pace is the team's throughput measured as hours of footage handled per week. This is the number many people misunderstand. It is not asking how many hours the editor sits at a desk each week. It is asking how many hours of source material can be processed into progress during a typical week. Pace changes with genre and complexity. A tightly storyboarded branded shoot with short takes may move quickly. A vérité documentary with long interviews, transcription, and story discovery may move far more slowly. If you are unsure, start with a conservative pace. It is usually better to be pleasantly surprised by a faster edit than to promise a date that assumes perfect momentum every week.

Review Cycles represents how many formal rounds of feedback you expect after the cut starts circulating. Some teams use one internal round and one client round. Others go through several producer passes, network notes, legal review, and stakeholder approvals. Each cycle matters because even when the actual revision work is quick, the project can still sit idle while people watch cuts, gather comments, and decide what they want changed. This input is often where schedule optimism hides. Teams remember the time spent editing, but they underestimate the time spent waiting for responses.

Review Turnaround is the average delay per cycle, measured in days. Treat it as calendar time, not just working hours. If a client takes two business days to respond but a weekend usually lands in the middle, the schedule effect may feel closer to four calendar days than two. Including the real delay here makes the result much more useful. A project with a fast editorial team can still finish late if approvals move slowly, and that is exactly the kind of bottleneck this calculator is trying to expose.

If you need a quick rule for choosing numbers, use this simple checklist before you calculate:

• Base footage on what the editor must actually review, not the final running time.
• Choose a weekly pace that reflects the project's complexity, not an ideal week with no interruptions.
• Count real approval rounds, including stakeholder or client notes that reliably happen.
• Use turnaround in calendar days so weekends and waiting time are not accidentally ignored.

Those four decisions do more to improve the estimate than any amount of spreadsheet polish. Once the inputs are grounded in the way your team actually works, the result becomes far more trustworthy.

How the film post-production formula works

The film post-production formula keeps the estimate simple by separating the active edit from the waiting time between notes. First, it measures how many weeks the editing pass takes. Then it converts that work into days so the review delays can be added in the same unit. Finally, it converts the total back into weeks, which is the most useful headline figure for scheduling.

Here, F is footage hours, P is editing pace in footage-hours per week, R is the number of review cycles, and T is review turnaround in days. The first term grows when the workload is larger or the team cuts more slowly. The second term grows whenever the project needs more approvals or the notes take longer to return.

That structure reflects how post-production slips in practice. A project can run long because the edit itself expands, because notes arrive late, or because both things happen at once. Using the same formula for every case helps producers compare projects with different footage loads and different approval habits without turning the estimate into a mystery.

Worked example: a 60-hour indie feature with three review passes

Suppose an indie feature enters post with 60 hours of source footage. The editor can comfortably process about 10 hours of material per week, the team expects 3 review cycles, and each round of notes usually takes 4 days to return. The editing block is 60 ÷ 10 = 6 weeks. The review delay is 3 × 4 = 12 days, or about 1.7 weeks. Add them together and the estimated film post-production time is about 7.7 weeks.

That result is useful because it shows where the schedule is going. The editing share is six of those weeks, while note turnaround adds the rest. If the delivery date is shorter than that, the options are the same ones producers actually have: increase editorial capacity, shorten the approval chain, pre-book review sessions, or accept that the finish date needs a buffer.

Scenario comparison for branded shorts, features, and documentary edits

Comparing a few film post-production scenarios usually tells you more than staring at one estimate. The table below shows how a lean branded short, a feature baseline, and a documentary-heavy review process can land in very different week counts even when the formula stays the same.

The documentary-style case grows because both the footage load and the review drag are heavier. That is exactly why this estimator is useful in planning meetings: it separates the cost of more material from the cost of more approvals, so you can see whether you need faster cutting, fewer notes, or both.

How to interpret a film post-production estimate without overpromising

When the calculator returns weeks, treat the number as a picture-edit planning estimate rather than a full finishing schedule. If you still need a sound edit, mix, score, color grade, conform, subtitles, QC, or deliverables, those stages may belong in a separate schedule line. Many teams use this result as the backbone for picture editorial, then layer other departments on top. That keeps the math honest. It also helps you explain to stakeholders why a project can appear nearly edited while still needing significant finishing time.

A good habit is to run at least three versions of the estimate: conservative, baseline, and aggressive. In the conservative case, use a slower pace and slightly longer turnaround. In the aggressive case, assume faster approvals and a highly focused editorial team. If the three answers stay close together, your schedule is probably robust. If they spread apart dramatically, that tells you the project is sensitive to feedback delay or throughput assumptions, and you should communicate that risk clearly before locking delivery dates.

You should also translate decimal weeks into calendar reality. A result of 6.4 weeks is not just an abstract number. It means about six weeks and three days, and those days may cross weekends, holidays, or talent availability constraints. The closer you are to a release commitment, the more valuable it becomes to pair this estimate with a real calendar and a buffer. Many production managers add 10% to 25% contingency for re-cuts, additional notes, or simple human scheduling friction. The exact buffer depends on the project, but almost every project benefits from one.

Assumptions and limits for film post-production planning

This film post-production estimator assumes the editing pace stays roughly steady across the project. Real life is messier. Early assembly can move slowly while story structure is still emerging, then accelerate once the shape is clear, or the opposite can happen if later rounds involve difficult creative revisions. The model also treats review turnaround as an average. One round of notes may return overnight while another stalls for a week because an executive is traveling. That kind of variation is normal, so the estimate should be read as a centerline, not a promise of exact completion on a specific afternoon.

The tool also does not split post-production into separate departments. Picture editorial, assistant editor prep, sound design, music, color, VFX, legal review, archival clearances, and final delivery can overlap or cascade in ways this simple model does not capture. That is not a flaw so much as a design choice. A lightweight estimator is most useful when it keeps the first conversation simple: how much editorial work exists, how fast can we cut it, and how much time do note cycles add? Once those answers are visible, you can decide whether the project needs a deeper master schedule.

Finally, be careful with unit interpretation. If you accidentally enter weekly labor hours instead of footage-hours processed per week, or if you count turnaround as working days while everyone else schedules in calendar days, the result can look misleading even though the math is correct. The safest approach is to define each input with your team before you calculate. That quick alignment often prevents far more confusion than any later schedule revision.

Use the estimator as a conversation tool. It is especially strong in kickoff meetings, producer-editor handoffs, client expectation setting, and deadline negotiations. A shared estimate makes tradeoffs visible. If someone wants more review rounds, you can show the likely schedule effect. If someone wants the same deadline with more footage, you can show the pace increase or staffing change that would be required to keep the plan credible.