Setting a Review Turnaround Time You Can Actually Hit

Most brands tell creators review takes 48 hours. Most brands do not hit 48 hours, and the number was never derived from anything. It came from a contract template, or from what sounded reasonable in a kickoff call.

An unreliable commitment is worse than a slower reliable one, and not by a little. A creator told four days will plan for four days. A creator told two days and given five has a scheduling problem, a stacked posting calendar, and a reason to distrust the next thing you tell them. The cost of the gap between promise and reality lands almost entirely on the creator's side, which is why brands underrate it.

Here's how to set a number you can defend.

Decide what the clock measures

Before picking a duration, define the interval. Three candidates, and teams routinely promise one while measuring another.

Delivery to first decision. The creator gets a verdict: approved, or notes. This is the one to commit to. It's the only interval you fully control, and it's the one the creator's calendar depends on.

Delivery to final approval. Includes however many rounds happen, which depends on the creator's response time. Committing to this makes you liable for someone else's schedule.

Delivery to publish. Includes the posting window, which is a campaign decision.

Commit to first decision, and set a separate, shorter re-review clock: a resubmission that only changes what the notes asked for should come back faster than a fresh cut, because it should not be a full re-review. One business day is realistic when the process is working.

Say both numbers out loud in the brief. "First notes within 2 business days, revisions within 1" is a commitment a creator can actually plan against.

Set the number from your data, not your intent

Measure your last 50 reviews. You need two numbers.

Median. Half of reviews finish faster than this.

90th percentile. Nine in ten finish faster than this. This is the number your SLA should be built on, because the promise is only meaningful in the bad cases. Nobody remembers the fast ones.

Most teams find a median of a day and a p90 of six, which is exactly the shape that produces an unreliable 48-hour promise. The average is fine. The tail is what creators experience and talk about.

Two ways to use this:

• Publish something near your current p90 and hit it consistently. Unglamorous and immediately credible.
• Publish the number you want and fix the tail first. Legitimate, but do it in that order.

Write the conditions, because they're where it breaks

An SLA without stated conditions gets argued about the first time it matters. Four things to specify.

Business days and a timezone. A cut delivered 6pm Friday by a creator two timezones away is not late on Monday morning. Say so up front, in the brief, not in the reply.

When the clock starts. It starts when the cut arrives through your intake, and if it arrives as a DM to someone's personal account it hasn't arrived. This only works with one intake door; a promise measured from an unknown start time is not measurable.

Who owns it, and their backup. Most missed SLAs are one person on PTO with an unnamed backup. Ownership is the fix, and it needs deciding per failure type rather than by seniority, which is the whole argument for naming the owner explicitly.

What's excluded. Legal escalation, new claims requiring substantiation, or an entirely new concept versus the approved one. Name the exclusions in advance, keep the list short, and give excluded items their own commitment rather than letting them fall into an open-ended void.

Build the queue so the SLA survives a spike

A turnaround time that holds at 20 videos a week and collapses at 60 isn't an SLA, it's a description of a quiet month.

Reserve capacity for launches. If launch weeks are 3x normal volume, an SLA calibrated to the average will miss during exactly the weeks it matters most. Either flex the number for launch periods in advance, or hold back capacity.

Give priority a rule, not a requester. Every queue has queue-jumping. Make it a written rule tied to the posting date rather than to who asks loudest, otherwise priority is allocated by seniority and the quiet creator with tomorrow's posting slot waits behind next month's asset.

Decide what happens when you're going to miss. The failure mode isn't the miss, it's the silence. A same-day message saying "this needs legal, expect notes Thursday" costs you nothing and preserves the thing the SLA was protecting, which is the creator's ability to plan. An SLA is a communication commitment before it's a speed commitment.

Know the volume at which it stops working. If the number holds only at current volume, it has an expiry date. Work out where the ceiling is and what you'd change, which is the capacity question rather than the SLA question.

Track it where the creator feels it

Two metrics, weekly.

p90 time to first decision. Not the average. The average hides the cases that damage relationships.

Share of reviews inside the committed window. Your actual hit rate against the promise you published. If that's under 90%, the published number is wrong and should change, in either direction.

One more worth watching: time from your notes to the creator's resubmission. If that number is long, your notes are unclear, and the total elapsed time creators experience is being driven by feedback quality rather than review speed. Blaming that on the creator is a common mistake and usually wrong.

The takeaway

Commit to time-to-first-decision, with a separate faster clock for revisions. Set the number from your 90th percentile rather than your median, and publish something you hit consistently instead of something aspirational. Write down the business days, the clock start, the owner, and the exclusions. Reserve capacity for launch spikes, give priority a written rule, and message early when you're going to miss. A slower number you keep buys more trust than a fast one you don't.