The Queue Math Behind Your Delivery Promise (And Why It Breaks Every October)

Your turnaround time is not a measure of how fast you edit. It is a measure of how many weddings are already in front of the one you just shot. Edit speed sets your capacity; queue depth sets your delivery date, and those two numbers only match when the queue is empty.

Which it is, in February. That is why almost every wedding studio quotes a turnaround it can genuinely hit in winter and then quietly misses it every autumn. The promise was not dishonest. It was calculated against an empty queue and then applied to a full one.

Here is the arithmetic, because the month it breaks is predictable long before it happens.

Why does editing faster barely help?

Because a backlog grows whenever work arrives faster than it is completed, and the gap compounds every month it persists. Speeding up the edit narrows the gap but does not close it, and anything short of closing it means the queue still grows, just more slowly.

This is the part that catches people out. Getting twenty percent faster feels like it should fix a delivery problem. It does not, because the problem is not the speed of any single edit. It is the accumulated difference between arrivals and completions across an entire season, and that difference only stops growing when your monthly capacity meets or exceeds your monthly intake.

The arithmetic on a real calendar

Take a studio shooting 25 weddings a year with roughly seventy percent of them falling between May and October, which is a normal northern hemisphere distribution.

• Peak season: about 17 weddings across 6 months, so roughly 2.9 arriving per month.
• Off season: about 8 weddings across 6 months, so roughly 1.3 arriving per month.
• Editing capacity: at 10 to 15 hours a wedding, someone editing alongside shooting weekends and running the business realistically completes about 2 a month.

Now run it forward. Through peak season, 2.9 arrive and 2 leave, so the queue grows by about 0.9 weddings every month. Across six months that is a backlog of roughly five and a half weddings.

Convert that to time, because that is what the couple experiences. Five and a half weddings at a completion rate of two a month is about two and a half to three months of queue. A studio that honestly quoted eight weeks in January is delivering at closer to nineteen or twenty weeks by October, without anything having gone wrong.

These are illustrative figures. Substitute your own volume, seasonal split and completion rate and the shape holds: if your peak arrival rate exceeds your completion rate at all, the backlog grows every month of the season and only unwinds in winter.

When exactly does the promise break?

It breaks when accumulated backlog exceeds the slack in your quoted turnaround, which usually lands two to three months into peak season rather than at the end of it.

Work it out for yourself with one calculation. Take your quoted turnaround in weeks, convert it to weddings using your completion rate, and that is the queue depth your promise can absorb. An eight week quote at two a month absorbs about four weddings. Then divide by your monthly backlog growth. At 0.9 a month, four weddings of slack is gone in a little over four months.

So a season starting in May puts you past your quoted turnaround somewhere in September, and the weddings that suffer most are the ones shot in August and September, which are also the ones whose couples are hearing from friends who booked in April and were delivered on time.

What are the three levers that actually work?

Only three things change the outcome: reduce the work per wedding, increase capacity during the months the queue is growing, or change what you promise. Everything else is a variation on working harder, which the arithmetic above already accounts for.

• Reduce work per wedding. Fewer deliverables, tighter runtimes, or handing off the mechanical stages. Culling and project prep is often the largest single block of time and the least creative, which makes it the first thing worth removing.
• Add capacity, but only where the queue is growing. This is the important qualifier. You need extra throughput for roughly six months a year, so any solution that costs the same in January as in September is solving the problem in the most expensive available way.
• Change the promise. Quote seasonally rather than annually, in the contract, at booking. This costs nothing and it is the lever almost nobody pulls deliberately.

Most studios end up using the third lever anyway, but accidentally and late, in the form of an apology email in November. Doing it on purpose in January is the same adjustment with none of the reputational cost.

How should turnaround be worded in a contract?

Quote a range that differs by season, state it at booking, and make the peak figure the one you can actually hit in your worst month rather than your best.

Something in the shape of: films from weddings between November and April are delivered within six to eight weeks; films from weddings between May and October are delivered within ten to fourteen weeks. Couples booking a September wedding are not surprised by a September timeline, and you have removed the single most common source of end-of-season conflict.

One further note that saves more goodwill than any of this. If you are going to be late, say so before the date passes, not after. A delivery that arrives two weeks after a warning reads as managed. The same delivery arriving two weeks after silence reads as forgotten.

Why outsourcing fits this shape specifically

The problem is seasonal by definition, so the useful solutions are the ones that can be switched on for six months and off for six. A per-project editing partner is elastic in exactly the direction the queue is: you send more in August and less in January, and you pay accordingly.

You also do not need to outsource everything to fix the arithmetic. You need to move roughly one wedding a month during peak, which in the example above is the entire difference between a queue that grows and one that holds flat. That is a far smaller intervention than most people assume they need, and it is why the first thing to hand off is usually the documentary edits and the culling rather than the hero film.

The bottom line

Turnaround is a queue problem, not a speed problem. If arrivals exceed completions during the season, the backlog grows every month regardless of how efficient any individual edit becomes, and the month your quoted date fails can be calculated in advance from three numbers you already have.

Run those numbers before next season rather than during it. Then pick your lever deliberately: less work per wedding, elastic capacity for the six months that need it, or an honest seasonal promise made at booking. Any of the three works. Discovering the arithmetic in October does not.