Search "electronic research notebook adoption" and most results are posts promoting one specific service. What's harder to find is an answer to the actual question a lab asks: "we're still on paper — what should decide which system we move to, and what tends to get missed during the switch?" This post covers the system types, the legal requirements to check before adopting one, the real migration steps, and the mistakes that keep coming up.
Why move to an electronic notebook now
Paper research notebooks carry real operational overhead — daily handwriting and on-the-spot signatures — and in joint research with multiple researchers or institutions, having a single physical original slows down access and sharing. Loss or damage risk is also concentrated in one physical object (see research notebook loss and damage). An electronic notebook makes search, sharing, and backup easy, but if the system doesn't actually implement what Korea's national R&D research notebook guidelines require — signature authentication, automatic timestamping, tamper evidence — it ends up as weaker evidence than paper (see electronic research notebook requirements). Adopting one is only worth doing if the tool actually meets those requirements — not just because it's more convenient.
What electronic research notebook systems exist
They fall into three broad categories.
| Type | Who it's for | Cost | Characteristics |
|---|---|---|---|
| IRIS (integrated national R&D support system) research notebook module | Institutions running government R&D projects | Free (government infrastructure) | Tied into government project administration, but awkward for private research or records unrelated to a funded project |
| In-house institutional system | Universities, government-funded research institutes, large corporate labs | High upfront build and maintenance cost | Fully customizable to internal policy and security rules, but needs dedicated development and operations staff |
| Commercial ELN (Electronic Lab Notebook) SaaS | SME-affiliated research institutes, startups, individual labs | Subscription (by seats/storage) | Fast to adopt and cheap upfront, but carries data-access risk if the vendor shuts down (see research notebook backup) |
If your lab runs government R&D projects, the IRIS research notebook system is the first thing to evaluate. Private corporate-affiliated research institutes that don't run funded projects aren't the target audience for that infrastructure, so they need to choose between an in-house build and commercial SaaS based on organization size and security requirements.
Four things to verify before adopting
Before the system's name or its UI, check whether it actually implements what the guidelines require.
- Recorder/reviewer signature authentication — is each entry
attributable to an individual login rather than a shared account?
- Automatic entry-time recording — does the system stamp the time
itself, rather than relying on a researcher typing in a date by hand?
- Permanent edit history — when content is corrected, does the prior
content and the fact that it was edited stay visible rather than being erased?
- Third-party verifiability — if the record is ever disputed later,
can it be checked independently from outside, rather than relying solely on the vendor's internal server logs?
A tool that doesn't cover these four — a shared Word document or a generic Notion workspace, for example — can look like an "electronic research notebook" on the surface without actually passing the guideline's requirements. It's worth getting written confirmation of all four from any candidate vendor during evaluation.
Migration steps — from paper to electronic
- Survey the current state — count researchers, list ongoing
projects (government and private), and inventory existing paper notebooks. Paper records tied to ongoing projects should not be discarded at the point of migration (see research notebook disposal) — keep the originals for their required retention period.
- Select a system — if government projects make up most of the
work, evaluate IRIS first; if private projects or in-house research dominate, compare an in-house build against SaaS options. Get written confirmation from the vendor on the four requirements above.
- Set a transition period — in practice, switching notebooks
mid-project causes less friction if ongoing work stays on the existing method through its natural completion point (a project or an experiment series), with the new tool applied to work that starts afterward.
- Update the ledger and signature workflow — moving to an
electronic notebook doesn't remove the obligation to maintain a management ledger (see research notebook management ledger). Fold the recorder/reviewer signature process into the system's own approval flow.
- Fold training and inspection into the rollout — errors cluster
right after a tool change. Train people on the new tool first, and add electronic-notebook items to the existing inspection process.
Common mistakes
- Moving to a generic document tool and calling it done — a shared
cloud folder or a general-purpose document editor rarely leaves a clear edit trail, which can make proving anything harder than it was on paper.
- Using a government-project system for private research — IRIS is
tied to national R&D administration, so it doesn't comfortably hold in-house research records unrelated to a funded project.
- Skipping inspection after adoption — switching tools doesn't help
if the actual habits (recording the same day, getting a reviewer's signature) don't follow; the requirements still aren't met.
- Not checking vendor-shutdown risk before signing — if you're using
commercial SaaS, confirm in the contract what format your data comes back in, and on what timeline, if the contract ends or the service shuts down.
Summary
Adopting an electronic research notebook isn't really about picking a system — it's about choosing how you'll satisfy four requirements: signature authentication, automatic timestamping, tamper evidence, and third-party verifiability. If you run government R&D, evaluate IRIS first; otherwise compare an in-house build against a commercial service using those same four criteria, sized to your organization and security needs. Migrate in stages with a transition period so ongoing projects aren't disrupted. For the detailed requirements and their legal basis, always check the original text of the National R&D Project Research Notebook Guidelines (Korean only).
nanalLabs Blog