nanalLabs Blog

← Blog

How to keep a lab notebook — in the form the regulations recognize

2026-08-15research-notesguideregulation

Search for "how to write a lab notebook" and you find plenty of example fields — but rarely where those requirements come from. This post collects the format Korean university research offices commonly teach, with links to the underlying sources.

What each entry must contain

Synthesizing university and industry-liaison guidance (for example, KAIST's newsletter summary):

FieldWhat goes inCommon deduction
Project nameWhich project this belongs toMixing projects in one stream
Entry dateThat day's dateBatch-writing with backdated entries
Experiment title & purposeWhat and whyData with no stated aim
MethodReproducible procedure"As usual"
ResultsOutcome and interpretation — success or failureNot recording failed experiments
Author & reviewer signature/dateWho wrote, who checkedCollecting reviewer signatures in bulk, later

A failure is still "an experiment performed, and its interpretation" — it belongs in the record. Practical details such as signatures and blank-space handling are frequently discussed in researcher communities.

When, and in what order

The core principle: don't jot now and transcribe later. Write directly into the notebook during or immediately after the experiment, in time order; pasting in memo slips is cited as improper. The KAIST summary and guides such as Yonsei's research-ethics pages teach the same — only immediate, chronological entry can later answer "when was this actually written?"

Corrections don't erase — the method is prescribed

These are summaries of guidance; details vary by institution and project. Check the National R&D Research Note Directive (in Korean) and your institution's rules before relying on them.

Electronic notebooks — the same goals, automated

Every rule above serves one purpose: making after-the-fact fabrication impossible. What paper enforces by hand (immediate entry, chronology, visible corrections), electronic systems enforce automatically — automatic timestamps, preserved edit history, tamper detection. For example:

Automatically recorded entry time, right after saving

An entry time and sequence number recorded the moment of saving (nanalStamp) — the "backdating" problem disappears structurally when the system writes the date instead of the hand. The electronic requirements are covered in the requirements post.

The mistakes to check for, one last time

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