The paper binder.
Signed sheets with no version on them.
Staff tick boxes on a printed form. A year later, nobody can say which copy of the procedure sat on the clipboard.
Every task files its own record.
When a team finishes a task, Quillery files a record against the procedure version they followed. Inspectors see the version, the person and the time without anyone digging through binders.
The gap
The procedure changed in May. Can you prove who followed which one?
The change email.
Sent to everyone. Read by some.
A new version goes out as an attachment. One shift opens it, another keeps the old printout, and the log can't tell them apart.
Document control.
Keeps every version. Records none of the work.
It knows version 4.2 replaced 4.1 on the 3rd. It cannot tell an inspector which one Tuesday's batch was made under.
Versions
A sign-off says the task was done. Quillery adds which procedure it followed.
Each record carries the procedure, its version and who approved that version. Flip the switch to compare a binder with Quillery.
Unlinked
A binder holds the signature.
Not the version that was on the clipboard.
36%with a version
- line-2-sanitation.pdfNo version
- allergen-changeover.pdfNo version
- autoclave-cycle.pdfNo version
- room-4-turnover.pdfNo version
- sample-intake.pdfNo version
Linked
Quillery files the version with the task.
Each record names the procedure in force.
100%with a version
- line-2-sanitation v4.21s ago
- allergen-changeover v3.14s ago
- autoclave-cycle v6.47s ago
- room-4-turnover v2.610s ago
- sample-intake v5.313s ago
Ask Quillery Inspection prep
Which allergen changeover did line 2 follow on 14 May?
Version 3.1, approved on 2 May. The night shift ran it at 22:40 and signed the record. Version 3.2 only came into force on 20 May.
Sources
/procedures/allergen/v3.1
- Changed by
- QA lead
- When
- 02 May
Tap a source to open the record behind the answer. It shows the procedure version in force and the person who changed it last. Inspectors check it themselves, so nobody has to vouch for it.
What your team did is what the inspector sees.
Rollout
Your first site takes a week. The next one takes an afternoon.
Load your procedures, map who signs what and set the scopes once. A new site copies that setup and files its first records the same day.
| Site | Setup hours per site | Procedures reused |
|---|---|---|
| 01 | 40 | 0% |
| 02 | 18 | 55% |
| 03 | 9 | 78% |
| 04 | 5 | 90% |
| 05 | 4 | 94% |
Access and audit
A request without scope never reaches the records.
Quillery checks every read, edit and tool action against the scope of the person or bot asking. Allowed requests go through, the rest stop at the gate, and each one prints a line in the audit log.
- Scopes by role and site
- Blocked edits stay blocked
- An audit line per request
Sites
Where inspections are part of the week.
Food production
Allergen and sanitation records.
A line switches from a nut product to a nut-free one. The crew follows the changeover steps on a tablet, and Quillery files the record with the version, the crew and the swab result before the line restarts.
Outpatient clinics
Room turnover and sterilization.
Nurses log each instrument cycle and room clean as they finish it. When the infection control procedure changes, every record from that hour on points to the new version.
Testing labs
Sample handling and calibration.
Each sample builds a chain of records from intake to report. An assessor can pick any result and see the method version used and who calibrated the instrument that morning.