nanalLabs BlogSearch "research note management ledger" (연구노트 관리대장) in Korean and you mostly get a single blank template file. The columns are there, but nothing explains when to actually fill them in, or why the notebook itself isn't enough and a separate ledger is needed at all. The short answer: the ledger doesn't prove what's in the notebook — it proves the notebook's history. However complete the notebook is, if there's no record of when it was issued, who accessed it and when, or when it was returned or destroyed, the notebook's own credibility is shaky.
Why a ledger exists — proving the notebook from the outside
Korean R&D institutions (a university's industry-academic cooperation foundation, or a company's research support department) are required to keep records covering access, copy issuance, retrieval, and disposal for the research notebooks they hold. That duty traces back to the National R&D Research Note Guideline, a ministry directive, with each institution's own internal rules (an industry-academic cooperation foundation's research-note management regulation, for instance) spelling out the actual procedure. Templates and details differ by institution, so always check your own institution's rules alongside the guideline's original text.
The reason a separate ledger is needed is simple. The researcher writes the notebook itself. But the claim that "this notebook has sat untouched, unaltered, since it was written" can't be proven by the researcher's own entries — it takes an independent record kept by a third party (the management office) of who accessed it and when, how many copies went out, and where the original currently sits. In other words, a notebook's trustworthiness isn't built by the notebook alone — it takes the notebook and the ledger together.
What actually belongs in the ledger
Across multiple institutions' research-note management regulations, the ledger typically covers:
| Item | When it's logged | Why it matters |
|---|---|---|
| Control number (issued per project, researcher, or department) | At notebook issuance | Identifies which project/researcher it belongs to |
| Access level / authorized viewers | At notebook issuance | Fixes in advance who is allowed to see it |
| Access history (who, when, why) | Every time someone requests access | Makes access to non-public data traceable |
| Copy-issuance history | Whenever a copy is requested or issued | Tracks leak/loss paths separately from the original |
| Return history | When a researcher leaves, takes leave, or changes projects | Prevents an individual from walking off with the original |
| Disposal history (date, reason, approver) | After the retention period lapses | Proves disposal followed a process, not an arbitrary decision |
Three moments the ledger actually has to work
When access is requested. Many institutions allow exceptions to the usual access-level rule — a department head standing in during an emergency, or a colleague who took over someone's work while that person is away. It's precisely these exceptional accesses that need a "who, why, when" entry in the ledger; without it, there's no way to later explain how the access happened at all.
When a researcher leaves, takes leave, or changes projects. It's common practice to require handing back all notebooks and related materials, up to that point, to the principal investigator or the management office. If the return isn't logged in the ledger, a departed researcher can end up walking away with the original still in hand — which can later turn into a fight over where the original even is, in a patent dispute or a research-misconduct investigation.
When the retention period has lapsed and disposal is being considered. Research notebooks have a fixed retention period (see our retention period post for the specifics), and once that period passes, disposal still isn't the staff member's personal call — it has to go through an approval step, logged in the ledger. Without that record, there's no way to rebut the suspicion, during a patent dispute, that "inconvenient material was simply destroyed."
Paper vs. electronic notebooks — the ledger runs differently
- [ ] Paper notebooks: the ledger exists as a separate document (a
spreadsheet or a physical logbook) that staff update by hand — if the staff member changes or the ledger itself is lost, the entire history can break at once.
- [ ] Electronic notebooks: access, download, and edit logs can be captured
automatically by the system, leading to the assumption that a separate ledger isn't needed — but as long as that log's owner is still the same institution's own internal system, it doesn't fully answer the objection that an administrator could edit the log itself.
- [ ] Either way, the core question is the same — are access, return, and
disposal records kept by someone other than the researcher, in a form that can't be altered after the fact?
Anchoring a hash of the original into an external trusted authority lets the ledger's claim — "the original has been untouched since this point" — rest on outside evidence rather than an internal log. We covered the legal basis for this in Three things an electronic research notebook actually needs.
What to check right now
- [ ] Does a research-note management ledger actually exist at our
institution, or does only the template exist while nothing is actually run through it?
- [ ] Are access and copy-issuance requests logged immediately, or logged
in a batch after the fact?
- [ ] Is the return of notebooks from departed, on-leave, or
reassigned researchers tracked through the ledger?
- [ ] Does disposal of notebooks past their retention period go through
approval and get logged?
- [ ] What proves the ledger itself hasn't been tampered with?
Building a ledger is the easy part. Keeping it in a state that's visibly untouched after the fact is the hard part. Check the exact procedure against your own institution's rules and the original guideline.