What Actually Moves FCOT in 90 Days

First-Case Delays Are Rarely One Problem

When first cases start late, the instinct is to blame whichever department was last to be ready that morning. In practice, delayed starts are almost always a stack of small, independent delays: pre-op not started early enough, consent or labs incomplete, anesthesia not staged, surgeon arrival timing, equipment not confirmed the night before. Fixing one of these rarely moves the number by itself.

Weeks One Through Three: Get the Real Data

Before changing anything, track the actual delay reason for every late first case, not the reason written on the incident report, the real operational cause. Most programs are surprised by what is actually driving delays once they look at three weeks of real data instead of assumptions.

Weeks Four Through Eight: Fix the Top Two Causes Only

Pick the two causes responsible for the most delay minutes and fix only those first. Trying to fix everything at once dilutes accountability and makes it impossible to tell what actually worked.

Weeks Nine Through Twelve: Make It a Habit, Not a Project

The last phase is about making the new process the default, not a temporary push. That means daily visibility into the next day's readiness, not a monthly report reviewed after the fact.

What This Actually Looks Like

Using this approach, one health system moved first-case on-time starts from 67% to 79%, a 12-point improvement, within three months. The change was not a single fix. It was disciplined sequencing: real data first, two causes at a time, then operational habit. See how we approach FCOT and OR utilization work →