What controllers see first before the owner sees the loss
Controllers see leakage before owners do. They notice reductions, write-offs, reconciliation gaps, and odd AR patterns months before those numbers roll up into an owner-level report. Most are stuck fighting those fires in isolation instead of surfacing them as one picture, which is the gap NanoForce closes for restoration and reconstruction contractors.
By Mark Kurywczak, Founder & CEO, NanoForce Technologies ·
- Controllers usually spot reductions, write-offs, and reconciliation gaps months before those numbers roll up into an owner-level report.
- Most controllers are stuck fighting these issues in isolation instead of surfacing them as one connected picture for ownership.
- A small, structured dataset, twenty reduced claims and 90 days of write-offs, is enough to start a real pattern-finding conversation.
- Repeats across the same carrier, location, or service line are the signal worth escalating, not the one-off exception.
Understanding what controllers see first turns their day-to-day signals into an early-warning system, instead of a stack of frustrating spreadsheets nobody connects.
What do controllers see that owners don't?
- Repeated claim reductions from the same carriers or TPAs.
- A growing bucket of "miscellaneous write-offs" or ledger adjustments.
- Invoices that don't reconcile cleanly to jobs or field records.
- Aging reports that look fine overall but hide stuck pockets of receivables.
These get documented, but rarely escalated as leakage. Controllers fix the symptoms, chasing adjusters, nudging locations, cleaning up the books,while owners only see the after-the-fact numbers, not the pattern the controller has been living with for months.
Why controllers rarely escalate this on their own
Part of this is the job itself. A controller's week is built around closing the books, not building a case for ownership about a pattern they've only half-articulated to themselves. Flagging "the same TPA keeps knocking a few hundred dollars off our water losses" feels like a complaint about a normal cost of doing business, not a finding worth interrupting the owner's day for. So it gets absorbed into the routine instead: another write-off, another adjustment, another line in a spreadsheet nobody circles back to.
The other part is that controllers usually see their own location or their own function, not the network. A controller at one office has no easy way to know that the same carrier is doing the same thing at two other locations, because nothing in their day-to-day tools shows them what's happening outside their own books. What looks like an isolated annoyance to three different controllers is, from the owner's seat, one carrier running the same play three times.
Tools report what happened. Not why it keeps happening.
Accounting systems show balances and adjustments, not root-cause leakage patterns. Claims systems show statuses, not whether documentation consistently fails the same carrier requirements. PM tools show completed jobs, not whether agreements or inbound calls are quietly dropping.
Without something tying those controller-level signals together across claims, invoices, maintenance, and calls, owners only get partial stories. And by the time the loss is obvious, it's usually been running for months.
What the owner is actually missing
It's not that owners are inattentive. It's that the reports built for ownership are built to summarize, and summarizing is exactly what erases the pattern. A monthly P&L shows total write-offs as one number. It doesn't show that eighty percent of that number traces back to two locations and one carrier, because that level of detail isn't what a P&L is for. The controller who reconciled every one of those line items knows exactly where they came from. The owner reading the summary a month later has no way to know that.
Closing that gap doesn't mean owners need to start reading raw ledgers. It means someone needs to sit between the controller's daily signal and the owner's monthly summary, translating "this keeps happening" into a number and a name the owner can act on.
What to actually check
Ask for the top 3
Have your controller name the recurring annoyances in claims and reconciliation. Ask for it in a five-minute conversation, not a written report. Most controllers can list these off the top of their head.
Pull a small dataset
The last 20 reduced claims, and 90 days of write-offs and adjustments. That's a small enough ask that it doesn't compete with month-end close, and large enough to show a real pattern if one exists.
Look for repeats
Same carriers or TPAs in reductions, same locations or service lines in write-offs. A single reduction from a carrier is a negotiation. Three from the same carrier in ninety days is a pattern worth naming.
This turns controller frustration into something actionable. Not more reporting, but a clear connection between what they already see every week and what it's actually costing at the owner level. It also tells the controller their frustration was worth raising, which matters more for retention than it gets credit for.
Questions owners actually ask
Are controllers supposed to fix leakage on their own?
No. Controllers are the early-warning system. Owners need something that acts on those signals, not just more reports landing on the controller's desk.
How do we get this without adding to the controller's workload?
Start with one question and a small dataset. Their top three recurring annoyances already point at the biggest leaks.
What if different controllers flag different issues?
That's useful information. It means leakage varies by location and function, which is exactly why an owner-level view matters.
What if our controller isn't the type to speak up?
Then ask directly instead of waiting for it to surface on its own. Most controllers have the pattern in their head already. They just haven't been asked the question in a way that made it worth raising.
NanoForce is built around what controllers already see: Claims-to-Cash and Reconciliation turn their daily signals into measurable leakage numbers owners can see across every location. Instead of fighting isolated fires, controllers feed one leakage map. See how the systems connect →
Send us one file, one question, or one number that looks off.
Mark reads these personally. No sequence, no sales follow-up you didn't ask for.
Ask your controller for three real examples.
A reduced claim and a messy reconciliation they've had to clean up recently. Bring those to a Margin Leakage Consult and we'll show you how those signals connect to a much larger number across every location you own.