Here’s a sentence that comes up a lot: “We have a system. People just don’t use it right.”
Usually that’s half true. People are using it. Every person logs in, enters things, clicks buttons. They’re each just doing it their own way. Add up a dozen people’s own ways and you get data that technically exists and practically can’t be trusted.
What it looks like
Take time tracking. Everyone tracks time. But the entries don’t look alike.
Some people pick the client and the specific service. Some pick the client and leave the service blank. Some write clear descriptions. Some write “work” or “emails.” Some mark internal time as internal. Some put it under a client because that’s first in the dropdown. Some enter time daily. Some catch up at the end of the pay period from memory.
Nobody is trying to make a mess. Each habit makes sense to the person doing it. But billing and payroll both depend on those entries, and every inconsistency turns into cleanup for somebody else later.
What the owner usually thinks is wrong
The instinct is to blame the software or the team. “This tool is clunky, let’s find a better one.” Or, “I’ve told them how to do it. They don’t listen.”
Before agreeing with either, I’d ask a simpler question: where is the correct way written down?
Often it isn’t. There was a training when the tool rolled out, or the owner explained it once. “Do it right” is not a standard. If I can’t tell someone what good looks like, I can’t fairly hold them accountable for missing it.
What I’d check
- What choices does the tool allow? (Usually a lot.)
- Which of those choices matter downstream? Not every field matters equally.
- What does billing need? Payroll? Reporting?
- When someone enters something wrong, does anyone find out? How long after?
That last one is usually the real gap. Mistakes don’t get caught close to when they happen, so nobody learns from them. The person who entered the time never hears about it. The cleanup lands on whoever is closest to the invoice.
What I’d change
Three things, in this order.
A written standard. Not a binder. A practical page that covers the handful of things that matter: how to pick the client and service, what a useful description looks like, what counts as internal versus client-billable time, and the deadlines for entering and adjusting time each pay period.
Training with real examples. Not theory. “Here’s an entry that works. Here’s one that causes a problem. Here’s why.”
A feedback loop. This is the part people skip. Billing and payroll reconciliation become the place where missing, unclear or miscategorized entries get caught, and they go back to the person who made them to correct. That’s not punishment. It’s the system telling you, close to the moment, that something didn’t land.
What I’d leave alone
The software. It’s tempting to think a new platform will force consistency, and some tools help by requiring fields. But move a team with no shared standard into a new tool and you usually get the same inconsistency with a new logo on it.
The tradeoff
A standard with no follow-up is just a document. The follow-up is what changes behavior, and it’s also what takes effort. Somebody has to own the check. Somebody has to have a few slightly awkward conversations at first.
Why this keeps happening
Most tools are built to be flexible. Flexible means five ways to do almost anything. If nobody decides which way your business does it, you’ll get all five.
This probably made sense when the business was smaller. Three people can stay consistent by talking to each other. Twelve can’t. The business didn’t fail at anything. It outgrew “we all kind of know how we do it.”
And it’s not only time tracking. Project boards where everyone names tasks differently. CRMs where one person updates stages and another never does. Job apps where half the crew uploads receipts and half texts them. Same problem: a flexible tool and no decision.
So, a question to sit with: if I asked three people on your team to show me how they enter the same thing, would I see one way or three?
If it’s three and you’re not sure which one is right, bring it to a Systems Fit Call.
