qAI agent for utility work orders
AI agent for utility work orders: who approves each step
An AI agent for utility work orders carries an inspection finding to a closed job. The planner approves spend and the crew lead signs the field ticket.
3 min readRunning it, Agent design
by Grisha Pertaia
- session
- credential
- write
- intake
- route · human review· sent for review
- write
- sign
- intake
- intake · refused· outside permission
An inspection finding starts a chain of office work. The finding becomes a work order. The work order needs a part, a contractor and a job pack. The crew does the job and signs the field ticket. The contractor's invoice has to agree with that ticket before anyone pays it.
An AI agent for utility work orders can carry each of those steps across your business systems. The question this post answers is narrower: at each step, does the agent act, does a person approve, or is the step refused?
The workflow is designed. It has not run in the sandbox yet. The steps below are how we build it in a pilot, and the energy page shows it beside the other energy and utility workflows, with the state of each.
What the agent touches, and what it never touches
The agent works in documents, the maintenance system, purchasing, email and accounting. It does not work in the control room. Operational technology stays outside the permission for every job, and we do not connect agents to it. Everything below happens in the business systems around the field crew.
Four places a wrong action costs money
Each is a step below, with a fixed answer: allowed, sent to a person, taken out, or refused.
The workflow, from finding to closed job
- Step 1
A credential for one asset
The agent takes the inspection report and receives a credential for this asset and this job only.
- Step 2
The finding read
It reads the finding, the photos and the asset reference in the report.
- Step 3
Work order opened
It opens the work order in the maintenance system and links the report to it.
- Step 4
The planner approves the part
A replacement part above your spend threshold waits until the maintenance planner approves it.
- Step 5
Job pack sent, checked on the way out
The job pack goes to the contractor. Customer names and account numbers are taken out before it leaves.
- Step 6
Early close refused
The agent tries to close the work order before the crew lead signs the field ticket. The step is outside the permission, so it is refused.
- Step 7
Invoice matched
The contractor invoice is matched to the signed field ticket, and each difference is flagged for the controller.
Below the threshold you set, the agent drafts and routes the order. Above it, the planner approves, as today. The record shows which side each order fell on.
Why the early close is refused, not just flagged
A closed work order is a statement that the job is done. The office cannot know that until the crew lead signs the field ticket. So the permission for this job allows a close only after that signature is on file. Before it, the step is refused, and the reason goes on the record: no field sign-off.
That is a different control from an alert. An alert tells someone that a rule was broken. A refusal means the rule was never broken. The work order stays open, and the record shows the attempt.
The maintenance work order workflow applies the same idea to the permit. The agent may read a permit and its state, so the supervisor knows whether one is open. It may not mark an isolation as done, because that is a statement only the person who isolated the equipment can make. The step is refused.
Who approves what
- allowed
Reads the report, the photos and the asset reference
- allowed
Opens the work order and links the report
- redacted
Takes customer details out of the job pack before it leaves
- allowed
Matches the invoice to the field ticket and lists each difference
- refused
Closing the work order before the field sign-off
- human review
The maintenance planner approves spend above the threshold
- human review
The crew lead signs the field ticket
- human review
The controller decides on each invoice difference
The agent does not settle an invoice difference, and it does not approve a payment.
Contractors on the other side
Much field work is done by contractors. Each contractor receives only the pack for its own job, with customer data taken out. Tickets and invoices come back the same way. The record shows what was sent, what was removed and what came back.
What you can check
The record holds one line per step, from the credential to each invoice difference, with the planner's name on the part and the reason on the refused close. A regulator or an auditor can check that record with the open verifier, without us. The guarantees page explains how a step waits for a person and where that control stops.
The workflow can run on one machine in your own building, with the record kept on site. Local models differ from the largest cloud models, and we say which runs where. See deployment.
What it does not do
- It does not operate control systems or touch equipment.
- It does not decide which spends or closures need a person. Your supervisors set the thresholds.
- It does not diagnose a fault or judge a repair. Your crews do.
- It has not run in the sandbox yet. The closest run today is requisition, where an order above the threshold waits for a person.
Related notes
- illustration
- session
- credential
- write
- notify
- notify
- file
3 min read
AI agent for late shipments: what the planner approves
An AI agent for late shipments works a delay note through to the customer update. The planner approves the new date, and an unapproved carrier is refused.
- illustration
- session
- credential
- write
- notify
- file · human review
- write
6 min read
Evidence, not logs: what an auditor can actually verify
A log is a file the operator controls. A trace adds structure, not independence. Evidence is a record more than one party confirmed before it was written, that an auditor can check against another copy without trusting the vendor.