SystemField Service & Work Management

Repeat Visit Analysis

Repeat visit analysis that names and prices why the first visit failed, then fixes tomorrow's jobs before the vans load

Meters fitted on the first visit, because every return visit has a cause and a cost.

See one case, screen by screen ↓
target90%first-time fix in meter operations, up from 83.0 % — the target the fixes are measured against
demoAED 639Ka yearof return visits traced to one cause: the wrong meter type on the van — 695 of 2,240
demoAED 1.23Ma yearof return visits the eight proposed fixes would avoid — 1,340 visits, the solution's own estimate
demo6.3 → 0.7visitsexpected return visits on tomorrow's 186 meter jobs, once the planner applies 9 changes before the vans load
The problem

Why the work order just says “rebook”

A crew arrives for a meter exchange and finds a 3-phase CT-connected board where the work order promised single-phase. The van carries no CT meter, so the technician writes a note in shorthand, closes the job as “Not completed – rebook” and drives on. The next visit brings a 3-phase direct meter. The one after that sends a technician without CT-metering authorisation. Every return visit is a van, a crew and a customer's day off, and the field service system records each one as the same closure code.

The reasons are there, but in places nobody joins: free-text notes, the van loadout from 06:40 that morning, the skills register, the access log, a connection file from 2019 that never reached the meter register. First-time fix arrives as one average — 83 % — and an average has no owner. Stores, planning, training, asset data and customer operations each hold one piece of the cause, so the same failure is booked again tomorrow.

typical26%of field dispatches need a follow-up visit
typical$250–$500a visitfor a utility truck roll, at the conservative end
typical~89%first-time fix in best-in-class field service, against ~75 % on average
Where a month's repeat-visit review goes, in hoursestimated
By hand54 days
With the solution8.2 days
  • Finding which visits went back to the same premise or asset10 → 0.5 d
  • Reading technician notes, photos and closure codes12 → 1 d
  • Checking van loadouts, the skills register and connection files16 → 1.5 d
  • Pricing return visits by cause and job type4 → 0.2 d
  • Agreeing fixes with planning, stores, training and asset data8 → 3 d
  • Confirming causes and approving fixes4 → 2 d

Estimated split for one division's monthly review of return visits, in hours, by hand and with the solution.

How it works

How a return visit is explained

Six agents link, read, explain and price every return visit; the field service manager confirms the cause and approves the fix.

What comes in
Visits in38,400 jobs a year · notes, van stock, skills, records, complaints
Agents at work
Chain buildersame premise, 30 days
Then
Note readerwhat was found
Then
Cause finderwork order ≠ site ≠ van
Cost keeperAED per cause
Then
Fix recommender
Tomorrow checkerbefore the vans load
A person decides
Field service managerconfirms causes, approves fixes
What comes out
Cause and cost of every return visit
Fixes: kitting, skills, records
Tomorrow's jobs put right
One case, step by step

One meter, four visits, and the cause behind 695 more

