# Authorise and record a full retest

Repeat every selected check and resolve the earlier finding explicitly.

Source: https://help.smartfact.ai/manuals/checkstation/full-retests

Review edition: 25 October 2026

Roles: supervisor, operator

A retest is a complete successor inspection of the unit, not a replacement reading on the earlier attempt. Use it after the responsible people have decided the actual physical work and reason for another inspection.

## Authorise the successor

The Supervisor opens the terminal predecessor and reviews its failures, evidence, holds and physical disposition. Use Authorise a full retest with a reason and current authentication where offered. An in-progress attempt, already released predecessor, existing successor or exhausted cycle cannot use that authorisation.

The supported cycle permits up to three attempts. Reaching that bound requires the separate supervised new-cycle decision when appropriate; do not create another unit identity to bypass it. A new inspection cycle can revoke earlier releases and requires current new-work authority.

## Confirm and repeat the complete method

The Operator identifies the same physical unit at the current station and prepares its authorised retest. Review selected requirements and source details again and confirm the physical unit before starting.

Record every selected check, repetition and required file afresh. The earlier passing checks do not carry forward. A retest requires supervision for release. Independent safety, source, plan, instrument or restore holds must be reviewed before restart; a failed-check hold alone remains visible while its authorised full retest is performed.

Complete the successor honestly, even if it fails again. Do not record only the failed dimension and describe that as the full retest.

## Resolve the earlier failure

For a completed conforming successor, the Supervisor returns to the earlier failed-check or rejected-evidence hold and uses Review resolution of this hold. Enter the conforming successor attempt identity and a meaningful reason.

The successor must be for the same unit and cycle and later than the predecessor. A similarly named unit or a passing isolated reading is insufficient. The old finding remains retained with its addressed-by-retest resolution.

## Make a separate release decision

After relevant holds are resolved, inspect all current references, evidence and disposition. Use [failures and release](/manuals/checkstation/failures-and-release) for the separate passed-only release. No concession release is available.

Keep both attempt identities and physical work reason with the handover. Historic failed and successor results remain distinct in [history and reports](/manuals/checkstation/history-and-reports). If any command is uncertain, reconcile it before creating another attempt or resolving the same hold again.