The Six Information Gaps Behind Every Field Service Problem

Picture one job. A technician is sent on Tuesday to a customer whose heating has failed. She diagnoses it, but her certification for that equipment lapsed last month and nobody's board showed it. She writes the parts and hours on a paper ticket. The quote for the repair reaches the customer on Friday, priced by whoever in the office had a minute, and lower than it should have been. The invoice goes out the following week after someone re-types the ticket, and two parts that were fitted never make it onto it.

Late invoice. Missing billable parts. Inconsistent quote. Slow estimate. An unqualified dispatch. It looks like five failures, and it is one.

Every one of them is a fact that didn't travel: what the technician did, what it should cost, what the customer was told, who was allowed to do the work. That is what we mean by an information gap, and it is the thesis of this article. Pull on almost any operational failure in a field service business and you'll find one of six places where two systems that should share a fact don't.

The stack most field service companies actually run

The typical mid-sized field service company runs on five to eight systems that don't talk to each other. Work orders and dispatch live in a field service management tool. Scheduling is in another app, or on a whiteboard. Invoicing and financials sit in accounting software, fleet tracking in its own dashboard, and employee communication is a group text, a communication tool or nothing at all. HR and payroll are somewhere else, training and compliance somewhere else again, and spreadsheets fill whatever is left.

Each system has its own login, its own data model and its own mobile experience, or none. Job completion data doesn't flow to accounting. Training completions don't flow to dispatch. Fleet location lives in a different screen from the schedule. The business has no single source of truth, so people become the integration layer.

Knowledge workers switch between 11+ apps a day and lose 4+ hours a week to system switching (McKinsey). The person who pays the highest price is the dispatcher. They're the supervisor, the customer service rep and the first line of tech support, all in one chair, across most of those systems at once.

Each of the six gaps below is a place where that stack breaks. They're numbered because they tend to show up in this order as a company grows, not because the first is the worst.

Gap 1. The job is done before the invoice exists

Why do field service companies invoice late? Most of the time it's because the invoice starts from a paper work order that someone has to re-key. The job is finished, and the money can't move until the office catches up.

The delay is usually measured in days and often stretches into weeks. Every one of those days is your cash funding work you've already done. Payroll, fuel and parts have all been paid; the customer hasn't been asked to pay yet.

What closes it is a work order that closes on site and an invoice that's ready at price book rates the moment the job is marked complete. The full sequence is in From request to paid: the work order lifecycle on one record.

Gap 2. What happened on site is not what reaches the bill

Hours, parts and materials get written on paper, then typed into an invoice, then typed again into accounting. Every hop is a chance to lose something, and what goes missing leaves no trace. There's no line item for the part that was fitted and never billed.

That's what makes this gap hard to see. A late invoice is visible on a report. A missing part isn't on any report, because nobody knows it was supposed to be there.

The fix is to capture cost against the work order on the phone, as it happens: labor logged where the work is done, parts and materials recorded on site and priced from the same list the office bills from. Then what the technician captured is what the customer is billed for. More in the work order lifecycle.

Gap 3. The price depends on which technician turned up

Why do technicians quote the same job differently? Because the price they're quoting from isn't the same one. One tech quotes from memory, a new hire undercharges to be safe, and the parts price in the field differs from the one the office bills.

Ask two people on the same team what a common repair costs and you'll often get two answers. The gap doesn't announce itself. The job closes, the customer pays, and the margin that was left at the curb never shows up as a line item.

What closes it is a single price book: change a price once, and it appears on every technician's next estimate. We go through what that requires in the price depends on which technician showed up.

Gap 4. The estimate arrives days after the diagnosis

The technician sees the problem on Tuesday. The customer gets a quote on Friday. By then somebody else has already been out.

This is a timing problem, and timing costs real money: a customer's urgency fades faster than most offices assume. An estimate that's built on site, approved on the technician's device and converted to a work order with one click closes the customer's decision while they're still standing in the room. The same article on pricing covers how that works in practice.

Gap 5. The customer's only status channel is the phone

The job record knows the technician is on the way. The customer doesn't, so they call, and the dispatcher spends the afternoon answering.

Nobody involved is doing anything wrong. The customer wants to know when someone's arriving and the only way to find out is a person. A portal that reads the same record the dispatcher sees removes the reason to call. When the customer's only status channel is the phone goes into what that portal has to read, and what changes for customers with dozens of sites.

Gap 6. The dispatch board cannot see who is certified

Credentials live in one system. Assignments are made in another. So a technician gets sent to work they're no longer licensed to do, and that is an audit finding waiting for a date.

In a licensed trade, the HR record is an operational record. If work types carry the credentials they require, a lapsed technician stops being assignable, and a recertification recorded on Monday makes them eligible on Tuesday. This is the gap with the highest stakes, so it gets its own article: why an expired certification should block dispatch automatically.

Why the gaps compound

Go back to the Tuesday job. The late invoice, the missed parts, the low quote, the three-day delay and the expired credential aren't five separate events. They're the same failure told five ways. Any one of them alone is survivable. Together they stack on a single job, and there are dozens of jobs a week.

