Job-planning operations guide
How to turn Street Manager roadworks data into a practical job-risk workflow
Roadworks data becomes operationally useful when it is compared with a real job location and date. The objective is not to show every roadwork in England. It is to reduce the number of relevant access risks a planner has to find manually.
The Department for Transport says roadworks data entered into Street Manager is available for public viewing free of charge through an API and registration.
A saved job with a usable location, working date and customer context.
A nearby, time-relevant received roadworks event that deserves review.
A planner verifies the event and chooses whether to reroute, reschedule or monitor.
1. Start with the job, not the national feed
Relevance depends on place and time
A national roadworks stream is too broad for a useful daily workflow. A saved job narrows the question: could a received event affect access to this customer location during the planned service window? The result is a review queue, not an automatic route instruction.
2. Save enough context to make the alert actionable
The minimum useful job record
| Field | Why it matters | Good practice |
|---|---|---|
| Customer and site | Lets the planner identify the affected commitment. | Use a business or service-site label, not unnecessary personal data. |
| Postcode or location | Provides the geographic basis for matching. | Check accuracy before relying on proximity. |
| Planned date | Filters out works that do not overlap the visit. | Update the date when the job moves. |
| Internal reference | Connects the alert to the dispatch or CRM workflow. | Use a non-sensitive operational identifier. |
| Notes and status | Records the decision and prevents duplicate review. | Keep notes factual and time-stamped. |
3. Triage rather than panic
A three-level review model
- AMonitor.
The event is nearby or potentially relevant but does not yet justify a plan change. Recheck closer to the visit.
- BConfirm.
The timing and location overlap enough to check the source, customer access information or local authority detail.
- CAct.
A verified restriction affects the planned service. The responsible operator decides whether to reroute, change timing or contact the customer.
4. Measure whether monitoring changes operations
Useful JobGuard measures
Scheduled jobs with sufficient location and date data for comparison.
Received events that pass the system's location and time criteria.
Matches confirmed by an operator as affecting a planned job.
Reroutes, timing changes, customer updates or monitoring decisions captured in the workflow.
FleetStart JobGuard supports triage. It is not a navigation service, a safety authority or a guarantee that every restriction, delay or access condition is represented.