Tutorial 4: Run an Inspection End-to-End

This tutorial covers the full inspection lifecycle: build the checklist once, run it as often as you like, and link any failures into corrective actions automatically.

By the end you will know:

• The difference between an inspection template and an inspection run.
• How to build sections and items with stable IDs.
• How to schedule a run and conduct it on a phone in the field.
• How to raise an action from a failed item.
• How the score and BRAG colour are calculated.

Before you start

Continue from Tutorial 3. You’ll need a site.

Step 1 — Open Templates

In the sidebar, scroll to Templates under Capabilities. This is the templates list — not the same as the Inspections list, which shows runs.

Why split? Templates are the reusable shape (“monthly site walkthrough”). Runs are the executions (“monthly site walkthrough, May 2026”). Both live in the same underlying table; the isTemplate flag tells SteadyOn which is which. The split exists so the two never get muddled in your daily work.

Step 2 — Build a template

Click + Template. The template wizard opens.

Basics

• Title — Monthly site walkthrough.
• Description — what this template covers and how often.
• Category — pick from the lookup (e.g. General workplace).

Sections

Click + Section and add the first one — for example Housekeeping.

Inside it click + Item and add a question:

• Item title — “Walkways are clear of obstructions.”
• Pass/Fail/N-A — the standard three-state response.

Add a few items per section:

• Floors are dry and free of slip hazards.
• Bins are emptied; no overflowing rubbish.
• Emergency exits are unobstructed.

Add another section: Equipment.

• Fire extinguishers are in their stations and tagged this year.
• Eye-wash stations are charged.
• PPE storage is full and tidy.

You can drag sections and items to reorder. Each one gets a stable ID so reordering doesn’t break runs in flight.

Click Save. Your template appears in the Templates list.

Step 3 — Schedule a run

Now switch to Inspections in the sidebar.

1. Click + Inspection (or Schedule inspection).
2. The schedule dialog opens.
3. Pick Template — Monthly site walkthrough.
4. Title auto-fills from the template; edit if you like (“Monthly walkthrough — May 2026”).
5. Site — pick the site.
6. Scheduled date — pick today or a near-future date.
7. Inspector — pick yourself.
8. Click Schedule.

The new run appears in the Inspections list with status Scheduled. Its sections and items are copied from the template at schedule time — if you change the template later, in-flight runs aren’t affected.

Step 4 — Conduct the inspection

Open the inspection (click its title). The detail page tabs are typically:

• Conduct — the working surface during a run. Pass / Fail / N-A toggles per item, with a notes field and an “Add action” affordance per item.
• Sections — read-only view of the structure copied from the template.
• Schedule — when, where, who.
• Attachments — photos, sign-off sheets.
• Log — audit history.

Open Conduct.

For each item:

1. Tap Pass, Fail, or N-A.
2. Optionally add a note (mandatory if you fail an item, in some templates).
3. If you fail an item, click Raise action to open a small inline dialog. Fill in title and due date — the action is auto-linked back to this inspection finding.

Work through the whole list. Pass most items, fail one or two for the sake of the example.

On a phone, the page automatically uses the card-style mobile layout. Pass/Fail/N-A buttons are big targets, the keyboard pops up for notes, and the camera button is one tap away for photo evidence.

Step 5 — Complete the run

When you’ve answered every item:

1. From the detail page header’s kebab menu (⋯), click Complete.
2. Confirm.

SteadyOn calculates the score:

Score = Pass / (Pass + Fail) × 100

N-A items don’t count.

The BRAG colour for the completed run is:

Score	BRAG
100%	Green
80–99%	Amber
Below 80%	Red

The pass threshold defaults to 80% but is configurable per org — see Adjust BRAG thresholds.

Step 6 — Follow up on the actions

Switch to Actions in the sidebar.

The actions you raised from failed items are now in the list. They’re already linked back to the inspection — you can see this on each action’s Related tab. As they get worked through and verified, the inspection’s “open actions” count drops.

The next time you run this template, you can see this run’s findings on the new run’s history panel — useful context for the inspector.

Step 7 — Save a tweaked run as a new template

If during the run you discover the template is missing a question:

1. Add it as a free-text item in the run (this varies by your org’s setup).
2. From the run’s kebab menu, click Save as template.
3. Give it a new name. The new template includes the structure of the run.

What you learned

• Templates and runs are kept separate so you can iterate on the template without breaking history.
• Items have stable IDs; reordering doesn’t break in-flight runs.
• Pass / Fail / N-A drives both the score and the BRAG colour.
• Actions raised from failed items are linked back automatically — no extra wiring.

Next

Continue to Tutorial 5: Set Up Roles, People & Training.