Why we built a compliance badge that doesn't lie

Here's a story from our own testing — and the bug it surfaced — that changed how we think about compliance in UtilityWorkx.

We were running through a pre-release test scenario on a sample project. Multiple sites, multiple operative assignments, full training records loaded into the platform. The project dashboard showed a satisfying row of green compliance badges. Every site, fully compliant.

Except one of those sites shouldn't have been green. We knew it because we'd built the test scenario specifically to break compliance — the required NRSWA Operative card for one of the operatives on site had expired three weeks earlier.

The badge was still green.

 

How the bug happened

The original implementation worked like this: when the system checked whether a site was compliant, it looked at the required skill set for the work, then asked "does anyone in the company hold these skills, valid today?"

That sounds right. It isn't.

If the company employed 50 operatives and any one of them held a valid NRSWA card, the check passed. The fact that the specific operatives assigned to this specific site didn't include any of those qualified people was invisible to the compliance check.

Worse: inherited skills made the problem harder to spot. If a job role implicitly required a skill, and one operative in that role held it somewhere in the company, the requirement was treated as satisfied across all sites where that role was deployed.

This is a classic enterprise-software bug. It's not malicious. It's not even obviously wrong on a first read. It's the result of optimising for "the dashboard is green" rather than "the work is genuinely compliant".

 

Why most platforms have this bug

In our experience, this isn't unique to our first draft. Many compliance dashboards across the utility software market display green when the required skill exists somewhere in the system — not when the specific operatives on the specific site genuinely hold it.

The reason is partly technical. Checking the universe of "anyone qualified" is much cheaper than checking "this exact assignment, today, with valid expiry". The first is a simple existence query; the second is a join across assignments, operatives, skills, and expiry dates that has to run frequently and quickly.

The reason is partly cultural. Compliance dashboards are designed to be reassuring. A green tick is satisfying. A red flag generates work. Software vendors are rewarded for green ticks, not for honest red flags.

 

What we did about it

We rewrote the compliance check from the ground up. The new version asks a different question: "are the specific operatives genuinely assigned to this specific site qualified, today, with valid expiry, for the work being done?"

Specifically, the badge now considers:

•       The skill requirements derived from the work itself (not from an abstract role definition).

•       The specific operatives assigned to this site, today.

•       Each operative's actual held skills, with current expiry dates checked.

•       Plant-to-person compliance — whether the right operatives are matched to the right plant they're operating.

•       No inheritance shortcuts. No fallback fudges. No "someone in the company holds it" exceptions.

 

Green means: every required skill is genuinely held by the people on this site, with valid expiry, plus plant-to-person checks pass. Anything less than that, and the badge tells the truth.

 

Why honest compliance matters more than reassuring compliance

A dashboard that lies is worse than no dashboard at all.

If the dashboard says compliant and the work isn't, the operations director loses the ability to catch the problem before it becomes an incident. The supervisor turns up to a toolbox talk and discovers the issue moments before crews deploy — or worse, doesn't discover it and the audit finds it weeks later.

Honest compliance is harder to ship. It generates more red flags. It produces uncomfortable conversations. It makes the dashboard look less impressive in a sales demo.

It also catches actual compliance problems before they become incidents. Which is the entire point of the dashboard.

 

The wider principle

This isn't just about compliance badges. It's about a wider design principle in UtilityWorkx: the system should tell the truth, even when the truth is inconvenient.

Examples elsewhere in the platform:

•       The finance approval workflow flags when a creator has approved their own budget, rather than letting the rule slide.

•       The streetworks pre-condition check records that the check happened — including when no nearby works were found, which is also evidence.

•       The audit ledger captures every change to every value, including the changes that make a record look better.

•       Cold archive doesn't delete operational data — it preserves the audit trail even when files are cleared from active storage.

 

Honesty in software is a design choice. It costs more to build, generates more support questions in the short term, and pays back over years in trust.

UtilityWorkx was built by people who've been on the receiving end of compliance audits. We know what it feels like to discover, mid-audit, that a system was protecting a green dashboard rather than your actual operations. We built UtilityWorkx the way we wished our previous systems had been built.

If that resonates — UtilityWorkx is in early commercial release, taking on a small number of founding customers. Worth a 20-minute live demo if you've ever cursed at a dashboard that lied to you.