Pre-condition streetworks intelligence: the audit-ready check most software skips

Every UK utility contractor has had this conversation: a crew arrives on site to find another contractor's traffic management already in place, a permit clash they didn't know about, or an urgent works notice in the same area that nobody had checked.

The crew sits idle. The supervisor makes calls. The client wants to know what happened. The day is lost.

This is preventable. The data is there. Most software just doesn't use it.

 

What pre-condition streetworks intelligence is

A pre-condition streetworks check is the act of querying external streetworks data — permits, road closures, urgent works, scheduled traffic management — for the area around a planned site, before crews are deployed.

Done properly, the check:

•       Pulls live data from the relevant Streetworks Register sources (e.g. the DfT open data, regional Street Manager systems).

•       Identifies any permits, closures, or urgent works within a configurable radius of the planned site (typically 100-500 metres).

•       Flags potential conflicts — clashing time windows, overlapping traffic management zones, scheduled urgent works that affect access.

•       Records the check itself, with a timestamp and the planner's review, as audit-ready evidence of due diligence.

•       Optionally enforces the check — preventing assignment of crews to a site until a pre-condition note has been recorded.

 

The mechanics are simple. The data is open. The integration is moderately complex but well within the scope of any serious utility software.

Why don't most platforms do it? Three reasons.

 

Why most software skips this

Reason one: international FSM platforms don't have access to the UK Streetworks Register the way UK-specific software does. They model permits as a user-entered field rather than a live data source.

Reason two: it's optional under NRSWA. The Act requires you to coordinate; it doesn't specify the mechanism. Software that records permits has technically met the bare regulatory requirement, even if it doesn't help you avoid clashes.

Reason three: pre-condition checks generate work. They surface conflicts that schedulers then have to resolve. A platform without pre-condition intelligence looks simpler in a demo because nothing is flagging up.

All three reasons explain why the feature is missing from most platforms. None of them are good reasons from the operator's point of view.

 

The cost of skipping it

Industry estimates of conflict-clash cost are hard to pin down, but the categories are clear:

•       Wasted journeys. Crew and plant arriving at a site they can't work, then redeploying.

•       Idle time. Crews on standby while supervisors negotiate with other contractors or the Street Works Authority.

•       Permit penalties. Working outside the agreed window because the planned window collides with another permit.

•       Client friction. Clients who expected a job to start on time and now have to be told why it didn't.

•       Reputation. Site managers who develop a reputation for clashes don't get the next job.

 

Even a conservative estimate puts the cost of a single clash incident at £500-£2,000 in direct waste, before reputational and downstream effects. A contractor running 50-100 sites a week, hitting 1% clash rate, is looking at £25,000-£100,000 of preventable waste per year.

 

What audit-ready evidence looks like

A pre-condition check is more than a clash-prevention tool. It's audit evidence.

Under NRSWA, contractors must coordinate. If a clash incident becomes a complaint, an inspection, or worse, the question from the Street Works Authority will be: "what did you do to avoid this?"

"We always check" is a weaker answer than "the system recorded a pre-condition check on this date, by this planner, finding the following nearby works, with this planner's note explaining how we proceeded".

The evidence is the audit trail. Software that doesn't record the check at all leaves contractors with nothing to point to. Software that records it as a structured note, linked to the site, with timestamps and planner identity — that's the evidence Street Works Authorities accept.

 

How UtilityWorkx handles pre-condition checks

UtilityWorkx includes pre-condition streetworks intelligence as a native feature, not a bolt-on. When a planner opens a site for crew assignment:

•       The system queries our streetworks-service for nearby external works, automatically scoped to the site's coordinates and the planned work window.

•       Permits, closures, and urgent works within the configurable radius are displayed on a map alongside the planned site.

•       The planner reviews and records a pre-condition note — what was found, what's the plan, any mitigations agreed.

•       The note is captured in the site's audit trail with planner identity, timestamp, and the reviewed data.

•       Optionally, the company can configure pre-condition checks as mandatory before crew assignment is permitted.

 

Streetworks data is bundled into the platform with no per-call or per-permit charge. The check takes seconds. The audit trail it produces is defensible.

 

Where this fits in the bigger picture

Pre-condition streetworks intelligence is one of several features in UtilityWorkx that we built because we'd been on the wrong side of the absence of them. Honest compliance badges. Four-eyes finance approval. Immutable audit trails. Plant-to-person compliance enforcement.

None of these features are dramatic in a demo. None of them are the first thing you'd put on a marketing page. All of them save real money and real friction in real operations.

UtilityWorkx was built by people who've been on UK utility sites for decades. We built the features we wished we'd had. If you've ever sent a crew to a site only to find another contractor's TM in the way — UtilityWorkx is in early commercial release and we're taking on a small number of founding customers before broader rollout.