Lumina Utilities is exchanging meters across its villa districts. In twelve months Meter Operations did 9,860 jobs and fixed 83.0 % on the first visit. Villa 14, Street 27, Saffron Gardens took four visits in 18 days. Here is how the solution explains it and stops the next one, screen by screen.

  1. 01Morning

    The board opens on chains, not an average

    Layla Haddad · Field Service Manager

    Layla runs Meter Operations: 62 technicians, 31 vans. Her board shows 1,672 chains, 2,240 return visits and AED 2.06M a year, every visit to the same premise or asset within 30 days linked into one chain. Across the top, a ribbon splits the return visits by why the first visit failed: wrong meter type 31 %, no access 21 %, skill mismatch 15 %, part out of stock 11 %, site not ready 10 %.

    “I know our first-time fix is 83 %. I don't know why, and I can't fix an average.”

  2. 02One click

    Wrong meter type on the van: 695 visits

    Layla Haddad · Field Service Manager

    Layla clicks the largest cause. The board filters to its chains: Villa 14 in Saffron Gardens, Villa 3 and Villa 22 in Palmgrove, Villa 41 in Lumina Hills — all 3-phase exchanges where the van came out without the meter the board needed. The longest chain ranks first, with a complaint against it.

    “Wrong meter type on the van · 695 return visits · AED 639,400 a year”

  3. 03Overnight, 02:04

    Four visits in 18 days, each in the technician's words

    Chain builder and Note reader

    Visit 1, 24 Aug: Rakesh Pillai, van MV-22, 22 minutes — “3ph CT op meter onsite. no CT unit on van. rebook w CT meter.” Visit 2: Imran Qureshi brings a 3-phase direct-connected meter; the site needs CT. Visit 3: the right meter, but CT isolation needs a CT-authorised technician. Visit 4, 11 Sep: Saeed Al Hammadi fits the LM-3P-CT and verifies the CTs, 1 h 40 min.

    Note reader: “3ph CT op” = 3-phase, CT-operated meter found.

  4. 0402:11

    The work order, the site and the van, side by side

    Cause finder

    The work order said LM-1P-60, single-phase direct, from meter register MTR-0098311, installed 2012. On site: a 3-phase board, CT-connected, CTs 200/5. On the van at 06:40: 8 × LM-1P-60 and no LM-3P-CT. The reason sits in connection file CN-19-07734: a load increase to 3-phase 150 A with CT metering, approved in March 2019 and energised in April, with the meter register update “not recorded”.

    Cause: wrong meter type on the van, 92 % confidence — every cause cites the record it rests on.

  5. 0502:12

    What it cost, and what argues against

    Cost keeper and Fix recommender

    Three return visits × AED 920 = AED 2,760, 65 minutes on site for nothing, complaint CMP-26-3381 and a customer who took leave twice. Other causes are ranked and answered: information missing or wrong at 6 % — the out-of-date register is why the van was wrong, not a separate failure; skill mismatch at 2 % applies to visit 3, not the first. The pattern is still ahead: 1,312 premises left in the exchange programme have a load upgrade newer than their meter record, 412 of them CT-metered.

    “1 of them is on tomorrow's list: WO-2615521, Villa 18, Saffron Gardens”

  6. 06Causes and cost

    Every cause priced by job type, with an owner

    Cost keeper

    The heat table splits 2,240 return visits by first-visit cause and job type, each cause with the team that owns it: planning and stores, customer operations, planning and training, stores, connections, asset data, planning. The largest cell is wrong meter type on 3-phase exchanges — 470 return visits, AED 432,400 — and it opens on the chains behind it.

    “Where the AED 2.06M goes · Cost keeper · 2,240 × AED 920”

  7. 07The fixes

    Eight fixes, each with the visits it would have prevented

    Fix recommender

    F1: load the meter type from the latest connection file, not the meter register — 560 visits, AED 515,200 a year. F2: write the 1,312 load upgrades back to the register. F3: send CT-metered premises only to the 14 of 62 technicians who hold CT-metering authorisation — 240 visits, AED 220,800. F5, a day-before text with a 2-hour window, has been live since 1 Sep. Each fix names its owner and the chains it would have prevented.

    “Proposed by the Fix recommender for each cause … You approve; the owner makes it live.”

  8. 08Approved

    Layla approves F1, and the effect will be measured

    Layla Haddad · Field Service Manager

    The approval shows the fix, the estimate — 560 return visits and AED 515,200 a year — and the owner, Arjun Menon in Planning. Layla signs as Field Service Manager. A change to dispatch rules also needs the Head of Field Operations, Khalid Rahimi.

    “The Cost keeper measures the effect from the next month's chains.”

  9. 0916:00

    Tomorrow's 186 jobs, checked for the same causes

    Tomorrow checker

    For Wednesday 14 October, 186 meter jobs on 31 vans are checked against last year's causes. Nine carry one. The first is WO-2615521 at Villa 18, Saffron Gardens: the register says LM-1P-60 (2012), connection file CN-20-01192 says 3-phase, CT 200/5, and van MV-22 has no CT meter — 88 % risk of a return. Others include a CT job booked to a technician without authorisation and a critical customer who needs 48 hours' notice of a supply interruption.

    “Add 1 × LM-3P-CT to van MV-22 and move the job to Saeed Al Hammadi”

  10. 10Before 05:30

    Nine changes applied before the vans load

    Arjun Menon · Work planner

    Arjun applies all nine changes. Expected return visits for tomorrow fall from 6.3 to 0.7, and the van lists are updated for the 05:30 loadout. The agents proposed every change; the planner made each one.

    “All 9 changes applied — van lists updated for 05:30”

Who it’s for

Built for everyone who sends, drives and answers for a visit.

The same return visits, seen by the five people they touch — what their week looked like, and what it looks like now.

