UC2 · Resolving an activity error
Persona · Kavi Patel — Timekeeper · Pilot scope (all pilot lines)
Goal · Clear a hard-fail activity error so payroll close isn't held up
Time today · about 3 minutes from open to apply correction
Meet Kavi
Kavi has been a timekeeper at MTO for twelve years. On any given day he's juggling missing punches, meal exceptions, and activity mismatches — and historically each one came from a different report, a different spreadsheet, or a hallway question.
In the current process, an "activity error" might be a punch that doesn't match the staffing sheet, or a job code that wasn't keyed at all, or a number that doesn't add up on the PLP feed. Each one took digging across systems to figure out what really happened.
In the new app, every validation outcome from the staffing flow lands in a single Activity Errors workspace. Each item carries the punch context, the activity context, and the audit trail — Kavi can see the whole picture without leaving the screen.
What we'll walk through
- Open the Activity Errors queue
- Pick a hard fail and read the punch-vs-activity timeline
- Choose a fix
- Apply the correction — downstream clears
- Recap — what changed and what stayed the same
What success looks like
- Every activity error has one place to live, with the context Kavi needs.
- A hard fail can be resolved in minutes, not hours.
- Downstream feeds (PLP/BI, Activity Errors report, payroll continuity) reflect the fix automatically.
- Kavi spends his time on judgment calls and exceptions, not on hunting for evidence.
▶ Start: Step 1 — Open the queue · 🏠 Demo Home