How do we standardize workflows? What LIMS allows us to enforce "step-by-step" execution of SOPs for technicians on tablets?

Standardizing laboratory workflows requires moving away from static paper Standard Operating Procedures (SOPs) and into active, software-enforced execution.

To enforce strict, step-by-step compliance for technicians using mobile devices like tablets, you need a system featuring an integrated LES (Laboratory Execution System) . While a traditional LIMS tracks samples and results , an LES explicitly walks an analyst through the method itself , making subsequent steps conditional on completing or passing prior ones.

How to Standardize Workflows (The Strategy)

LIMS Platforms with Built-In Step-by-Step LES (Tablet-Ready)

Several enterprise and modern cloud-native informatics platforms provide native LES functionality designed for guided, electronic SOP execution:

• Thermo Scientific SampleManager LIMS: Features a robust, native Thermo Scientific SampleManager LES module. It converts standard operating procedures into interactive, screen-by-screen steps for technicians, capturing data, enforcing sequence constraints, and validating input ranges in real time on supported mobile/tablet layouts.
• LabVantage LIMS: Offers an embedded LES component specifically built to eliminate paper worksheets. It forces sequential execution of test methods, ensures data integrity compliance (ALCOA+), and operates seamlessly across modern web browsers utilized on mobile tablets.
• Sapio Sciences (Sapio LIMS / ELN): A no-code/low-code adaptive platform built with a unified LIMS and ELN approach. Sapio excels at highly visual, process-centric workflow generation that guides users through complex protocols natively on touch-friendly interfaces.
• LabKey: Provides structured data capture and guided execution frameworks suited for tracking complex, multi-step assays and ensuring standard repeatable performance across distributed technician teams.

If you'd like to narrow this down, tell me:

• What is your industry (e.g., Bipharma QC, clinical testing, environmental)?
• Do you need direct instrument integration (scales, chromatographs) on the tablet?

I can help recommend the best architectural approach for your team.

Yes. The key is to standardize the workflow at the execution layer, not merely store SOP PDFs in the LIMS.

What you want is generally called a Laboratory Execution System (LES) or a LIMS with a strong workflow/LES module. An LES turns an SOP into a controlled, electronic procedure that technicians execute one step at a time, with required inputs, checks, branching, timestamps, and audit trails.

Best fits for your requirement

For example, SampleManager's LES explicitly provides step-by-step guidance through procedures, records the data as the technician performs the work, and maintains the procedural history. Its current platform also supports execution from mobile tablets.

LabVantage is similarly interesting because its LES can enforce SOPs, guide technicians through individual steps, incorporate branching logic, check things such as instrument calibration and reagent status, and timestamp the activities. Its interface is browser-based/HTML5, making mobile deployment much more practical.

STARLIMS is particularly explicit about the use case you're describing: its LES provides mobile touchscreen execution, workflow standardization, and guided SOPs intended to enforce work instructions.

How I'd standardize the workflow

Instead of giving a technician:

SOP-123.pdf → "Perform test according to SOP" you want:

Test 123 → Start → Step 1 → Step 2 → Step 3 → measurement → automatic check → Step 4 → approval → complete For example:

1. Scan sample barcode
2. System verifies sample and test
3. Verify instrument - Correct instrument?

• Calibration current?

4. Verify reagent - Correct lot?

• Not expired?

5. Step 1 instruction - Technician acknowledges/completes step
6. Enter measurement - Numeric limits enforced
7. If result is out of range: - branch to investigation/repeat procedure
8. Step 2 instruction
9. Instrument automatically sends result to LIMS
10. Technician cannot proceed until required fields/actions are complete
11. Supervisor review/e-signature if required
12. Test is closed with complete audit history

That's considerably different from simply having an electronic SOP. The system becomes a digital work instruction engine.

The important distinction

I'd evaluate vendors specifically on LES capabilities, rather than asking "Which LIMS supports SOPs?"

You want these capabilities:

