Pharma 101 /Documentation Systems

ELN, LIMS & MBR academia to industry

Three connected systems that quietly run regulated industry — and that no one explains before a scientist's first week on the job.

Electronic Lab Notebook · ELN

Captures what you did

A controlled digital record of experiments and development work. Content can be flexible, but entries must remain attributable, traceable, and supported by an audit trail.

Laboratory Information Management System · LIMS

Organizes what was tested

A structured system for samples, tests, results, specifications, workflows, and laboratory records — often the system of record for QC data.

Master Batch Record · MBR

Defines what must happen

An approved, controlled template for producing a defined product at a defined scale. The executed version records what actually happened in a specific batch.

The mindset shift

Three systems, three jobs

If you are coming from an academic lab, you already have good habits: dating entries, writing things down, and preserving enough detail to explain your work. In regulated industry, those habits become part of a formal system that may support a filing, a batch disposition, or an inspection.

ELN, in one line

Where you document research and development — flexible content with controlled recording and traceability.

LIMS, in one line

Where you manage samples, tests, and results — structured laboratory data with controlled workflows.

MBR, in one line

Where approved manufacturing instructions live — the completed EBR records the batch execution.

Important distinction: These are common industry patterns, not universal product names. Some companies use different labels or combine ELN, LIMS, MES, and batch-record functionality in one platform. Your site's procedures and quality system are the authority.

Part 01 · Research record

The Electronic Lab Notebook

An ELN is a digital replacement for a paper notebook, built around data integrity and traceability. Entries, revisions, and signatures are associated with identified users and times. A correction is normally made through a controlled amendment or linked new entry rather than silently overwriting history.

Benchling LabArchives IDBS E-WorkBook Signals Notebook LIMS-integrated systems

Why it matters

In academia, a notebook is often primarily a personal record. In industry, it can become legal and regulatory evidence — an FDA, EMA, or other inspector may review the underlying data and its history. That is why an ELN controls identity, timestamps, revisions, signatures, permissions, and audit trails.

The ALCOA+ principles

The data-integrity expectations that an appropriately controlled ELN helps people follow:

A
Attributable
Tied to an identifiable person or system.
L
Legible
Readable and understandable throughout retention.
C
Contemporaneous
Recorded when the activity happens.
O
Original
The first record or a verified true copy.
A
Accurate
Correct, truthful, and supported by evidence.
+C
Complete
Includes relevant data, including failed or unexpected work.
+C
Consistent
Uses expected sequence, conventions, and date formats.
+E
Enduring
Survives for the required retention period.
+A
Available
Retrievable for review, inspection, or audit.

How it works day to day

01
Use a templateStandardized fields for the experiment or development activity.
02
Record in real timeMake contemporaneous entries instead of reconstructing work later.
03
Review or witnessA second person reviews critical work where the procedure requires it.
04
Preserve the historyRelevant edits, approvals, and signatures remain traceable in the audit trail.
Common transition mistakes: treating the ELN like a private scratchpad, backfilling from memory, bypassing required fields, or writing vague notes such as “ran the usual protocol.” If an entry is late, ask how to document it correctly.

Part 02 · Laboratory data system

The Laboratory Information Management System

A LIMS manages the operational flow of laboratory data: logging samples, assigning tests, recording results, checking them against specifications, and preserving the history of who did what and when. It is especially common in QC and analytical laboratories, where consistent sample and result handling matters as much as the test itself.

Sample login & chain of custody Test assignment Specifications & results COA generation Instrument integration

LIMS vs. ELN

An ELN is usually optimized for the context and narrative of research: why an experiment was run, what was observed, and how conclusions were reached. A LIMS is usually optimized for structured laboratory operations: which sample was tested, by which method, against which specification, and with what result. The same organization may use both, with integrations between them.

How it works day to day

01
Receive the sampleRegister identity, source, amount, storage, and chain-of-custody details.
02
Assign the workRoute the approved test method to an analyst or connected instrument.
03
Review the resultCompare the result with specifications and route exceptions through the quality process.
04
Release the recordApprove the data, preserve the audit trail, and generate reports or a certificate of analysis.
Common transition mistakes: treating a LIMS like a free-form notebook, entering results outside the controlled workflow, overlooking sample identity or status, or assuming an instrument connection removes the need for review. A LIMS manages the data; analysts and the quality system still determine whether the result is valid and fit for use.

Part 03 · Manufacturing document

The Master Batch Record

The MBR is an approved, controlled template for producing a particular product or process at a defined scale, using defined materials, equipment, parameters, and specifications. It is closer to a controlled manufacturing recipe than to a research notebook. The executed batch record (EBR) captures the instructions, observations, results, signatures, and comments for one actual batch.

