How to Plan an Editing Backlog Without Missing Client Delivery Dates

The quick answer

Estimate the remaining post-production hours for every open shoot, subtract work already completed, sort projects by promised delivery date and compare cumulative remaining hours with the editing capacity available by each deadline.

Backlog size alone is not enough

Forty hours of editing can be manageable if the first deadline is a month away and dangerous if two weddings are due next week. The queue needs both workload and time. A project should be evaluated in the context of all earlier deadlines because those projects consume the same editing capacity.

That is why the planner uses cumulative workload. A project due in fourteen days does not get fourteen days of capacity to itself when another project due in seven days must be finished first.

Estimate post-production from your own history

Break the work into components that match the studio’s process: ingest/culling, editing, album or export work and final delivery. Historical averages are stronger than generic online claims about “how long a wedding takes to edit.” Different shooting volume, style, outsourcing and client deliverables change the workload materially.

Update hours already completed rather than repeatedly lowering the original estimate. That preserves a useful record of how much work the project was expected to take and how much remains.

Protect capacity with a buffer

A photographer who enters forty theoretical editing hours per week and books exactly forty hours of work has no tolerance for a long shoot, urgent client communication, computer issue or personal interruption. A capacity buffer reduces the planned workload to a more realistic operating level.

For example, thirty weekly editing hours with a 15% buffer produces 25.5 effective planned hours. The buffer is an operating choice, not an industry standard.

Worked deadline example

Suppose the effective weekly capacity is 25.5 hours. Project A is due in seven days with six hours remaining. Project B is due in fourteen days with eighteen hours remaining. Project C is due in twenty-one days with thirty hours remaining.

• By day 7: cumulative work = 6 hours; capacity ≈ 25.5 hours.
• By day 14: cumulative work = 24 hours; capacity ≈ 51 hours.
• By day 21: cumulative work = 54 hours; capacity ≈ 76.5 hours.

All three fit under this simplified capacity model. If Project C had fifty-five remaining hours instead of thirty, cumulative work would reach 79 hours and the third deadline would be at risk.

What to do when the queue is at risk

A risk flag should trigger an operational decision before a client deadline is missed. Options include shifting internal admin, declining rush work, outsourcing an appropriate part of editing, rescheduling non-client work or communicating a revised delivery plan when the agreement allows it.

The point is not to work every available night. The point is to surface the mismatch while there is still time to act.

Connect capture decisions with the backlog

Wedding overtime creates downstream editing. If a timeline is likely to extend, use the Overtime & Associate Margin Planner to price the incremental workload and then add the expected extra editing hours to the backlog.