Case — Dual clock chaos
“We had plant hours and job hours—and nobody trusted the sum.”
Before: Builders punched a generic clock at the gate, then supervisors added job hours by hand in WIP. Finance found duplicates every month; WIP percentages looked “round” but hours didn’t foot.
After Plant Pay: Plant QR for facility time, job QR on WIP cards for job-scoped shifts. The product enforces one open shift per builder—plant or job—so you can’t double-count the same afternoon. When a job shift closes, hours roll into the job as a structured update.
Case — Friday paysheet panic
“Paysheet night was three people and a prayer.”
Before: Payroll spreadsheets, texted overtime, and a PDF someone printed from who-knows-where. New supervisors didn’t know which version was official.
After Plant Pay: Builders and lines live in one workspace. Paysheets show clock-derived hours beside piecework and job-hour pay. PDFs come from the same system everyone already logged into—audit trail optional but attitude mandatory.
Case — Multi-plant expansion
“We grew to two plants and permissions became a rumor.”
Before: Shared logins and “just don’t open that tab” training. Plant B’s data leaked into Plant A’s reports in uncomfortable ways.
After Plant Pay: Company switcher, plant-scoped sessions, module permissions, and builder rows filtered against real plant assignments. People see what they should—and your story stays legally boring in the best way.
Scenario — Start of quarter
The “Monday morning” rollout you can actually say out loud
- Ops lead imports plants, crews, and builder roster (or syncs via entity APIs post-migration).
- HR prints new QR posters per plant; operations pins WIP cards with “View QR code” on active jobs.
- Builders scan, PIN in, and punch. Finance watches the dashboard for hours concentration by plant.
- End of week: paysheet owner closes WIP notes, exports paysheets, sends PDF pack to payroll partner.