Deucalion Docs
How-to guideA task-oriented guide for completing a specific goal.
engineerinspectionsassetschecklistdefectsvisit-notesqr

Running Inspections in the Field

Move through assets, checklist items, defects, and visit-note flows without losing progress or context.

Before you start

  • The inspection has been assigned or created for the site.
  • The site context is visible, even if the exact system still needs to be confirmed on site.
  • You can identify the assets or zones you need to inspect.

Expected outcome

You can complete the inspection record with checklist results, defects, and visit notes that stay aligned with the real visit.

Start from the inspection workspace

  1. Open the inspection and stay inside the main workspace while you move between assets, checklist items, defects, and visit notes.
  2. Use the tabs and search controls to move quickly instead of reopening the visit from multiple entry points.

Use system discovery mode when the installation is not known yet

  1. If the inspection opens with System pending, keep working inside the visit instead of backing out.
  2. Capture visit notes and GPS immediately if that helps prove attendance or access before the plant is fully identified.
  3. Use Select Existing System when the equipment is already on the site register.
  4. Use Add New System when you discover a live installation that is not yet in Deucalion.
  5. Once the real system is bound, the checklist and asset workflows unlock in place without restarting the visit.
  6. Do not complete the inspection until the correct system has been attached.
Inspection workspace on mobile
Keep the inspection workspace authoritative for checklist state, defects, and notes.

Keep assets and checklist state connected

  1. If the system is still pending, expect the checklist and asset tabs to stay in discovery mode until you bind the real system.
  2. Review the asset context before you start marking results.
  3. Use QR or search tools when manual drilling is slower than direct lookup.
  4. Sync checklist structure only when the asset register genuinely changed during the visit.

Use visit notes as part of the inspection record

  1. Capture visit notes inside the dedicated visit-note flow when the observation belongs to the visit as a whole.
  2. Use defect detail when the note belongs to a specific issue.
  3. Keep the narrative aligned with the checklist and defect evidence rather than recording separate parallel notes in other apps.
Inspection list on mobile
Inspection lists and detail should stay in sync with the note and evidence history you build in the visit.

Finish with a review pass

  1. Before sign-off, check that checklist results, defects, and visit notes all match the real condition you observed.
  2. If something is incomplete, fix it in the inspection record before moving into certificate review.

Troubleshooting

ProblemWhat to check
The inspection opens but the checklist is missingCheck whether the visit is still in System pending. Bind the real system first, then the checklist will generate for that installation.
The visit notes feel disconnected from the rest of the recordRe-open the inspection note flow and confirm you saved them against the current inspection, not elsewhere.
The wrong checklist items are showingCheck service type, asset context, and whether the asset register changed after the visit began.
A feature like quotes or analytics is missing during the visitTreat it as an availability question first; it is not necessarily an inspection-data problem.

Reference surfaces

  1. Use Inspection Workspace for the live checklist, action bar, GPS, AI, and completion controls.
  2. Use Defect Resolution, Visit Notes, and Drafts and Comparison for the supporting flows that sit around the core inspection screen.
  3. Use the Engineer Screen Interaction Matrix when the key question is which evidence or follow-up screen the inspection can launch next.

On this page