What is a laboratory execution system? How LES fits with LIMS and ELN

In many QC labs, the LIMS knows that a sample needs an assay, a loss on drying and a pH test, and it knows the specification limits for each. What it doesn't know is how the analyst actually performed the work. That part lives on a paper worksheet or a controlled spreadsheet: weights written by hand, balance IDs copied from a label, a standard's expiry date checked by eye, a calculation done on a calculator and then re-done by the reviewer.

A laboratory execution system (LES) is software designed for exactly that gap. This guide explains what an LES does, how it differs from and fits with LIMS and ELN, what guided execution looks like in practice, which labs get the most from it, and how to start.

What a laboratory execution system is

An LES guides an analyst through a laboratory procedure step by step and captures data as the work happens. Instead of a paper worksheet that records what someone says they did, the LES presents the method as a sequence of steps, collects each entry or instrument reading at the point it is generated, checks it against rules defined in the method, performs calculations, and records who did what and when.

The unit of work in an LES is the method execution: one analyst running one procedure, often on a set of samples, with all the supporting detail that a reviewer would otherwise reconstruct from paper. That includes reagent and standard lots, instrument identity and calibration status, intermediate values, and anything that went differently from plan.

LES vs. LIMS vs. ELN

The three categories overlap, and vendors don't always draw the lines in the same place. Some LIMS products include execution modules, and some ELNs support structured templates. Still, the core purposes are distinct.

Aspect	LIMS	LES	ELN
Primary purpose	Manage samples, tests, specifications, results and reporting across the lab	Enforce how a defined procedure is performed at the bench	Document experiments and research flexibly
Unit of work	Sample, batch, test	Method execution and its steps	Experiment or notebook entry
Structure	Highly structured master data and workflow	Highly structured, versioned procedures	Flexible, often free-form with optional templates
Typical users	Sample receiving, analysts, reviewers, QA, lab management	Bench analysts and first-line reviewers	Scientists in R&D and method development
Typical data	Reportable results, status, specifications, CoAs	Raw entries, instrument checks, reagent lots, calculations, exceptions	Observations, protocols, narrative, attachments
Best fit	Any lab that tracks samples and results	Routine, standardized methods, often in QC	Exploratory and development work

A practical way to think about it: the LIMS decides what needs to be tested and whether the result passes. The LES controls how the test is executed. The ELN records why a scientist tried something and what they learned.

What guided execution means in practice

"Guided execution" can sound abstract. At the bench it comes down to a set of concrete behaviors.

Versioned methods

Each method is defined once, reviewed and approved, and given a version. When the method changes, a new version is released and executions in progress keep the version they started with. Every result can be traced back to the exact procedure that produced it, which is difficult to demonstrate with photocopied worksheet templates.

Step-by-step instructions and enforced sequence

The analyst sees one step at a time, with the instruction, the data to capture and any acceptance criteria. Where the order matters, the system enforces it: the system suitability step must pass before sample injections are recorded, and the sample weight must be entered before the dilution calculation can run. Where order doesn't matter, the method can allow flexibility.

Instrument, reagent and standard checks

When a step uses a balance or pH meter, the LES can require the analyst to identify the instrument and then check that its calibration or daily verification is current. Reagents and reference standards can be checked for expiry and approval status before use. The check happens at the point of use rather than during review days later.

Calculations and limits evaluated at the bench

Calculations are defined in the method and run on the captured values, so the reviewer no longer needs to recalculate by hand. Limits can be evaluated immediately: a replicate RSD outside its criterion or a result outside specification is flagged while the analyst is still at the bench and the sample preparation is still available.

Exceptions captured in context

When something goes wrong, such as an out-of-limit value, an instrument that fails its check or a step that has to be repeated, the LES records it as an exception attached to that specific step, with the analyst's comment and the time it occurred. That context is valuable when the event later becomes a deviation or an OOS investigation.

Review by exception

Because the system has already enforced sequence, checked instruments and calculated results, the reviewer can concentrate on what the system flagged: exceptions, manual overrides, repeated steps and comments. Review by exception does not remove the reviewer's responsibility. It focuses attention where the risk is, while the full record stays available.

Audit trail

Every entry, change and signature is recorded with user, timestamp and, for changes, the previous value and a reason. Unlike corrections on paper, the audit trail is generated by the system rather than relying on the analyst to strike through and initial correctly.

The data-integrity motivation

Much of the interest in LES comes from data integrity expectations that regulators and auditors apply to laboratory records. These are commonly summarized as ALCOA+, a set of principles referenced in guidance from regulators and bodies such as the FDA, MHRA, WHO and PIC/S. Records should be:

• Attributable to the person who generated the data and the time it was recorded.
• Legible and permanent, readable throughout the retention period.
• Contemporaneous, recorded at the time the work is performed.
• Original, the first capture of the data or a verified true copy.
• Accurate, free from errors, with any corrections documented.

The "plus" adds complete, consistent, enduring and available: all data including repeats is retained, events are recorded in a consistent sequence, records last for their required retention period, and they can be retrieved for review and inspection.

