Closing the Loop: A Twelve-Question Exit Protocol for Reproducible Lab Handovers

Laboratory reproducibility is usually treated as a technical problem: standardize the protocol, version the code, deposit the data. Those measures matter. Yet many reproducibility failures begin at a more human point—the day a student graduates, a postdoc rotates off a project, or a technician changes roles. The experiments remain in the freezer; the knowledge that made them interpretable leaves with the person.

A technical exit interview is a practical remedy. It is not the HR conversation about benefits and grievances. It is a structured, one-hour handover that captures the tacit knowledge a successor needs and links that knowledge to durable records: lab notebooks, data dictionaries, code repositories, and reagent inventories. In 2026, as more labs maintain shared electronic records, the exit interview can become a routine piece of reproducibility infrastructure rather than an afterthought.

Why Handover Is Reproducibility Infrastructure

Frozen code, orphaned samples, and undocumented shortcuts are not signs of personal failure. They are predictable consequences of distributed work. A student who spent two years optimizing an assay knows which reagent lot caused trouble, which step can be shortened, and which instrument setting is misleadingly labeled. None of that knowledge appears in a methods section. Without a handover process, the next researcher reconstructs it by trial and error—or does not reconstruct it at all.

Treating handover as infrastructure changes the question from whether a departing member is conscientious to whether the lab has a reliable system. The system should specify who conducts the interview, when it occurs, where the record is stored, and how a successor confirms access. A one-hour conversation cannot capture everything, but it can identify the artifacts and people that hold the rest.

The Twelve-Question Template

The interview should be scheduled at least two weeks before the member’s last day, while access to files and instruments is still active. The mentor or lab manager leads; the departing member answers; a successor attends when possible. The output is a shared document linked from the lab notebook index, not a private email thread.

1. Which project files, notebooks, and code repositories are yours, and what is the current state of each?
2. What runs, what is frozen, and what is known to be broken?
3. Which samples, reagents, or specimens require transfer, disposal, or continued storage, and where are they logged?
4. What data dictionaries, naming conventions, or metadata fields would a successor misunderstand without explanation?
5. Which experimental shortcuts or deviations from written protocols did you use, and why?
6. What decisions are pending, and which people or documents hold the context?
7. Which vendor contacts, instrument settings, or scheduling constraints remain undocumented?
8. What would you do in the first week if you were continuing this project?
9. Which results are trustworthy, provisional, or known to be flawed, and how should that status be recorded?
10. What safety, compliance, or training records require update before access changes?
11. Which artifacts should be archived, transferred, or deleted, and under what retention rule?
12. Who should be named as the point of contact for each remaining question, and for how long?

These questions are deliberately concrete. They ask for locations, states, and owners rather than general reflections. A departing member who cannot answer a question has still produced useful information: the gap becomes visible and can be assigned before departure.

A Lightweight Rubric for Archive Decisions

Not every handover artifact deserves permanent storage. Labs need a defensible way to decide what to keep, what to transfer, and what to discard after retention review. A simple rubric can be applied during the interview and reviewed by the lab manager.

Score each artifact from 0 to 2 on four criteria: reproducibility value, retention or compliance requirement, cost of reconstruction, and risk if lost. An artifact that scores 2 on risk or reconstruction cost should be archived with a named owner. An artifact with reproducibility value but no active use should be transferred to a project archive or data repository. Deletion should occur only after checking institutional retention rules and confirming that no pending publication, patent, or compliance obligation depends on the material.

The rubric is not meant to create paperwork. It is meant to prevent two opposite errors: keeping everything until storage becomes unmanageable, and discarding the one file that explains why a figure cannot be reproduced.

Making the Protocol Stick

A handover protocol succeeds only if it is routine. Add the exit interview to the lab calendar when a member announces a departure. Store the completed template with the project record and link it in the onboarding checklist for the successor. At the next lab meeting, ask the successor to confirm that they can locate the code, samples, and data dictionary named in the interview. If they cannot, the protocol has found a real gap while the departing member is still available to close it.

None of this replaces good record-keeping during a project. It does, however, recognize that reproducibility depends on transitions as much as on protocols. A lab that interviews its departing members is not being sentimental. It is treating knowledge transfer as part of the experimental record.