Handing off a research notebook — who gets what when a researcher changes

Search "research notebook handover" and you'll usually find a single, generic sentence: notebooks must be handed off when someone leaves or changes jobs. What people actually need to know comes after that — is the procedure different when a participating researcher leaves versus when the principal investigator changes, is there a specific form for the handoff, and can the person receiving the notebook keep using it. This post works through those questions using Korea's National R&D Research Note Guideline and university-level manuals as the basis. The guideline gets made concrete by each institution's own rules, so verify against the guideline text and your institution's or university's own policy before relying on any of this.

Three situations, three different procedures

A notebook handover isn't one procedure — who it goes to and how depends on who's changing and why.

• A participating researcher changes, resigns, or takes leave —

someone leaves the project partway through, or steps down or takes leave from their role. The rule is that their notebook materials go back to the principal investigator.

• The principal investigator resigns, moves on, or is replaced — the

person running the project changes. Here the PI submits all of the project's notebook materials to the administrative office (a university's tends to be its technology-transfer/industry-liaison office). Unlike a single researcher's handback, this moves the entire project's record at once.

• The project ends or is discontinued — this isn't really a handover

so much as a shift into retention, governed by its own 30-year retention principle.

All three share one thing: a notebook is not something an individual holds onto and passes along informally — it's a managed asset that must move through the administrative office. Leaving it in a personal drawer or personal cloud account and handing it off verbally isn't the procedure the guideline contemplates.

Handing it off isn't the end — reactivating a returned notebook

Here's the part people miss most often. A notebook returned to the administrative office doesn't just sit in a cabinet — a successor PI or researcher can go on to use it to continue the same line of research. But that isn't a matter of just pulling it back out; it typically goes through its own approval step, commonly something like a "notebook return/reuse request" submitted to the administrative office. The exact form name and approval chain vary by institution, so check your institution's notebook management manual for the actual attached forms.

In other words, handover splits into two separate steps: who it goes to, and whether the notebook can be reactivated afterward. Handle only the first and skip the second, and a successor researcher ends up able to read a predecessor's record but with no formal basis to keep writing in it.

Verifier and access rights don't transfer automatically

The verifier of a notebook is, by default, the principal investigator. A PI can designate a supervisor or another senior staff member as verifier instead, depending on the nature of the research — but that designation itself has to be revisited whenever the PI changes. A verifier a predecessor appointed doesn't automatically carry authority under a successor PI.

Access rights work the same way. The guideline doesn't fix who may view a notebook and under what scope — it leaves that to each R&D institution's own internal rules. So the answer to "who can see this notebook" differs by institution, and whether re-confirming that access scope at handover time is even part of the institution's own rules is something worth checking directly.

Paper and electronic notebooks fail differently

Where handovers actually break down differs between paper and electronic notebooks.

Most of an electronic notebook's risk comes from "access rights" and "history" living apart from the file itself. Copy just the file over and the handover looks complete on the surface — but if the history data or signature record proving who wrote or edited it, and when, doesn't move with it, there's no good answer later to "is this really the record as it stood at the time." That's the same integrity problem discussed in the requirements post.

It's also where an externally anchored sealing approach helps. When the integrity evidence for a record isn't tied to an internal company system or a specific person's account permissions, but instead sits somewhere a third party can verify independently — Bitcoin, a trusted timestamp — the fact that a record existed as-is at a given time survives regardless of whether the handover itself went smoothly.

A handover checklist

• When a participating researcher leaves, was the notebook returned and

confirmed by the PI — not just handed over verbally?

• When the PI changes, was the entire project's notebook set submitted to

the administrative office?

• Have you checked your institution's manual for the form and approval

needed before a successor can reuse a returned notebook?

• Was the verifier designation and access scope re-confirmed at the point

of handover?

• For electronic notebooks, does the signature/edit history (audit trail)

migrate along with the account access?

• Even if every person involved eventually changes, is there a way for a

third party to independently verify when the record itself was created?

That last item is the one handovers miss most often. However carefully you manage the paperwork and account access, if the only proof of timing is your institution's own word, both a successor and any outside party are left asking whether the record was really created when it claims to have been. Ownership itself — as opposed to handover — is a separate question this blog has covered elsewhere.