10-minute demo walkthrough
Step-by-step script for showing RoadEye to a council audience.
ⓘ Demo mode. The data on every screen below is live — your demo Supabase has been seeded with 4 demo drives + ~140 detections + ~80 AI jobs spread across providers / QA states / segmentation states. Re-seed with
./scripts/deploy-pending.sh --skip-apk. Demo rows carry metadata->>'demo' = 'true' so they're queryable / removable.Honest limitations to mention up front
- "PAS 2161-style" — readiness + export, NOT certified compliant. Network baseline + chainage / road class are gaps.
- YOLO26 is wired but not actively running — server-side YOLOv8 with HF pothole model is the live default; YOLO26 needs a Modal/HF Space deploy of the included Python service.
- Mobile inspector review mode, real EdgeSAM masks, FixMyStreet integration — all on the roadmap; not in v1.
- No multi-tenant org federation — single demo org for now.
1. Network map (home)
/
What it shows
Top KPI strip + clustered detection markers + sidebar nav.
What to say
"This is the operational view. Every survey by every device shows up here within seconds."
Expected
Map renders with clusters; KPI strip at the top reflects the seeded demo counts.
2. Attention centre
/attention
What it shows
Aggregates everything that needs a decision today.
What to say
"Inspectors and managers don't hunt for problems — RoadEye surfaces them."
Expected
8 cards with counts, sorted by urgency. "Copy daily summary" button copies a plain-text digest to clipboard.
3. Work queue
/work-queue
What it shows
7 categories of operational triage with deep links into QA.
What to say
"This is where the morning starts. Triage the queue, then act."
Expected
Tabs across the top, each with counts. The Field-check tab shows linkage to existing field_checks rows.
4. QA review
/admin/qa
What it shows
Detection-by-detection review with mask preview, lifecycle pickers, trust score, and bulk actions.
What to say
"Every AI detection comes through here. Approve, reject, or send to field check."
Expected
Table of detections sorted by severity then confidence. Per-row → FC button creates / opens a field check.
5. Field checks
/field-checks
What it shows
Items requiring on-site verification, status: open → assigned → checked → confirmed/rejected.
What to say
"For anything you can't resolve from the office. Driver visits the site, photographs, decides."
Expected
Status tabs with counts. Detection-id column deep-links back into QA. CSV export available.
6. Maintenance planner dashboard
/dashboards/maintenance-planner
What it shows
High-severity defects + hotspot view + recommended next actions.
What to say
"Maintenance planners see what to fix this week."
Expected
KPI tiles + ranked defect table.
7. Reports + exports
/reports
What it shows
CSV / GeoJSON / HMDIF-subset / Field-check CSV / PAS-style. Browser-side processing.
What to say
"Outputs go straight to GIS, contractors, or council reporting. No server round-trip."
Expected
Filters set; pre-flight modal appears before each download with row counts + warnings.
8. PAS 2161 readiness
/reports/pas2161
What it shows
Live readiness checklist + PAS-style CSV export with __GAP columns for missing fields.
What to say
"We're honest about what we can and can't claim. PAS 2161-style today, not certified compliant."
Expected
Checklist with green/amber/red rows. Honest "not certified" disclaimer is visible.
9. Network coverage
/network
What it shows
Drives + distances + honest banner about needing a road-network baseline.
What to say
"For full network coverage we need an OS MasterMap import. Until then, drive distance is the honest number."
Expected
Honest banner + drive list with distance/duration metrics.
10. In-product help
/help
What it shows
Searchable + role-filtered help with 10 sections.
What to say
"Pilot users can self-serve. We don't want every council to call the supplier."
Expected
Search filters topics live; role selector hides irrelevant sections.
11. Mobile install (indoor E2E start)
/install
What it shows
APK download + indoor walkthrough entry point.
What to say
"Sideload the APK on an Android device, sign in with TRYME001, then walk through the office tap-logging some demo detections."
Expected
APK link works; mobile indoor E2E is documented in MOBILE_INDOOR_E2E_GUIDE.md (no fresh APK needed during the May EAS quota freeze).
Wrap-up: what's next?
RoadEye is open-source and free-tier hosted. The next step for any interested authority is a 1-3 km constrained outdoor pilot — single street, one device, server provider with the HF pothole model. The pilot guide is in /help → "Driver mobile app guide".