Paper worksheets can meet these principles, but only through analyst discipline and reviewer vigilance. An LES moves several of them into the system's design: entries are attributed to the logged-in user, timestamps are automatic, instrument readings can be captured directly, and repeated steps can't quietly disappear. Software of this kind supports compliance with frameworks such as 21 CFR Part 11, EU GMP Annex 11, ISO/IEC 17025 and GLP, but it does not achieve compliance by itself. That still depends on validation, procedures, training and the lab's quality system.

Which labs benefit most, and which don't

An LES pays off where work is repetitive, standardized and documentation-heavy. It is a weaker fit where methods are fluid.

Strong candidates

• Routine QC labs running validated or compendial methods many times a week, such as pharmaceutical, food, cosmetics or chemical release testing.
• Labs with high training turnover or multiple shifts, where a guided procedure helps new analysts perform consistently and reduces dependence on tribal knowledge.
• Labs still on paper worksheets or controlled spreadsheets, especially where review cycles regularly find calculation errors, missing entries or incomplete instrument records.
• Multi-site organizations that want the same method executed the same way everywhere.

Weaker candidates

• Research and method development groups, where procedures change constantly and an ELN is the better tool.
• Very low-volume labs that run each method rarely, where the effort of designing and validating digital methods may outweigh the benefit.
• Methods dominated by a single instrument system, such as a chromatography data system that already controls sequence, calculations and audit trail. Here the job is often integration rather than guided execution.

How to start with an LES

The most common mistake is treating LES adoption as transcription: taking the existing paper worksheet and recreating it field by field on a screen. That produces an electronic form with the same gaps as the paper. Digitizing a method is a design exercise. A practical sequence looks like this:

1. Pick one pilot method. Choose a high-volume, stable method with a known pain point, such as recurring calculation errors, frequent review comments or instrument documentation gaps.
2. Observe how the method is really performed. Watch analysts run it, collect completed worksheets and read the reviewer comments. The SOP and the bench rarely match perfectly.
3. Redesign the method for guided execution. Decide which steps must be enforced in sequence, which values are captured versus calculated, where limits are checked, which instruments, reagents and standards must be verified, and what counts as an exception.
4. Define the integration boundary. Agree what comes from the LIMS (sample, test assignment, method version, specifications) and what goes back (reportable results, status, exceptions).
5. Build, test with analysts, then validate. Let the people who run the method try it before formal testing. Validation effort should be proportionate to the risk and intended use.
6. Run it, learn, then expand. Gather feedback from analysts and reviewers, adjust the method design, and use what you learned to build a template for the next methods.

Labs that are still on spreadsheets for sample tracking as well as worksheets may want to look at the broader picture first. Our article on moving from spreadsheets to a LIMS covers that transition.

Integrating an LES with your LIMS

In most labs the LES is not a standalone system. It sits between the LIMS and the bench, and the integration design determines whether the two feel like one workflow or two.

• Receiving work. The LIMS creates the sample and assigns the test. The LES receives that assignment with the sample ID, test, method version and applicable specifications, so the analyst never retypes identifiers.
• Returning results. When execution and first-level review are complete, the LES sends reportable results back to the LIMS against the right sample and test, along with status and any exception flags. Raw data and step-level detail typically stay in the LES, linked by reference.
• Master data ownership. Specifications, products and sample types normally belong to LIMS master data. The LES should read them rather than maintain a separate copy that can drift out of sync.
• Review and release. Decide where each level of review happens. A common split is step-level review in the LES and result approval, OOS handling and CoA generation in the LIMS.
• Identity and audit trail. Users should be the same people in both systems, with consistent identities and timestamps, so an auditor can follow a result from bench to certificate.

Where the LIMS has a supported API, this integration is usually straightforward. Where it doesn't, the design needs more care. Our article on extending versus replacing a LIMS discusses the risks of coupling to internal schemas, and laboratory integration covers the connections to instruments and other systems.

Where SpectraLIMS fits

SpectraLIMS builds laboratory execution and guided-procedure applications designed around a lab's own methods and integrated with its existing LIMS. To make early conversations concrete, we maintain a Laboratory Execution System accelerator: a working demonstration with a versioned method designer, guided step-by-step execution with calculations and limits, exception capture, review, audit trail and a simulated LIMS integration. It is a functional starting point for a project, not a finished or validated product, and it is a useful way to test a pilot method design before committing to a full build.

Frequently asked questions

What is the difference between an LES and a LIMS?

A LIMS manages the lab's work at the sample level: registration, test assignment, specifications, results, approval and reporting. An LES manages how an individual method is performed at the bench, step by step, capturing raw observations, instrument checks and calculations. In most labs the two work together, with the LIMS assigning the test and the LES returning the result.

Is an LES the same as an electronic lab notebook?

No. An ELN is designed for flexible documentation of experiments, typically in research and development. An LES enforces a predefined, versioned procedure for routine work, which suits QC and other environments where the method is fixed and the goal is consistent execution.

Does a laboratory execution system make a lab Part 11 compliant?

No software makes a lab compliant on its own. An LES can provide technical controls that support requirements such as 21 CFR Part 11 and EU GMP Annex 11, including audit trails, access control and electronic signatures. Compliance also depends on validation, procedures, training and the lab's quality system.

Which methods should be digitized first in an LES?

Start with a high-volume, stable method that is run often, has a known pain point such as recurring calculation or transcription errors, and uses instruments that are straightforward to check. A successful pilot on one such method teaches the lab more than a broad rollout planned on paper.