Why it matters
Day to day, you see individual shifts. Over weeks and months, a pattern forms — who's reliably on time, who's drifting, who keeps missing Mondays. The Performance page rolls that up for one worker so you don't have to reconstruct it from memory. Every number is measured against the same 60-day rolling window, with a 12-month trend and the shop average alongside for context.
This is a record of how someone works — not a pay calculation. Nothing here changes the hours you export.
Opening it
Path: Admin → Users → [select a worker] → Performance
The Performance page appears for workers who use the time clock (kiosk access). The header summarizes the window: number of shifts, total hours, and when their last shift was.
Headline metrics
Three headline numbers, each with the shop average beside it and a 12-month sparkline:
- Punctuality — on-time clock-ins and clock-outs. "On time" means the worker's recorded time rounds to their scheduled time — within half the account's rounding interval, either direction.
- Schedule adherence — shifts worked out of shifts expected. A cancelled shift leaves the count entirely — not counted for or against. A missed shift classified excused is also neutral, the same as cancelled; only unexcused, no-call-no-show, and unclassified missed shifts count against it.
- Task coverage — how much of the worker's clocked time is attributed to job tasks vs. unaccounted.
Each shows the current value, the change vs. the prior period, and how it compares to the shop average — so a number is always in context, not floating on its own. Each percentage appears once at least 10 qualifying shifts are recorded — until then the card shows progress toward it ("N of 10 shifts recorded") instead of a rate a small sample can't support.
The header above these cards summarizes total clocked hours for the window — raw clock time, not a payroll or legal determination. Your payroll provider derives hours worked and overtime from what FabWise records.
Supporting metrics
Three more for depth: average variance (how many minutes, on average, their start/end differs from schedule), average tasks per shift, and average task duration.
Pattern lenses
Below the metric cards sit six tiles over the same 60-day window — a closer look at how time gets recorded, rather than how much of it there was.
- Tap variance — the average gap between a worker's raw clock tap and their scheduled time, shown separately for arrival and departure. Positive is late-side, negative early-side. This one reads the raw tap rather than the rounded one, so it shows a pattern that rounding would otherwise hide.
- Recorded times — how often the worker supplied their own start or end time instead of it coming from a tap, with the cumulative minutes that added or removed.
- Correction burden — the share of their shifts where a supervisor adjusted a start, end, or meal status.
- Auto-ended shifts — how often a shift ended automatically because there was no clock-out tap.
- Meal claims — how often the worker reported a missed or short meal.
- Unscheduled shifts — shifts worked with no matching schedule.
FabWise sets no thresholds on any of these, deliberately. There is no line at which a number turns red, no flag, and no score. What counts as too many auto-ended shifts, or a tap variance worth a conversation, is a judgment for your shop — some run lenient, some run strict, and a number that means trouble in one shop is unremarkable in another. Software guessing that line for you would be worse than useless; it would be confidently wrong.
What the panel is for is simpler than that: you can't improve what you can't see. These are the patterns that are invisible when you look at shifts one at a time, and obvious when you look at sixty days of them at once.
The presentation is deliberately neutral — plain figures, no colour coding, no accusatory language — for the same reason the rest of FabWise avoids red and green on anything a person self-reports. A number that arrives looking like an accusation gets argued with. A number that arrives as a fact gets acted on.
Arrival & departure patterns
Two cards break down how shifts start and end over the window, as a stacked bar with a legend and a 12-month on-time-percentage trend:
- Arrival — on time, arrived early (waited), started early, late, forgot to clock in, or unscheduled.
- Departure — on time, left early, worked late, forgot to clock out, or unscheduled.
Patterns tell you more than a single number: someone "85% on time" who is always a few minutes late reads differently from someone usually perfect with two bad weeks.
Absences
A panel summarizing missed shifts over the window:
- Counts by classification — Excused, Unexcused, No-call-no-show, and Unclassified (missed but not yet reviewed).
- Trend — missed shifts per month over the last 12 months.
You set the classification when you review a missed shift on Timecards — see Hours Review → Missed shifts. A missed shift later corrected to "worked" drops out of these counts automatically.
Absence log
Below the counts, the Absence log lists every missed shift in the last 12 months — each with its classification, your manager note, who recorded it, and a link to the shift. This is your accountability record: contemporaneous, attributed, and always ready. It's the difference between "I think they've been late a lot" and a dated, documented list.
The absence log and notes are manager-only — they never appear on the worker's own view.
Work distribution
Where the worker's time went — broken down by customer, by job, and by labor code. Useful for job-costing visibility and for understanding what a worker actually spends their day on.
What workers see
If you enable the Self Performance module (Settings → Features), each worker can see their own standing on their Workstation Performance page: their three headline metrics, with the shop average alongside when you've also turned on shop performance visibility and enough of the team is active (at least 4 workers with a completed shift in the window).
It's deliberately the motivating half of the same picture — workers see where they stand, presented the same unbiased way you see it. The premise is that people manage their own performance better when the information reaches them plainly, without a judgment attached to it.
Precisely what a worker sees on their own page:
| On the worker's own page | Admin-only |
|---|---|
| Punctuality, schedule adherence, task coverage — their three headline metrics | The three supporting metrics |
| The shop average alongside, when you've enabled shop performance visibility | The six Pattern lenses |
| Their shift count, total hours, and last shift for the window | The Absences panel and counts |
| The Absence log, including every manager note and who recorded it | |
| Arrival and departure pattern breakdowns | |
| Work distribution by customer, job, and labor code |
A worker never sees another worker's numbers — the only comparison available to them is the shop average, never a named colleague. Attendance classification and the manager note are a supervisor's judgment call and stay on your side of the line.
Good to know
- Everything is a rolling 60-day window (with a 12-month trend), so the page reflects recent behavior, not a worker's entire history. The absence log is the exception — it reaches back a full year.
- Shop average, not peers. Workers compare against the shop average, never against named co-workers.
- None of it is a pay or compliance determination. Excused, unexcused, and no-call-no-show are all zero worked hours; your payroll provider classifies pay.
Related
- Hours Review — where you classify a missed shift
- Shift Detail
- Enrolling Workers for Workstation
Last updated: 2026-08-29