Time by job for a period
Period 2–15 Aug 2026 · hours onlyLabor hours by job, by crew, by week — close to live, from the same approved hours the payroll batch is built from, read back the other way. Deliberately no dollar rates: job costing stays in Sage, where it already works. A project manager who needs dollars asks accounting — same as today, minus the two-week wait for the hours.
| Job | Crews | Week 1 | Week 2 | Period hours |
|---|---|---|---|---|
| J-2041 Cottonwood Clinic | 4 | 1,644.25 | 1,640.25 | 3,284.50 |
| J-1975 Ridgeline Data Center | 3 | 1,458.50 | 1,451.75 | 2,910.25 |
| J-2088 Riverbend Warehouse | 3 | 1,071.25 | 1,074.75 | 2,146.00 |
| J-2103 Maple Ridge Apartments | 2 | 936.50 | 942.25 | 1,878.75 |
Top four jobs of the current batch, in hours. The same numbers land in Sage through the payroll import — this is the hours view, not a second set of books.
The second signature
Approval depthSome divisions want one approval on a timesheet, some want two. That is approval depth — configuration per division, one step or two, rows an administrator edits rather than a rebuild.
What is confirmed: the North and South chains differ, and the depth is one step or two. Which applies to which division — and who each chain ends at — is being confirmed rather than guessed, because a wrong chain routes approvals to somebody with no authority to give them. See the setting →