Checking account…

You have unsaved changes

Signing out erases unfinished forms saved in open Metra tabs. Records already saved to Metra are retained.

Browse guides

Reference

Calibration event status reference

Plain-language guide to event lifecycle, allowed moves, and correction paths.

Reference and support For Owner, Administrator, Quality manager, Calibration manager, Calibration engineer About 4 minutes to read

Calibration events only move through the rules below.

Lifecycle flow

draft -> awaiting_approval -> approved -> superseded
  |             |               |
  |             v               -> voided
  |          rejected
  |             |
  |             -> draft
  |             -> cancelled
  -> cancelled

Status meaning and next step

StatusWhat it meansAllowed next statusWhat to do
draftWork is being prepared and can be editedawaiting_approval, cancelledComplete result and attach current certificate, then submit. Cancel with reason if not doing this work.
awaiting_approvalEvent is frozen for reviewapproved, rejectedA different authorised reviewer reviews the frozen content and certificate, then approves or rejects.
rejectedEvent needs correctiondraft, cancelledRead the rejection reason, reopen, correct, then submit again.
approvedControlled evidence approvedsuperseded, voidedLeave unchanged; create supersession if replacement needed.
supersededReplaced by newer approved eventNoneKeep this event for history.
voidedEvent is explicitly made ineffectiveNoneOpen a new calibration event later. Keep voided record for history.
cancelledWork was deliberately stoppedNoneDo not reopen this event.

approved, superseded, voided, and cancelled are final states and stay in history.

Submission rules

Before submission, each event needs:

  • event result (passed, passed_with_limitations, failed, or indeterminate)
  • result summary
  • current retained certificate
  • valid requirement, equipment, and organisation context

The submitted requirement revision and certificate version are frozen while under review. Certificate replacement is not available while awaiting_approval. The person who performed/submitted cannot approve their own event.

Approval outcomes

ResultEffect on schedulingOther outcome
passedBecomes the accepted schedule baseline for that requirement and recalculates next due dateEvent becomes approved evidence
passed_with_limitationsSame scheduling rule as passedLimitation text remains in evidence
failedNo schedule advanceEquipment is quarantined and an out-of-tolerance case opens
indeterminateNo schedule advanceEquipment is quarantined and an out-of-tolerance case opens

Approving older acceptable work does not replace a newer acceptable schedule if one exists.

Failed as-found evidence remains visible even when the overall result passes. Saving failed or indeterminate evidence creates a provisional concern and stops use immediately; the final investigation opens at approval. Passing as-left work or correcting a draft does not erase the finding or release equipment. Permitted engineers can record a reasoned manual concern before approval. Independent quality review and a separate authorised equipment-release decision are required; an unsaved selection does not change equipment status.

Correcting rejected work

  1. Reopen to draft.
  2. Fix editable fields.
  3. Replace certificate if needed.
  4. Resubmit.
  5. Get a different authorised reviewer to approve.

All previous submissions and versions are retained.

Supersede approved work

  1. On an approved event, select Create supersession and add a reason.
  2. Record new work and certificate as a draft event.
  3. Submit and get independent approval.
  4. When replacement is approved, the original event becomes superseded.

Only one open supersession can exist at a time for one approved event.

Void approved work

Voiding requires permission, correct version, and reason.

  • It keeps the original evidence for audit history.
  • Schedule recalculates from other effective events and/or manual adjustment.
  • Voiding does not create replacement work automatically.

Create a new event when fresh calibration is needed.

Permissions

Different actions require distinct permissions: create, update, assign, submit, approve, reject, reopen, cancel, supersede, and void.

Permissions are checked in the service layer; UI visibility does not bypass workflow or organisation rules.