One Stores the Story; the Other Stores the Aliquot

Electronic lab notebook versus LIMS are two laboratory informatics categories that store different objects. An ELN stores the experiment story — design, execution, and the conclusion you wrote down. A LIMS stores aliquot and process state — which vial, which status, which procedure step. A vendor can ship both screens under one logo. That does not make the two records the same thing, and it does not turn a shared drive into either system.

Two Systems, Two Stored Objects

ASTM E1578 treats laboratory informatics as a landscape of tools, not a single product. The public scope lists LIMS, ELN, LES, LIS, SDMS, and CDS as distinct members of that landscape. The useful question in a demo is not “do you have digital lab software?” It is “which object does this screen persist?”

The audience is a lab lead being walked through both acronyms in one hour. The purpose of the split is to keep the story of a run from being confused with the state of a tube. If you cannot point to those two objects on the screens you are buying, you do not yet know what you were shown.

What an ELN Record Is Allowed to Prove

ASTM’s public origin note is the cleanest non-vendor sentence available: ELNs were created so scientists could document experimental design, execution, and conclusions electronically instead of in a paper notebook. That is prose about a run. It can be structured, templated, or messy. The record is still about what was planned, what was done, and what the author claimed afterward.

Secondary vendor pages say the same job in product language. IDBS describes an ELN as the place for experimental data and scientific observations, including unstructured notes that a repeated QC workflow would reject. Treat that as orientation, not as a ranking. An ELN entry can mention a sample ID. Mentioning a vial is not the same as owning that vial’s chain of custody.

What the notebook can prove, when it is complete, is that a named person recorded a dated method and result. What it cannot prove, by itself, is that aliquot A is still in box B at status “released.” If your dispute is “which experiment did we run on Thursday,” you want the story. If your dispute is “where is tube 14 and who last changed its status,” you want a different record.

What a LIMS Record Is Allowed to Prove

The same ASTM note says LIMS were originally created to manage laboratory operations and data, provide traceability for samples and equipment, and help ensure procedures are followed. That is aliquot and process state. The primary key is usually the sample, the lot, or the test request, not the paragraph the scientist wrote about why the method was interesting.

IDBS’s secondary contrast is consistent with that origin: LIMS handle structured processes, sample tracking, and workflow automation. High-throughput and QC labs live here because the same assay is supposed to happen the same way to the next tube. Discovery notes do not. A LIMS can attach a file or a result value. Attaching a PDF is not the same as storing the experimental argument that produced it.

What the LIMS can prove, when it is complete, is a state machine for the aliquot: registered, in test, reviewed, disposed. What it cannot prove, by itself, is why the scientist changed the buffer mid-run and what they thought that meant. Those sentences belong in the story record.

Overlap Does Not Collapse the Categories

ASTM’s note also warns that the division has softened as vendors added features to each category. That sentence is the information gain worth keeping: overlap is real, and it does not retire the origin jobs. A modern suite can show a notebook page and a sample tree in one browser window. You still have to ask which object each click commits.

Chooser blogs will tell you to pick ELN for R&D and LIMS for QC, or to buy both. Those are buying postures. This page is a definition. If a salesperson says the product “is a LIMS and an ELN,” ask them to open the aliquot status and the experiment narrative as two inspectable records. If they can only open a folder of instrument files, they showed you a repository, not either category.

Inventory software is a third job — stock, lots, and unopened catalog items — and it already has a selection page. Do not use this definition to choose inventory software. That work lives on the lab-inventory selection page. An ELN context comparison, not a LIMS definition, lives on the academic versus industry ELN page.

A File Store Is Not a Third LIMS

Team file storage keeps files, folders, and permissions. It does not assign aliquot status, and it does not write the experiment story unless someone pastes that story into a document by hand. After the two records are named, ZettaNote is one electronic laboratory notebook. ZettaFile is team file storage inside the same workspace. It is not a LIMS, and it should not be sold or described as one.

Software features can support documentation or access control. Software alone does not make a laboratory complete 21 CFR Part 11. Do not treat an ELN, a LIMS, or a drive as a finished compliance outcome. The takeaway is the stored object: one system keeps the story; the other keeps the aliquot. Buy the object you cannot reconstruct from a folder name.

Frequently Asked Questions

Can one product replace both an ELN and a LIMS?

Only if it actually stores both objects — experiment prose and aliquot state — and you can point to each. A shared brand name is not proof.

Is team file storage a LIMS?

No. A file store keeps files and permissions. A LIMS keeps aliquot and process state. ZettaFile is the former.