UC4 · TTS spread job
Persona · Maria Rivera — Staffing Clerk · Dept 3630 / Line 5
Goal · Capture one employee's time across multiple shop orders without manual math
Time today · about 2 minutes
What "TTS" actually means
TTS = Time To Spread. Some shop orders are flagged as "spread-eligible," meaning one employee's activity time should be split across several shop orders for reporting and downstream payroll, weighted by shop-order line hours.
Today, this is one of the most error-prone parts of staffing — either the clerk has to split the time by hand, or the timekeeper has to do it later from a separate note. Either way, the link between the keyed activity and the allocation lives outside the system.
Why this is a separate use case
UC1 walked through the normal staffing flow. TTS is an edge case that the proposed solution explicitly handles: one keyed activity, multiple shop-order tags, automatic allocation by line-hour weighting.
There's still one open implementation choice for Ryan / IT about where the allocation rows live (in the new database or computed by the Mt Olive IT poll/extract). That doesn't change what the staffing clerk does. See future-state diagrams §4 for the contract decision.
What we'll walk through
- Spot a spread-flagged order in your scope
- Key one activity, tag the shop orders
- See the allocation preview
- Recap — what changed and what stayed the same
What success looks like
- Maria doesn't do allocation math.
- The activity is captured once.
- The downstream warehouse / PLP feed sees the spread the same way whether persistence lives in the new DB or the IT extract.
▶ Start: Step 1 — Spot a spread-flagged order · 🏠 Demo Home