Skip to main content

Field workflow

The repair record starts at the machine.

FaultPilot gives maintainers one field workflow for mobile equipment and site assets: fault intake, safety, diagnostic work, evidence, parts, verification and handover.

One connected field record

Capture the fault. Preserve the work.

The demonstration follows FP-1001 from fault description into a controlled template and a pending named handover.

MAINTAINER APPLICATION

One field record carried through the work.

FP-1001 · HT-214 · Template workflow

Three stages. One attributed field record.

Cancel

Log a fault

SiteAsset3Symptom4Attach

HT-214Unbranded electric drive haul truck

Change
BackNext: attach
01

Capture the faultTie the symptom to the asset while the operating context is still fresh.

Back

Intermittent loss of drive under load

FP-1001 · HT-214

In progressTemplate workflow2 photos0 of 5 done
Template0 of 5 done0%
Safety acknowledgement requiredConfirm all required safety checks before starting any workflow step.
Locked
Tap to confirm safety, then start
01
Diagnostic check 01Available after safety acknowledgement.
02
Diagnostic check 02Available after safety acknowledgement.
03
Diagnostic check 03Available after safety acknowledgement.
04
Diagnostic check 04Available after safety acknowledgement.
05
Verification checkAvailable after safety acknowledgement.
PartsToolsSpecsHazards

Template information only. Diagnostic assistance and governed source retrieval are not represented in this demonstration.

Hand over context Safety gate required
02

Hold the safety boundaryThe 5-step template remains locked at 0 of 5.

BackRefresh

Inbox

FP-1001

Intermittent loss of drive under load

From Priya N. · Pending

2
Asset
HT-214
What was found
Moisture observed at connector C17 after wash-down. No pin damage visible.
Next action
Inspect and dry connector C17, verify pin retention, then complete the remaining controlled checks.
DeclineAccept
HomeDiagnoseHandover1SocialProfile
03

Pass the known contextThe named recipient reviews the finding, evidence and next action.

Illustrative Maintainer journey using synthetic demonstration data. Template demonstration: safety remains unacknowledged and all five steps remain locked at 0 of 5. No AI generation or governed source retrieval is represented.

Field operating model

A repair record, not another checklist.

Each action contributes to the same attributed history so the next person can see what was tried, found, changed and verified.

01

Capture the fault

Connect the asset, symptom, operating context and supporting evidence to one attributed record while the details are still fresh.

02

Keep task hazards and controls visible

Place task specific hazards, paired controls and the acknowledgement gate before the checks, tools, parts and escalation points.

03

Carry the work forward

Keep findings, repair evidence, verification and the exact next action together through closeout or a named handover.

Attributed repair trailFrom first check to final verification
  1. 01

    What was checked

    Completed and skipped steps remain attributed to the person doing the work.

  2. 02

    What was found

    Notes, readings and photos stay connected to the relevant fault and workflow.

  3. 03

    What changed

    Repair action, parts used and part numbers can be captured during closeout.

  4. 04

    What proved it

    Verification and after repair checks close the loop before the job becomes history.

Field noteRead what a useful equipment fault record needs to capture.Diagnostic intelligenceSee how machine context shapes the next useful work.Shift continuitySee how responsibility moves to the next person.

Field evaluationBring one real fault path, the site safety boundary and the handover standard you want the crew to follow.

Scope the field workflow