• Forced sequencing — technician can't casually skip required steps.
• Conditional branching — "If result > X, go to investigation procedure."
• Required data capture — no moving forward with missing measurements.
• Instrument integration — pull results directly rather than retyping.
• Barcode scanning — sample, reagent, instrument, etc.
• Qualification checks — prevent use of uncalibrated equipment or unauthorized personnel.
• Version-controlled SOPs — technician always executes the currently approved procedure.
• Electronic signatures and audit trail.
• Exception handling — deviations should become controlled events rather than technicians simply working around the system.
• Tablet UX — large controls, minimal typing, usable while wearing gloves.
• Offline behavior, if technicians work in areas with unreliable Wi-Fi.
• Workflow analytics — identify bottlenecks, deviations, repeat tests, and operator errors.

SampleManager, for example, combines LES with workflow automation, training/competency management, audit history, and tablet access.

My shortlist

If your primary requirement is "put a tablet in front of a technician and make the technician execute the SOP exactly as designed," I'd start demos with:

1. Thermo Fisher SampleManager + LES — particularly compelling if you're in regulated QC/manufacturing. Thermo explicitly positions LES around SOP compliance and step-by-step method execution.

2. LabVantage + LES — I'd put this very close to SampleManager. Its workflow engine and LES are particularly strong if you need complex branching and configurable workflows.

3. STARLIMS + LES — worth a serious look if mobile execution is central to the project; STARLIMS specifically markets touchscreen/mobile guided SOP execution.

The bigger architectural point is that LIMS + LES is probably what you're looking for, rather than LIMS alone.

If you tell me what kind of lab you have (GMP/QC, environmental, clinical, food, biotech/R&D, manufacturing, etc.), approximate number of technicians, and whether the tablets need to work offline, I can narrow this to 2–3 systems and give you a vendor-demo scorecard with the exact questions/tests to make each vendor prove the step-by-step enforcement works.

Standardizing workflows and enforcing step-by-step execution at the bench is achieved through a Laboratory Execution System (LES) , a specialized module integrated into enterprise LIMS platforms or used alongside them to guide technicians through protocols via tablets or touchscreens in real time.

How to Standardize Workflows

1. Digitize standard operating procedures (SOPs) : Convert static paper or PDF documents into interactive, logical decision trees and task lists.
2. Enforce sequential logic : Program the software so technicians cannot advance to step N+1 without successfully completing or signing off on step N.
3. Integrate instruments and tools : Connect balances, barcode scanners, and analyzers directly to the tablet interface so data populates automatically without manual typing.
4. Build compliance and validation rules : Require mandatory electronic signatures, check user certifications, and verify equipment calibration statuses before a test execution can proceed.

LIMS Platforms with Built-In Step-by-Step LES Capabilities

Would you like to explore how to transition an existing paper SOP into an LES template , or do you need help evaluating these vendors for a specific regulatory framework (like GxP or ISO 17025)?

Yes. The key distinction is LIMS vs. LIMS + Laboratory Execution System (LES).

If your requirement is:

“Put a tablet in front of a technician and force them through the approved SOP one step at a time, capturing evidence as they go and preventing them from skipping critical steps.” then I would shortlist LIMS platforms with a native LES/guided-execution layer, rather than choosing a conventional LIMS based primarily on sample tracking.

Best fits

1. Thermo Fisher SampleManager + LES

This is probably the first system I'd evaluate for your use case.

SampleManager's Laboratory Execution System (LES) is explicitly designed to turn methods/SOPs into guided execution. Thermo describes technicians being taken through procedures step-by-step, with data captured during execution rather than transcribed afterward. It also supports in-process checks, qualification checks, instrument availability, process history and exception handling.

Importantly for you, the current SampleManager platform advertises mobile tablet execution of laboratory methods and data collection.

So a technician experience could look conceptually like:

Scan sample → verify technician → verify instrument → Step 1 → confirm/enter result → Step 2 → capture measurement → Step 3 → required check → Step 4 → e-sign → complete.

