The work that decides revenue isn't written down

Your clinic has a system. Part of it isn't written down anywhere — it lives in your receptionist's head, and that head goes home at seven.

Nobody here is being careless. The method worked, and worked well, for years. It simply reached a size that one head can't hold.

The things nobody wrote down

A partial list of the things that decide revenue in a practice and have no record anywhere:

• The patient who said "I'll call after the holiday."
• A treatment plan approved out loud, with no appointment attached.
• A call that came in at 13:20, while everyone was chairside.
• The patient who was due for a check this year and never came.
• An insurance form waiting on a signature, on a desk.

Every one of them is money. Not one of them is written down in any system. And each one passes, at some point, through a single person who has to remember.

Three things memory doesn't have

Memory doesn't survive absence. Your receptionist takes a week off. Whoever covers opens the diary and sees appointments — they don't see the three people who were promised a call back this week.

You can't count memory. Try it now: how many treatment plans were approved in the last three months with no appointment booked? If the answer is a number, you have a process. If the answer is "let me check," you have a person.

And memory fails silently. This is the expensive part. A patient nobody followed up doesn't complain. They don't leave a review, don't call to ask why, and don't show up in any month-end report. They just don't come back. A quiet failure never reaches the top of the list — which is how it can run for years without anyone ever deciding to allow it.

The spreadsheet is half a step

The usual first move is to open a sheet. It's a real improvement: a sheet has memory, and you can count it. But it's missing the other half — it doesn't start anything. A spreadsheet won't remind anyone to open it on Tuesday morning, so after two busy months it becomes the file everyone knows exists and nobody has opened since March.

A loop that works needs three things, not one. Memory — where it's written. A trigger — what makes it happen. And an owner — by name. A sticky note gives you a trigger with no memory. A spreadsheet gives you memory with no trigger. Both lean on one person who is already busy.

Loops fall between the chairs

Tasks are almost never forgotten the moment they arrive. They're forgotten when they change hands. The phone rings while your receptionist is standing in front of a patient at the counter, she writes a name on a pad and tells herself she'll call back. Two hours later the pad is under a file, the next patient is in, and the task exists nowhere except a vague sense that there was something.

Every one of those crossings — phone to note, note to memory, memory to another person — is a place the loop can drop, and nobody logs the drop. If you want to map this in your own practice, count how many hands touch one enquiry between the moment it arrives and the moment it has a time in the diary. The more hands, the more places to fall.

A five-minute test

Ask your team three questions, unannounced:

• Who was due back this month and didn't come?
• Which approved treatment plans have no appointment?
• How many enquiries went unanswered yesterday, and what happened to them?

It doesn't matter whether the answer is right. What matters is where it comes from. If it comes from a screen anyone on the team can open, you have a process. If it comes from someone's memory, or a file only they know how to maintain, they aren't working inside the process — they are the process. Which works beautifully until the day they're ill, or resign, or are simply too busy.

The data is probably already yours

Here's the surprise. The instinct on seeing the gap is to go shopping for software — but the software is usually already sitting there, and much of what's listed above is already inside it: last visit date, the treatment that was approved, the charge that was opened, the enquiry that came in. What's missing isn't somewhere to keep it. What's missing is someone whose job is to look, every day, at exactly those questions. The record exists. The looking doesn't.

It's worth checking what your own system actually holds, because it isn't obvious. Some practice-management systems don't hold a recall field at all — and then "who is due" is something you have to derive from visit history rather than read from a field.

Where to start, this week

Not everywhere. Pick one loop — usually recalls, or approved plans with no booking — and write it down in three lines:

• What triggers it. "A year since the last visit."
• Who owns it. By name, not "reception."
• Where it lives. One place anyone can open without asking.

Do it on paper if you have to. The tool isn't the point. The point is that the loop becomes visible. You can't automate a process you can't describe — which is why this hour, rather than the choice of technology, is the hour that pays for itself.

A practice can be excellent and run exactly this way. It isn't a sign of carelessness. It's a sign that the practice grew, and the method that carried it this far has become too small for it. The only question is how much longer you run it.

---

SoliumOS does exactly this: who's due is surfaced from your own records rather than a list someone remembers to keep, the message goes out in your own wording, and no message goes out without approval. It all runs in your cloud, under your keys — we build it, and we can't read it.

Want to see it against your own records? Book a demo.