ISO/IEC 17025 evidence workflows

Make the evidence part of the work.

Obsidian Metra connects controlled methods, technical results and quality records so your team can prepare a coherent audit view without rebuilding the story from scattered files.

A continuous evidence path

From controlled intent to reviewable proof

The strongest audit record is built as work progresses, with context carried forward instead of recreated later.

  1. 01

    Define the controlled work

    Separate equipment, recurring requirements and performed calibration events, then connect each event to the applicable procedure revision.

  2. 02

    Capture technical evidence

    Record the reference standards used, measurement results, uncertainty calculation and conformity decision while context is still available.

  3. 03

    Review and preserve

    Use independent review, personnel authorisations and immutable approved evidence to retain what was known and applied at the time.

  4. 04

    Prepare the audit view

    Freeze a client, site and reporting-period scope into a dossier revision that can be reviewed without reconstructing the work.

Controlled work, clearly separated

Know what was required, what was done and what was approved

Metra keeps the physical equipment record separate from recurring calibration requirements and individual calibration events. Controlled procedures then give technicians the applicable revision and evidence prompts while work is being performed.

  • Multiple calibration requirements for one asset
  • Versioned procedure steps with stable identities
  • Independent review and frozen approved evidence
Resumable controlled procedure showing saved steps and the next unresolved task
Technicians work against the frozen procedure revision and can resume saved progress without recreating earlier evidence.

Traceability as structured evidence

Follow the measurement back through the standards used

Reference standards are controlled equipment profiles with calibration status, certificates, uncertainty, valid range, accreditation information, traceability and restrictions. The calibration event records the standards actually used and retains eligibility findings or acknowledgements.

Traceability completeness is assessed from connected records, helping reviewers see both the available chain and any unresolved evidence gaps.
Reference standards register showing controlled assets, capability bands and calibration status
Reference capability and calibration state remain connected to the asset that provides them.

Technical decisions with context

Preserve how the result was reached

A value is easier to review when the controlled inputs, calculation and reporting decision remain attached.

VERSIONED MEASUREMENT MODEL

Measurement uncertainty

Build Type A and Type B components with distributions, divisors, sensitivity coefficients and degrees of freedom. Approved calculations retain the exact budget revision used.

Controlled uncertainty budget authoring with versioned calculation components
Calculation inputs and outputs remain readable as one technical record.

CONTROLLED CONFORMITY MODEL

Decision rules and guard bands

Connect tolerance, measured error, uncertainty, guard band and boundary policy so a pass or fail can be understood and reproduced by an authorised reviewer.

Quality controls around the result

Technical evidence does not stand alone

Competence, controlled information and nonconforming work need their own reviewable history.

Personnel authorisations

Record scoped permissions and limits for performing, reviewing and approving controlled work.

Evidence library

Retain controlled evidence with ownership, site scope and retention context.

Out-of-tolerance action

Connect investigation, impact, containment and corrective action to the calibration that triggered them.

Scoped, reviewable, immutable

Prepare the dossier without changing the source evidence

Select a client or internal sites and a reporting period. On submission, Metra freezes the scope and evidence selection into a dossier revision. Later changes require a new revision.

  • Equipment and deployment context
  • Calibration work and approved results
  • External evidence and generated certificate revisions
  • Uncertainty and conformity evidence
  • Personnel and controlled-document evidence
  • Nonconforming work and corrective actions
  • System audit history and readiness findings
ISO audit dossier workspace showing site scope, reporting period and evidence selection
The dossier workspace makes scope and evidence choices visible before the revision is submitted.

Connected evidence controls

A clearer review surface for the quality team

Each capability contributes to the same organisation-scoped history rather than producing another isolated record.

Equipment context
Asset identity stays distinct from time-bounded deployment history, recurring requirements and completed work.
Controlled methods
Versioned procedures save completed steps immediately and resume at the next unresolved task.
Metrological traceability
Reference standards carry capability, calibration state, certificates, restrictions and traceability information.
Measurement uncertainty
Versioned Type A and Type B budgets retain calculation inputs, combined uncertainty and expanded uncertainty.
Decision evidence
Controlled decision rules connect tolerances, uncertainty, guard bands and boundary policy to the reported outcome.
Controlled certificates
Procedure-defined readiness, independent signed approval, sequential numbering and accreditation-scope checks freeze the evidence behind each generated revision.
Competence evidence
Personnel authorisations and controlled evidence records help reviewers understand who was permitted to perform or approve work.
Nonconforming work
Out-of-tolerance investigations keep impact, containment, root cause, disposition and corrective action connected to the triggering result.
Audit scope
Dossier revisions freeze the selected client or internal sites, date range and included evidence without altering source records.

An evidence system, not an accreditation body

Professional judgement remains essential

Obsidian Metra supports the management and presentation of ISO/IEC 17025-related evidence. It does not confer accreditation, certify conformity, replace professional judgement, or automatically prove compliance. Your organisation remains responsible for its methods, competence, decisions, quality system and engagement with its accreditation body.

Read the guides

Build evidence as the work happens

Make the next audit easier to prepare for.

Explore readiness workflows, review the product capabilities in detail, or create an account and start with your equipment register.