The classic scenario: an area hasn’t been cleaned in a while, but nobody notices until a visitor complains. By then the damage is done — a bad impression, maybe a lost customer. The root problem is simple: in a paper system, "not done" information doesn’t travel anywhere on its own; it only surfaces if someone happens to notice and report it.
What should trigger an alert?
In an effective system, alerts fire on three main conditions:
- Timeout: The scheduled check time has passed by a set margin with no scan recorded.
- Low rating: A visitor/customer rating falls below a set threshold.
- Incomplete task: A check happened, but an item on the list was left unchecked.
Who gets it, and when?
Alerts should go to the manager actually responsible for that area, not a generic inbox — a notification sent to everyone becomes a notification nobody feels responsible for. Timing matters too: an instant alert the moment it happens makes the real difference, not an end-of-day summary email.
Watch out for alert fatigue
Sending an alert for every tiny detail eventually gets ignored. Setting thresholds around genuinely significant deviations (e.g. "45 minutes late," not "5 minutes late") keeps alerts something people actually act on.
A well-designed alerting system doesn’t force a manager to watch everything — it only steps in when something truly needs attention.
The bottom line
In QRapor, every task is tied to a schedule; when that schedule is missed, or a task is left incomplete, the relevant manager is alerted instantly. That mostly eliminates the "why did nobody notice" question.