Oversight
A dashboard that can name the worst rep will be used to name the worst rep.
Whatever it says on the tin. Build a per-person severity colour and within a quarter it is the only thing anybody looks at, and the numbers underneath it stop being true because everyone has learned what turns a tile red.
So the refusals here are as designed as the features.
What it shows
Four counts, three rates, and a rate it will not print.
Planned, logged, missed, unplanned. Then the proportion of weeks actually committed, the proportion of visits that happened on the day they were planned for, and how often anybody checked in.
Below five data points, a percentage is withheld and the tile says so. The reason is written into the product: a small-sample percentage could identify one rep by inference, and a misleading hundred per cent is worse than an honest gap.
The third one is withheld on purpose. Below a floor of five, a percentage could identify a single rep by inference — so the screen says so instead of printing a misleading hundred.
- On time means on the day planned —
A real definition rather than "was logged at all".
- Eight weeks of trend, and no per-visit list —
The shape of the team's habits, not a place to read somebody's diary.
- A rep's own numbers, still numbers —
Opening one person shows the same tiles scoped to them, and a link to their week. Still no visit list.
- It says what it refuses to do —
The screen tells the manager, on the screen: no ranking, no severity colouring — what happened, not who is doing better.
Nudging
The reminder goes to the rep. Nobody else is told.
An overnight sweep finds visits that were planned and never logged, and tells whoever owns them — once, deep-linked, and the rep can mute it.
After a week, an unlogged visit is closed as missed on the rep's behalf so the week's numbers are true rather than permanently pending.
There is exactly one notification in this entire module, and that is it. No manager alert, no daily digest of who is behind, no escalation. The service states the rule in its own words: nothing here notifies a manager about an individual visit.
›Can a manager see everybody, or only their reports?
Today the team view is the whole workspace for anybody holding the permission — there is no reporting-line scope on it yet. Grant it accordingly.
›Is there an export of visits?
Not from this module. Visits are reportable through the ordinary report builder — planned against logged, by rep, by week — and the coordinates are deliberately not among the fields available there.
›Does the check-in rate show when check-in is switched off?
It does, and it will read as zero, which is a rough edge rather than a signal. Read it only where check-in is actually in use.