←
WE People Settings · Configuration — rows you edit, not code we ship
Every panel below looks editable and none of it saves — this is a prototype. What is real is the shape: each one is a table of rows in your tenant's configuration. Changing any of it is an afternoon for an administrator, not a release for us.

Holidays

7 paid
Paid holiday calendar Preview only
New Year's Day
Memorial Day
Independence Day
Pioneer Day Utah state holiday — the one a federal calendar omits
Labor Day
Thanksgiving
Christmas
Rows in your configuration, not code.
Birthday — a leave type, not an eighth holiday Preview only
Paid days
Usable within Computed from each person's own date, so no two people get the same day
Carries over
Rows in your configuration, not code. Modelled as an eighth holiday it would give all 185 people the same day off.
Still being confirmed on this panel How many paid hours a holiday is worth, what happens when one falls at a weekend, how a worked holiday is treated, and whether one calendar covers both divisions. Your handbook has answers for some of it; the handbook is not the same thing as your confirmation, so these stay blank rather than guessed.

Time-off policy

Granted, not accrued
PTO grant mechanics Preview only
Mechanic A grant is one dated event. An accrual is a calculation every period. Different engines, not two settings on one.
Determined by Position is a real input — same tenure, different position, different grant
Yearly increase
Ceiling Confirmed that it maxes out; the number was not stated
Waiting period before use
Carryover permitted
Carryover cap Answered as “a specific amount” with no amount
Above the cap Paid out, not forfeited — which makes it a payroll event, not just a balance change
Paid out on separation Answered “typically but not always”, which is not a rule — and it is a Utah wage-law question, so it is not ours to settle
Rows in your configuration, not code.
Holiday eligibility tiers Preview only
Master, journeyman, office
Apprentice, laborer Whichever comes first — which is why a licence is not a display field
Rows in your configuration, not code. The day an apprentice's journeyman licence is verified, their eligibility changes — mid-year, on an event, not on an anniversary.
There are no blackout dates here — confirmed, not assumed, and worth as much as a yes. There is also no separate sick bank and no bereavement bank: sick time comes out of PTO. We will not seed balances you told us you do not have.

Time rules live in WE Time

Pointer

Rounding to the nearest quarter-hour and the approval depth per division are configuration of the time app, not of the people record — so they live on WE Time's own settings page, next to the screens they govern. What stays here is everything about people and leave: holidays, PTO grants, certifications, onboarding.

Certification types

Admin-editable
Registry Preview only
Journeyman Electrician Licence
Master Electrician Licence
Apprentice Registration
OSHA 10
OSHA 30
CPR
First Aid
Confined Space
Aerial / Scissor Lift
Forklift
Driver's Licence
Commercial Driver's Licence
Add your own — this list is never fixed in the software
Rows in your configuration, not code. Each type can hold a number, issue date, expiry, issuing state and a scanned copy — which of those you actually record is being confirmed. Reminders run at your stated 2 months, 1 month and 1 week before expiry.

Onboarding checklist variants

3 variants
Variants by position Preview only
Office No licence upload, no tool list, no safety equipment acknowledgment
Field Adds licence upload, tool list review, safety equipment acknowledgment
Apprentice Field, plus apprentice registration and the class reimbursement briefing
Rows in your configuration, not code.
Task order — and one real dependency Preview only
1 · Electronic disclosure consent
2 · Form I-9
3 · Form W-4
4 · Licence uploads
5 · Benefits review
6 · Tool list review
7 · Drug and alcohol policy
8 · Safety equipment
Rows in your configuration, not code. The order above is a proposal — see the note below.
One ordering question we cannot answer for you Consenting to sign electronically has to come before anything legally binding is signed — a signature collected before the signer agreed to sign electronically stands on weaker ground. Your stated order puts the I-9 and W-4 first, and both are binding. So something has to move: either the consent step comes first, or those two move after it. The constraint holds either way; which task moves is your call, and we have shown consent first only so the screen is coherent.
Worth saying because it changes the shape: this is a real dependency the engine enforces, not a sort order. A number on a row can be bypassed by a direct link or a “finish later” flow. “This task blocks those tasks” cannot.
What this screen teaches. Everything a stranger would call “the Wilkinson version” of this product is on this page, and all of it is data. Pioneer Day, the 8-hour increment, the licence accelerator on holiday eligibility, your certification list, your checklist variants — a contractor we have never met is the same software with different rows. Where a value is genuinely unknown, the field says being confirmed rather than showing you a number we made up, because a guessed setting is indistinguishable from a real one six months later.