Headcount by division
Who is employed, where, and in which division — the count everything else gets checked against.
| Division | Field | Office | Total |
|---|---|---|---|
| North | 82 | 16 | 98 |
| South | 73 | 14 | 87 |
| Total | 155 | 30 | 185 |
185 is your stated headcount. Your BambooHR export has 186 rows. One of those is probably a placeholder record — but “probably” is not good enough for a number that becomes the migration check that asks “did everybody land?”, so it gets reconciled before it becomes an assertion.
Certifications expiring
Licences, safety cards and driving credentials against the 60 / 30 / 7-day reminder ladder.
| Window | People | Status |
|---|---|---|
| Within 7 days | 3 | Act now |
| Within 30 days | 9 | Notice sent |
| Within 60 days | 14 | Notice sent |
| Already expired | 0 | Clear |
Not a vanity metric: without a current Utah licence a person is a laborer, which changes what they may be assigned tomorrow. Who receives these reminders — the holder, their manager, HR, or all three — is still being confirmed, and telling only the holder is the weakest of the three.
PTO liability
Unused paid time off held across the company, in hours, by division.
| Division | People | Hours held |
|---|---|---|
| North | 98 | 2,216.00 |
| South | 87 | 1,904.00 |
| Total | 185 | 4,120.00 |
Hours, not dollars — deliberately. Pricing hours is payroll's job and stays in Sage. Two inputs are also still open: the carryover ceiling, and whether unused time is paid out on separation. That second one is a Utah wage-law determination, not a product setting, so we will not pick a reading for you.
Job & time reports
Time by job, approved hours and the approval-chain views live in WE Time, next to the timesheets they read from.
New hires this quarter
People who started between 1 July and today, with their onboarding status.
| Division | Started | Onboarding open |
|---|---|---|
| North | 4 | 1 |
| South | 2 | 1 |
| Total | 6 | 2 |
A hire is also a manual keying job in Sage today, and that stays true after cutover. So this report is the trigger for real work downstream, which is why the new-hire alert has to be reliable rather than a courtesy copy.
Compliance reports
EEO-1 · OSHA 300 · ACA
The reports section of your intake form came back blank — all nine questions, these three included. So this card names them and claims nothing: we do not know today whether Wilkinson files an EEO-1, maintains an OSHA 300 log, or produces ACA filings in-house, nor who would do it. Each answer changes what data has to be collected, from whom, and how it is classified — EEO self-identification in particular has to be voluntary with an explicit decline, which is a design consequence, not a checkbox.
One nearby thing we do know. Certified payroll is filed, federal and state, and it is produced from Sage today. It stays there. We are not building a certified payroll report and we are not becoming a payroll engine to do it.
Need something that isn't here?
Custom report builderThe builder lets an admin assemble a report from the employee fields their role is permitted to see — including custom fields you add yourself. It is also the screen where the security model is most visible, so it is worth two minutes.