Solution
Quality Management
The procedure, the form it asks for, and the proof that someone filled it in.
Overview
An auditor asks to see the cleaning record for last Tuesday. Then they ask which revision of the cleaning procedure was in force that day, who approved it, and whether the balance used was in calibration. On paper that’s four binders and an afternoon.
A quality system is a chain. A procedure says what must be done. A format sheet says what must be written down. A filled-in sheet is the proof that it was done. Most plants keep the first in Word, the second in a folder of blank templates and the third in a cupboard. The links between them live in someone’s head.
We keep the whole chain in one place, with the links in the data. And then we let the floor write to it directly.
Procedure, template, proof
Controlled document the procedure: what must be done SOP-18
└── Format sheet the template: what must be recorded F-SOP-18-03
└── Record the filled sheet: proof it was done
Every format sheet points at the procedure that requires it. Every record points at its sheet. So “what does SOP-18 make us record, and have we recorded it?” has an answer you can click on.
Quality manuals, procedures, work instructions, specifications, site master files, validation protocols and reports all work the same way. Each gets its own number series and its own revision history.
Change control
Nobody edits an approved document. You raise a revision, and it goes through the people whose names have to be on it.
Draft
An author raises a revision.
- Starts from the last approved version, not a blank page
- Upload the Word file you already have and it becomes the body; the page header fills in the document number, issue and dates
- Submit stays greyed out until the content, effective date, reviewer and approver are set
- One revision in progress per document, so two people never edit the same procedure at once
Review
A reviewer checks it.
- Only someone holding the reviewer role sees the button, and only at this stage
- The picker lists active users only; someone who has left drops off on their own
- Fields lock once the revision leaves draft
Approve
An approver signs it off.
- The revision becomes the current document, rendered to PDF with its number, revision and effective date
- The issue number goes up and the previous version is marked superseded
- Every step lands in the audit log with who, what and when
Separation of duties isn’t a policy document here. The author can’t approve their own work because the system never shows them the button.
Forms that look like the paper, filled in at the machine
Plants spend years getting their forms right, and auditors know what they look like. So we don’t redesign them. Each format sheet is rebuilt with the same fields, the same column order and the same sign-and-date blocks as the original, and it exports to a PDF that looks like it too.
What changes is where it gets filled in. Not at a desk at the end of the shift but on a phone or a rugged tablet, next to the equipment. A QR code on the autoclave opens that autoclave’s log. A code on the room door opens the cleaning record for that room. The app works offline and syncs when the network comes back, which in a plant with thick walls is most of the time.
And some of it needn’t be typed at all. A weight comes off the scale. A temperature comes off the sensor. A cycle’s start and end come off the machine’s own log. The operator confirms, signs and moves on.
Production records
Most plants start with document control and stop there. The procedures are digital and the batch records are still paper.
That’s backwards. The batch record is the thing the customer and the regulator actually ask for.
Before the batch
Check that everything is fit to use.
- Scan the batch label and the right batch record opens, against the current revision of the procedure
- Scan each piece of equipment; anything out of calibration or overdue for maintenance is refused
- Only operators trained on that procedure can sign
During the batch
Record it as it happens.
- Weights, temperatures, pressures and times captured from the scale, sensor or machine where one is connected
- Out-of-limit readings stop the step and raise a deviation then and there, not at review
- Photos and attachments go on the record, timestamped
Release
Review by exception.
- QA sees what is missing, late or out of limits, instead of reading every page
- Open deviations block release until they are closed
- The released record renders to the same PDF format as the paper one it replaced
Equipment, calibration and maintenance
Every instrument a procedure depends on is an asset with a history. A QR label or a BLE tag gives it an identity, and the record behind that identity holds its calibration certificates, its due dates, its maintenance schedule and every batch it was used on.
Calibration. Due dates raise tasks before they lapse. An instrument past its date can’t be selected for a batch, so “was it in calibration?” stops being a question at audit.
Preventive maintenance. Schedules by calendar or by use. The technician scans the machine, works through the checklist on the phone and signs it off there.
Where is it? BLE tags on the portable kit, read by gateways on the ceiling, show which room a data logger or a balance was last in. Nobody walks the plant looking for it.
Which batches did it touch? When a calibration comes back out of tolerance, the list of affected batches is a query, not a week of reading logbooks.
The rooms themselves
Stores, cleanrooms and cold rooms have limits too. Temperature and humidity sensors log continuously to the same system, so an excursion at 3 a.m. raises a deviation at 3 a.m. and the record shows exactly how long it lasted. Wristband tags at the cleanroom door can show who was inside while a batch ran.
Roles
| Author | Creates documents, raises and edits revisions, submits for review |
|---|---|
| Reviewer | Marks revisions reviewed |
| Approver | Approves revisions and releases batches |
| Operator | Fills in records for the procedures they are trained on |
| Viewer | Reads |
Permissions follow the site and the process as well as the role. A plant running several processes keeps a separate controlled set for each, and a person only sees the sites they’re assigned to.
In production
A medical-device sterilisation plant runs its quality system on IoTReady Engine. It started with document control: every procedure, every format sheet and every approval moved off paper. Production records followed. Equipment maintenance and asset tracking are on trial now.
That order is the usual one, and it’s why it’s one system rather than three. The procedure that tells you to calibrate the balance, the balance’s calibration history and the batch record that used it all point at each other.
All of it is configuration on the same Engine that runs inventory and asset tracking. When a sheet needs a new column, that’s a change on your instance, not a change request to a vendor.
The cleaning record for last Tuesday is two clicks away. So is the procedure that asked for it, and the balance’s calibration certificate.
The model
Identity + Quantity + Context = Truth
Three inputs. Get all three at the moment of movement and the record needs no reconciling afterwards.
- Identity
- A QR code or BLE tag on the batch, the instrument and the room, so every record knows what it's about without anyone typing it.
- Quantity
- Readings from scales, sensors and cycle logs, captured as they happen rather than copied onto a sheet at the end of the shift.
- Context
- The procedure revision in force that day, the person who did the work, the role they held, the site and the time.
What captures it
Next step
Tell us what you are trying to trace.
Describe the flow: what arrives, what happens to it and what leaves. We will tell you what it takes to capture it.
or write to [email protected]





