Independent and not affiliated with the FDA, MHRA, ISPE, PDA, or any agency. Get the appgoutham@madhadi.com
madhadi.comData Integrity & GxP Quality
Browse all topics -> Articles Templates & Procedures Learning paths GlossaryScenariosToolsRegulatory ReferencesLearning PathsTopics About Start here
Form Plug-and-play starting point Data Integrity

Form: Calibration Certificate and CMMS Reconciliation Log

A plug-and-play periodic reconciliation log that samples calibration management system (CMMS) due dates and pass/fail statuses against the actual certificates behind them, catching unattached certificates, mismatched due dates, and binary pass fields that hide an as-left adjustment, with instructions and a filled sample row.

Document type: Form

Read and copy the template below into your own quality system. It is a generic starting point for your own internal use, provided as is, with no warranty; see the Terms and License. Adopting it does not by itself create compliance.

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

  1. 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.
  2. For each sampled instrument, retrieve the certificate behind the current CMMS status and complete one row.
  3. 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.
  4. Retain completed logs per the records retention schedule, for not less than <<FILL: retention period>>.
  5. 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

FieldFormatRequiredWho completes itWhen
Instrument ID / asset numberText, matches CMMS asset tagYesReviewerAt sampling
CMMS status (due date, pass/fail)As shown in the system at time of reviewYesReviewerAt sampling
Certificate located and attached in CMMS (Y/N)Y/NYesReviewerAt sampling
Certificate due dateDate, as stated on the certificateYes, if certificate foundReviewerAt sampling
Due dates match (Y/N)Y/NYes, if certificate foundReviewerAt sampling
Certificate as-found resultIn tolerance / Out of tolerance, adjusted / Out of tolerance, not adjustedYes, if certificate foundReviewerAt sampling
CMMS result matches certificate as-found result (Y/N)Y/NYes, if certificate foundReviewerAt sampling
Multi-point data reviewed, any single point out of tolerance despite overall “Pass” (Y/N)Y/NYes, where the certificate reports multiple test pointsReviewerAt sampling
Finding raised (Y/N, reference)Y/N and deviation/CAPA number if YYesReviewerAt sampling
Disposition<<FILL: resolved how>>YesReviewer + QAAt closure

What a finding means

What you foundHow to treat it
Certificate attached, due dates and pass/fail matchNo finding. Record and move on.
Certificate not attached but located elsewhere and confirmed to matchDocumentation gap. Attach it, note the gap, trend for pattern.
Due date on the certificate disagrees with the CMMS due dateInvestigate whether the instrument was used past its true due date before correcting either record; raise a deviation if it was.
Certificate reports “out of tolerance, adjusted” but CMMS shows only “Pass” with no narrativeSignificant finding. Assess product/data impact of readings taken before the adjustment; correct the CMMS to carry the full result, not a collapsed binary.
Certificate cannot be located at allTreat the CMMS status as unsupported until the certificate is found or the calibration is repeated; do not treat “system says Pass” as sufficient on its own.

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

FieldEntry
Instrument IDBalance BAL-0142
CMMS statusPass, due 14 March 2027
Certificate located and attachedY
Certificate due date14 March 2027
Due dates matchY
Certificate as-found resultOut of tolerance at the 200g point, adjusted
CMMS result matches certificateN, CMMS showed only “Pass” with no adjustment narrative
Multi-point data reviewedY, the 200g point was out of tolerance; 10g and 1000g points were in tolerance
Finding raisedY, DEV-2026-0311
DispositionProduct-impact assessment opened for batches weighed on BAL-0142 between its prior calibration and this event; CMMS narrative field updated to record the as-found deviation and adjustment

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

  1. 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.
  2. Point the deviation reference field at your actual data integrity or quality event procedure.
  3. 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.
Use madhadi.com as an app Full screen, works offline, one tap from your home screen.