Inspections
Quality inspections with customizable templates, multi-party review workflows, and automatic quality issue creation. From field execution to final approval — every step enforced.
Purpose-built quality inspections
Templates, enforced review, field-first execution, and defects that land in Issues — not a form builder with a checkbox attached.
Reusable templates for every inspection type
Build checklists once — concrete, MEP, safety, structural — and group them into collections for multi-part inspections in one go. Each item can carry its own response type: Pass/Fail, Yes/No/N/A, Conforming, Text, Measurement, or Select, mixed freely in a single checklist.
- Checklist templates for any inspection type
- Collections bundle checklists for multi-part inspections
- Six response types, mixable within one checklist
- Versions auto-increment on save; running inspections stay locked to their version
Multi-party review — nobody signs off alone
Inspections follow a Performer → Checker → Approver sequence. Each party reviews the previous party's work with the full history visible before passing it forward. Rejection sends the inspection back for reinspection with all prior feedback attached.
- Sequential handoff enforced — nothing skips the chain
- Each party sees every prior verdict, note, and photo
- Reject triggers reinspection with feedback visible to the performer
- A counter tracks how many reinspection cycles have occurred
Two field modes, built for gloves and sun
Swipe Mode shows one full-screen item at a time with large verdict buttons — ideal for moving through a checklist sequentially on a phone. Table Mode puts every item in a compact scrollable list for experienced inspectors who know the checklist by heart.
- Large Pass/Fail/N/A buttons sized for gloved hands
- Swipe navigation with a progress indicator, camera always in reach
- Table Mode: inline verdicts, tap to expand for notes and photos
- Both modes feed the same review workflow
Evidence with GPS, defects straight to Issues
Photos capture directly from the phone with GPS coordinates attached, so every verdict has a location record. When an item fails, one toggle auto-creates a quality issue — the defect lands in Issues with the item's label, notes, evidence, and a link back to the inspection.
- Camera capture with automatic GPS coordinates
- Evidence tied to the specific checklist item, not a camera roll
- Failed items become quality issues with one toggle — no double-entry
- Issues follow their own lifecycle, linked back to the source inspection
More in the Inspections module
The supporting register — everything else the module carries, on the record.
- Reinspection flow
- Rejected inspections cycle back to the performer with prior feedback visible and a cycle counter.
- Offline execution
- Active inspections cache locally — verdicts and photos queue without signal and sync when back online.
- Single-party mode
- Set the policy at creation to skip the handoff — one person performs, checks, and approves.
- Template versioning
- Saving a template auto-increments its version; running inspections stay locked to the version they started with.
- WBS-linked or standalone scope
- Tie an inspection to specific WBS items or run it standalone — set at creation.
- Full audit trail
- Every verdict, note, photo, and review decision is logged with timestamps on the completed record.
Every view of the inspection
Two field modes and the review workflow — the working views.
One item per screen with large verdict buttons — sequential field execution on a phone.
How it works
Four steps from template to approved inspection with full audit trail.
Create the inspection
Pick a collection or individual checklist, set the scope (WBS-linked or standalone), and assign the performer, checker, and approver.
Why switch from paper checklists?
Paper forms and spreadsheets still dominate field inspections. Here's what breaks and what changes.
The old way
- Paper checklists filled in the field, then transcribed to a spreadsheet days later — data entry errors and delays.
- No enforced review chain. The inspector signs off alone. Nobody checks the checker.
- Failed items noted on paper but never tracked — defects slip through because there's no follow-up system.
- Photos stored in camera rolls with no link to the specific checklist item they document.
- Reinspection means printing a new form and starting over. Previous results are lost or buried in a folder.
With Construction Hub
- Digital checklists executed on phones and tablets. Data is captured once, in real time, with no transcription.
- Multi-party workflow enforces Performer → Checker → Approver sequence. Every review is logged with timestamps.
- Failed items auto-create quality issues with one toggle. Defects land in Issues with a link back.
- Photos attached to the specific checklist item with GPS coordinates. Evidence is always connected to context.
- Reinspection reuses the same inspection — all prior feedback visible. Counter tracks how many cycles occurred.
Built for the field
Inspections are a field-first workflow. Two mobile modes designed for how site teams actually work — with gloves, in the sun, one-handed.
- Swipe Mode for sequential execution — one item per screen with large verdict buttons
- Table Mode for rapid marking — all items visible in a compact scrollable list
- Offline support — verdicts and photos queue locally and sync when back online
Frequently asked questions
Works with
Issues
Issue tracking from discovery to verified closure — quality, safety, and punch list categories in one register.
Work Breakdown Structure
Hierarchical work planning with a 9-step construction workflow and multiple views.
Reports & Analytics
Pre-built analytics dashboards covering progress, quality, schedule, and cost.
See Inspections in action
See how inspection teams enforce quality with multi-party workflows, auto-created quality issues, and offline-capable field execution.
3-party review workflow trusted by field teams