MBR · the template

What should happen

Blank and approved before execution. Changes go through the site's document-control and change-control process.

EBR · the executed record

What actually happened

Completed for a specific batch, including actual values, checks, signatures, and any properly documented discrepancies.

What's inside an MBR

The exact sections vary by product, process, and quality system.

§1 IDENT
Batch identificationProduct name, batch number, batch size, dates, and document version.
§2 INPUTS
Materials and equipmentApproved materials, grades, quantities, lot numbers, and equipment IDs.
§3 METHOD
Step-by-step instructionsUnit operations such as media preparation, expansion, harvest, purification, or fill/finish.
§4 IPC
In-process controlsChecks such as pH, bioburden, cell count, pressure, or temperature with acceptance criteria.
§5 SIGN
Verification stepsOperator entries and second-person verification where required for critical steps.
§6 DEV
Deviation and commentsA controlled place to document something that did not follow the approved instruction.
§7 QA
Review and dispositionRecord review, reconciliation, investigation status, and QA batch disposition before release.

Who touches it, and when

Process Development
Drafts technical content during process development and tech transfer
QA / Document Control
Reviews and approves, or oversees approval of, the controlled template
Manufacturing
Executes the approved MBR and produces the EBR
QA
Reviews the completed EBR and makes or oversees batch disposition

When execution does not match the script

EVENT
Unexpected resultOut-of-range value, alarm, missed step, or other departure.
LOG
Document the deviationRecord what happened promptly and according to the procedure.
RCA
Assess and investigateDetermine product impact and root cause when required.
CAPA
Prevent recurrenceCAPA may be opened when the investigation identifies a systemic fix.
Common transition mistakes: treating an MBR like an informal protocol, assuming a faster step does not need documenting, asking an operator to “just fix” a typo, or confusing an MBR with an SOP. An SOP is generally reusable guidance; an MBR is tied to a defined product/process and manufacturing execution.

How they connect

One product lifecycle, three systems

Development work builds the process knowledge, laboratory systems structure the evidence, and manufacturing documentation locks the approved process into a repeatable execution.

R&D / Process Development

Uses the ELN

Experiments, optimization, characterization, and the evidence behind process decisions.

QC / Analytical Lab

Uses the LIMS

Sample identity, test execution, results, specifications, review, and laboratory data integrity.

GMP Manufacturing

Uses the MBR / EBR

Approved instructions, actual batch data, deviations, review, and controlled release decisions.

These systems are not always used in a single straight line, and they may be integrated into a broader MES or quality platform. An ELN or LIMS record does not automatically become an MBR or EBR; each controlled record still requires its own intended use, review, approval, and change control.

Reference

Glossary

ELNElectronic Lab Notebook — records experiments and development work.
MBRMaster Batch Record — the approved manufacturing template.
EBR / BRExecuted Batch Record — the completed record of an actual batch.
GxPUmbrella term for Good Practice standards such as GMP, GLP, and GCP.
ALCOA+Data-integrity principles covering attributable, legible, contemporaneous, original, accurate, and more.
CSVComputerized System Validation — evidence that a system is fit for its intended use.
21 CFR Part 11US FDA requirements for trustworthy electronic records and signatures.
QA / QCQuality Assurance oversees the system; Quality Control performs testing and related checks.
LIMSLaboratory Information Management System — manages samples, test results, workflows, and laboratory data; often integrates with an ELN.
DeviationA documented departure from an approved procedure, instruction, or expected result.
CAPACorrective and Preventive Action — a formal response when systemic action is needed.
Change controlFormal review and documentation of a proposed change to a controlled or validated item.
SOP / IPCStandard Operating Procedure / In-Process Control.

Before day one

Practical tips

  1. Assume every controlled record may be inspected years later and write for a reader without your context.
  2. Learn “template versus executed” instantly: MBR vs. EBR, protocol vs. report.
  3. Do not backfill or quietly alter an entry. Ask how a late entry or correction should be documented.
  4. Expect document control to take time; the review is part of keeping the process defensible.
  5. Ask whether the work is GMP-controlled or R&D/exploratory before choosing where to record it.

Sources & further reading

Start with the primary sources

These references explain the underlying expectations. Your site's approved procedures and quality system determine how they apply to a specific ELN, LIMS, MBR, or EBR.

Keep learning

The record is part of the product

ELNs preserve the evidence behind development decisions. MBRs and EBRs show that manufacturing happened as approved — or explain, through the quality system, why it did not.

Subscribe free