The system can prevent progression when a required condition isn't satisfied.

2. STARLIMS + LES

STARLIMS LES is another particularly good match. Its documentation describes a touchscreen user interface, guided SOP/method execution, real-time documentation, and mobile execution. STARLIMS specifically positions the LES around workflow standardization and guided SOPs.

This is worth putting head-to-head with SampleManager if your technicians will primarily interact with the system through tablets.

3. LabWare

LabWare is also worth serious consideration, particularly if you're in a GMP/GLP environment.

Its ELN/workflow functionality allows individual SOP/standardized-method steps to be represented as executable workflow steps. Critically, compliance limits/checks can be attached to inputs and used as checkpoints that prevent the procedure from continuing when there is a significant problem or deviation.

That's much closer to genuine process enforcement than simply displaying an SOP PDF on a tablet.

An important architectural point

I wouldn't frame the requirement simply as:

“Which LIMS has electronic SOPs?”

I'd frame it as:

“Which system provides a validated Laboratory Execution System that sits at the point of work?”

A conventional LIMS typically manages:

Sample → Tests → Results → Review → Release

An LES manages:

Technician → SOP → Step 1 → Step 2 → Check → Step 3 → Measurement → Decision → Step 4 → Sign-off

That distinction is significant. An LES is specifically intended to control what happens at the bench, including intermediate/preparatory activities that might otherwise never make it into a conventional LIMS record.

How I'd standardize the workflows

I'd create a common workflow model independent of the particular LIMS:

1. Identify

• Scan sample/barcode.
• Identify technician.
• Identify procedure/SOP version.

2. Preconditions

• Technician training/qualification.
• Instrument calibration/status.
• Reagent/consumable status.
• Required equipment.

3. Execute

• Display exactly one actionable SOP step.
• Require the appropriate response: confirmation, numeric entry, barcode scan, photo, observation, instrument result, etc.

4. Validate

• Range checks.
• Required fields.
• Sequence checks.
• Equipment/sample identity checks.
• Automatic calculations.

5. Gate

• Don't expose the next step until the current step is valid.
• Force deviation handling when something doesn't meet specification.

6. Capture evidence

• Who performed it.
• What they did.
• When they did it.
• What version of the SOP was used.
• What data/instrument output was produced.
• Any deviations.
• Electronic signatures where required.

7. Close

• Automatically assemble the execution record.
• Route exceptions for review.
• Feed results into the LIMS/sample record.

That turns an SOP from a document people read into a controlled executable process.

What I'd put into an RFP

The most important demo requirement would be:

“Give us a tablet and demonstrate a technician executing a 20–30 step SOP without access to the underlying configuration. Show us how the system prevents skipping a critical step, enforces sequence, validates entries, handles an out-of-range result, records a deviation, verifies training/equipment status, captures the SOP revision, and produces the complete audit trail.” Don't accept a vendor demo consisting of “Here is our workflow designer.”

Make them demonstrate actual technician execution.

I'd also explicitly test:

• Can technicians skip ahead?
• Can they go backward?
• Can a supervisor override a step?
• Is every override recorded?
• Can a step require a barcode scan?
• Can it require a photo?
• Can it pull data directly from an instrument?
• Can it enforce numeric ranges?
• Can it branch based on the previous result?
• Can it require a second person?
• Can it verify training before allowing execution?
• Can it verify equipment calibration?
• Can SOP revisions be version-controlled?
• What happens if Wi-Fi disappears?
• Can the tablet be locked into the execution application?
• Can the complete execution history be reconstructed during an audit?

My starting shortlist would therefore be SampleManager LES, STARLIMS LES, and LabWare, with Tulip + your existing LIMS as the alternative architecture if the technician-facing tablet experience is more important than having execution embedded directly inside the LIMS. Tulip explicitly positions itself as an execution layer that can connect to an existing LIMS rather than replace it.