LH
Layla HaddadField Service Manager, Meter Operations · confirms causes and approves fixes
Field Service Manager
Before
Runs 62 meter technicians and 31 vans through about 40 exchanges a day, with first-time fix as one number. “I know our first-time fix is 83 %. I don't know why, and I can't fix an average.”
Now
Opens chains ranked by length under a ribbon of priced causes, confirms or changes each cause, and approves fixes with the return visits and AED they would avoid.
AM
Arjun MenonWork planner, Meter Operations · builds tomorrow's runs and van lists
Work planner
Before
Builds tomorrow's runs at 16:00 and loads the van lists from the meter register. “If someone told me at four o'clock which jobs will fail, I'd fix them before the vans leave.”
Now
Gets the jobs that carry a known cause, with the evidence and the change that removes it, and applies them before the 05:30 loadout. Confirms causes the agents rate below 70 %.
RP
Rakesh PillaiMeter technician, Grade 2 · 7–9 premise jobs a day
Meter technician
Before
Arrives with what the work order and the van list say. “I drove to Saffron Gardens with a single-phase meter for a CT board. Nothing I could do.”
Now
His notes are read as written, shorthand and all, and the job he couldn't finish is traced to the record that sent him wrong. On tomorrow's list, the CT job on his run moves to a CT-authorised technician.
NS
Noura SalehCustomer Operations lead · owns complaints, callbacks and access fixes
Customer Operations lead
Before
Takes the call when a customer has been visited three times. “Three visits and nothing done is a complaint, every time.”
Now
Sees each complaint linked to its chain and its cause, and owns the access fix — a day-before text with a 2-hour window, live since 1 Sep.
SA
Saeed Al HammadiSenior technician · one of 14 CT-metering authorised technicians out of 62
Senior technician
Before
Is sent last, after the others could not finish. “Send me first and it's one visit.”
Now
CT-metered premises are matched to the 14 authorised technicians, and the van list shows what each van needs against what is loaded.
Built on the engine

6 agents. Each with one job, and hard limits.

Six agents link, read, explain and price every return visit; the field service manager confirms the cause and approves the fix.

Chain builder

Each night links every visit to the same premise or asset, in the same job family, within the 30-day repeat window into one chain. Planned multi-stage jobs, customer-requested reschedules and cancelled jobs are left out.

  • Never links visits at different premises
  • Read-only access to work orders — never changes one
Note reader

Reads technician notes, photo captions and closure codes, in shorthand English or Arabic, expands the shorthand (“3ph CT op” = 3-phase, CT-operated meter) and states what was found on site and why the job stopped.

  • Quotes the note it used
  • Never edits a note
Cause finder

For the first failed visit of each chain, compares what the work order said, what was found on site and what was on the van, and checks the skills register, the access history, the meter register and the connection files. Chooses one of the seven causes, with a confidence and the evidence against.

  • Every cause cites a record
  • Below 70 % confidence the planner confirms
  • Shows the evidence against
Cost keeper

Costs each chain as return visits × the loaded cost of a return visit (AED 920), plus any compensation paid, and rolls it up by cause, job type and division.

  • Uses only the rate set in Settings
  • Shows the working
Fix recommender

For each cause above 5 % of return visits, proposes the fix that removes it at the source — van kitting, skill routing, record correction, customer contact or stock — estimates the visits avoided from the chains it would have prevented and names an owner.

  • Never changes dispatch rules
  • The field service manager approves
Tomorrow checker

At 16:00 on working days checks every job for tomorrow against the known causes: meter type against the connection file, CT premises against authorisations, access history, van stock against need, slot length against median duration and customer notices. Proposes the change and the risk left.

  • Never reassigns a job or reloads a van
  • The planner applies
Field service manager

Confirms causes and approves fixes; the planner applies tomorrow's changes. The agents propose; a named person decides.

Ask in plain words

Ask why a job took more than one visit

Ask why a job took more than one visit, what a cause costs, or what to change before tomorrow. Every answer points to its records.

Why did Villa 14, Saffron Gardens take four visits?

The van was loaded from an out-of-date meter record. The meter register still shows a single-phase LM-1P-60 from 2012, but connection file CN-19-07734 approved a 3-phase CT supply in March 2019. Van MV-22 carried no CT meter; the rebooked visit brought a 3-phase direct meter, and the third sent a technician without CT authorisation. Three return visits, AED 2,760, and complaint CMP-26-3381.

What does the wrong meter type on the van cost us a year?

An estimated AED 639,400 a year. It explains 695 of Meter operations' 2,240 return visits, 31.0 %, at AED 920 each; 470 of them are 3-phase exchanges. 1,312 premises left in the exchange programme have a load upgrade newer than their meter record.

