Sector

The batch record as it happens, not as it's reconstructed.

Controlled work instructions, in-process checks and operator competency captured at the point of execution — so review is a check, not an investigation.

Quality inspector using a tablet to check a medical device assembly against controlled batch records
A controlled batch instruction checked on a tablet during production.

Powered by Axiom — controlled process and competency records, with equipment status from Dinsdale Apex One and ERP/MES integration through Select.

Explore Axiom

Execution and evidence in the same act

If the record is produced after the work, it describes the work. If it is produced during the work, it controls it.

Controlled work instructions

Issued by version to the point of use, with the operator acknowledging the version they worked to.

Execution records

Sequenced steps completed on the line, capturing values, verifications and timestamps as the work happens.

In-process checks

Measurement and inspection steps with tolerances enforced, so a failure stops the step rather than being noticed later.

Operator competency

The system knows whether the person executing the step is authorised for it, and records that they were.

Second-person verification

Independent checks captured as distinct signatures with meaning, not a shared login and a countersign at the end of the shift.

Equipment status

Where Dinsdale Apex One is in use, the calibration and maintenance status of the equipment used is bound to the record.

Deviations & NCRs

Non-conformances raised at the step that failed, categorised, assessed for impact and tracked to closure.

Batch documentation

A complete, reviewable pack per batch, assembled from the records rather than compiled afterwards.

Review by exception

Reviewers see the steps that deviated first, instead of reading a hundred compliant pages to find three that aren't.

Review by exception

Most batch review time is spent confirming that compliant steps were compliant. That is a poor use of the most experienced people in the building, and it makes the genuine deviations harder to spot, not easier.

When steps are executed against a structured template, the system already knows which ones were in tolerance, correctly sequenced and properly signed. Review can start with what didn't go to plan.

The rest of the pack remains fully available and fully auditable. It simply stops being the thing a reviewer has to read line by line before they reach anything that matters.

What quality gets

  • A batch pack that assembles itself as production proceeds
  • Deviations captured at the point of failure with impact assessment
  • Operator authorisation evidenced per step, not per shift
  • Equipment calibration status bound to the record it produced
  • Trend data across batches, because every value is a field rather than ink

Common questions

Is this an MES?
No. Axiom covers controlled process execution and the people evidence around it. Where you run an MES or ERP, Select keeps orders, batches and outcomes aligned rather than duplicating them.
Can it enforce competency at the step?
Yes. A step can require a specific authorisation, and the record shows that the operator held it at the time of execution.
How are electronic signatures handled?
Signatures are bound to an authenticated user, the record version and a stated meaning, with a full history of who signed what and when.
What about paper we can't remove yet?
Hybrid working is normal during transition: some steps are captured digitally while others are scanned in as evidence against the same batch record.

Your route to go-live

We deploy Dinsdale Apex One with you.

This is not software handed over with a login and a manual. We work through the process with your people, prepare the information it needs and stay involved after launch.

  1. 01

    Understand and customise

    We learn how your work happens now, where it slows down and what your teams need. Then we shape Dinsdale Apex One around the process you want to improve.

  2. 02

    Connect your data

    We prepare and import the agreed customers, sites, people, assets and working information, then connect the systems involved where required.

  3. 03

    Train you and your teams

    We work with the people who will use the system, using their real responsibilities and day-to-day tasks rather than generic training examples.

  4. 04

    Go live

    We test the complete working process with you, confirm the key information is ready and support your teams as the system moves into everyday use.

  5. 05

    Ongoing support

    We stay involved after launch, helping you answer questions, refine the process and make sensible changes as your operation develops.

See the manufacturing workflow in action

Book a demonstration of the work instruction, execution record and completed batch evidence.

Book a Demo