Guide your team through each step of a laboratory SOP.
Build a procedure once, publish a version, and run it the same way every time. No code needed.
- Scan sample barcode
- Tare balance
- Capture 10 mass readings3 / 10 captured
- Review average
- Approve & finishApproval
Clear steps for the operator and a record of the run.
Workflows lets you build a lab procedure as a series of clear steps, such as scan a barcode, capture readings, review a result, retry if needed, and get an approval. Once it is published, anyone can start a run. Each step guides the operator, captures the data on its own, and holds people to the rules you set. Every run is versioned and audited, so results stay consistent and ready for inspection.
No-code builder
Assemble steps from a palette into the exact procedure your SOP describes.
Publish & version
Publish a workflow and track versions so everyone runs the current one.
Guided runs
Operators follow each step; capture, review, and retry are built in.
Role-based approvals
Add approval gates so the right people sign off before a run continues.
No code, just steps
Build the procedure from a palette
Put the steps your SOP describes into order: scan a barcode, capture a reading, review a value, branch on a condition, loop a section, or require an approval. A procedure that lived half on paper and half in someone's head becomes one clear, repeatable flow.
- Step types for scanning, capturing, reviewing, branching, and looping
- Reads pull instrument values straight into the run
- No coding, just build and reorder the steps
One source of truth
Keep the workflow version with each change.
When a workflow is ready, publish it to the library so anyone can start a run. Every change creates a new version, so the team always runs the current, approved procedure, and you can see exactly which version produced a given result.
- Publish to a shared library of ready-to-run workflows
- Use the workflow version released for your procedure.
- Favourite and search across your published workflows
Guided and enforced
Runs that can't skip a step
During a run, the operator is walked through each step, and readings are captured automatically. The rules hold: Continue stays locked until the step's conditions are met, and approval gates make sure the right person signs off. Every run is recorded from start to finish.
- Continue is locked until each step's conditions are satisfied
- Include repeat-measurement steps where the procedure allows them.
- Role-based approvals and a full run audit trail
Walkthrough
In practice: Balance · Mass Over Time
How a published weighing SOP runs the same way every time, guiding the operator, capturing the data, and locking a complete, audited record.
- 1
Identify the sample
Scan or confirm the barcode to open a run of the Balance · Mass Over Time workflow.
- 2
Tare the balance
The workflow prompts the operator to tare, and Inniti confirms the balance is zeroed before continuing.
- 3
Record mass over time
Capture the readings from the Radwag balance. The full mass trace is logged automatically.
- 4
Review average mass
The operator checks the average and the measurement times before the step can complete.
- 5
Complete & export
The run locks as complete with a full execution and review log, ready to export or add notes to.
Consistent, compliant, repeatable
- Build visually with if-then logic, no coding
- Capture instrument readings straight into the run
- Retry loops and conditional steps for real procedures
- Role-based approval gates for regulated work
- Every step logged for ALCOA+ audit trails
- Reuse and adapt workflow templates across sites