Usul Dynamics: People Analytics
Usul Dynamics is a fictional robotics company simulated from founding in June 2018 through today: ... synthetic employee records, zero real people. Every pattern in the data was planted on purpose, documented, and recovered by a validation gate before this page shipped (receipts at the bottom).
View SQL
View SQL
View SQL
Metric definitions
- Headcount
- People actively employed on the date shown: hired on or before it, not yet exited.
- YoY growth
- Headcount today divided by headcount exactly one year earlier, minus one.
- Annualized voluntary turnover
- Voluntary exits in the trailing 12 months divided by average month-end headcount over those 12 months.
- Involuntary turnover
- The same calculation using involuntary exits (performance and restructuring).
- Regretted share
- Of voluntary exits in the window, the percent who carried a performance rating of 4 or 5.
- Median tenure
- The middle value of years-since-hire across everyone currently employed.
- Open reqs
- Requisitions with no hire yet at the data cutoff. Reqs carry a department and level, not a location.
- Turnover by tenure
- Voluntary exits while in a tenure range divided by the person-years worked in that range, annualized.
- Person-years
- Time worked summed across people, in years: two people for six months is one person-year.
- Payroll cost
- The sum of active employees' annual base salaries in that month, divided by 12: a monthly run rate.
A seeded generator simulates the company month by month and writes plain CSVs (employees, comp events, requisitions). A DuckDB transform aggregates them into the single JSON file this page fetches. The build refuses to ship unless every planted effect is recovered within its documented tolerance, so the numbers above are not just plausible: they are checked.
Validation report: planted vs recovered
View SQL (full transform)
View SQL
View SQL
View SQL
View SQL
Models run in the pipeline over every active employee as of ; nothing statistical runs in this page, so the module 1 filters do not apply here. The binary gap compares women and men (ethnicity is module 2's lens); nonbinary colleagues are included in the remediation scan but not the two-group gap.
Both are honest answers to different questions. The unadjusted gap asks: what does the typical woman earn here vs the typical man? It bundles pay setting together with who holds which level in which department. The adjusted gap asks: are two colleagues with the same level group, department, location, tenure, and performance paid alike? Closing the adjusted gap is a comp-policy fix; closing the unadjusted gap also takes the representation shifts in module 2.
View SQL
View SQL
View SQL
View SQL
Validation report: pay effects, planted vs recovered
View SQL
View SQL
View SQL
View SQL
Model constants and what is excluded
Same suite, your HRIS
Usul Dynamics is fictional; the method is not. Pointed at your real HRIS and ATS exports, the same pipeline ships a validated workforce mart and an interactive suite your leadership can actually explore, with every number backed by SQL you can audit.