This is a ready-to-use periodic reconciliation log for the hybrid record formed by a calibration certificate (paper or signed PDF) and its corresponding entry in an electronic calibration management system (CMMS). It does not replace the calibration record itself (the as-found/as-left data for a single event); it is a sampling control that proves the CMMS status a reviewer trusts actually matches the certificate behind it. Replace every <<FILL: ...>> placeholder. A filled sample row follows. This content is general educational reference, not legal or regulatory advice.
Instructions
- Pull a risk-based sample of instruments from the CMMS each reconciliation cycle, biased toward high-criticality equipment, instruments due or recently calibrated, and any instrument flagged in a prior cycle.
- For each sampled instrument, retrieve the certificate behind the current CMMS status and complete one row.
- Any mismatch is a finding; route it per the instructions in the Field table below, never silently correct the CMMS without a record of why.
- Retain completed logs per the records retention schedule, for not less than
<<FILL: retention period>>.
- Who performs this:
<<FILL: role, e.g. Metrology Coordinator>>. Who reviews and approves: <<FILL: role, e.g. Quality Assurance>>. Frequency: <<FILL: e.g. quarterly, sample size N instruments or X% of the active population>>.
Field table
What a finding means
Acceptance criteria
Every sampled instrument’s CMMS status is supported by an attached, matching certificate. Due dates on the certificate and in the CMMS agree, or a documented investigation explains and resolves the discrepancy. Any as-left adjustment on a certificate is reflected in the CMMS narrative, not hidden inside a binary pass. Every finding is dispositioned with a record of what was done, not a silent correction.
Filled sample row
Common inspection findings this log prevents
- A CMMS status relied on with no certificate ever produced to support it.
- A calibration due date quietly changed in the CMMS with no corresponding change on, or explanation against, the certificate.
- An out-of-tolerance-then-adjusted result buried inside a system that only records “Pass,” hiding a product-impact question that was never asked.
How to adapt this log
- Set your sample size and frequency from the size and criticality of your equipment population; a larger population generally needs a larger or more frequent sample to give the same assurance.
- Point the deviation reference field at your actual data integrity or quality event procedure.
- If your CMMS already captures multi-point data natively, adjust the “multi-point data reviewed” field to a direct system query rather than a manual re-check of the certificate.