Most compliance software is sold on the same promise: one place for records, automatic reminders, reports when you need them. For utilities that promise is necessary and nowhere near sufficient. A distribution business does not fail an audit because a certificate was missing from a folder. It fails because nobody could show who assessed the operative, who authorised them, and what that authorisation actually covered.
This guide covers what to test when your shortlist is utilities-specific. If you want the general evaluation framework first, our training records software overview sets out the fundamentals that apply to any sector.
The criteria that separate utilities platforms
Does it model authorisation, or only certification?
This is the fastest way to sort a shortlist.
A certification is a thing a person holds. An authorisation is a permission somebody granted them, for specific work, after an assessment. The two behave differently. A certificate has an issue date and an expiry date. An authorisation has an assessment behind it, a sign-off that granted it, a scope, and a review cycle.
Ask any vendor to show you an authorisation record where the assessment and the authorisation are distinct, evidenced steps, with the employee’s own acknowledgement captured separately again. If the system records all of that as a single “approved by” field, it is storing certification and calling it authorisation.
Does it cover NERS, GIRS and WIRS properly?
The UK utilities schemes carry their own requirements, and a platform built for general industry will not know them. Competency Cloud provides full NERS, GIRS and WIRS certificate lifecycle management, from creation through assessment, authorisation and employee sign-off.
The practical question is not whether a vendor recognises the acronyms. It is whether the system reproduces the workflow: creation, assessment, authorisation and employee acknowledgement, each captured digitally and each retained.
Can it show the full history behind a record?
Auditors do not only ask what is true today. They ask to see how a record got to where it is.
That means every certificate and training item ever added against a person, the completion and expiry dates attached to each, and who uploaded it, retained rather than overwritten when the next renewal lands. Ask how far back the history goes and whether anything is purged on a schedule. Competency Cloud stores records indefinitely, so a worker’s profile shows every item ever recorded against them, with the dates and the person who added it.
How does it handle annual review at scale?
Reauthorisation is the workload that catches utilities businesses out. It is not one renewal date in the future, it is a rolling programme across a distributed workforce, each with a different anniversary.
Look for automated alerts with enough lead time to schedule the assessment rather than discover the lapse, and check whether you can set those lead times yourself rather than accept fixed defaults. Competency Cloud lets you configure renewal notifications to whatever intervals suit your programme. Also check whether a certificate can be regenerated once the subsequent sign-off is captured, rather than rebuilt by hand. Our guide to utilities authorisation tracking covers the mechanics in more detail.
Does it work for a workforce that is not in the office?
Utilities work happens at the point of supply, not at a desk, and compliance data goes stale in the gap between the two.
Test whether a supervisor can view and verify a worker’s records from site, and whether an operative can reach their own record and complete assigned training from a phone. Access to a dashboard through a mobile browser is not the same thing as being able to do the work remotely.
Can it hold site-specific requirements without fragmenting?
Most utilities businesses run different requirements across regions, depots or client contracts. The common failure is a system that forces one standard everywhere, or one that fragments into separate instances nobody can report across.
What matters is whether site-specific controls can be applied where they are needed while leadership keeps a single consolidated view. Competency Cloud is built for multi-site operations, so compliance requirements, certification matrices and workforce data across every location sit on one centralised platform. Ask any vendor to show you both pictures, local and national, from the same data.
Does it separate competency from authorisation, and connect the two?
These are two different things, and a platform worth shortlisting treats them as such.
An authorisation certificate records what an individual has been assessed as competent to do and issues them permission for those specific activities. Two operatives assessed on the same day can hold very different authorisations, one cleared for high voltage work and the other for low voltage only, each with their own certificate listing the activities they can carry out.
A competency framework works the other way round. It defines the mandatory requirements for a job role, then runs across your workforce to show who meets them and who does not. That is what turns a collection of certificates into an answer to the question “can this person do this job”.
Ask to see both, and ask what happens when a framework is run against somebody whose authorisations do not cover the role.
A shortlist test
One exercise separates platforms quickly. Ask each vendor:
Show me an operative whose authorisation lapses next month, the assessment that supported the current one, who signed it off, and what happens automatically between now and the expiry date.
A system built for utilities answers that from one record. A general compliance platform will show you an expiry date and leave the rest to your team.
Where to start
If you are earlier than shortlisting, our utilities compliance overview sets out how authorisation tracking, training records and competency fit together for a distributed workforce.
When you are ready to see how Competency Cloud answers the questions above, book a demo.