Common Workflows

Step-by-step tasks, plus the scripted demo storylines in the seed data

Everyday Tasks

Record an inspection

  1. Inspections & Observations → Inspection → Create
  2. Choose the Road Section from the lookup (sections display as "18A-01 - Western Hwy — Town Reach")
  3. Set inspection type (Scheduled / FollowUp / Complaint / Incident / JointAssessment), method, date and inspector
  4. Save. Defects found during the inspection are added as Defect Observations linked to it.

Record a defect

  1. Defect Observation → Create
  2. Pick the Defect Sub Type (e.g. PH02 for a large pothole), the Road Section and optionally the Inspection it came from
  3. Enter measurements (length, width, depth, count, area, quantity) and set the source type
  4. Save with status Observed.

Assess a defect

  1. Select the observation → Defect Assessment child tab → add an assessment
  2. Pick the matching Intervention Rule (sub-type × road category), the priority, and the weightings
  3. Calculated score = corporate × field weighting; set the response due date from the rule's response time
  4. Update the observation status to Assessed (then Logged once it enters the defect log).

Plan and order work

  1. Check Valid Defect Activity for the permitted repairs for the defect's sub-type
  2. Create a Planned Work record (activity, quantity, unit rate → estimated cost)
  3. Create a Work Order from it; record execution under the work order's Work Execution child tab
  4. Verify with a Completion Inspection, then create the Defect Closure and set the observation status to Closed.

Demo Storylines (in the seeded data)

A — A pothole's complete lifecycle ★

OBS-2026-0201: 450 mm pothole at the Boundary Creek bridge approach, found by inspection INS-2026-0032.

Follow it: Inspection INS-2026-0032 → child tab shows the observation → its assessment (PH02 × CAT1 rule, score 10×8 = 80, 2-day response) → log entry (Fixed) → planned work (Heavy Patching 103, 4.5 m²) → Work Order WO-2026-0140 (coldmix make-safe same day, then permanent heavy patch) → execution by DP Crew 2 → completion inspection Pass → closure Rectified. Follow-up inspection INS-2026-0044 is already scheduled to check the patch after three months.

B — Priority 1 Hazard, still in flight

OBS-2026-0205: guardrail struck over 12 m below the lookout. Priority 1 — mandatory action, 24-hour response, field weighting not applied. Emergency WO-2026-0143 is InProgress: 6 of 12 m of rail fitted, remainder on backorder, site signed and made safe.

C — Backlog: when funding runs out

OBS-2026-0202: 40 m² crocodile cracking in the school zone. Log entry CarriedForward; the Defect Backlog record explains why (routine budget exhausted, deferred to reseal programme RESEAL-2027-DP-04) with review and target dates. The Planned Work entry sits at Deferred.

D — Below intervention level: monitoring

OBS-2026-0210: worn centreline, below the initial intervention level — status Monitoring, no assessment, no log entry. The rules say wait; the system records it and waits.

E — The rules are data

Reference Library → Intervention Rule: the two PH02 rows show a 2-day response on CAT1 vs 7 days on CAT3. Valid Defect Activity shows the pothole's repair options. Maintenance Activity 103 → Activity Standard holds the restoration standard and work operations. A new guideline edition is a data load, not a software release.

A fuller manual with a timed 10-minute demo run sheet: User Manual & Demo Guide.