modules
Workforce
Never staff a shift with the wrong hands again — rosters prove qualification first.
The 2 a.m. call no one wants: a line down because the only certified operator called in sick and nobody qualified is on shift. Workforce ends that lottery. Rosters resolve against live demand, skills, certifications, and availability — so the schedule only ever offers hands that can legally and actually do the work.
Why workforce truth matters
Most ERP systems keep HR in a separate module and export labor to operations as an afterthought. Shifts get planned against stale headcounts, attendance lands in payroll weeks late, and nobody can say which hours belong to which work. XRP treats the workforce as operational truth: rosters resolve against live demand, punches allocate to the work actually run, and costs flow while the shift is still on the floor. When a worker clocks in on the shop floor, their time allocates to the work order they are running. Labor costs flow to finance as payroll-ready events — live facts, not batch exports. Union contracts, benefits, and regional compliance sit on the workforce model as governed extensions.
data Viz
data View
section: thesis
Who answers for Workforce
Four roles, four anxieties, one worker graph answering each.
data Viz
data View
section: personas
Section 1
col Title: COO
col Cont: Coverage without the lottery. Every shift staffed with qualified hands, absence re-offered automatically, and labor costs flowing while shifts run.
Section 2
col Title: Plant Manager
col Cont: Skill matrices per cell with cross-training gaps named. Overtime pressure visible before rosters commit instead of discovered in the paycheck.
Section 3
col Title: CFO
col Cont: Labor costs accrue to work orders and projects live — no month-end scramble to explain variances nobody tracked while they happened.
Section 4
col Title: Compliance Leader
col Cont: Certifications gated at offer time, grievances cased with policy references, and wage-hour regimes applied per jurisdiction as governed extensions.
How Workforce works
Demand plans and work orders emit labor requirements with skill and certification constraints. Scheduling resolves them against the worker graph — role, skill, certification, shift pattern, attendance state — and proposes rosters that satisfy coverage without breaking compliance or overtime policy. Punches then validate against roster and assignment state, allocate to active work, and accumulate into timecards with overtime, exceptions, and approvals resolved before payroll-input events emit.
data Viz
data View
section: how-it-works
Workforce capabilities
- Qualified offers only
- Uncertified or unavailable workers are never offered for constrained shifts
- Overtime visibility
- Overtime pressure and availability surface before the roster commits, not after
- Live allocation
- Attendance allocates to work orders and service work as it validates
- Payroll certification
- Exceptions and approvals resolve before payroll-input events emit to finance
- Multi-site identity
- One session model and one access decision path whether you run one site or fifty
- Change propagation
- Demand or absence changes revalidate affected assignments automatically with markers downstream
- section
- capabilities
From staffing lottery to proven coverage
subtitle: What each stage feels like after adoption.
layout: alternating
enable Slideshow: false
slideshow Interval: 5000
Rosters prove qualification
date: Phase 1
status: in-progress
Shift offers filter through skills, certifications, and availability first.
has Learn More: false
Hours allocate live
date: Phase 2
status: upcoming
Punches land on the work actually run with costs flowing same-shift.
has Learn More: false
Exceptions resolve, not accumulate
date: Phase 3
status: upcoming
Absences re-offer automatically; payroll certifies instead of estimating.
has Learn More: false
Labor plans from facts
date: Phase 4
status: upcoming
Hiring and training target the qualification gaps the roster names.
has Learn More: false
Workforce in daily operation
Each surface below reads the same worker graph — schedules offer only qualified hands, clocks prove the hours, and every exception resolves before payroll.
data Viz
data View
section: applications
Demand Scheduling
Labor requirements from work orders, service slots, and demand plans resolve against skills, certifications, and availability. Coverage gaps show with the missing qualification named, so hiring and training target real holes.
Time Capture
Badge, biometric, and mobile punches validate against roster state and allocate to active work. Missed punches raise supervisor-routed exceptions instead of estimated hours.
Leave and Absence
Leave balances, requests, and approvals with coverage impact shown before approval. Approved absence invalidates affected assignments and triggers re-offer automatically.
Certifications
Skill and certification records with expiry tracking gate shift offers. Lapsing credentials flag weeks ahead with the affected roster dates listed, so retraining lands before coverage breaks.
Deployment and integration
Workforce runs inside every XRP topology — self-hosted, cloud, hybrid, air-gapped, or edge — with time-capture devices syncing through signed offline bundles where connectivity is intermittent. Biometric and badge clocks, mobile punch apps, and supervisor consoles all write the same assignment and attendance truth. External payroll owns pay computation; XRP hands it certified inputs with cost rollup attached.
data Viz
data View
section: deployment
Governance and compliance
Every assignment carries reason, authority, effective instant, and source evidence. Grievance and disciplinary records are first-class objects with case state, policy reference, and participants. Wage-hour, timekeeping, leave, and safety regimes apply by jurisdiction as governed extensions, and every access to sensitive workforce data is issued through ARGUS with purpose, scope, and evidence receipt.
data Viz
data View
section: governance
Workforce sub-modules
subtitle: Roster the work, then prove the hours.
data View: workforce:sub-modules
Shift Scheduling
desc: Qualified, available rosters from live demand.
link: /sub-modules/shift-scheduling
Attendance Tracking
desc: Punches allocated to the work actually run.
link: /sub-modules/attendance-tracking
Workforce questions
Section 1
Does Workforce replace HR administration?
No. Operational workforce truth — roster, assignment, attendance, labor events — lives here and references Part 3C HRCM. Broad HR administration remains with its canonical owner.
Section 2
How does labor reach payroll?
Validated attendance allocates to work orders and projects, then emits payroll-input events with cost rollup for Part 3A finance. No manual reclassification between grant-funded and general positions.
Section 3
What happens when a scheduled worker calls in sick?
The absence invalidates affected assignments and the scheduler re-offers the shift to qualified, available workers. Downstream work orders and service slots see the impact immediately.
Section 4
Can uncertified workers cover constrained operations?
No. Certification constraints are hard gates resolved against HRCM truth. The roster shows the coverage gap rather than offering an unqualified worker.
Section 5
How does this work across fifty sites?
One worker graph with effective-dated edges for location, department, and assignment. A transfer supersedes edges with new effective dates instead of rewriting history, so reporting stays correct across the move.
Section 6
Our union contract has complex work rules. Can this handle them?
Work rules sit on the model as governed extensions — overtime triggers, seniority preferences, mandatory rest — enforced at offer time instead of grieved afterward.
Section 7
Will supervisors lose control over their crews?
No. Supervisors approve, override with authority, and handle exceptions — the system just stops them from accidentally assigning unqualified hands or blowing overtime budgets blind.
data View
section: faqs
content section
value: One identity boundary across every site: one session model, one access decision path, and workforce facts that downstream planning, costing, and compliance consume directly. Schedules reference Part 3C HRCM worker truth — employee, assignment, skill, certification, shift, and attendance — and emit payroll-ready events that finance consumes without batch reconciliation.
Section 12
Demand-driven rostering with skill and certification gates
Section 13
Availability, overtime pressure, and exception visibility before commit
Section 14
Attendance capture allocated to live work orders and service slots
Section 15
Payroll-ready labor events with cost rollup for finance
Section 16
Effective-dated assignments — superseded, never overwritten
Section 17
Multi-site coverage from one identity boundary and session model
Section 18
Grievance, disciplinary, and compliance case linkage
Section 19
Downstream revalidation when demand, absence, or plans change