Leave a handover someone can pick up.

Treat handover as a transfer of usable knowledge

In a study of data availability, Vines and colleagues requested datasets associated with 516 articles published between two and 22 years earlier. Among papers whose authors reported the status of their data, the odds that a dataset still existed fell by 17% for each additional year of article age. This was not a study of cell-culture handovers, and odds are not the same as the percentage of files lost. It nevertheless illustrates the fragility of relying on individuals to preserve research context indefinitely. ^[1]

Nature’s August 2026 reporting on leaving a laboratory highlighted early communication and documentation during the project, rather than a last-minute attempt to organise years of work. Those are useful habits even when the “departure” is just a long weekend: the transfer is easier if the current state already lives with the culture record. ^[2]

The framework below is a practical recommendation, not an experimentally validated handover intervention. Its test is operational: can the receiving researcher find the culture, explain the next task, access the relevant protocol, and recognise a situation that needs escalation?

Define the scope before listing the tasks

Covering one feed, looking after a culture for several days, and taking ownership of a project are different responsibilities. State which transfer you intend, when it begins and ends, and what stays with the original owner. For temporary cover, make the return of responsibility explicit rather than assuming that everyone remembers the arrangement.

The receiving person needs enough time, access and training to do the work. A schedule can assign a name without establishing any of those conditions. Confirm that the colleague can enter the relevant workspace, find the physical material, use the equipment, and access the approved procedure before you rely on the handover.

The OECD’s 2025 GIVIMP guidance includes roles and responsibilities, procedures, materials and records among its ten areas of in vitro practice. Its focus is regulatory safety assessment; it does not prescribe this particular handover format. For a research team, the useful principle is to manage responsibility alongside the scientific method rather than leaving it in a separate conversation. ^[3]

Build a brief that answers the next decision

Lead with the stable culture identifier, a readable name and the physical location. Then state the last relevant observation and its date, the next scheduled action, and the procedure to follow. An old image without a timestamp can be actively confusing; a recent observation linked to its original file gives the recipient something they can assess.

Keep detailed procedural instructions in the maintained protocol. The handover should point to the version actually in use and call out a documented deviation, not create a second unofficial protocol in a chat message. Where the next action depends on an observation, identify the protocol’s decision criteria and who should resolve an ambiguous result.

Separate readiness from intention. “Medium change tomorrow” may be scheduled, while the medium preparation is still unavailable. Name the prepared lot if one has been selected; otherwise make preparation or confirmation a visible dependency. Do the same for equipment access, pending test results, and materials that have not yet been located.

• Identity: culture or batch ID, readable name, location and the relevant vessels.
• Current state: dated observation, recent action and any unresolved concern.
• Next work: action, date or agreed window, governing protocol and dependencies.
• Responsibility: named recipient, scope, cover period and route for questions.
• Evidence: links to the culture history, relevant images, notes and material records.

Use acknowledgement to expose misunderstandings

A message sent is not the same as a handover understood. Ask the recipient to summarise the next action and any dependency in their own words. This need not become a formal ceremony: a short reply can reveal that the wrong culture, day or medium was assumed.

For a complex or unfamiliar culture, walk through one record together. Ask the receiver to locate the protocol and supporting image using their own access. That makes an inaccessible attachment or private folder visible before it becomes an interruption during the work.

Record any clarification beside the handover or culture record so that the correction does not exist only in a conversation. Acknowledgement does not remove the need to check the culture at the time of work; it establishes what was agreed, not what the biology will look like tomorrow.

Separate temporary cover from a permanent departure

For a permanent transfer, hand over more than the active schedule. Identify banked stocks, source records, raw data, analysis files, relevant approvals, outstanding questions, and work that should be stopped or archived. Agree who will answer later queries and where that agreement is recorded. Follow institutional decisions on ownership, access and retention rather than copying everything into a personal account.

The FAIR principles describe data that are findable, accessible, interoperable and reusable, with identifiers and informative metadata. Applying that idea locally means making a handover point to stable, interpretable records. It does not mean that confidential research material should become public, or that a shared folder alone makes the contents reusable. ^[4]

Check access from the recipient’s account, include a short index explaining the files, and retain the originals under the laboratory’s approved arrangements. Exported PDFs may help someone read a summary, but they should not be the only surviving copy of raw data or the only explanation of how an analysis was produced.

Make the handover useful after the task is finished

Close the loop with an outcome: what was done, when, by whom, and whether anything differed from the plan. If the task could not be completed, record that promptly with the reason and the next responsible person. The outgoing owner should not have to infer completion from the absence of a message.

Review recurring friction across several handovers. Are colleagues repeatedly asking where a flask is? Are materials unavailable at the scheduled time? Does the receiving person have to search private chats for the protocol? Each pattern points to information that should move into the maintained record.

A short team exercise is to select one current culture and have someone unfamiliar with it reconstruct the next action. Time spent finding the record, unresolved questions and missing access are useful improvement signals. Use the exercise to improve the system, not to reward beautifully written handovers that are difficult to act on.