PlaysbyMoat8
Back to the library
The workflow guideOperations

Prototype a visual infrastructure-inspection queue

Flag possible defects in inspection imagery for qualified maintenance specialists.

6 implementation stepsAdvanced

How this works

Flag possible defects in inspection imagery for qualified maintenance specialists.

Create a review queue of suspicious image regions for a qualified inspector. Capture conditions and defect definitions matter: a shadow, blur or unfamiliar surface can resemble a defect, and a model flag is not a maintenance diagnosis.

Before you start

Defined operating scope

Maintenance specialists have inspection imagery and verified examples for a bounded visual-review pilot.

Required source material

Obtain Inspection imagery; Verified defect examples. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

An image is blurred or lacks the required view. Request recapture rather than classifying absence of evidence as no defect.

Prepare the inputs

inspection_images
Required

Image IDs, asset and capture metadata

Preserve originals, scale and location where available.

defect_examples
Required

Verified labels and region annotations

Keep defect class and reviewer provenance.

capture_rules
Required

Required angles, lighting and resolution

Define unusable-image conditions.

review_protocol
Required

Specialist findings and escalation rules

Separate candidate flag from confirmed defect.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check inspection_images, defect_examples, capture_rules, review_protocol before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected inspection_images and any missing required fields.

  2. Validate the examples and capture conditions

    • Check example quality and capture consistency, holding images that cannot support the intended inspection.
    • Review both flagged and unflagged images against specialist labels.

    Checkpoint: A saved intermediate result for: Validate the examples and capture conditions.

  3. Flag suspicious regions for review

    • Flag candidate regions with location references and alternative explanations, retaining unflagged examples for evaluation.
    • Track capture-quality failures separately from model classification errors.

    Checkpoint: A saved intermediate result for: Flag suspicious regions for review.

  4. Record specialist findings and follow-up checks

    • Have specialists review candidates, record confirmed findings and required follow-up inspection, and track false alarms and missed examples.
    • Review both flagged and unflagged images against specialist labels.

    Checkpoint: A saved intermediate result for: Record specialist findings and follow-up checks.

  5. Reconcile the proposed result

    • Review both flagged and unflagged images against specialist labels.
    • Track capture-quality failures separately from model classification errors.

    Checkpoint: The listed discrepancies have a named reviewer or an explicit unresolved status.

  6. Package the result and unresolved work

    • Concept-stage workflow: specialists validate defects and maintenance decisions.
    • This is a concept-stage inspection aid; specialists decide defects and maintenance actions.

    Checkpoint: A reviewed inspection queue. Unresolved items remain visible in the review record.

Decisions along the way

An image is blurred or lacks the required view.

Request recapture rather than classifying absence of evidence as no defect.

A candidate resembles a known lighting artifact.

Present that alternative and require specialist confirmation.

A potentially serious defect cannot be verified remotely.

Escalate through the maintenance protocol without prescribing an unqualified repair.

What you will produce

inspection-image-review-queue-result.json

JSON

A reviewed inspection queue. Label proposed and completed states separately.

Include: image_id · asset_id · candidate_region · suspected_class · capture_quality · specialist_finding · followup · status · evidence_reference · review_note

inspection-image-review-queue-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving review_protocol.

Include: source_reference · question · owner · next_action

Check the result

  • Review both flagged and unflagged images against specialist labels.
  • Track capture-quality failures separately from model classification errors.
  • Inspect inspection_images and defect_examples in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Concept-stage workflow: specialists validate defects and maintenance decisions.

When something goes wrong

An image is blurred or lacks the required view.

Request recapture rather than classifying absence of evidence as no defect. Retain the affected evidence and recovery status.

A candidate resembles a known lighting artifact.

Present that alternative and require specialist confirmation. Retain the affected evidence and recovery status.

A potentially serious defect cannot be verified remotely.

Escalate through the maintenance protocol without prescribing an unqualified repair. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Prototype a visual infrastructure-inspection queue for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Image I-8 shows a dark line on an asset surface, but lighting differs from the verified crack examples and no scale is present.

Expected result

Synthetic expected result: Create a candidate region with uncertainty and request a closer, properly lit image with scale. Do not label the asset defective or safe from this image alone.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure specialist-confirmed precision and recall; missed critical defects and review time.

Stop or revise

A potentially serious defect cannot be verified remotely. Pause affected records and apply this recovery: Escalate through the maintenance protocol without prescribing an unqualified repair.

Keep the scope clear

  • This is a concept-stage inspection aid; specialists decide defects and maintenance actions.
  • Do not claim safety clearance or automate physical intervention from image confidence.

Check before using

Concept-stage workflow: specialists validate defects and maintenance decisions.

Business activities

  • Inspect and maintain physical assets

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Inspection imagery · Verified defect examples

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