nanalLabs Blog

← Blog

Who's actually responsible for the lab notebook — the institution head, the PI, or the tech transfer office?

2026-09-15lab notebookmanagementregulation

Search "who is responsible for managing the research notebook" and most results stop at "a management officer must be appointed." What's left unclear is who that officer actually is — the principal investigator, the head of the institution, or an administrative office like a university's industry-academic cooperation foundation. The short answer: all four parties carry responsibility, but each at a different level. This post lays out the responsibility structure that the National R&D Research Note Guideline and multiple institutions' own research-note regulations consistently draw.

Four levels of responsibility

"Who manages the notebook" doesn't have a single answer. Across the guideline and institutional rules, the duty splits into four levels.

PartyLevel of responsibilityCore duty
Head of the research institutionInstitution-wide systemEstablish internal rules, train researchers
Principal investigatorProject-level operationOversee participants' writing and management compliance
Industry-academic cooperation foundation / research support officeAdministration outside the notebook itselfLedger, access control, storage and disposal
Individual researcher (the writer)Personal record-keepingWrite their own notebook, submit it when the project ends

These four levels aren't supposed to overlap — each has to cover its own piece for a single notebook's evidentiary weight to hold together. If any one level is missing, the other three doing their part perfectly still doesn't close the chain.

Head of the institution — the duty to write the rules sits here

This is the point most often misunderstood. The person who actually writes the notebook is the researcher, but the duty to write the rules themselves belongs to the head of the research institution. The National R&D Research Note Guideline requires the institution head to establish and operate internal regulations — built on the guideline but adapted to the institution's own circumstances — that spell out detailed standards for writing and managing notebooks, and to train the institution's researchers on them. It also requires that, before setting criteria to exclude certain projects from the notebook requirement based on their nature, the institution consult with the relevant specialized agency (or, absent one, the responsible central government agency) — meaning the head can't unilaterally widen the exemption.

In other words, "our lab just doesn't have its own research-note regulation" is, by itself, already a guideline violation. However meticulous an individual researcher's notebook is, if the institution has no internal regulation and no training record, an audit will flag "there was no system" before it ever gets to an individual researcher's sloppy entries.

The principal investigator — the person who actually enforces it at the project level

Turning the institution's rules into practice on an actual project falls to the principal investigator. The lead institution and PI are required to faithfully carry out notebook writing and management duties, which in practice means checking whether participating researchers are actually recording on schedule and whether reviewer signatures are keeping pace (see our post on signature intervals) over the course of running the project. If a PI's attitude is "the notebook is each researcher's own business," the resulting finding isn't pinned on an individual researcher — it's assessed as management failure across the whole project.

The industry-academic cooperation foundation — proving the notebook from outside it

The industry-academic cooperation foundation (or, at a company, the research support office) is required to keep records — in a management ledger — covering everything needed to manage stored notebooks: access, copy issuance, retrieval, and disposal. This role isn't about the notebook's content — it's about proving the notebook's history, which connects directly to what we covered in what actually belongs in the management ledger. When a project ends or a researcher leaves it, the notebooks they wrote have to be submitted to this office — and it's the one running that submission and storage process.

The individual researcher — the smallest duty, and the one most often cited

Even when the other three levels build and run the system properly, the actual writing is the researcher's own job. Entries have to record objective facts accurately and in detail, without forgery or alteration, at a level of detail a third party could later reproduce the work from. Most of what actually gets flagged in an audit happens at this level — gaps in the record, missing signatures, incorrect correction methods (see our post on how to make corrections) — though tracing the root cause often leads back up to a failure at a higher level: missing training, or an unchecked approval process.

What actually happens when there's no internal regulation

The patterns that keep showing up in audits and evaluations tend to look like this.

formality copy-pasted from the guideline with the institution's name swapped in → flagged as the institution head's responsibility

ever trained on it → "we didn't know the rule" shouldn't hold up as a defense, yet training gaps like this are common in practice

were actually writing their notebooks → flagged as project-level management failure

the credibility of notebook custody itself

were ever retrieved or submitted → can escalate into a dispute over where the original document even is

These five failures sit at five different levels. But audit reports routinely lump them into one line — "notebook management deficiencies." Without separating out which level actually owns each failure, the response tends to land on individual researchers while the institution head, who should be the one rewriting the regulation, goes untouched.

What to check right now

circumstances, rather than a copy of the guideline?

attendees?

status?

foundation or research support office?

there a record that the specialized or central government agency was consulted?

Exact procedures and provisions vary by institution and project, so check the guideline's original text and your own institution's regulation before applying any of this.

nanalStamp — automatically seals your Obsidian notes the moment they settle and anchors the proof into Bitcoin, so anyone can verify your records are tamper-free. About the service · 75 free record kits