What’s inside: company memory · audit trail
The question this file answersHow many gauges on my floor are overdue right now — and would I know before the auditor does?
Fits: plants where quality certificates are read, retyped and filed by hand.
Typical pattern, not a measured desk; the manufacturing playbook covers quality certificates but gives no calibration count. A certificate comes back with each instrument; someone files the PDF, updates the register if there is time, and hunts both before the audit. It hurts when a gauge turns out overdue mid-production.
Before the next audit, the register already answers which instruments are due, which are overdue and which came back out of tolerance, with the certificate a click away from each. Quality's attention goes to the failed gauge and what it touched, not to matching PDFs to serial numbers.
Typical, not a measured client result. Every figure here comes from the playbook source named below.
the same certificate-reading build as certificate-of-analysis intake — no dated figure for calibration records
Before: certificates are filed as PDFs and hunted the week before the audit. After: due dates and as-found values sit in the register with the certificate attached; overdue and failed gauges go to a person. No percentage — we hold no dated figure for this desk.
The ASQ audit-preparation figure in our manufacturing playbook could not be pinned to a dated document, and SAP/Siemens (2023) measures incoming quality documents rather than calibration records, so this file carries no percentage; the sourced range stays on the certificate-of-analysis file. Not an audit-outcome claim.
Your QMS and calibration register stay — SAP QM, ETQ, MasterControl or the spreadsheet you actually use. This is the same certificate-reading build as our certificate-of-analysis file, pointed at instruments:
Deciding what that gauge measured in the meantime is a person's job.
Failed gauges. Impact on production already run. Auditor questions that need a sentence.
Not an audit-outcome claim.
If instrument IDs on certificates do not match the register — relabelled gauges, lab typos — the certificate cannot be attached and goes to a person; a clean instrument list comes first. The production-impact judgement on an out-of-tolerance gauge is outside the build, and if your register is a spreadsheet, updates go through file import rather than an interface.
The path: free 60-second estimate → free 20-minute review → paid audit of this one process (€1.5–3K, typically two weeks) → pilot with your people in the loop (€10–20K, weeks, not quarters). No transformation programme. Prices are public, on the services page →
Scoped in the audit — the playbook has no estimate for this exact desk.
That depends on your volumes and wage costs — this page will not invent the number. The free 60-second estimate runs that calculation from your answers, with every multiplier sourced.
Not a named Aperanda client. Process file · Manufacturing.
Short process file. Same build as its parent file; the playbook has no separate volume or benchmark for this desk.