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 punch items → resolve → reinspect

Before You Begin

Prerequisites

You need at least Engineer role to access Inspections. Admin permissions are required to create and manage templates.

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

1

Set Up Your Templates

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

  1. Go to Inspections → Templates → Checklist Library tab
  2. Click New 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"
    • Response type: Pass/Fail (default)
    • Severity: Critical, Major, Minor, or Observation
  4. Organize items into sections (e.g., "Main Bars", "Stirrups", "Cover")
  5. Click Save

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

Checklist builder showing items with sections, response types, and severity settings
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 New Collection → enter name (e.g., "Concrete Pre-Pour")
  3. Add your checklists — select from the library, mark some as required
  4. The collection is now available as a source when creating inspections
Collection editor showing grouped checklists with party sequence settings
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, location, and scope (link to WBS items or enter custom)
  5. Step 3 — Parties: Assign team members to Performer, Checker, and Approver roles
  6. Click Create

The inspection appears in the list as Not Started.

Create Inspection wizard showing collection source selection
Step 1 — select a collection or individual checklist as the inspection source
Create Inspection wizard showing party assignment step
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 toggle Auto-Create Punch Item
  5. Attach photo evidence using the camera button
  6. When all items have verdicts → click Submit for Review

The inspection advances to the Checker.

Inspection ready state showing checklist preview and Begin Inspection button
The ready state — click Begin Inspection to start recording verdicts
Active inspection with checklist items and verdict buttons
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 issues found → Reject → triggers reinspection, cycles back to Performer
Approver review view showing prior party verdicts alongside own verdict buttons
Approver view — review all prior verdicts and make the final call
Submit for Review confirmation dialog showing verdict summary
Confirmation dialog — review your verdict summary before submitting
6

Handle Punch Items (If Any)

Failed items with auto-punch create entries in the Punch List:

  1. Go to Inspections → Punch List
  2. Find the punch items linked to your inspection
  3. Assignee works on the fix → updates status: Start Fix → Mark Fixed
  4. When all punches are Fixed → the Performer can reinspect
  5. On successful reinspection → punches auto-close
Punch list table showing items with status, priority, and assignee
Punch list — track defect resolution with status transitions
Punch item row actions showing Start Fix, Mark Fixed, and Close options
Row actions — transition punch items through their lifecycle

Next Steps

Now that you understand the workflow: