Capture tool-cycle evidence

Submit an attributed cycle reading with its asset, event date and work-order reference for review.

Step by step

Confirm the event Technician

Technician checks the physical asset and identifies the work-order reference for the reading. Use the agreed event date and count convention so later reviewers can interpret the number.
- Identify the tool and textual work-order reference
- Updates Assets, Work orders
Prepare the submission Technician

Technician records the count with its asset and reference. Check a late entry against the date the reading actually describes, then submit through the authorized cycle-capture action.
- Capture count and recorded event date
- Updates Tool cycles
Validate and retain evidence Technician

The workflow checks the linked asset, reference, count and recorded event date against the current revision. It saves the attributed cycle record and submits immutable evidence to the responsible reviewer.
- Validate the current submission and retain attributed evidence
- Updates Tool cycles, Assets
Review in context Maintenance Reviewer

Maintenance Reviewer examines the submitted evidence. The linked work-order detail and tool-cycles page refresh so Maintenance Manager can use the recorded information when considering further maintenance.
- Examine evidence and the refreshed work context
- Updates Tool cycles, Work orders

And how to keep it from happening.

Ambiguous reference. The work-order reference is text. Agree a consistent format and resolve an uncertain match before relying on the entry.
Wrong count interpretation. Cumulative readings and incremental counts need different calculations. Set the convention before reviewing totals.
Outdated submission. A current-revision check can stop evidence prepared against an earlier state. Reconcile the change before trying again.

Start free, then use Proto to change fields, steps and approvals before your team goes live.