Block Time Utilization Explained: Adjusted vs. Raw

Block scheduling runs on a single number that almost everyone quotes and surprisingly few define the same way: block time utilization. Worse, there are two versions of it — raw and adjusted — that can describe the same surgeon's month very differently, and using the wrong one (or using either one in isolation) leads straight to bad, contentious allocation decisions. This guide explains both, works a concrete example, and lays out why utilization should inform OR-time decisions without dictating them.

What block time is and why centers use it

Block time is reserved OR capacity — a recurring slot (say, every Tuesday, 7:30 to 3:30) allocated to a surgeon or service. Blocks exist because they create predictability: surgeons can build clinic and patient schedules around guaranteed OR access, and the facility can staff and plan around a known pattern. The tradeoff is that reserved-but-unused capacity is expensive, which is exactly why utilization gets watched so closely.

Raw vs. adjusted utilization (a worked example)

The two definitions differ in what they count as "used":

• Raw utilization = operative (in-room) time ÷ allocated block time.
• Adjusted utilization = (operative time + turnover time, and often credit for cases that run past the block) ÷ allocated block time.

A worked example makes the gap obvious. Suppose a surgeon has an 8-hour (480-minute) block and performs cases totaling 330 minutes of in-room time, with 60 minutes of associated turnovers:

• Raw: 330 ÷ 480 = 69% — looks mediocre, like wasted capacity.
• Adjusted: (330 + 60) ÷ 480 = 81% — looks solid.

Same day, same surgeon, two very different stories. Adjusted utilization is usually the fairer basis for decisions because turnover is real, unavoidable time the block consumed — but you have to know which one you are quoting before you draw any conclusion.

The downsides of block scheduling

Blocks buy predictability, but they have well-known failure modes: access (a new or growing surgeon can't get time that is locked up in legacy blocks), hoarding (blocks held for status or convenience rather than need), and unfilled capacity (blocks that routinely go partly empty while cases wait elsewhere). Utilization is the lens that surfaces these problems — but only if it is read carefully.

Why utilization alone shouldn't drive allocation

Here is the principle most often violated: utilization is an input to an allocation decision, not the decision itself. A widely cited Anesthesiology study by Dexter and colleagues demonstrated that utilization alone is not an accurate metric for allocating OR block time to individual surgeons — especially those with lower caseloads — and recommended that allocations rest on broader criteria such as OR efficiency. The same work cautions that even substantial windows of utilization data may lack the statistical precision to reliably identify persistently low-utilization surgeons.

The takeaway: utilization tells you where to look, not what to do. Allocation decisions need utilization plus efficiency, access, case mix, and trend — applied with enough data to separate signal from noise. We get practical about acting on it in reclaiming underutilized block time.

Turning utilization data into block decisions with ORbit

Doing this well by hand is genuinely hard: computing adjusted utilization consistently, separating real underuse from a couple of light weeks, and viewing it by surgeon and service over a meaningful window. ORbit computes raw and adjusted block utilization on your real case data, holds consistent definitions, and shows the trend with enough history to tell persistent underuse from noise — median-based, facility-scoped, and broken out by surgeon and service line. It connects directly to lost-case scoring, so an unfilled block reads as the cases it could have held. For the broader metric picture, see the OR efficiency metrics that actually matter. To see your own utilization both ways, take a look at your own data.