The Unplugged Incubator: A Tabletop Rehearsal for Student-Led Labs

Student-led labs often inherit equipment, passwords, and a filing system whose logic has long since left the building. The result is a familiar asymmetry: the people most likely to be present when a freezer warms or a shared drive disappears are often the least likely to know which decisions are theirs to make. A tabletop drill addresses that gap without requiring a single hour of instrument downtime.

Why rehearse a failure you cannot prevent

Most lab safety training rehearses hazards to people. Continuity exercises rehearse hazards to work: samples, strains, datasets, and the records that make them intelligible later. The distinction matters. A freezer failure is not usually a safety emergency, but it can become a data-integrity problem within hours and a reproducibility problem within weeks.

A tabletop drill is not a checklist audit. An audit asks whether the backup freezer is labeled, whether the emergency contact list is current, and whether the inventory spreadsheet exists. A drill asks a different question: when the alarm sounds, who decides what, in what order, and with what record? Checklists verify state. Drills rehearse coordination under ambiguity. Student labs need both, but they tend to skip the second because it looks like theater. It is closer to practice.

The thirty-minute format

Schedule the exercise for a regular lab meeting and protect the full half hour. The structure is deliberately simple: five minutes to brief roles and ground rules, fifteen minutes to play the scenario, and ten minutes to debrief. The facilitator reads updates at fixed intervals and does not solve the problem. The incident lead may be a graduate student, a lab manager, or a rotating undergraduate coordinator. The point is to let someone practice the role before a real event assigns it by default.

Ground rules matter. No one leaves the room to check equipment. No one opens the inventory spreadsheet to settle a dispute. The drill is about decisions and documentation, not about whether a particular freezer is currently at temperature. If the team cannot answer a question from memory or from the posted materials in the room, that is a finding, not a failure.

A ready-to-run scenario

Tuesday, 9:10 a.m. The lab's minus 80 degrees Celsius freezer begins an intermittent alarm. A student notices the display and posts a message to the lab channel. The shared network drive is also unavailable because of scheduled maintenance that no one remembered. The lab has twelve boxes of student samples, two of which belong to a collaborator at another institution, and a manuscript revision due Friday.

At minute five, the facilitator injects a facilities update: the compressor is failing, and a service technician can arrive within four hours. At minute ten, the facilitator adds that the backup freezer in the adjacent room is at minus 65 degrees Celsius and contains space for approximately half the boxes. At minute thirteen, the facilitator notes that the collaborator has emailed asking for a sample status update. The team must decide what to move, who authorizes the move, what gets written down, and what gets communicated before the technician arrives.

The scenario is fictional, but the injects are ordinary. Real disruptions rarely arrive with complete information. The drill trains the team to act on partial information and to record the basis for its decisions.

Roles and decisions

Assign roles before the scenario begins. A compact set works for most student labs: facilitator, incident lead, equipment owner, data steward, communications lead, and scribe. The facilitator keeps time and reads injects. The incident lead sequences decisions and escalation. The equipment owner supplies service history and manufacturer guidance. The data steward tracks sample locations, priority, and backup status. The communications lead drafts messages to the principal investigator, collaborators, and campus safety. The scribe records decisions and open questions in a shared document.

The decisions checklist should be displayed, not memorized. Useful prompts include: Who confirms the alarm and rules out a door left ajar? Who authorizes moving samples, and to which unit? Which samples are irreplaceable, and which are replaceable? Who notifies the principal investigator, and within what window? What gets entered in the incident log, and by whom? Which message goes to the lab channel, and which stays private until verified? When does the team stop troubleshooting and call service?

These are decision prompts, not action items. The drill does not require anyone to move a box. It requires the team to say aloud who would move it, why, and how the move would be recorded.

The after-action template

The debrief should produce a short memo with five fields. First, assumptions we discovered: for example, that the backup freezer was assumed to be empty. Second, decisions we made with confidence: who owns the alarm response, who authorizes sample movement. Third, decisions we deferred: temporary storage for the collaborator's samples, notification thresholds for the principal investigator. Fourth, documentation that failed: the inventory was outdated, the emergency contact list was on a drive that was offline. Fifth, one change before next Tuesday: a named owner and a completion date.

Keep the memo in the lab handbook and revisit it at the next drill. A single change per exercise is enough. Teams that attempt a full continuity overhaul after a thirty-minute simulation usually produce a document no one reads. Teams that make one durable change per month build a system that survives turnover.

From exercise to habit

Student labs experience high turnover, which makes continuity a teaching problem as much as an infrastructure problem. Rotate the facilitator role so that more than one person has practiced reading the alarm, finding the inventory, and making a decision without waiting for permission. Repeat the drill quarterly, and vary the scenario: a CO2 incubator drift, a broken chain-of-custody log, a shared drive that returns from maintenance with missing folders. The equipment changes; the decision architecture does not.

The unplugged incubator is not a prediction. It is a rehearsal of the first ten minutes, when the lab is least certain and most likely to improvise. A short tabletop exercise will not prevent the next failure, but it can make the response legible, documented, and easier to hand over.