The Eight-Forty Check
For three years, the same ritual. The office manager gets in at eight-thirty, pours coffee, and at eight-forty pulls three numbers: yesterday’s completed visits, the charges entered, the claims created. When they agree, she moves on with her day. When they don’t, she finds the visit that fell out of the chain and fixes it while it’s a day old. Twice a week, maybe. Nobody else in the building knows this ritual exists or what it catches, because nothing it catches ever gets big enough to be seen.
Then she takes a job forty minutes closer to home. Her replacement gets the binder, the logins, two weeks of training. The eight-forty check isn’t in the binder. It was never written down anywhere, because it lived in her, and it leaves with her. Nobody decides to stop checking. The checking just ends.
The Chain, and What Falls Out of It
Every completed encounter should end as a charge, every charge as a claim, every claim as a known outcome. An unreconciled encounter fell out of that chain somewhere, and none of your instruments can see it, because reports start where the data starts and this visit’s data stopped early. The manual defense is the morning match itself, covered in the missing charges piece, and the method is sound. The fragility is that the control’s uptime is one person’s uptime: her vacations, her sick days, her two weeks’ notice. And the busy weeks, when the most slips through, are exactly the weeks the ritual gets skipped.
Give the Habit to a Machine
The build turns the match into machinery. Every night, the system walks the whole chain: encounters to charges, charges to claims, claims to outcomes. Whatever matches, matches silently, and that’s nearly everything. Whatever doesn’t lands on a short exception list by morning, each item carrying its own context: the visit, the missing link, the age. One named person works that list with their coffee, and the list is usually three items instead of three hundred, because nothing has had time to pile up.
The human role changes shape here, and into the right shape. The machine does the finding, the person does the deciding, which is the 80% standard applied to reconciliation. Nobody hunts through spreadsheets. Nobody has to remember anything. The person who used to be the control becomes the judge of exceptions, and judging was the only part that ever needed a human.
What Changes
Speed: a visit that misses its charge gets caught in hours, while it’s cheap to fix, instead of surfacing as a soft month at close, when it’s archaeology. Coverage: the match runs every night, including the nights after the worst days, and the worst days are where the misses live. Visibility: “unreconciled today” becomes a standing line on the weekly page, read by name, sitting near zero. The day that number drifts upward, something upstream changed: a new visit type, a new hire’s workflow, an integration that hiccuped. You find out that week, from your own screen, instead of next quarter from your accountant.
Two Questions That Size It
First: who matched last Tuesday’s chain, all three links? If there’s a name, ask what happens the week that name is out. If there’s no name, you already have your answer. Second: right now, how old is the oldest encounter that never became a charge? A practice with the machine answers in one click. A practice without it usually can’t answer at all, and that not-knowing is the leak’s entire cover.
Where to Start
Run the manual match daily for two weeks; that sizes the leak and proves what the habit is worth. Then hand the habit to the machine before it erodes, because it will erode; they all do. If you want to see the built version first, grab 30 minutes with us. Prep nothing. We’ll show you the nightly reconcile’s morning exception list from real operations, and you’ll see how short the list stays when nothing has time to hide.