The jobs that leave no trace

Every quality check you run rests on one quiet assumption: that the work you are checking is all the work there was. You review the jobs your crews logged, you score them, you chase the bad ones. It feels complete. It is not.

A while back a business I work with had three jobs go missing. Not done badly. Missing. No visit, no note, no photo, and no explanation for where they went.

Here is why that is worse than a bad job. A bad job at least exists. It shows up in the system, it gets a score, someone follows it up. A job that silently never happened leaves no record at all, so it never enters the list of things to check. Your review queue only ever sees the work that got logged. The work that vanished is invisible to it by design.

You cannot fix a gap you cannot see. So I stopped checking only what was done and started comparing it against what was planned. The schedule says these jobs were meant to happen today. The record says these ones actually did. The space between the two is your missed work, and until you put the two side by side, that space does not exist anywhere you can look at it.

Once it was side by side, the missing jobs surfaced on their own. Each one traced back to a real customer who would otherwise have called in angry, or worse, quietly left. Now a skipped job is not a silent hole. It lands on a list, someone owns it, and it gets closed before the customer is the one who tells you.

The lesson is not really about schedules. It is about trusting a system that can only report what it was told. If your checks run only on the work that got recorded, you are grading the jobs that went fine and staying blind to the ones that never showed up. Put the plan next to the reality. What is missing from the middle is the part that costs you accounts.