First Case On-Time Starts (FCOTS): The Complete Guide

First case on-time starts (FCOTS) is the percentage of a surgical day's first scheduled cases that begin on time. It is one of the most-watched numbers in perioperative operations, and for good reason: the first case is the only one that has the entire rest of the day to compound its mistakes. Start it late and the delay ripples through every case, turnover, and block behind it. This guide is a complete reference — how first case on-time starts is defined, how it's measured (and quietly gamed), what a "good" rate actually means, what delays cost in real dollars, and how to improve the number honestly.

It is also one of the most misreported metrics in the building — not usually out of bad faith, but because the definition is slippery and a generous one flatters everyone. Before you can improve first case on-time starts, you have to agree on what one is.

What is a first case on-time start?

A first case on-time start is exactly what it sounds like: the day's first scheduled case in a given room beginning at or before its scheduled time. FCOTS is reported as a percentage — first cases that started on time divided by total first cases — usually rolled up by day, service line, surgeon, and facility.

The reason it earns its own metric, separate from general start-time tracking, is leverage. Mid-day cases inherit the delays of everything before them, so a late afternoon case tells you as much about the morning as it does about that case. The first case starts from a clean slate. If it slips, that slip is owned entirely by the morning's readiness process — and it is the delay with the most runway to grow.

That isolation is what makes FCOTS such a clean diagnostic. It is the one start time in the day that is not contaminated by upstream events, so improving it is both measurable and attributable in a way that mid-day starts never quite are.

How FCOTS is measured (in-room vs. incision, and the grace-period debate)

Here is where two facilities can run the identical operating room and report wildly different numbers. The FCOTS percentage depends almost entirely on two definitional choices: what event marks the "start," and whether you allow a grace period.

The table below shows how the same first case can be "on time" or "late" depending purely on the definition:

Incision is a much higher bar than in-room: it includes anesthesia induction, positioning, prep, and drape, all of which can run long after the patient is physically in the room. Stack a grace period on top of a lenient start event and the reported rate climbs further. This is exactly where gaming happens — a program that measures in-room within a 10-minute grace period will post a number that looks excellent next to one that measures incision with no grace period at all.

When one published quality-improvement case study deliberately switched to measuring first case starts by incision time with no grace period, it found on-time performance of about 74 percent — exposing operational gaps that a more lenient definition had been masking. The number got "worse" overnight, because it finally got honest.

This sits inside a broader argument about which OR metrics are even worth trusting. In a 2020 British Journal of Surgery review, Charlesworth and Pandit argue that several routinely tracked theatre metrics are flawed and gameable, and that efficiency is better defined as completing the scheduled list within the allocated time without over- or under-runs. The lesson for FCOTS is direct: a metric you can flatter by adjusting its definition is a metric your team will, consciously or not, learn to flatter. We expand on that idea in our guide to the OR efficiency metrics that actually matter.

What counts as a good FCOTS rate?

The honest answer is that there is no single national benchmark — and you should be skeptical of anyone who quotes one as gospel, because without knowing their definition the number is meaningless.

What the literature gives you instead is a sense of range and of what sustained improvement looks like:

• A multi-service-line Six Sigma quality-improvement project moved first case on-time starts from a baseline of 49 percent to a peak of 92 percent, and — importantly — sustained around 78 percent after the initial push. The sustained number is the one to anchor on; peaks are easy, plateaus are hard.
• A pediatric OR QI project improved on-time starts from 62 percent to 77 percent while cutting weekly first-case delay minutes from roughly 198 to 133.
• The strict, no-grace-period case study mentioned above landed near 74 percent — measuring the hardest version of the metric.

Put those together and a reasonable internal target for most programs is 80 percent or higher on a clearly defined measure — with the understanding that a strict definition will read lower than a lenient one for the same underlying performance. The most useful comparison is not against another facility's number; it is against your own baseline, measured the same way every week.

Why first-case delays cascade through the whole day

The case for prioritizing FCOTS rests almost entirely on cascade. A first-case delay is rarely just that delay. It pushes the second case's start, which compresses or eliminates the planned turnover, which pressures the third case, and so on. By mid-afternoon the room is either running behind, burning overtime, or quietly dropping the last case — and the root cause was a readiness gap that morning.