Which of tomorrow's jobs will need a second visit?

9 of 186 meter jobs for Wednesday carry a known cause. The biggest is WO-2615521 at Villa 18, Saffron Gardens: the register says single-phase, connection file CN-20-01192 says 3-phase CT, and van MV-22 has no CT meter. Expected return visits: 6.3 as planned, 0.7 with all nine changes.

Only send CT-authorised technicians to CT-metered premises

Approved on your instruction, recorded as Layla Haddad: fix F3. CT exchanges and CT faults now go only to the 14 CT-authorised technicians. It removes an estimated 240 return visits, AED 220,800 a year. Tomorrow it moves WO-2615534 from Imran Qureshi to Fatima Rahman.

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

Repeat-visit chainsEvery return visit traced to why its first visit failed and priced, with chains on a 30-day scale, the longest first, and the selected chain's first failure and agent run.
Filtered by one causeWrong meter type on the van: 695 return visits and AED 639,400 a year, with the chains it explains.
The chainFour visits in 18 days, each with its technician, van, time on site and note, and why the first visit failed as three records side by side.
The record behind the causeConnection file CN-19-07734: a 2019 load increase to 3-phase 150 A with CT metering, never written back to the meter register.
Causes ranked, cost and patternThe cause at 92 % with the alternatives answered, the cost of the chain and its complaint, and 1,312 premises still ahead with the same mismatch.
Causes and costReturn visits by first-visit cause and job type, the cost of each cause and its owner, and the chains behind the selected cell.
FixesKitting, data, skills, access, stock, information and time fixes, each with its owner, the chains it would have prevented and the visits and AED it would avoid.
Approve a fixThe fix, its estimate and its owner on one screen, signed by the field service manager.
Tomorrow, checkedTomorrow's 186 meter jobs checked at 16:00: the 9 that carry a known cause, the evidence, the risk of a return and the change that removes it.
Changes appliedAll nine changes applied by the planner before the 05:30 loadout; expected return visits down from 6.3 to 0.7.
First-time fixFirst-time fix by month against the 90 % target, and return visits by month with wrong meter type rising from 41 to 77 a month as phase 2 of the exchange programme reached older villa districts.
Crews and vansEach technician's authorisations, first-time fix and skill-mismatch returns, and tomorrow's van lists against what each van needs.
Your rulesWhat counts as a repeat visit, the loaded cost of a return visit and whether compensation is added, and the owner of each cause.
Governance

Every cause cited, every fix approved, every change made by a person.

Every cause cites its recordsEach first-visit cause rests on the records behind it — the technician's note and photo, the van loadout, the meter register, the connection file, the skills register, the access history — and any of them opens from the chain.
People confirm causes and approve fixesThe agents propose. Layla Haddad confirms or changes each cause and approves or declines each fix, with a reason recorded on a decline. A change to dispatch rules also needs the Head of Field Operations, Khalid Rahimi.
Low confidence goes to the plannerA cause below 70 % confidence is never tagged on its own: the work planner confirms it. Chain CH-26-0450, a smart meter with no communication, sits at 64 % because its second visit may be a separate signal problem.
Read-only on work orders, vans and assignmentsThe agents read work orders, notes, stock and registers. They never change a work order, an assignment or a van list; the planner applies tomorrow's changes, and each fix owner makes their fix live.
One rate, with the working shownEvery chain and cause is priced at the loaded cost set in Settings — AED 920, two technicians × 1.5 hours, a van and a 24 km round trip — and the sum is shown: 3 × AED 920 = AED 2,760.
Every decision on the activity trailEach agent step and each human decision — a cause confirmed, a cause changed with the agents' original proposal kept, a fix approved, a change applied for tomorrow — is recorded with the name and the time. Customer data stays with Lumina.
Configuration

Your field rules, not ours

What counts as a repeat visit, what one costs, who owns each cause and who approves are settings, chosen by the utility.

SettingDefaultChoose from
Repeat window30 days14 days · 30 days · 60 days — a visit within this many days of an earlier one joins its chain
Link visits byPremise or assetPremise or asset · Premise only · Asset only — the same asset counts if it has moved
Not countedAll three excludedAll three excluded · Exclude cancelled only — planned multi-stage jobs, customer-requested reschedules, cancelled jobs
Loaded cost of a return visitAED 920AED 920 · AED 1,100 · AED 1,840 — two technicians × 1.5 hours, van and a 24 km round trip
Add compensation paidYesYes · No — missed-appointment payments are added to the chain's cost
Tag a cause without review above70 %70 % · 80 % · 90 % — below this confidence the work planner confirms the cause
Tomorrow check16:00 working days16:00 working days · 15:00 working days
Fixes approved byLayla HaddadLayla Haddad · Khalid Rahimi — changes to dispatch rules also need the Head of Field Operations
Connections

