UC5 · Step 3 of 3 — Recap
Maria Rivera · Staffing Clerk · Dept 3630 / Line 5
What just happened
In about 90 seconds at end of activity, Maria:
- Reopened the assignment for the job 0055 order.
- Entered the team's case count in the Units captured field.
- Saw the implied rate (52.6 / h) — looked normal for 32oz spears.
- Saved. Hours and units are captured atomically.
What changed vs today
| Today | With the new app |
|---|---|
| Hand-pack unit counts live in a spreadsheet or paper tally. | Unit count lives on the activity record. |
| Hours come from one source, units from another. | Both saved atomically by the same person. |
| Payroll piece-rate reconciliation is a hunt. | Reconciliation is automatic — the link is the record. |
| If the spreadsheet is lost, the units are lost. | The record is the source of truth. |
What stayed the same
- The piece-rate math is unchanged.
cases × rate, split evenly across packers on the team. - Job 0055 is still the trigger. Other job codes don't show the field.
- Payroll continuity is preserved. The downstream feed delivers the same shape of data; payroll doesn't need to change anything to consume it.
What to take into the workshops
- Are there other piece-rate job codes beyond 0055 that need this treatment? (Today the project is scoped to 0055; the model can extend.)
- Should the implied rate field be optional, or always shown?
- Should there be expected rate ranges per product (with a warning if the implied rate falls outside), or is "plausibility check by eye" sufficient?
- Who needs to see the unit count after capture? Just payroll and timekeeping, or also the supervisor's dashboard?
- How does this interact with mid-shift team changes? If someone joins or leaves Team A1 mid-activity, how does the per-person allocation adjust?
Related reading
- Proposed Phase-One Solution for Ryan Review
- Future-State Solution Diagrams
- Open Question Register — see piece-rate continuity items
⬅ Prev: Step 2 — Capture the count · Use Case Index · 🏠 Demo Home