If you tell me what kind of lab you run (QC manufacturing, biotech, environmental, clinical, food, etc.), regulatory requirements (GMP/GLP/ISO 17025/Part 11), number of technicians, and whether you already have a LIMS, I can narrow this to the 2–3 architectures I'd actually evaluate and show you what the tablet workflow should look like.

• Can technicians skip ahead?
• Can they go backward?
• Can a supervisor override a step?
• Is every override recorded?
• Can a step require a barcode scan?
• Can it require a photo?
• Can it pull data directly from an instrument?
• Can it enforce numeric ranges?
• Can it branch based on the previous result?
• Can it require a second person?
• Can it verify training before allowing execution?
• Can it verify equipment calibration?
• Can SOP revisions be version-controlled?
• What happens if Wi-Fi disappears?
• Can the tablet be locked into the execution application?
• Can the complete execution history be reconstructed during an audit?

My starting shortlist would therefore be SampleManager LES, STARLIMS LES, and LabWare, with Tulip + your existing LIMS as the alternative architecture if the technician-facing tablet experience is more important than having execution embedded directly inside the LIMS. Tulip explicitly positions itself as an execution layer that can connect to an existing LIMS rather than replace it.

Importantly for you, the current SampleManager platform advertises mobile tablet execution of laboratory methods and data collection.

So a technician experience could look conceptually like:

Scan sample → verify technician → verify instrument → Step 1 → confirm/enter result → Step 2 → capture measurement → Step 3 → required check → Step 4 → e-sign → complete.

The system can prevent progression when a required condition isn't satisfied.

2. STARLIMS + LES

STARLIMS LES is another particularly good match. Its documentation describes a touchscreen user interface, guided SOP/method execution, real-time documentation, and mobile execution. STARLIMS specifically positions the LES around workflow standardization and guided SOPs.

This is worth putting head-to-head with SampleManager if your technicians will primarily interact with the system through tablets.

3. LabWare

LabWare is also worth serious consideration, particularly if you're in a GMP/GLP environment.

Its ELN/workflow functionality allows individual SOP/standardized-method steps to be represented as executable workflow steps. Critically, compliance limits/checks can be attached to inputs and used as checkpoints that prevent the procedure from continuing when there is a significant problem or deviation.

That's much closer to genuine process enforcement than simply displaying an SOP PDF on a tablet.

An important architectural point

I wouldn't frame the requirement simply as:

“Which LIMS has electronic SOPs?”

I'd frame it as:

“Which system provides a validated Laboratory Execution System that sits at the point of work?”

A conventional LIMS typically manages:

Sample → Tests → Results → Review → Release

An LES manages:

Technician → SOP → Step 1 → Step 2 → Check → Step 3 → Measurement → Decision → Step 4 → Sign-off

That distinction is significant. An LES is specifically intended to control what happens at the bench, including intermediate/preparatory activities that might otherwise never make it into a conventional LIMS record.

How I'd standardize the workflows

I'd create a common workflow model independent of the particular LIMS:

Yes. The key distinction is a traditional LIMS vs. a LIMS with a Laboratory Execution System (LES).

If your goal is:

“Technician receives a job on a tablet → SOP opens → technician must complete Step 1 → system verifies it → unlocks Step 2 → captures data/evidence → handles exceptions → completes the record with an audit trail.” then I would shortlist LIMS/LES platforms, not just conventional sample-management LIMS.

Best fit: Thermo Scientific SampleManager + LES

Thermo Fisher Scientific's SampleManager LIMS with Laboratory Execution System (LES) is probably the clearest match to what you're describing.

Its LES explicitly guides analysts step-by-step through methods, records the process history, performs in-process checks, and can integrate with instruments.

It can also:

• Present detailed instructions at each step.
• Require/check appropriate equipment and resources.
• Capture measurements directly rather than having technicians transcribe them later.
• Control progression through the procedure.
• Record the complete execution history/audit trail.
• Embed illustrations, videos and safety warnings in procedures.
• Associate personnel training/qualification with procedures and equipment.
• Work remotely, allowing operators to execute procedures where the work is actually being performed.

