STRATALStart with a representative utility work order
A utility programme can depend on the availability of a competent gang, the right plant, permissions, controlled documents and access to the work location. A status on a schedule is useful only when the people responsible can see those dependencies. Choose a typical job and an exception case before comparing suppliers.
Ask the supplier to demonstrate who owns each dependency, how a blocker is recorded and how the planner knows that work is ready to release.
Connect resource planning to mobilisation
Workforce management for utility contractors needs to reflect competencies, gang composition and availability as well as dates. Review vehicles, plant and supporting job information alongside the allocation. A change to one dependency should be understandable to the supervisor responsible for delivery.
During evaluation, move an allocation and follow the change into the field workflow. Check the supported approach to notifications and interrupted connectivity; do not assume every action is available offline.
Keep permits and streetworks in context
Where streetworks or permits apply, their state should be visible in the context of the work that depends on them. Establish which provider connections are supported, what information is exchanged and which approvals remain with the responsible authority or team.
Request a demonstration of a delayed permit decision and an amended planned start. Agree how those exceptions are owned and reviewed rather than relying on a separate spreadsheet to reconcile the plan.
Make evidence usable for assurance and handover
Photographs, checks, controlled drawings and completion records are most useful when they remain linked to the job. Review how the field team records evidence, how a reviewer identifies missing items and how corrections are returned to the right person.
Test a job that is physically complete but has an outstanding defect or evidence requirement. The distinction between site progress, assurance acceptance and handover readiness should be clear.
Bring the commercial team into the same evaluation
Operational completion and commercial readiness are different decisions. Commercial reviewers need to reconcile delivered quantities, supporting evidence and variations before preparing an application or closeout discussion.
Follow one delivered item through its evidence and review history. Ask how a disputed quantity or changed scope is represented, who can amend it and what remains visible for the final account.
Agree a pilot and an acceptance record
Define the users, sample jobs, devices, source data and interfaces needed for a meaningful trial. Include planning, site supervision, assurance, commercial and IT representatives so that no single team accepts a workflow on everyone else’s behalf.
Record each requirement as demonstrated, needing clarification or outside the agreed scope. Name an owner for open questions and agree which dependencies must be resolved before wider rollout.
Evaluate your utility delivery workflow.
Bring a representative programme and the questions your teams need answered.
Request a utilities demonstration →