Work Order Auditor
Finds the missing photo before the invoice bounces, not after
- 8hard rules
- Things it must never do, enforced in every run
- 5handover rules
- Conditions where it stops and gives the work to a person
- 7output fields
- A structured result, not a paragraph you have to re-read
- ≤5steps per run
- Bounded work: at most 4 tool calls, enforced by the runtime
Read-only by design. This agent has no path to sending, spending, publishing or committing anything. Where that limit is the product, removing it would remove the reason to trust the output.
Overview
Field service businesses do not get paid late because of pricing. They get paid late because a job report is missing a before photo, a signature, a serial number, or a meter reading — the customer rejects the invoice and the money moves out sixty days.
Nobody catches it at the time. The engineer has driven away, the office sees a job marked complete, and the gap surfaces when the invoice bounces weeks later.
This agent reads what your contract or SLA requires as evidence of completion, checks each job report against it, and reports exactly what is missing per job — while it is still same-day and an engineer can still return or send a photo. It also flags jobs closed inside the SLA window on paper but without the evidence to prove it, which is the version that fails an audit. It invoices nothing and closes nothing.
Benefits
Invoices that do not bounce
The commonest reason field service cash is late.
Fixable while the engineer is nearby
Same-day beats same-quarter.
Evidence for an SLA claim
Or honest notice that you do not have it.
What it does
Checks against your contract
What that customer requires as evidence, read from your knowledge base — not a generic checklist.
Same-day, while it is fixable
A missing photo found today costs a message. Found in sixty days it costs the invoice.
Separates missing from unreadable
A photo nobody took and one nobody can read are different problems with different fixes.
Checks SLA evidence, not just SLA dates
A job marked complete in time without evidence of completion fails an audit.
Finds the recurring gap
The same field missing across many jobs is a process problem, not an engineer problem.
Invoices nothing
It reports readiness. Billing and closing stay with a person.
What this changes
What this changes about your week
- It takes over
- Checking every job report has the evidence the contract requires before you invoice.
- Done today by
- The office, weeks later, when the invoice bounces.
- How often
- Every job, every day.
- Typical manual effort
- Checking a day of job sheets against contracts is an hour.
Why Field Services in particular. Field services are not paid late over pricing. A missing photo found today costs a message; found in sixty days it costs the invoice.
Runs unattended
Started by you or by an event, and it finishes on its own. Nothing waits for someone to be at a desk.
The same standard every time
The two-hundredth item is held to the bar the first one was. Consistency is the part people cannot sustain.
It cannot act on its own
Work Order Auditor has no path to sending, spending or committing. That limit is why its output is safe to act on.
How it runs
This agent runs server-side through the PROMIVO runtime. Each run is logged step by step and every tool call is permission-checked before it executes.
- 1InputValidated against the agent input schema
- 2Modelclaude-sonnet-5 with automatic fallback
- 3Toolssearch_knowledge, extract_structured_data
- 4PermissionsRuns READ actions automatically; anything higher waits for approval
- 5OutputStructured result matching the output schema
- 6LoggingTokens, duration and every step recorded
Demo
Demo dataIllustrative sample output, abridged.
Input
{
"jobs": [
{
"report": "…",
"reference": "WO-7741"
}
],
"customer": "City Facilities"
}Output
{
"jobs": [
{
"slaMet": "unevidenced",
"fixNeeded": "One before photo. The engineer attended this morning and can supply it today.",
"reference": "WO-7741",
"requirements": [
{
"status": "missing",
"requirement": "Before and after photographs"
},
{
"status": "present",
"requirement": "Customer signature"
},
{
"status": "referenced-unverified",
"requirement": "Serial number of any part fitted"
}
],
"readyToInvoice": false
}
],
"escalate": false,
"disclaimer": "An evidence completeness check against the contract. No assessment of workmanship, no SLA compliance conclusion, and no invoice raised.",
"contractFound": true,
"processFindings": [
"Before photographs are missing on 14 of 38 jobs this week. That is a capture problem in the app flow, not an individual one."
],
"contractDocument": "City Facilities MSA — schedule 3, evidence of completion"
}Requirements
Integrations
No integrations required.
Before you start
- Completed job reports
- A knowledge base holding the customer contracts or SLAs stating evidence requirements
- Requires the Starter plan or higher
Use cases
End of day
Every job closed today, checked before invoicing.
Before a billing run
Find the jobs that will be rejected.
SLA reporting
Which claims you can actually evidence.
Pricing
Starter
Billed monthly through your PROMIVO subscription. Cancel at any time.
Runs consume your plan allowance for agent executions and tokens. See plan limits
FAQ
Does it look at the photos?
It checks whether the required evidence is recorded and referenced. Whether a photo shows what it should is a judgement for a person, and it says so rather than pretending to assess an image it was given as a filename.
Can it raise the invoice?
No. It reports which jobs are ready to invoice. Billing stays with a person.
What if the contract is not loaded?
It checks internal completeness only and says the contract check was not performed. Evidence requirements differ per customer, so there is nothing generic to assume.
Reviews
Reviews open once customers have run this agent.
Need this agent to work differently?
Tell us what to change and our team will scope a customised version for your business.
Customize this agent