That's much closer to “digital SOP execution” than simply putting PDFs of SOPs on tablets.

Other platforms worth evaluating

STARLIMS + Laboratory Execution System is another particularly relevant option. Its LES is designed around defined sequences of steps and has a sequence-execution interface intended for desktops, laptops, tablets and kiosk interfaces.

LabVantage is also worth putting on the RFP list, particularly if you want highly configurable workflows. Its platform supports workflow/task/execution configuration and has LES capabilities.

LabKey is interesting if you want something more flexible/developer-oriented. Its workflow functionality supports sequential tasks, assigning work to users, workflow templates and progress tracking.

How I'd standardize the workflow

I would design the system around executable SOPs, rather than treating the SOP document itself as the workflow.

For example:

SOP: Receive + Process Sample

1. Scan sample barcode
   ↓
2. Verify sample identity
   ↓
3. Verify technician qualification
   ↓
4. Verify equipment is calibrated
   ↓
5. Display preparation instructions
   ↓
6. Technician performs preparation
   ↓
7. Enter/scan measurement
   ↓
8. System checks acceptable range
      ├── PASS → Step 9
      └── FAIL → deviation / exception workflow
   ↓
9. Perform next operation
   ↓
10. Capture result automatically from instrument
   ↓
11. Technician confirms completion
   ↓
12. Supervisor review, if required
   ↓
13. Complete test + audit trail

The important part is that the technician isn't merely instructed to follow the SOP. The software controls what they can do next.

For example, if Step 4 requires a calibrated balance, the system should check the instrument status rather than simply displaying “Use a calibrated balance.” SampleManager specifically supports controlling equipment based on whether it is in service/calibrated.

Likewise, if Step 7 produces a result outside the acceptable range, the system can branch into a predefined exception/retest/deviation workflow rather than letting the technician improvise. Workflow engines can make subsequent actions conditional on previous results.

The requirements I'd put into your LIMS RFP

I'd make these must-have requirements:

One important architectural point

Don't make the SOP PDF the source of truth.

Instead, structure each SOP as:

Procedure → Steps → Preconditions → Technician actions → Required inputs → Validation rules → Evidence → Branching → Completion criteria

The human-readable SOP can then be generated/displayed from that controlled procedure.

That gives you something much more powerful:

SOP = document LES = executable SOP

For your specific requirement, I'd start a proof-of-concept with SampleManager LES and STARLIMS LES, using one genuinely painful SOP from your lab. Don't let vendors give you a generic demo. Give them a real 20–50-step procedure containing equipment checks, measurements, conditional decisions, exceptions, signatures and at least one instrument integration.

Then ask each vendor to demonstrate exactly how they prevent a technician from skipping Step 7 and how the system proves that Step 7 was actually performed. That will reveal very quickly whether you're looking at a true execution system or merely a LIMS with a workflow diagram.

Standardizing laboratory workflows requires moving away from static paper or PDF SOPs and implementing an active Laboratory Execution System (LES) layer—either embedded within a modern LIMS or tightly integrated with one.

How to Standardize Workflows

1. Map and Deconstruct Current Processes: Break down conventional, narrative SOPs into discrete, sequential atomic actions (e.g., Pipette 10 μL, Scan Reagent Lot, Weigh Sample).
2. Build Interactive Protocol Templates: Convert the deconstructed steps into version-controlled digital templates where fields, value limits, and mandatory check-offs are explicitly defined.
3. Enforce Gatekeeping Logic: Program rules so that Step B cannot unlock until Step A is digitally signed, verified, or receives an automated data capture confirmation from a connected instrument.
4. Deploy to the Bench via Mobile/Tablets: Provide technicians with touch-friendly tablet interfaces so they execute the protocol live at the bench rather than transcribing notes later.

