v2026.06.10
June 10, 2026
We rebuilt the shift review flow from the ground up. The changes are significant — not because the basic idea changed, but because the mechanics underneath it were producing subtle errors that were hard to see until hours were exported. Here's what's different and why it matters.
Hours Review — exception-driven, per-week navigation
The old review page was a list of flagged shifts. You'd click one, see the flag reason, and click Approve. It worked, mostly. But if you were reviewing 20 shifts on a Friday afternoon, it was easy to lose the thread of what you'd already reviewed and what still needed attention.
The new Hours Report is an exception-driven grid. It shows every worker, every shift, and every open exception for the week — organized so you can work through top to bottom without losing your place. You acknowledge exceptions in context, correct times inline, and sign off on a worker's week when everything looks right.
Each week now has its own URL. Click away, come back later, use your browser's back button or a bookmark — you always land on the same week's grid. No more starting over because you navigated away.
When you acknowledge an exception, FabWise records what the shift looked like at that moment. If something about the shift changes afterward — a time gets corrected, a break gets updated — the acknowledgment automatically reopens. You review the corrected version, not the old one. No stale approvals.
Meal breaks — the question now appears less often, and means more
Previously, every clock-out asked whether you took your scheduled meal break. Workers on short shifts, workers who left before the scheduled lunch window, workers on their third cup of coffee at 10 AM — all of them saw the same question. Most of them tapped through without reading.
Now, the meal break question only appears when the shift actually qualified for a lunch break — long enough, and actually overlapping the scheduled window. Workers on a 4-hour shift don't see it. Workers who left at 11 AM before the noon window don't see it. The question appears when the break could plausibly have happened.
When it does appear, the framing is clearer: Yes, I took my meal break is the first option — because taking the break is the normal case. Skipping requires an affirmative choice.
If a worker's answer doesn't match what a supervisor saw, supervisors can correct it directly from the shift detail.
Job costing — direct vs. indirect time split
For shops using FabWise to track job costs: the Hours Report now shows you how much of each shift was directly on a job task, and how much was indirect (walking, setup, clean-up, between tasks).
The split gives you a better read on your true labor cost per job. Time on a task rolls up to the job. Time between tasks — what we're now calling indirect — stays separate so it doesn't silently inflate job costs with time that wasn't actually spent on that job.
Sign-off for payroll export
There's now a formal sign-off step before you export to payroll. When a worker's week is clean — all exceptions resolved — you sign off. That locks the week. The CSV export includes only signed-off workers.
If you need to make a correction after signing off, unlock the week with a note explaining why. The system marks the week as amended and shows it in the report. Your payroll provider sees clean, deliberate numbers.
Historical weeks (before this update) are grandfathered and can still be exported. Going forward, the sign-off is required.
This is a significant workflow update. If anything looks unexpected after upgrading, open Foreman in the corner of the app and ask — it knows the new flow.