When Your OR Time Gets Disrupted in PGY-1: Verify Case-Log Protection

Your first year is supposed to put you in the room. Then the board changes. Cases cancel. An add-on steals your block. You get pulled for an emergency, and by afternoon you are back on the floor with nothing logged. That fear is not drama. Disrupted OR time in PGY-1 hits confidence fast and quietly erodes case-log targets before anyone notices.

Here is the fix. Do not wait for goodwill. Run a verification checklist now: confirm written protection, define what actually counts, audit weekly, manage schedule risk, escalate with data, and recover lost cases on purpose. This is the protocol I wish every intern ran in week two.

Why OR Disruption in PGY-1 Feels Personal (and How It Actually Threatens Case Logs)

It feels personal because your identity is still forming around being useful in the OR. When you are sent out, left unscrubbed, or bounced between services, it reads like a verdict on you. It is usually not. The system is messy.

Common causes I see on almost every busy service:

• Elective cancellations and late starts that cascade
• Add-ons assigned without continuity for the junior
• Service reshuffling mid-week
• Staffing gaps that push interns to floors or consults
• Emergent cases that pull you away from a planned primary or assist

The real threat is mechanical, not emotional. Case-log protection is not automatic. Programs talk about "exposure" and "team-based learning." Those phrases do not equal logged cases. What protects your log is coverage rules, assignment patterns, and minimum participation expectations, written, enforced, and checked against your actual schedule.

If you only show up and hope, you will spend months present and still thin on eligible cases. Presence is not participation. That gap is where PGY-1 logs die.

Step 1: Collect Proof That Your Program Has a Case-Log Protection Plan

Start with paper, not vibes.

Ask for the written policy. Email or message program leadership (chief, coordinator, PD as appropriate) and request:

1. Case-log expectations for PGY-1 by rotation
2. Protected rotations or OR blocks
3. Minimum participation / role expectations
4. Escalation pathway when OR time is disrupted

Save the reply. Screenshot it. File it.

Build your own audit trail the same week:

• Photos or PDFs of posted OR schedules
• Rotation calendars and block assignments
• Hand-off notes and emails that reassigned you off a case
• A simple running log: date, planned case, what happened, who decided

You are not being difficult. You are creating a comparison set: policy versus reality. Without that, every conversation becomes "I feel like I am not getting cases." Feelings lose. Documents win.

If leadership says "we protect junior OR time" but cannot point to a document, treat that as a yellow flag. Ask them to put the expectation in writing for your current rotation. Short. Specific. Dated.

Work this sequence in order. Skipping to escalation without documents wastes political capital.

Step 2: Know What "Protection" Means, Participation, Not Just Presence

Programs love soft language. Translate it into countable items.

For every case you care about, define:

• Is it eligible for logging under your system's rules?
• Your role: observer, assistant, critical steps, primary/performed
• Supervision level and whether that affects credit
• Whether the case actually happened with you scrubbed for the portions that count

Edge cases matter. I have watched interns assume a canceled case somehow still "counted toward experience." It does not. Clarify:

• Canceled cases: usually zero for the log
• Broken scrub / sent out before key portions: often partial or none, ask
• Delayed start that pushes you off service: may not count if you never scrub
• Pulled for emergencies mid-case: document what you did before you left
• Off-service for floor fires: presence on the team is not OR credit

Get the local rule set from whoever owns case logging (coordinator, education chief, ACGME/case-log admin contact). Write a one-page "what counts" cheat sheet for yourself. Update it once, then stop guessing.

Exact rules vary by program and logging system. Use the chart as a pressure test, not gospel: if your week is mostly "present but not scrubbed," your log will stall even if you lived in the OR hallway.

Step 3: Run Your Weekly Case-Log Audit (15 Minutes, Every Friday)

Friday. Fifteen minutes. Non-negotiable.

Template (copy into a note or spreadsheet):

1. Total eligible cases this week (by your local definition)
2. Your role on each (assist / critical steps / primary)
3. Subspecialty distribution (so you do not accidentally stack one niche and starve basics)
4. Gap versus prior 2-3 weeks (trend, not single bad day)
5. Disruptions: cancellations, pull-aways, unscrubbed presence
6. Action needed? Yes/No + who you will contact Monday

Red-flag threshold: if logged eligible cases fall below roughly 80% of what your rotation's expected pace implies for two weeks running, or a single week collapses without a make-up plan, trigger action. Do not wait for the mid-rotation evaluation.

