Closing the Gap Between the Field and the Office
Published by
Throne of Profit EditorialReviewed by
William Hassell
Founder & Chief Editor, Throne of Profit
A plumbing company runs on two halves that have to stay in sync. The tech is on the job — diagnosing, changing scope, adding parts, agreeing to a price with the customer at the sink. The office is booking, invoicing, collecting, and answering the phone when that same customer calls back. Everything the field decides has to reach the office cleanly, and everything the office knows has to reach the field. When that flow breaks, the work still gets done — but the details, the changes, and the money leak out the gap in between.
Most owners think of this as a paperwork problem or a software problem. It's neither. The real problem is information handoff: whether what happened on the job arrives at the office complete, accurate, and in time to bill, collect, and follow up. When that handoff is unreliable, you're not losing jobs — you're losing pieces of jobs you already did.
THE HANDOFF
FIELD OFFICE
───── ──────
scope change ──┐ ┌──► invoice correctly
parts added ──┤ gap? ├──► collect the balance
price agreed ──┤ ░░░░░░ ├──► answer the callback
next step ──┘ └──► schedule the return
│ │
└──── clean handoff = paid ────┘Owner symptoms
Invoices go out missing parts, changes, or the price the tech actually agreed to.
The office gets blindsided by a customer callback the tech never logged.
What the customer was told on-site and what the office says on the phone don't match.
Why this happens
The field and the office live in different worlds during the job. The tech is heads-down in a crawlspace with dirty hands; the office is fielding the next three calls. The moment a scope change happens — a second valve, a price adjusted at the door, a "we'll come back Tuesday" — is the moment it's most likely to be captured, and the least convenient moment to capture it. So it gets remembered instead of recorded, and memory decays by the time the truck hits the next stop. The handoff isn't missing because anyone's careless; it's missing because nobody built a reliable way for what happened in the field to travel to the office the same way every time.
Common mistakes
Relying on memory for changes — the tech plans to "tell the office later," and later never carries the full detail.
Capturing the job but not the money — parts and labor get logged, but the price actually quoted to the customer doesn't.
One-way flow — the field reports to the office, but the office never pushes back what it knows (account history, prior visits, balance owed).
No standard for what a completed job must contain before it leaves the site.
Treating callbacks as separate from the original job instead of connected to it.
Business consequences
A broken handoff bleeds money quietly. Invoices go out low or wrong because the change never reached billing. Balances go uncollected because nobody knew a partial payment was agreed at the door. Return trips get scheduled twice or not at all. And the customer — who was told one thing on-site and hears another on the phone — starts to wonder whether this company has its act together. Each miss is small; the sum is a steady leak of revenue and trust. The owner who closes the gap bills the full job the first time, collects what's owed, and presents one consistent face to the customer whether they're talking to the tech or the front desk.
How experienced operators think about it
They treat the completed job as a package that has to arrive intact, not a set of facts scattered across a tech's memory. The mental model is a chain of custody: every job leaves the site carrying everything the office needs to bill it, collect on it, and follow up — scope, changes, parts, the agreed price, the next step, and anything the customer was promised. And they make it two-way. Before the tech rolls, the office has already handed forward what it knows — this customer's history, their balance, the note from last visit. The field and the office aren't two departments passing paperwork; they're one operation sharing one picture of the job.
Practical actions
Define what a "closed job" must contain before the truck leaves — scope, changes, parts, agreed price, next step, and customer promises. Make it the same list every time.
Capture changes at the moment they happen, on-site, not from memory at day's end. The change and its price get recorded together or not at all.
Push information forward before the visit — give the tech the account history, balance, and prior notes so the field speaks with what the office knows.
Reconcile the agreed price to the invoice — the number the customer heard at the sink is the number that gets billed, every time.
Link callbacks to the original job so the office sees the history and the tech isn't walking in blind.
Questions every owner should ask
When a tech changes scope or price on-site, how does that reach billing — and how often does it not?
Does the office know what the customer was told before they pick up the callback?
Are we billing the price the tech actually agreed to, or the price we guessed afterward?
Frequently asked questions
Isn't this just a job documentation problem?
Documentation is part of it, but the problem is bigger than records. You can have thorough photos and notes and still lose money if that information doesn't travel to the person who bills, collects, and answers the phone — in time to act on it. Documentation is about what gets captured; this is about whether what's captured actually flows to the office, and whether the office flows back what the field needs. It's the handoff, not just the record.
We already use field software. Why do details still fall through?
Software moves data, but it doesn't decide what has to be captured or enforce that it happens before the truck leaves. If there's no standard for what a closed job must contain, a tool just gives you a faster way to send incomplete information. The fix is defining the handoff first — what travels, when, in both directions — then letting the software carry it. Tool second, standard first.
Related articles
Running a Profitable Plumbing Company — the pillar.
Photos, Notes, and Job Records That Protect the Work — what gets captured on the job.
Writing Down How You Do It: SOPs for a Plumbing Company — standardizing the handoff.
The Customers You're Quietly Losing — how quiet leaks cost you customers.
Do You Know Your Repeat and Churn Rate? — measuring what the gap costs.
Every business has more decisions than time
Whether you need help solving one problem, evaluating a major opportunity, or making a company-changing decision, Throne of Profit gives you consulting capacity on demand.
Purchase only the consulting capacity you need and use it across Weekly Focus, Strategic Focus, Financial Focus, and ThinkTank engagements.