PleoStack

Getting Started with Inspections

A complete walkthrough from building templates to executing your first inspection and reviewing results.

This guide walks you through the complete Inspections workflow — from setting up templates to running a field inspection, reviewing results across parties, and handling defects. By the end, you'll have a working inspection cycle.

Quick Summary
  1. Build checklist templates with items to inspect
  2. Group checklists into collections for multi-part inspections
  3. Create an inspection from a collection, assign parties
  4. Performer records verdicts in the field → submits for review
  5. Checker and Approver review → approve or reject
  6. Failed items create quality issues → resolve → reinspect

Before You Begin

Prerequisites

Every project role except RFI Coordinator can open Inspections. Contractors and Subcontractors see only the inspections they created or are assigned to; Client Representatives and Viewers are read-only. Only the project owner can delete an inspection.

If your project has Inspection Policies configured (Admin → Inspections → Policies), those policies control evidence requirements, auto-create issue defaults, and reinspection behavior.

1

Set Up Your Templates

Before running inspections, create the checklists that define what to check:

  1. Go to Admin → Inspections → Templates and open the Checklist Library tab
  2. Click Create Checklist → enter a name (e.g., "Reinforcement Inspection") and select a category
  3. Add items — each item describes one thing to check:
    • Label: "Rebar spacing at 150mm c/c per drawing"
    • Severity: Critical, Major, Minor, or Observation
  4. Organize items into sections (e.g., "Main Bars", "Stirrups", "Cover")
  5. Click Create Checklist

Repeat for each checklist type you need — one for reinforcement, one for formwork, one for safety, etc.

Checklist builder — define what gets checked during inspections
2

Create a Collection

Collections group related checklists so you can run them together:

  1. Switch to the Templates tab (collections view)
  2. Click Create Template → enter name (e.g., "Concrete Pre-Pour") → Next
  3. Add your checklists — select from the library, mark some as required
  4. Click Create Template — the collection is now available as a source when creating inspections
Collection editor — group related checklists for multi-part inspections
3

Create an Inspection

  1. Go to Inspections (main list page)
  2. Click New Inspection → the creation wizard opens
  3. Step 1 — Source: Select your collection (e.g., "Concrete Pre-Pour")
  4. Step 2 — Details: Set the inspection name (required) and the location (optional)
  5. Step 3 — Parties: Assign team members to Performer, Checker, and Approver roles
  6. Click Create Inspection

The inspection appears in the list as Not Started.

Step 1 — select a collection or individual checklist as the inspection source
Step 3 — assign team members to Performer, Checker, and Approver roles
4

Execute the Inspection (Performer)

The Performer goes to the site and records results:

  1. Click the inspection in the list → the detail page opens
  2. Click Begin Inspection → checklist items appear with verdict buttons
  3. For each item:
    • Click Pass (✓) if it meets requirements
    • Click Fail (✗) if it doesn't — add mandatory notes explaining the failure
    • Click N/A (—) if the item doesn't apply
  4. For failed items → optionally switch on Auto-create issue in the item's detail sheet
  5. Attach photo evidence in the item's detail sheet — click the item to open it
  6. When all items have verdicts → click Submit for Review

The inspection advances to the Checker.

The ready state — click Begin Inspection to start recording verdicts
In progress — record Pass, Fail, or N/A verdicts for each checklist item
5

Review and Approve (Checker → Approver)

The Checker reviews the Performer's work:

  1. Open the inspection → see all verdicts, notes, and evidence from the Performer
  2. Record your own verdicts — agree or disagree with each item
  3. Click Approve & Forward → advances to the Approver

The Approver makes the final call:

  1. Review verdicts from both prior parties
  2. If satisfied → Approve Inspection (status: Completed, verdict: Pass)
  3. If they fail any item, the button reads Submit Review (Failed) → triggers reinspection, cycles back to Performer
Approver view — review all prior verdicts and make the final call
6

Handle Issues (If Any)

Failed items with the auto-create toggle on become quality issues in the Issues register:

  1. Open Issues from the sidebar
  2. Find the issues linked to your inspection
  3. Assignee works on the fix → updates status: Start Fix → Mark Fixed
  4. When all issues are Fixed → the Performer can submit the reinspection
  5. When the Performer submits the reinspection → the Fixed issues close automatically
Issues — track defect resolution with status transitions
Row actions — transition issues through their lifecycle

Next Steps

Now that you understand the workflow:

Questions

Can I change the parties, the name or the location after I create it?

No. None of them can be edited once the inspection exists. If something is wrong, have it deleted and create a new one. The project owner can delete any inspection; anyone else only one they created, if their role allows deleting inspections.

Can one person run the whole inspection?

Yes. In the wizard's parties step, remove the Checker and Approver rows so one party remains. That inspection has a single Complete Inspection step and no review chain. Anyone whose role can work on inspections can record and submit a single-party inspection, not only the person named on it.

Does the Performer find out the inspection is waiting for them?

Yes. The person in the Performer slot is notified as soon as you press Create Inspection. The Checker and Approver are notified later, when it reaches them.