LimsPulse
MODULE · WORKFLOWS

Workflows

One approval engine for every module. Design your SOP visually, with no code.

  • 21 CFR Part 11
  • ALCOA+
  • GAMP 5
Workflow
Engine
No Code · SOP-Driven
01Design02Roles03Approve04Branch05Notify06Versions

Workflows at a glance.

Every record in LimsPulse, from specifications and instruments to chemicals and documents, is approved through one shared workflow engine. Draw the flow on a canvas, decide who approves each stage and how many must agree, add decision points and optional stages, and require an e-signature wherever your SOP needs one.

WHY THIS MODULE

Why teams choose Workflows.

Model any SOP

Drag-and-drop stages, decisions and approvers on a visual canvas.

Flexible approvers

Approve by user, role, department or designation: all, any one, or N of M.

Right people, every time

Authors pick approvers at send time when the right reviewer changes per record.

Enforce compliance

E-signature with meaning can be required on any approve or reject.

CAPABILITIES

What you get

Visual workflow designer

Draw stages, decisions and connections on a canvas; no developer needed.

One engine, every module

The same engine approves masters, samples, inventory, calibration, stability and documents.

Group approval rules

Groups by user, role, department or designation, with All, Any one, or N of M.

Runtime approvers

The author picks the specific approvers when sending the record.

Decision points

Diamonds with two or more labelled outcomes that route the record down different paths.

Optional stages

Stages the author can include or skip, such as an inter-discipline check.

Author step

Send the record back to its author, who can be required to upload a new version.

Stage stamps

Text or image stamps with user, date, stage and version applied at each step.

Per-stage e-signature

Require re-authentication and a signature meaning on approve or reject.

Notifications

In-app and email alerts when an action is waiting for someone.

HOW IT WORKS

End-to-end workflow

  1. 01

    Design

    Draw the SOP on the canvas with stages, decisions and approver groups.

  2. 02

    Assign

    Link the workflow to a module or record type.

  3. 03

    Run

    Records move through each stage; approvers get notified and sign.

  4. 04

    Trace

    Every action, comment and signature is kept in the audit trail.

INSIDE THE DATA
100%
audit-trail completeness
99.8%
data-integrity coverage
0
uncontrolled spreadsheets
3
compliance frameworks aligned
FAQ

Questions about Workflows

The questions we hear most from labs evaluating this module.

Do users need IT to change a workflow?
No. An administrator updates workflows in the visual designer. Changes apply to new records, and every action is kept in the audit trail.
Can different documents follow different paths?
Yes. Decision points and optional stages let one workflow branch, for example sending a document for an inter-discipline check only when it needs one.
What if the approver changes for every record?
Use runtime approvers. The author picks the specific people when sending, either from a fixed group or freely.

Ready to roll out Workflows?

Tell us how your team works today — we'll show you exactly how LimsPulse fits.

Request a demo