Why generic field service software fails utility work

Generic field service management (FSM) software is sold to UK utility contractors every day. BigChange, ServiceNow Field Service, Salesforce Field Service Lightning, dozens more — all marketed as fits-everything platforms covering scheduling, dispatch, mobile capture, and customer management.

Some utility contractors adopt these tools and make them work. Many adopt them, struggle for two years, then either give up or limp along filling the gaps with Excel and WhatsApp.

This post is about why generic FSM software fails utility work — not because the software is bad, but because utility work has a shape that generic FSM tools weren't designed for.

 

What generic FSM software is good at

To be fair to the category, generic FSM software does several things well:

•       Dispatch and scheduling — assigning the right person to the right job at the right time. The original problem FSM was built to solve.

•       Mobile data capture — basic forms, photos, signatures, timestamps. Universal across most field work.

•       Customer management — accounts, contacts, jobs, history. CRM-adjacent functionality.

•       Standard reporting — utilisation, on-time arrival, jobs completed. Operational dashboards.

•       Integration breadth — most generic FSM tools have hundreds of integrations to accounting, CRM, payroll, and mapping systems.

 

If your business is electrical maintenance for commercial buildings, or HVAC servicing for a national chain, or appliance repair for consumers — generic FSM software is probably what you want. The shape of the work fits.

 

Where utility work breaks the model

Utility work has six characteristics that generic FSM tools handle poorly or not at all.

Streetworks compliance

NRSWA permits, Section 50 inspections, traffic management plans, reinstatement evidence — none of this exists in a meaningful way in generic FSM software. At best, you get a permit number field. At worst, you bolt on a separate streetworks tool and reconcile the two systems manually. The gap is structural: NRSWA is a UK-specific regulatory regime that international FSM platforms have no incentive to model deeply.

 

The variable unit of work

Utility contractors run jobs that span from £200 microsite reinstatements to £2m civils projects. Both are "sites" but they need radically different handling. Microsites in volume need lightweight dispatch and minimal admin. Civils need full project structure, multi-phase scheduling, finance integration.

Generic FSM tools model jobs at a single level. You either treat every reinstatement as a full project (and the system groans under thousands of trivial records) or you treat every project as a job (and lose the structure for anything serious).

 

Plant-to-person compliance

In utility work, the operative isn't just doing a job — they're operating regulated plant on a public highway under specific compliance regimes. The right operative needs to be matched to the right plant, with valid training, every time. Generic FSM tools track operators and equipment as separate entities; they don't model the compliance-enforced relationship between them.

 

Subcontractor and client access

Utility work often involves subcontractors working under the main contractor's frameworks, plus clients who need visibility into their own work without seeing the contractor's other business. Generic FSM tools handle this as full multi-tenant user separation (expensive and complicated) or simple access controls (data leaks across boundaries).

 

Geospatial precision

Sub-metre RTK GPS positioning, as-built records that satisfy asset owner standards, geospatial queries against utility infrastructure — these are core capabilities for utility work and afterthoughts in generic FSM tools.

 

Audit defensibility

Utility work happens in a regulated environment. NRSWA audits, asset owner audits, internal audits, regulator enquiries — all require defensible evidence months or years after the event. Generic FSM tools have audit trails; they don't have audit-grade evidence retention engineered for adversarial scrutiny.

 

Why this isn't fixable by adoption

Some operations directors believe they can adapt generic FSM software to utility work through configuration. Sometimes they can — to a point. The platforms are flexible, custom fields and workflows are possible, and skilled implementation partners can get a long way.

But beneath the configuration sits the data model. The data model is the limit. If the platform models a job as a single thing with one assigned operative, you cannot configure your way to multi-operative shifts on the same site with role-based compliance checks. If the platform doesn't model permits as first-class objects, you cannot bolt them on without parallel systems.

The configuration approach also fails the audit-defensibility test. Custom fields can be edited. Configured workflows can be bypassed. The audit trail records what happened in the configured workflow — but doesn't enforce the workflow itself.

 

What works instead

Vertical-specific software, built for the actual shape of utility work, with the right concepts as first-class objects in the data model:

•       Projects, schemes, sites, microsites — with the appropriate hierarchy and tooling for each level.

•       Permits and streetworks compliance as first-class concerns, not user-defined fields.

•       Plant-to-person compliance enforced at assignment time, not reported on after the fact.

•       Subcontractor and client scoped access without full multi-tenant complexity.

•       Audit-grade evidence retention designed for regulatory and adversarial scrutiny.

 

UtilityWorkx was built specifically for the shape of UK utility work. We're 42 years of utility experience deep. We've used the generic FSM tools, hit their limits, and built the platform we wished we'd had.

If your operation has outgrown generic FSM software — or you're evaluating it for the first time and want to understand whether it'll actually fit — UtilityWorkx is in early commercial release. We're taking on a small number of founding customers before broader rollout.