LIMS & LES Platforms Supporting Tablet-Based, Step-by-Step SOP Execution

• LabWare ELN / Workflow Automation Manager: Offers robust guided execution of Standardized Testing Methods (STMs). It breaks down SOPs into interactive electronic steps with built-in compliance limits and data checks via its workflow engine without requiring custom code.
• Agilent OpenLab LES / SLIMS: Combines LIMS sample tracking with dynamic lab execution, offering clear visual, step-by-step digital instructions on mobile devices and capturing bench data directly.
• Sapio Sciences LIMS: Features a low/no-code drag-and-drop workflow builder that structures protocols and data capture natively, supporting fluid execution and tracking on modern screen interfaces.
• SciNote ELN / Protocol Execution: Turns static methods into interactive, runnable checklists that technicians can check off step-by-step on tablets while linking directly back to inventory and sample IDs.
• Tulip (Dedicated LES Layer): Often deployed as an agile, customizable execution layer that runs seamlessly on tablets at the bench and syncs bi-directionally with a separate system of record or LIMS.

To help narrow down the best platform fit, could you share:

• Are you looking for an all-in-one LIMS or an execution layer (LES) to sit on top of an existing system?
• Does your lab operate under strict GxP / FDA 21 CFR Part 11 validation requirements?

Standardizing workflows and enforcing step-by-step Standard Operating Procedure (SOP) execution on tablets requires a specialized operational layer known as a Laboratory Execution System (LES).

While a traditional LIMS handles high-level logistics (sample accessioning, tracking, scheduling, and final result storage), an LES manages the "how-to" at the bench level . Modern enterprise platforms increasingly combine LIMS with built-in LES/ELN modules optimized for touchscreens and mobile tablets.

How to Standardize Workflows (The Framework)

1. Deconstruct & Version-Control SOPs : Convert static PDF or paper SOPs into granular, atomic tasks (e.g., Step 1: Weigh sample, Step 2: Add 10 mL of H₂O).
2. Implement Logic-Based Gating : Program rules so technicians cannot proceed to "Step B" until data for "Step A" is successfully captured or verified.
3. Incorporate Point-of-Activity Capture : Eliminate manual transcription by linking barcode scanners/tablet cameras for reagents/samples and pulling measurements directly from connected instruments (balances, pH meters, HPLCs).
4. Enable Review-by-Exception : Configure the system to instantly flag out-of-spec entries or missed sequence orders, allowing QA reviewers to focus only on flagged deviations rather than re-reading entire paper packets.

LIMS Platforms with Step-by-Step Tablet Execution (LES Capabilities)

• LabWare LIMS & ELN/LES : LabWare offers robust guided execution through its Electronic Lab Notebook (ELN) and Workflow Automation Manager . It allows SOPs to be rendered in split-screen or pop-up views on mobile devices . Technicians are walked through standardized testing methods (STMs) step-by-step, with mandatory data fields and hard-stop compliance limits that prevent progress if a deviation occurs.
• Agilent SLIMS : Merging LIMS and ELN architecture, Agilent SLIMS functions natively as an LES . Its handheld "Bench UI" is explicitly designed for touchscreen tablets at the bench, guiding personnel through protocols step-by-step while capturing instrument data and scanning barcodes on the fly.
• STARLIMS LES : STARLIMS provides a dedicated Laboratory Execution System module that extends core LIMS functionality directly to mobile-optimized tablet interfaces . It enforces step-by-step execution, captures contemporaneous timestamps, and integrates bidirectional instrument data collection to ensure ALCOA+ data integrity compliance.
• Sapio Sciences Platform (Sapio LIMS / QC LIMS) : Sapio’s science-aware informatics platform unites LIMS and ELN/Execution capabilities . It features a responsive touch-friendly interface designed for tablets and mobile devices with robust protocol templates that enforce step adherence, barcode tracking, and real-time validation checks.
• Tulip (As an Execution Layer) : While technically a dedicated frontline operations and Laboratory Execution System rather than a traditional standalone LIMS, Tulip specializes in building rich, no-code, step-by-step tablet and glass-screen SOP guidance that integrates seamlessly via APIs to sync data back into legacy LIMS or ERP systems of record.

