# Field work order close-out

> Field work order close-out: Work done as recorded; billable Checked: cross-checked. Produces closed orders, rework.

Source: https://www.sumarity.ai/library/field-work-order-close-out/

Energy and utilities 

# Field work order close-out

Reads work orders, photos, parts used. Produces closed orders, rework. Code works out every figure, the Judgement Engine answers the narrow questions, and whatever stays uncertain goes to a person.

Cross-checkedBilling and revenue assurance
Start from this workflowMore for energy  

What it decides

## Narrow questions, each with a check behind it.

Work done as recorded; billable
Cross-checked: photos, parts. A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides.

| Reads | Work orders, photos, parts used 
| Produces | Closed orders, rework 
| Who signs | A person on your team, with every figure traced to its document and every call on record 
| Process | Billing and revenue assurance 
| Industry | Energy and utilities    

See it run

## Every line, decided where it's safest.

An example run. Each stage lights up as a line is decided there; pick a stage to see its lines.

ReadsWork orders, photos, parts usedCodeReads, matches, ties out and works out every figure.JudgementWork done as recorded; billable. Settles only when it clears the cutoff and a second source agrees.A personGets whatever stays uncertain, with the evidence. Their ruling tunes the next run.ProducesClosed orders, rework  
Field work order close-out · example run Example run  

| Ref | Item | Value | Decided by  
| WO-901 | Meter exchangePhoto and new serial recorded |  | Code · complete 
| WO-902 | Line repair, 3 hParts match the job · 0.93 |  | Engine · cross-checked 
| WO-903 | Visit, no accessBillable call-out? · 0.70 |  | To a person 
| WO-904 | InspectionChecklist complete |  | Code · complete 
| WO-905 | Extra parts usedFault type explains them · 0.90 |  | Engine · cross-checked  
|  

Settled 4 To a person 1 Settled wrong 0      Illustrative lines. Amber rows are the Judgement Engine's calls; each settles only above its cutoff and when its check agrees.    

What it could save

## Your volumes in. Your hours out.

In our tests, between 24% and 42% of items still went to a person after tuning. Set your own share; a pilot measures it on your data.

Items per run 
Runs per month 
Minutes per item by hand 
Cost per hour

Share of items that still need a person: 30%  

By hand today80 ha month 
With Sumarity24 ha month, for the items people decide 
Saved56 hCHF 53,760 a year    

Related

## Start from what's closest.

### Billing and revenue assurance in other work

Asset management

### Management and performance fee check

Fee basis, rates, periods

Proven by codeHealthcare

### Charge capture reconciliation

Services delivered vs billed

Proven by codeRetail and hospitality

### Supplier rebates and promotional allowances

Rebate earned under which agreement

Proven by code

### More for energy

### Meter-to-bill validation

Reading plausible; bill right

Vetoed by code

### Energy trade confirmation matching

Our trade vs the counterparty's confirmation

Proven by code

### Renewable certificate reconciliation (REGOs, GOs)

Certificates vs generation and sales

Proven by code  

Questions

## What buyers ask

What happens when Sumarity isn't sure?

Nothing settles below the cutoff, or when the check disagrees. The item goes to a person in the inbox with what the engine saw, its best answer and the runner-up. The person's ruling is kept and tunes the next run.

How are its judgements checked?

A second source has to agree: a register, a contract, a list. When it does the judgement settles; when it doesn't, a person decides.

Can we change it to fit how we work?

Yes. Start from this workflow and describe your differences in plain words. The design assistant revises it, the validator checks it, your expert reviews it on the canvas, and your admin publishes it.

Does it read our files as they are?

Yes: spreadsheets and CSV in any layout, PDFs, bank formats and e-mail attachments. Sumarity suggests how each column maps, proves the mapping on a sample and remembers it once a person confirms it.

Where does our data go?

Sumarity runs in Zurich. Your data, backups and logs are stored in Switzerland.

How does it get better?

Your team's rulings become an answer key. Better questions and cutoffs are proposed, tested on data they haven't seen, and published only when your admin approves. It improves itself, with permission.

## Start from this workflow. Run it on your data.

A pilot runs alongside your own process for a few weeks, at our cost, and ends in a line-by-line comparison.

Talk to usBack to the library