Early detection beats heroic catch-up in month four.

In the pattern above, week 3 is the alarm. That is when you escalate, not after week 6 when the deficit is structural.

Step 4: Prevent the Next Disruption, Schedule Risk Management for PGY-1

You cannot control the whole board. You can control your approach to it.

Before high-volume days:

• Confirm first-case expectations the night before or at morning huddle: Are you scrubbed? On which room?
• Ask the senior or attending how add-ons are assigned and whether juniors stay with continuity cases
• Request predictable coverage on known heavy days (double rooms, long lists), not as a demand, as a plan: "Where should I be to protect PGY-1 case participation today?"

Build Plan B in advance:

• If you are pulled to an emergency, who re-slots you when you return?
• If a case shifts late and collides with clinic or floor duty, is there a designated make-up assist?
• Which attending or chief prefers a text versus a face-to-face ask for reassignment?

Write your Plan B as two lines in your phone notes. When the board explodes, you will not invent process under stress. You will execute the backup you already chose.

Control the controllable. Relinquish the rest without abandoning the log.

Step 5: Escalate the Right Way, A Script That Gets Answers

Escalation fails when it is emotional, vague, or late. Keep it calm and data-shaped.

Script structure:

1. What happened (dates, cases, role outcome, one minute)
2. What policy or expectation says (quote the written piece)
3. What you need changed (specific coverage or protected slot)
4. By when (this week / next block day)
5. Ask for confirmation in writing (email reply is enough)

Example tone: "On Tuesday and Thursday I was reassigned off two eligible assists after the board changed. Our rotation expectations list protected junior participation on X service. I am at 5 logged eligible cases versus an expected pace near 8. Can I be assigned to [specific room/attending/list] on Friday and Monday, and can we confirm that plan by email so I can track follow-through?"

Ladder:

1. Chief / attending on the rotation
2. Documented mismatch + request for immediate adjustment
3. Surgery chief / program logistics if unresolved
4. Program director / GME-facing confirmation of protection policy and written coverage plan
5. Track follow-through for 1-2 weeks

Do not skip rungs without cause. Do not skip documentation either. The ladder works because each step carries proof forward.

Step 6: Convert Lost OR Time Into Recoverable Case Opportunities

Lost time is recoverable if you stop scavenging randomly.

Prefer make-up mechanisms that map to logging eligibility:

• Additional assistant slots on the same service (fastest path, highest utility)
• Different day or attending alignment where juniors actually scrub
• Targeted case queues on known high-yield lists
• Structured simulation for fundamentals when live cases are scarce, skill yes, log credit often limited; use it as bridge, not substitute

Avoid the trap: chasing whatever is open without checking rotation expectations or logging rules. A random case that does not count, or pulls you off a service where your evaluations and expected case mix live, costs more than it returns.

Ask directly: "What is the make-up pathway when PGY-1 OR time is disrupted this block?" If none exists, propose one tied to a specific list and date, then get the yes in writing.

Prioritize low time-to-recover and high log utility. Simulation keeps skills alive; it rarely fixes a thin case log by itself.

When You Have Verified Protection: How to Build Confidence and Keep It

Once protection is real, policy in hand, weekly audit humming, escalation path clear, change how you score success.

Case count still matters. It is not the only metric. Track:

• Role progression (more critical steps over time)
• Consistency week to week, not heroic spikes
• Supervision quality and whether feedback is specific
• OR schedule stability on your protected blocks

Set a monthly check-in with yourself (and, when useful, a chief or mentor): fifteen minutes, same scorecard, same honesty. Protection erodes when services get busier and nobody is watching the junior board. Your job is to keep watching.

Update the bars monthly. If schedule stability or logged cases slip, rerun Steps 1-5. Do not wait for the annual review to discover the leak.

---

Key takeaways

• Do not assume OR time protection exists, verify in writing what "counts" toward case logs and how coverage works when disruptions happen.
• Run a weekly 15-minute case-log audit with clear thresholds; escalate early using a data-driven script and request confirmation in writing.

Do this next: Open a note titled "Case-Log Protection." Paste the Friday audit template. Request the written policy before your next OR day. Compare one week of your schedule to that policy. If they do not match, send the escalation script with dates and a concrete ask.

Reclaim the board on purpose. Your log, and your confidence, follow the system you verify, not the one you hope for.