Use Past Audit Findings to Scope Your Access Migration
Your last three audit reports already list what a new calibration system must prove. Turn each finding into a requirement and a parallel-run test.
Your last three audit reports already list what a new calibration system must prove. Turn each finding into a requirement and a parallel-run test.
One row per gauge, every recalibration overwritten. How to rebuild calibration history from certificates and old backups before you leave Access.
Access said 9 overdue. The new system says 61 on day one. Where the gap comes from, and how to brief management before go-live instead of after.
Two technicians, one Access calibration record, one dialog box. How 'Save Record' can erase an as-found result without a trace, and how to close the gap.
Leaving retired instruments in the old .accdb looks tidy, until a complaint reaches a gauge you scrapped two years ago. How to scope them.
The DAkkS calibration mark can print a next calibration date. Your interval rule still sets the due date. Here's how to handle a mismatch.
Your auditor will ask when you changed calibration systems and where the change record is. What clause 6.3 expects when you retire an Access database.
At-line CT and smart gauges move measurement out of the lab. Here's who must own their calibration record, due date and traceability — before the audit.
Your Access calibration DB lets anyone edit a past result with no trace. Here's why that's an audit finding waiting to happen — and how to migrate safely.