Ghost hours: the money you pay for time nobody worked
A ghost hour is time that shows up on payroll but never happened: the paper rota says clock-in at 9:00, reality says 9:40. It isn't dramatic fraud — it's a slow leak you sign off on every month because, on the rota, everyone was on time.
What a ghost hour is (and why it shows up in no report)
A ghost hour is the gap between the time you pay for and the time actually worked. The rota says the team clocked in at 9:00 and left at 18:00; the room was empty until 9:35 and someone slipped out before the till was closed. Nobody is openly lying — they just never record the gap, and that gap gets signed off on every payslip.
The problem is that a ghost hour leaves no trail. There's no transaction to reconcile, no client complaint. The paper rota or the shared spreadsheet capture intent — the theoretical schedule — not real presence. Come month-end, everyone looks punctual on paper, and the leak becomes a fixed cost nobody questions because it's never visible.
The leak you sign off every month
Excel rotas, timesheets filled in at the end of the week, and everyone's word for what time they arrived. The result: you pay for presence nobody has proven, and questioning it becomes personal instead of a data point.
Why your current setup doesn't catch it
Most centers rely on three mechanisms that share the same flaw: they run on good faith. The paper rota gets filled in from memory. The spreadsheet can be edited by anyone with access. And buddy-punching — the classic "clock me in, I'm five minutes away" — is invisible, because the system only knows someone pressed a button, not who or from where.
The second gap is absence management. Holidays get requested over WhatsApp, sick days get phoned in, and approvals live in the manager's head. When two people each believe they have the same long weekend approved, the clash surfaces too late and with no record of who approved what. The chaos isn't in the people; it's that no tool holds the truth of who was present and who granted the leave.
- Paper rota: filled in from memory, not in real time.
- Shared spreadsheet: editable by anyone, with no change history.
- Buddy-punching: a colleague clocks in for you and the system can't tell the difference.
- Holidays and sick leave over WhatsApp: no traceable approval, no shared calendar.
How Qleven proves real presence
Qleven's team management replaces good faith with proof. Anti-fraud clock-in validates presence through three methods, depending on how your center works: GPS geofence (the clock-in only counts inside the clinic's radius), QR kiosk (a physical clock-in point at reception), and trusted IP network (the clock-in is only valid from the center's own connection). It's no longer about believing the time each person reports: the system knows where and when the clock-in happened.
On top of that, per-person granular permissions define what each team member can do and see. Whoever should approve holidays approves; whoever only clocks in, only clocks in. And absence management leaves WhatsApp behind: a request-and-approval workflow for holidays and leave, with a shared calendar, where every decision is recorded against the person who made it.
Proof isn't a word, it's a record
The difference between a rota and an anti-fraud clock-in isn't cosmetic: one captures what was supposed to happen, the other captures what happened. When there's a doubt, you stop arguing and check a record.
A connected team, not a surveilled one
Let's be clear: anti-fraud clock-in isn't staff surveillance. It's a system that protects the center and the team alike. The person who shows up on time stops carrying the suspicion earned by the one who doesn't; the person who requested leave has proof it was approved; and disputes over who was present get settled with a record instead of someone's word.
And the team doesn't just clock in — it works connected. Internal notices between staff replace the sticky notes and the parallel WhatsApp groups, and task assignment means every job has an owner and a follow-up. The goal isn't to control people more, but to stop the organization from depending on anyone's memory. And because it all lives on the same platform as the agenda and billing, there are no integrations to juggle and no data to migrate by hand: Qleven handles the migration.
The four-room center
Picture an archetype center with four treatment rooms and six people on staff. If each one averages twenty minutes of ghost hours a day — late arrivals, early exits, the odd buddy-punch — that's two hours a day paid but not worked. Over a month, that's a part-time hire whose cost generates not a single appointment. (Illustrative scenario to show the order of magnitude, not a measured average.)
From suspicion to data: where to start
You don't need to redesign the organization to close the leak. The first step is deciding how your center clocks in — geofence, QR or trusted network, or a combination — and moving holidays and leave out of WhatsApp into the approval workflow. From there, the theoretical schedule and real presence start to be the same data.
When that happens, the conversation changes. You stop reviewing rotas from memory and mediating arguments over who arrived when, and you start working from a record nobody disputes. Team management isn't a punishment: it's what turns paying for time worked from an act of faith into a fact.
What if your center stopped having invisible leaks?
We show you Qleven working on your center's real operations. No commitment, in 15 minutes.
See Qleven in your center · 15-min demoFrequently asked questions
Keep digging deeper
The Qleven features that solve what you just read about.