Alex Voltner

Legal name

Alexander James Voltner

Preferred name

Alex

Home address

4820 Copperline Way, Apt 6
Ogden, UT 84403

Mobile

(555) 555-0147

Personal email

a.voltner@example.invalid

Work email

alex.voltner@example.invalid

Shirt / jacket

L / XL

Legal name and preferred name are two fields, not one. Payroll documents and the I-9 must carry the legal name; the directory, the crew list and the app greeting should carry the one he answers to. Collapsing them into a single field forces a choice that gets somebody’s paperwork rejected or somebody’s name wrong every day.

Notice what is visible and what is not. That the split is 60/40 across two accounts is structure — payroll needs it, and it is not a secret. The account numbers and the amounts are, and they stay masked for this role. Bank details are the reason this data sits in a separate database schema that the ordinary application account holds no privileges on at all.

Position

Journeyman electrician

Classification

Regular full-time · non-exempt

Division

North

Reports to

Riley Ohm · field supervisor

Hire date

14 March 2023

Years of service

3

Employee number

WE-4417

Sage employee ID

4417

Pay cycle

Biweekly · Sunday → Saturday

The Sage employee ID is the link, and it is deliberately Sage’s number rather than ours. This system does not mint payroll identity; it borrows it, so there is never a question of which record is the real one.

There is no balance field anywhere in this system. The number at the top is the sum of the rows underneath it, and a correction is a new dated row rather than an edit to an old one. “Why is my balance 16?” has a printable answer, and nobody can quietly change it.

Request time off in WE Time →

Every acknowledgment binds to a version, and the 2025 row is kept rather than replaced. “Has this person signed the handbook?” is not an answerable question; “which version did they sign, and is it current?” is. The signed copy is stored exactly as it was shown, so it can be produced later.

All files, company and personal →

Reminders fire at 60, 30 and 7 days before expiry, and each one is recorded once — a retry does not re-send it, and an argument about whether somebody was told has an answer. The arc flash row was entered once for a whole class and landed on 41 individual records; it is one training event, not 41 pieces of data entry.

Last completed class

Code Update · Spring 2026

Grade

B+

Reimbursement band

$250

Apprentice hours logged

—

Two different records that look alike and must never be merged: a class with a grade drives tuition reimbursement, and total hours inside a date range serves licensure reporting. Alex is past his apprenticeship, so the second row is empty rather than zero.

Your reviews run on the EOS People Analyzer in the Hub: each person is assessed against the company’s core values, plus GWC. The frame is below. The scoring is not, and we have not invented one.

Review cadence

Not yet configured

Last review

—

Reviewer

Riley Ohm · field supervisor

There is nothing behind this panel to reveal. The query a field supervisor makes returns no rows at all — not a count, not a date, not “3 items hidden”. A screen that hides content it has already loaded is one developer mistake away from showing it; a query that never returns the content is not.

For the record: nothing about Alex is stored in this section in this prototype. There is no synthetic disciplinary content anywhere in this demonstration, invented or otherwise.

An assignment is a dated range, not a checkbox on a person. “Who had V-12 in April?” is a question an accident report asks and an insurer asks, and it has to survive the van being reassigned twice since. The same dated list is what the offboarding checklist reads when somebody leaves, so nothing has to be remembered.