Film Post-Production Time Estimator

Map footage, editing pace, and feedback loops into a usable schedule

Post-production is where a project finally reveals how much work was really captured on set. The shoot may be over, but the calendar pressure has only changed shape. Editors still need to screen footage, build assemblies, cut scenes, export versions, collect notes, revise, and wait for approvals. Producers usually know those tasks are coming; what they often do not know is how to turn them into a schedule that feels concrete enough to put on a production board. This calculator is meant to answer that practical question. It takes the amount of footage you expect the editorial team to handle, combines it with the team's weekly throughput, then adds the delay created by formal review cycles. The output is a simple estimate in weeks, which makes it easier to talk about deadlines, staffing, and whether the requested finish date is realistic.

The estimate is intentionally compact. It does not try to model every craft department separately, and it does not pretend that a documentary, a narrative feature, and a commercial all move through exactly the same pipeline. Instead, it gives you a planning baseline. If the result already looks too long for your release target, you know early that you need a faster pace, fewer rounds of notes, shorter approval delays, or a narrower scope. If the estimate looks comfortable, you can then add buffers for sound, color, visual effects, captions, deliverables, festival requirements, or any client-specific approval steps that sit outside the calculator. In other words, the result is not the last word on your schedule; it is the first disciplined draft of it.

What each input means in real editorial terms

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 formula works

The math behind this page is straightforward, which is part of its value. First, the calculator estimates how many weeks the editing stage takes by dividing footage hours by editing pace. Then it converts that editing time into days so it can add review delay in the same unit. Finally, it converts the total back into weeks for a clean headline result. Written directly in weeks, the model is:

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 tells you how long the actual edit takes if the team works at a steady pace. The second term adds the waiting time created by approvals. That means the result grows in two different ways: more footage or a slower pace increases the editorial portion, while more feedback rounds or slower responses increase the delay portion. If you double the pace, the editing share of the schedule is cut in half. If you add one more review cycle, the total grows by exactly one more turnaround block.

For readers who like to connect a practical estimator to a more general mathematical model, the calculator is still an example of a function built from multiple inputs. In abstract form, the result depends on several variables acting together:

And many planning tools can also be described as a total assembled from several weighted contributions:

That abstract view is useful when you want to explain the estimate to a team. It reminds everyone that schedule length is not caused by one magical factor. It is the sum of workload, throughput, and delay. When a finish date moves, you can ask which of those pieces changed rather than treating the shift as a mystery.

Worked example

Suppose you are planning a small independent feature with 60 hours of footage to sort and cut. Your editor can reliably process about 10 hours of footage per week. You expect 3 review cycles, and each round of notes usually takes 4 days to come back once a cut has been shared. The editing portion is 60 ÷ 10 = 6 weeks. The review delay is 3 × 4 = 12 days, which is about 1.7 weeks. Add those together and the estimate becomes about 7.7 weeks.

That number does not mean the film is magically complete in 7.7 weeks. It means that, under the assumptions you entered, editorial plus note turnaround will likely occupy that much time. If your distributor wants a locked picture in seven weeks, the example tells you that you are already close to the edge before adding any contingency. You could respond in several sensible ways: increase editorial capacity, tighten the review chain, reduce turnaround days by scheduling approvals in advance, or formally add a buffer to the schedule so the final date is not supported by wishful thinking alone.

Scenario comparison

Planning becomes more useful when you compare several realistic cases instead of trusting a single number. The table below shows how different types of projects can land in very different schedule ranges even with modest changes in pace and review burden.

Notice what the table illustrates. The documentary-style case does not become long only because it has more footage. It also absorbs much more delay from repeated reviews. That is why this estimator is helpful in production meetings. It gives you a way to separate workload from approval drag and decide where intervention will matter most.

How to interpret the result without overpromising

When the calculator returns a number of weeks, read it as a planning estimate for editorial and feedback flow, not as a complete 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

This calculator 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.