Here is the cascade made concrete for a single room with four cases:

That compounding is why first-case starts so often show up as the highest-leverage intervention in OR efficiency work: it is the cheapest minute to save, because saving it saves every minute downstream of it too. It is also the most visible to surgeons and staff, which makes it a good place to build credibility before tackling messier levers like turnover or block utilization. If you are weighing where to start, we compare the two head-to-head in first-case delays vs. turnover time.

What first-case delays actually cost

Cascade is not just an operational annoyance; it has a dollar value. Operating room time costs roughly $37 per minute in a typical facility — and far more at high-cost academic centers — covering staff, supplies, and overhead. (We break this down in the real cost of one OR minute.)

At that rate, a recurring 20-minute first-case delay in a single room is roughly $740 of wasted, already-paid-for time per day. Sustained across a week and a year in just one room, that is six figures — from a problem that feels, day to day, like "just a few minutes." Multiply across rooms and FCOTS stops being a scorecard line and becomes a budget line. The downstream cancellations and overtime that late starts trigger only add to the total.

The most common delay owners

Improving first case on-time starts starts with diagnosis, not exhortation. "Everyone get here earlier" is not a plan. The delay owners generally cluster into four buckets:

• Patient readiness — late arrival, incomplete pre-op preparation, missing labs or consent, transport delays.
• Anesthesia — pre-op evaluation not complete, lines and blocks running long, induction delays.
• Facility and equipment — room not ready, instruments or implants not available, staffing gaps.
• Surgeon arrival — the surgeon not present and scrubbed at the scheduled time.

The relative size of these buckets varies by facility, but the literature points at one in particular. An integrative review of first-case start delays identified surgeon late arrival as a leading cause, and found that earlier surgeon arrival correlates with more on-time starts. That is a politically delicate finding, which is exactly why it has to be grounded in your own data rather than asserted. A delay-owner taxonomy that surgeons trust — because it is applied evenly and visibly — is worth more than any benchmark.

How to start measuring FCOTS honestly

If you are standing up FCOTS tracking, or cleaning up a number you no longer trust, four steps get you to an honest baseline:

1. Write down the definition. Pick your start event (in-room or incision) and your grace period (ideally zero, or small and explicit). Document it. Apply it everywhere. The definition matters more than the threshold.
2. Measure by surgeon and service line, not just facility. A facility average hides the distribution. Improvement happens at the surgeon and service-line level, where the conversation is specific.
3. Capture a delay reason on every late start. Structured, mandatory, blame-neutral. This is what turns a number into an action.
4. Trend against yourself. Watch your own line move week over week on a stable definition. Resist the urge to benchmark against facilities whose definitions you cannot see.

Common mistakes that quietly ruin the number

Even well-intentioned FCOTS programs undermine themselves in predictable ways:

• Quietly loosening the definition when the number looks bad, instead of fixing the process. The metric improves; nothing real changes.
• Reporting only a facility average, which hides the two surgeons or one service line where the actual problem lives.
• Using the mean instead of the median, so a single disastrous morning drags the whole number and hands skeptics a reason to dismiss it.
• Letting reason codes be optional or free-text, which decays into uselessness within weeks.

None of the fixes require software. But this is exactly the kind of measurement that is tedious to do by hand and easy to do consistently when it is automated — which is the gap general reviews of OR efficiency keep returning to: the data exists, but turning it into a reliable, trusted, surgeon-level signal is the hard part. Once you have an honest baseline, the interventions that actually move FCOTS have somewhere to aim.

How ORbit makes FCOTS honest and actionable

That reliable-signal problem is the part ORbit is built for. ORbit captures first case on-time starts on your real case data, holds a single consistent definition so the number stays honest, breaks it down by surgeon and service line, and tracks delay owners automatically — so the morning's readiness gaps surface as a chart instead of an argument. It is median-based, so one outlier morning never distorts the trend, and it ties late starts to their downstream cost so the stakes are visible. It also feeds the real-time day board, so a first case trending late surfaces while there is still time to recover it.

If FCOTS is the first lever you want to pull, the next step is simply seeing your own number, measured honestly, in one place.