If you'd like to narrow this down, let me know:

• Is your lab operating in a highly regulated environment (like GMP/FDA 21 CFR Part 11) or a more flexible R&D setting?
• Do you need direct instrument integration (weighing scales, HPLCs) tied to the tablet steps?

To standardize workflows with step-by-step SOP execution on tablets, you usually do not look for a traditional LIMS alone. The capability you are describing is typically a Laboratory Execution System (LES) integrated with a LIMS. A LIMS is generally the system of record for samples, results, inventory, and traceability; an LES is the layer that guides and enforces technician actions at the bench.

Key capabilities to require:

• Electronic SOPs / methods converted into guided workflows
• Sequential step enforcement (technician cannot skip required steps)
• Required data capture at each step
• Conditional branching (“if result fails, open deviation workflow”)
• Training/authorization checks before execution
• Electronic signatures and audit trails
• Instrument integration where possible
• Tablet-friendly interface at the point of work
• Version-controlled procedures so only approved SOPs are executed

Platforms worth evaluating:

A typical architecture looks like:

SOP document → electronic workflow template → LES tablet interface → technician executes steps → data captured automatically → LIMS stores sample/result record → QA reviews exceptions

For selection, I would test vendors with a real SOP and ask them to demonstrate:

1. Can a technician be prevented from moving to Step 5 before completing Step 4?
2. Can required photos, measurements, instrument readings, or observations be captured?
3. Can the system force a supervisor approval at defined checkpoints?
4. Can SOP revisions automatically invalidate old workflows?
5. Can the full execution history be reconstructed during an audit?

If your goal is true SOP enforcement rather than just electronic recordkeeping, prioritize LES + LIMS combinations (for example SampleManager LES, STARLIMS LES, Agilent SLIMS, or a tablet execution layer such as Tulip connected to your existing LIMS).

The best choice depends heavily on your environment: GxP pharma/QC, clinical diagnostics, academic research, environmental testing, food testing, or manufacturing QC will lead to different recommendations.

Yes. The key distinction is that you don't really want a traditional LIMS alone. You want a LIMS + Laboratory Execution System (LES), where the LES turns an approved SOP into a controlled, executable workflow.

What I would shortlist

The first three are particularly close to what you're describing. LabVantage LES explicitly guides technicians through defined steps, checks things such as instrument calibration and reagent status, timestamps activities, and routes completed work for approval. It also has a mobile-enabled HTML5 interface.

SampleManager LES similarly turns procedures into step-by-step digital execution, checking resources and recording information as the technician progresses.

STARLIMS LES specifically advertises a touchscreen/mobile interface and "Workflow Standardization & Guided SOPs," with the ability to enforce work instructions and SOPs.

What "enforce step-by-step" should actually mean

I'd make this a requirement in your URS:

1. Technician logs in on tablet
2. System assigns/selects the work order/sample.
3. Step 1 is displayed — with text, image/video, required inputs, etc.
4. Technician must acknowledge/complete Step 1.
5. Required data are entered/scanned directly into the system.
6. System checks prerequisites:
   • correct sample
   • correct reagent/lot
   • reagent not expired
   • instrument calibrated
   • required environmental conditions met
7. Only then does Step 2 unlock.
8. Conditional logic determines the next step.
9. Deviations require a controlled reason rather than simply skipping the step.
10. Every action is recorded with technician, timestamp, sample/batch, SOP revision and result.
11. Critical steps can require electronic signatures or second-person verification.
12. At completion, the system produces the complete execution record.

That is substantially different from putting a PDF SOP on an iPad and asking technicians to check boxes.

One important architectural point

I'd standardize the workflow before standardizing the software.

Take each SOP and convert it from prose into something like:

