Record findings with evidence

An inspection captures what the technician sees against a template. Each row carries a severity, notes, and photo, video, or voice evidence. You can work the whole inspection on a phone in the bay.

  1. Open the repair order on your phone and start the inspection template attached to the job.
  2. Work through each item. Set a severity, then add notes or a measurement where the item asks for one.
  3. Capture photos or video on the row as evidence. Photos are optimised automatically, and HEIC images from an iPhone are converted for you.
  4. Use the voice assistant to dictate findings without typing. Openhood drafts the text into the form, and you confirm it.
  5. Submit the inspection when you have worked through the checklist.

Setting severity on a row

Each checklist item takes a severity so the advisor can triage the report quickly. Tap a severity on the row to record it. Some items also take a measurement, such as tread depth or tyre pressure, or a short note.

If you tap a row that already has an answer, Openhood reopens the edit sheet instead of clearing your work. To clear a row, open the sheet and use the explicit Reset action. That returns the row to an unanswered state without deleting it.

Reset is the only one-tap clear

Repeat-tapping an answered item opens it for editing. It does not wipe the result. Use the Reset action inside the sheet when you actually want to clear a row.

Attaching photos and video

Add evidence directly on the item. Photos are resized for you and HEIC images are converted to a standard format, so you do not need to prepare anything before uploading. Video is handled separately for streaming playback.

If an upload reports that it cannot save, the message tells you what went wrong rather than a generic error, so you can see whether it was a network drop or a save problem.

Dictating with voice

The voice assistant is there to save typing in a noisy bay. You speak, and Openhood writes the finding into the form for you to review.

The voice assistant types for you, it does not talk back

Voice writes findings into the form for you to confirm. It never speaks aloud, and it never sends anything to a customer on its own.

A few things the assistant is built to respect:

  • When you say a section is "all OK", it only fills the untouched, selectable rows in the section you are working in. Rows where you already recorded a fault, measurement, or note are left alone.
  • If you call out a sub-component that matches an existing template row, the detail is written into that row's notes rather than creating a stray custom item.
  • Saying "submit the inspection" finishes the inspection gate. Casual or future-tense phrases like "when I submit the inspection" do not trigger a submit.

Adding a custom item

If you find something with no matching template row, add it as a custom item. Give it a title and assign it to a section. It saves as a finding straight away, shows up in Today's Results and the inspection report, and you can attach photos to it like any other row. During advisor review, a custom item can be moved to a different section or deleted, while template rows stay fixed to the checklist.

Your work is saved as you go

In-progress inspections are checkpointed on the device, so a network drop mid-inspection does not cost you the work you have captured. When the connection returns, your saved results are preserved rather than overwritten by stale local state.

What happens next

Findings feed the rest of the workflow. After the inspection is reviewed and approved, an advisor can turn a finding into a quote recommendation. Until that approval, findings still display with their severity, notes, and photos, but they cannot be one-clicked into a quote.