Purpose
Reduce reporting noise and improve the quality of right-of-way issue intake before it reaches public-sector teams.
Explainer-ready
Verified reporting
StreetWatchTO
A lightweight field-data pipeline designed to improve right-of-way reporting quality before issues reach public-sector teams.
Review fitRight-of-way and public-realm operations
Pilot typeVerified field-data pipeline
Core measureCompleteness, duplicates and routing quality
Decision pathRoute, refine or stop
What the pilot tests
Whether verified reporting produces cleaner operational intake.
The model combines planned routes and structured evidence with QA and duplicate filtering before a weekly routing summary is prepared.
Pilot structure
Planned patrol routes, photo capture, GPS location, timestamp, standardized categories, QA checks, duplicate filtering and weekly summaries.
Who reviews it
Right-of-way operations, public-realm maintenance, 311-adjacent intake teams or corridor-management groups.
What gets measured
Submission completeness, duplicate removal, time-to-forward, issue distribution and weekly routing quality.
Review-ready outputs
A structured record from route to routing summary.
- Planned patrol routes
- Standardized photo and GPS capture
- Issue categorization rules
- QA and duplicate filtering logic
- Weekly operational summary
- Route, refine or stop recommendation
Decision supported
Whether verified reporting improves triage quality and reduces avoidable repeat visits.
This is an independent pilot concept prepared for public-realm review. No endorsement or adoption is implied.