Trigger → Preconditions → Step → Required input → Acceptance criterion → Decision → Next step → Exception path → Evidence captured

For example:

Receive sample → scan barcode → verify sample identity → check container → aliquot 1 → record weight → centrifuge → verify centrifuge parameters → transfer supernatant → QC check → continue/reject.

That gives you a reusable workflow model rather than merely digitizing your existing paper SOPs.

My recommendation

If you're buying/replacing a LIMS, I'd put LabVantage LES, SampleManager LES, and STARLIMS LES into the first evaluation round.

If you already have a LIMS you're happy with and the problem is primarily "we need technicians to execute procedures correctly on tablets", I'd seriously evaluate Tulip LES alongside your existing LIMS. Tulip is explicitly positioned as a guided-execution layer that connects to an existing LIMS rather than requiring you to replace it.

And if you're heavily invested in Agilent/OpenLab, OpenLab Sync is worth looking at because it combines LIMS/ELN/LES capabilities and specifically supports guided protocol execution at the bench.

The phrase I'd use when talking to vendors is:

"We need a validated Laboratory Execution System that can convert controlled SOPs into sequential, gated, tablet-based workflows, with conditional branching, prerequisite checks, exception handling, audit trails, and electronic signatures."

That will separate the systems that merely display SOPs from those that actually control execution.

Standardizing laboratory workflows and enforcing step-by-step Standard Operating Procedure (SOP) execution on mobile devices requires a blend of clear change management and a specialized software tier known as a Laboratory Execution System (LES) , which is either native to or tightly integrated with a LIMS.

Part 1: How to Standardize Workflows

1. Map the As-Is vs. To-Be Processes : Conduct a Business Process Analysis (BPA) to document every physical and data touchpoint in your current manual workflows. Identify hidden variations and bottlenecks.
2. Refine and Modularize SOPs : Break monolithic, text-heavy PDF or paper SOPs into discrete, logical micro-steps (e.g., Pipette 10 μL of Reagent A, Verify balance ID, Capture weight).
3. Define Gating and Dependencies : Establish hard rules in the workflow design—such as preventing a technician from advancing to Step 3 until Step 2 has a valid timestamp, instrument reading, or electronic signature.
4. Digitize and Pilot Test : Build the step-by-step template in a staging environment and run a small pilot group of technicians using tablets at the bench to smooth out ergonomics and UI friction before a full rollout.

Part 2: LIMS Platforms with Native Step-by-Step SOP Execution (LES) for Tablets

To strictly enforce step-by-step execution on touchscreens or tablets, look for systems that feature a built-in LES (Laboratory Execution System) or advanced Electronic Lab Notebook (ELN) workflows designed for mobile/tablet interfaces.

• Thermo Scientific SampleManager LIMS : Features an industry-leading, native LES (Laboratory Execution System) capability. It explicitly guides analysts step-by-step through an SOP, blocks progression if data or instrument checks fail, and supports native mobile/tablet applications optimized for execution at the bench.
• LabWare LIMS : Offers robust workflow and electronic worksheet functionality coupled with ELN/LES features. It allows administrators to construct enforced, linear or branching execution paths that technicians can follow seamlessly on touch-enabled devices.
• Sapio Sciences (Sapio LIMS / ELN) : Built on a modern, highly adaptable low-code/no-code framework with unified LIMS and ELN/LES data models. It provides brilliant responsive tablet designs that render step-by-step protocols cleanly and capture structured inputs dynamically.
• STARLIMS : Includes advanced process execution and electronic procedural execution tools designed to replace paper notebooks and rigid PDFs, enforcing compliance and real-time data entry via web-enabled mobile hardware.

To help narrow down which platform fits best, tell me:

• What regulatory framework does your lab operate under (e.g., GMP, ISO 17025, CLIA, or research-only)?
• Do you need the tablets to integrate directly with benchtop instruments (balances, pipettes, analyzers) via Bluetooth/Wi-Fi?