Works with the records a field visit already leaves behind

Work orders and notesevery premise visit with its technician note, photos, closure code and times
Van loadouts and storeswhat each van carried at loadout — meters, seals, isolators, CT test blocks
Skills registereach technician's grade and authorisations — 1-phase, 3-phase direct, CT metering, water meters
Meter register and connection filesthe meter on record and every approved load upgrade, to catch the two disagreeing
Access history and meter-reading noteslocked cupboards, gates, dogs and key holders, from field and reading visits
Complaints and meter data alarmscustomer complaints linked to their chain, and open comms alarms from the meter data system
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
90%
first-time fix in meter operations, up from 83 %; best in class is about 89 %
Today83.0 %
Target90 %
estimated
640KAED
a year of return visits from one cause: the wrong meter type on the van
695 of 2,240
meter return visits a year × AED 920
estimated
16,700km
of van journeys a year not driven once that cause is fixed

“demo” = seen in the working solution, on its sample data, including the estimates it shows for fixes and for tomorrow's jobs · “target” = the design goal, measured in the live solution · “estimated” = our estimate: the hours split above; on the results, 695 return visits × AED 920 ($250, the conservative truck roll) and × 24 km round trip · “typical” = published figures: Aberdeen Group via Microsoft Dynamics 365 (26 % of dispatches need a follow-up); Aberdeen via OptimoRoute (first-time fix ~75 % on average, ~89 % best in class); NetSuite (25 % of field service cases need another visit, 2022); S&C Electric and TSIA via Ventavid ($250–$500 per truck roll, ~$1,000 fully loaded). Lumina Utilities, the people, premises, work orders and records named on this page are fictional — characters and sample data in the working solution.

Questions

What field service teams ask us.

What is repeat visit analysis?

Repeat visit analysis finds why field crews go back to the same premise or asset. Repeat Visit Analysis links every visit within the repeat window into a chain, names why the first visit failed — wrong meter type on the van, no access, a skill or authorisation mismatch, a part out of stock, a site not ready, missing information or a slot too short — and puts a cost on each cause.

How does repeat visit analysis software work for utilities?

Six agents work overnight. The chain builder links visits; the note reader reads the technicians' notes and photos; the cause finder checks them against the van loadout, the skills register, the access history, the meter register and the connection files; the cost keeper prices each cause; the fix recommender proposes fixes. At 16:00 the tomorrow checker checks the next day's jobs for the same causes.

How does it improve the first-time fix rate?

It turns one average into causes with owners and fixes. In the sample, eight proposed fixes would avoid an estimated 1,340 of 2,240 return visits a year in meter operations, and the target is 90 % first-time fix, up from 83.0 %. Tomorrow's jobs are checked for the same causes, so the planner can correct them before the vans load.

Does it cover water service, LV faults and connections, not only meter exchanges?

Yes. The chains, first-time fix trend and causes can be shown for meter operations, water service, LV faults, connections or all field work. The same seven causes are used, but the mix differs: in water service the largest is no access, in LV faults information missing or wrong, in connections site not ready. Each cause's owner is set in Settings.

How is the cost of a return visit worked out?

Each return visit is priced at the loaded cost set in Settings — AED 920 in the sample, two technicians × 1.5 hours, a van and a 24 km round trip, the conservative end of published truck-roll costs — plus any missed-appointment compensation paid, if that setting is on. The working is shown on every chain.

Does it change work orders, van lists or dispatch rules?

No. The agents have read-only access and never change a work order, an assignment or a van list. The work planner applies tomorrow's changes; the field service manager approves fixes; a change to dispatch rules also needs the Head of Field Operations.

Do people stay in control of the causes?

Yes. The agents propose a cause with a confidence, the records it rests on and the evidence against. The field service manager confirms or changes it, and the change is recorded with the agents' original proposal. Below 70 % confidence the work planner confirms the cause.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your work-order history and notes, van loadouts, skills register, meter register and connection records — and it goes live once every quality gate has passed. We will walk you through it on your own return visits first.

See it on
your return visits.

We'll run Repeat Visit Analysis on a sample of your own closed work orders, van loadouts and connection records.