Trust the measurement. Trace the impact.

Calibration belongs with the work that relies on it. A certificate can describe an instrument at one point in time; the operating record also needs its intended use, range, procedure, current restrictions and the measurements it supported.

The TT-204 example follows a shelf-temperature instrument through five calibration points. Its low-end error changes from −0.8°C to −0.1°C after adjustment. That answers one question about its final condition. It does not settle what happened during earlier freeze-dryer cycles.

Seal records each point with both observations, timestamps, recorder, procedure and reference standard. The event connects to an assessment of two batch cycles and a qualification run. Open the views in Figure 1 to follow those records; compare the same measurements below.

1Define the measurement hierarchy before the schedule.

Sites, systems, equipment, loops, instruments, channels and measurement points form a controlled hierarchy. A transmitter can serve a control loop, an instrument can contain several ranges or channels, and a portable device can move between areas. Each keeps its own identity, tag, location, range, resolution and parent equipment, and replaced assets retain their lineage.

1.1Criticality comes from intended use.

The criticality assessment links the instrument to the process parameters, methods, alarms, interlocks, release tests and safety functions that depend on it, with the failure effect, detectability and independent checks. Criticality then drives calibration frequency, procedure, tolerances, review, overdue behaviour and impact assessment. A utility pressure gauge and a release-assay balance should not inherit the same controls because they share an asset class.

1.2Range and tolerance are use-specific.

The master record distinguishes manufacturer, calibrated and operating ranges, resolution, acceptance tolerance and the process or method requirement. Multi-range instruments retain separate points and criteria.

Configure the use workflow to check the relevant range and requirements. A device can be within its calibration acceptance yet inappropriate for the precision required by a particular method. Retain the reason for the eligibility decision with the work, including any missing prerequisite or restriction.

1.3Why teams choose Seal for calibration

An as-found failure matters because of the tests and batches that relied on the instrument, yet a metrology or maintenance system holds only certificates and due dates, and those uses sit in LIMS, batch records and logbooks. Seal records the calibration event against the recorded uses of the instrument, so an as-found failure opens an assessment of the work it may affect. Neil can look across calibration history for drift and propose a changed interval or procedure for people to verify and approve.

2Procedures are executable measurement designs.

An approved procedure defines prerequisites, environmental conditions, reference-standard requirements, calibration points, repetitions, calculations, uncertainty treatment, tolerances, adjustment rules and exception behaviour. For automatic, mechanical and electronic equipment in US drug manufacturing, routine calibration follows a written program.¹ An event instantiates the effective procedure against the exact asset, range, location, standards and due requirement.

2.1Keep the reference evidence with the event.

Reference and working standards retain their range, uncertainty, certificate, traceability source, drift, expiry, status and use history. A standard needs to be suitable at event time, not merely current when someone later opens its record. Configure validity and suitability checks for the procedure, and retain the certificate, corrections and standard version used. If a standard later fails, its recorded uses provide the starting population for investigation; missing or unrecorded uses need to remain explicit.

2.2Schedule around the measurement and the work.

Time-based, usage-based, campaign, before-use and condition-triggered strategies can coexist. Due dates account for grace policy, production windows, access, cleanroom state and dependent maintenance, and forecasting groups work by location, standard set and technician qualification. Deferral is a governed decision with risk, duration, conditions, approval and revised due state, not a changed date.

3Keep the original result beside the final condition.

The technician confirms asset identity, procedure, standards, conditions and configuration before collecting as-found data. Each point retains its reference value, observed value, error, tolerance, pass state and actual time.

Preserve as-found data before adjustment, repair or configuration change. Use attributable correction and version history to retain what was recorded and why it changed; do not overwrite the discovery state with a passing final result.²

3.1Adjustment creates a new dataset.

When permitted, adjustment records what was changed, why, by whom and under which authorisation. As-left testing demonstrates the final condition with a complete new data set.

Seal distinguishes calibration without adjustment, adjustment, repair, limited-use return, failure and inability to calibrate. A passing as-left result cannot hide a failing as-found condition.