None of this needs a catastrophe. It compounds through ordinary weeks, and because each gap is filled by someone quietly working around it (re-keying, chasing, answering the phone), it rarely shows up as a problem to solve. It shows up as "how we do things."

That's why most companies have never added it up. If you'd like to, what disconnected field service systems actually cost gives you six formulas to run on your own numbers.

Which gap to find first

You don't need a consultant to see which gap is costing you most. Look at where you feel it.

If cash is tight even though the schedule is full, start with Gap 1, and pull the average number of days between job completion and invoice. If margins are thinner than the quotes suggest, look at Gaps 2 and 3, and audit twenty completed jobs against what was billed. If you're winning fewer estimates than your technicians expect, it's Gap 4. If your dispatcher can't get through a morning without a queue of status calls, it's Gap 5. And if your compliance lead has ever said "I think everyone's current," it's Gap 6.

Most operators find that two or three of the six are live at once, and that they trace back to the same handful of systems. That's useful, because it tells you where a single change does the most work. A price book helps Gaps 3 and 4 together. A work order that captures cost on site helps Gaps 1 and 2 together.

Ask the people who do the job as well as the person who owns the budget. The dispatcher knows how many status calls there are. The office manager knows how many tickets get retyped. The technician knows which fields they skip. The gap is usually on the shortlist of things they've already complained about.

What actually closes a gap

There's a difference that matters here. A platform designed as one system shares a data model. A platform assembled through acquisition or bolt-on integration shares a login screen.

You can tell them apart by asking what's underneath. In a unified system there's one data layer: one job record and one customer record that every capability writes to and reads from. A gap is only ever a fact that failed to travel, so the way to close it is to stop having two places for the fact to live. The other way is to build an integration for each pair of systems, and then to maintain it.

Here is what that looks like, one line per gap:

• A work order closes on site, and the invoice is ready at price book rates.
• Hours, parts and materials are logged against the job on the phone as they happen.
• Change a price once and it shows up on every technician's next estimate.
• An approved estimate becomes a work order with one click, and nothing is re-keyed.
• A customer's portal request enters the work order queue, and they track the same record the dispatcher sees.
• A credential lapses, and the technician stops being assignable.

MangoApps Field Service Suite runs on the same platform as communications, HR, learning and AI, which is why those lines can be true at once: the technician's certification, the price list and the customer's request all live on the same record. MangoApps is The AI Platform for the Frontline Workforce, and it has been built for that workforce for 18+ years and has 2M+ users.

You don't need all of it on day one. Close your biggest gap first. Skip what you don't need. The article on whether you have to throw away the FSM tool you already own explains how that sequencing works.

The gap that was never a staffing problem

For twenty years these gaps have been filled by people, because the infrastructure to close them at a price a mid-sized company could justify didn't exist. That's a big part of why it's been accepted as normal, a story we tell in why field service software has been split down the middle.

It exists now. The question left for most operators isn't whether the gaps are real. It's which one you close first.

If you're in a licensed trade, the answer may already be obvious. See how the same six gaps show up in fire and life safety, electrical contracting and utilities and telecom. To pick a vendor, start with 12 questions and a scorecard. To see the platform, look at the Field Service Suite.

Want the whole argument in one place? The complete Field Service Management guide covers the six gaps, the cost formulas and the vendor scorecard, and it's a free download with no email required.

Frequently asked questions

What is an information gap in field service?

An information gap is a place where two systems that should share a fact don't, so a person has to carry it between them. In field service there are six common ones: invoices that wait on paperwork, billable work that never reaches the bill, prices that depend on the technician, estimates that arrive days late, customers who can only get status by phone, and dispatch boards that can't see who is certified. They look like separate problems and usually share one cause.

Why do field service invoices take so long to go out?

The invoice usually starts from a paper work order that someone has to re-key, so it can't go out until the office catches up. Hours, parts and materials are written on paper, typed into an invoice and typed again into accounting, and each hop adds delay and a chance to lose a billable item. Invoicing from the work order at price book rates, the moment the job is marked complete, removes the re-keying.

How can a technician be dispatched to a job they are not certified for?

When credentials are tracked in one system (a spreadsheet, a learning system, an HR record) and assignments are made in another, nothing connects the two except someone's memory. A certification can expire without the dispatcher ever seeing it. If work types carry the credentials they require, the board can refuse the assignment at the moment it's made.

What is the difference between a unified field service platform and integrated point solutions?

A unified platform shares one data model, so a job, a customer and a credential each live in one place that every capability reads and writes. Integrated point solutions are separate products connected to each other, which usually means they share a login screen and a set of sync rules while each keeps its own copy of the data. The difference shows up in the gaps between the products, where copies drift apart.

Do you have to replace every system to close these gaps?

No. Start with the gap that costs you the most, keep the systems you depend on, and expand when you're ready. Accounting, payroll and identity systems can stay in place and connect to the platform. Read how the three paths work.