Calibration-certificate cleanup looks like data entry until two records disagree, an asset identifier is missing, or a due date is absent. Those cases are not blanks for an operator to complete. They are decisions for the organization's authorized quality or metrology representative.
The workflow below is the operating boundary behind YY's Calibration Register Cleanup. The linked example is fictional, so every row and exception can be inspected without exposing a real facility.
1. Freeze a bounded intake
Start with one existing gage list and a numbered set of readable certificate PDFs from one site. Record which files were accepted, excluded, or unreadable before copying fields. A changing source set makes it impossible to reconcile the output cleanly.
2. Match records only on supplied evidence
Use explicit asset IDs, serial numbers, certificate numbers, and source filenames to propose a match. If a certificate has no matching supplied asset ID, leave it unlinked. Similar names or instrument models are useful review clues, not authority to create a match.
3. Keep a page reference beside every copied field
The output should let a reviewer move from a register value back to the certificate page that states it. Source references make the copy operation inspectable and make corrections cheaper than searching a shared folder again.
4. Copy dates; do not invent intervals
A calibration date and a stated next-due date can be copied. If the next-due date is absent, record that it was not stated. Do not derive a date from an assumed annual interval or from another instrument's schedule. The organization's approved interval policy belongs outside the cleanup step.
5. Separate observed results from quality decisions
If a certificate states an as-found failure and an as-left pass, copy both results and flag the record. Do not turn those observations into an instrument-status decision or a product-impact assessment. Those decisions require the organization's procedures, use history, and authorized judgment.
What the fictional sample makes visible
The two-page sample contains eight certificate records. Six have an explicit next-due date, two do not, and four records enter the review queue:
- QA-003: the next-due date is not stated in the source certificate.
- QA-004: the certificate reports as-found FAIL and as-left PASS; no product-impact assessment is supplied.
- SYN-006: the certificate has no matching asset ID in the supplied list, so it remains unlinked.
- QA-008: the next-due date is not stated, and no interval is calculated or inferred.
These are intentionally ordinary exceptions. The useful output is not a register with every cell filled. It is a register that distinguishes copied facts from unresolved work.
6. Reconcile the output independently
Before delivery, a reviewer should compare the register against the accepted file inventory, spot-check copied values against their page references, and confirm that every unresolved item remains visible. That reconciliation checks the bounded data-entry work; it does not validate the laboratory's measurement or certify the records.
What this workflow does not establish
- It does not perform or certify calibration.
- It does not assign intervals or invent due dates.
- It does not reinterpret pass/fail results.
- It does not perform out-of-tolerance product-impact analysis.
- It is not a compliance opinion or an audit-readiness guarantee.
- It does not prove that the source records are complete or correct.