In the TT-204 example, the indication at −40°C is initially −40.8°C. After adjustment it is −40.1°C. The comparison at the start of this page shows both datasets; the native point record retains their separate observation times and source references. The new result is within the example’s assigned limits, while the original failure still needs its own impact assessment.

3.2Record the uncertainty model and decision rule.

Where required, the event records uncertainty contributors, the calculation, coverage factor and decision rule, with versioned budgets and formulas.

Guard banding and statements of conformity are configured deliberately. Do not claim more precision than the model supports, or imply that all GMP calibrations require the same metrology model.

4Follow the failure into the work it may affect.

An OOT calibration identifies the last known acceptable point, discovery time, potential failure start, maximum observed error, direction, affected range or channel, and immediate equipment state. The initial interval is conservative and can be narrowed only with evidence.

The investigation distinguishes standard failure, instrument drift, damage, environment, procedure, technician, data and use-related causes. Retesting or adjustment does not erase the discovery condition.

4.1Use history identifies a population to assess.

Where identity and time are captured with the use, follow the instrument into batches, process phases, samples, tests, environmental observations, alarms, qualification tests, cleaning records and decisions during the review window. Check completeness before treating that population as exhaustive.

Actual Seal interface, fictional TT-204 records. Three recorded uses are shown; completeness and impact remain under review. Published is a saved version, not an impact approval. View full size

For each use, reviewers compare the affected range and observed error with process limits, independent measurements, control-system redundancy, product data, method tolerance and decision margin. Retain inclusion and exclusion rationale, unresolved evidence and the required decisions. Finding a linked batch is not proof that it failed; passing an as-left check is not proof that earlier batches were unaffected.

5Keep use permission separate from a passing check.

A label can show tag, status, due date, restrictions and a verification code, and scanning it resolves the live record, which catches replaced, quarantined, overdue or range-restricted assets. A label does not override the system state.

5.1External calibration remains under site control.

Vendor capability, scope, accreditation where required, procedures and adjustment authority are assessed, and shipments preserve chain of custody. Incoming review reconciles the serial number, ranges, points, as-found and as-left data, tolerances, standards and adjustments. A PDF certificate alone does not release the asset.

5.2Check the relevant function before use.

Manufacturing, laboratory, maintenance and qualification workflows can check eligibility before use, and the response gives the range or function, current status, restrictions and reason. Continuity rules define what happens during an interface outage: cached status, independent checks, controlled override and later reconciliation.

5.3Change and replacement preserve measurement lineage.

A range change, move, firmware update, tolerance change or instrument swap identifies the affected schedules, open work, methods and validated uses. Replacement records predecessor, successor, equivalence assessment and baseline calibration, and historical use remains tied to the actual serial number.

6Ask Neil to investigate and configure the improvement.

Bring a failed standard, a calibration procedure or an instrument family’s drift history. Neil can analyse the records the requester is permitted to see, follow their relationships and author the assessment, workflow or controlled change needed for the next step. The useful output is linked work and inspectable configuration, not just a summary to copy elsewhere.

For a new procedure, Neil can author instrument and measurement templates, capture fields, calculations and review states. It can prepare verification cases for an expired standard, a missing point, an out-of-range result, a changed formula or an unauthorised completion attempt. Where a script is needed, Neil can write and lint it for operator-run testing. Metrology specialists review the model and decision rule; authorised people execute verification, approve and publish the change.

Keep requirements, risk assessment, configuration versions and verification evidence with the change. Review the effect on open work, validated uses, training, labels and interfaces before cutover. Existing events retain their recorded procedure and source evidence.

6.1Measure whether the change helped.

Useful measures include overdue critical assets, as-found failure rate, drift by family, repeat failure and impact-assessment age. Completion counts alone can reward unnecessary work. Interval optimisation uses stable history, risk, use, environment and failures under approved change, not automatic schedule extension.

7Start with one instrument. Prove the whole chain.

Take one critical instrument from master data and risk through procedure, standards, execution, an as-found failure, adjustment, as-left pass, quarantine, use-history extraction, batch and test impact, and interval review.

Include a multi-range instrument, overdue standard, external certificate mismatch, mobile asset location gap, interface outage and successor replacement. The implementation is ready when each measurement decision can show its traceability and suitability.

Book a demo.