Industry
Where public-sector workforce complexity meets HCM that handles it.
Civil service rules, prevailing wage, certified payroll, multi-union scheduling, and budget appropriation cycles — where generic HCM hits its limits, our public sector practice picks up.
Challenges we see
Public agencies run civil service rules and multi-union contracts on the same workforce. Civil service carries classifications, seniority, bumping rights, and layoff order. Multi-union contracts carry separate pay scales, scheduling protections, and grievance mechanisms per bargaining unit. Both touch the same payroll and the same scheduling surface. Generic HCM handles one or the other, rarely both, and almost never the way they actually intersect.
We design HCM configurations that model civil service rules and multi-union contracts as parallel, intersecting systems — not as one bolted onto the other. Classifications, bumping logic, seniority, and union-specific rules all encode correctly, and the intersection points hold up when reduction-in-force or reorganization tests them.
Public sector workforce structure is shaped by compliance regimes that aren't negotiable. Davis-Bacon and prevailing wage on capital projects. Certified payroll reporting per project, week, union, and classification. Public records requests that turn payroll detail into FOIA-disclosable documents. Audit trails that survive accountability review. Generic HCM was designed for compliance as an output. Public sector compliance is more often an input.
We build configurations that treat compliance as a design constraint, not a reporting overlay. Prevailing wage classifications, certified payroll structure, and audit-ready labor distribution all encode at the configuration layer, where they hold up under inspection without manual reconstruction or after-the-fact reporting workarounds.
Our expertise
Where the depth comes from
Civil service classification systems
Civil service is a parallel rule system that touches every part of HCM. Class specs define position scope, qualifications, and pay range. Examination-based promotion ties advancement to formal processes that have to be auditable. Reclassification cycles change classification without changing the person, and the HCM has to handle that distinction without breaking salary history, seniority, or pension contribution continuity. We've configured class spec systems for agencies where every position has been classified through formal study, where class code counts run into the thousands, and we've designed reclassification workflows that preserve the audit trail civil service review boards actually look at.
Prevailing wage and certified payroll
Davis-Bacon, state prevailing wage acts, and local prevailing wage ordinances all carry their own rate determinations, fringe benefit calculations, and reporting cadences. Certified payroll has to track project, week, classification, hours, gross wages, fringe, and deductions per worker — and it has to reconcile against the prevailing wage rates in effect on the project's start date, not the rates in effect when payroll runs. We build configurations that handle multi-jurisdictional prevailing wage on one workforce, with certified payroll output that passes accountability review without manual reconstruction.
Multi-union scheduling and contract management
Public agencies often run six or more bargaining units on the same payroll: AFSCME, SEIU, IUOE, IBEW, Teamsters, police and fire associations, and agency-specific bargaining units. Each contract carries its own pay scales, scheduling protections, hour banks, premium pay structures, and grievance procedures. When a contract renegotiates, the changes ripple through accruals, scheduling, premium pay, and benefits simultaneously. We design configurations that handle multi-union reality without hard-coding union-specific logic into rule structures that break at the next contract cycle.
Public sector benefits and pension systems
Public sector pensions don't work like corporate retirement. CalPERS, IMRF, MERS, and state retirement systems each carry contribution structures, vesting schedules, service credit calculations, and reporting requirements that the HCM has to feed correctly. OPEB obligations (retiree health benefits) carry their own actuarial inputs. Some agencies replace social security with their pension system, which changes payroll tax treatment fundamentally. We configure pension system integration at the contribution and reporting layer — the data that keeps actuarial valuations accurate and that survives the audit cycle pension boards run annually.
Workforce reductions and bumping rights
Reduction-in-force in a public agency is one of the hardest moments HCM has to handle. Civil service rules dictate layoff order by classification and seniority. Union contracts dictate displacement and bumping rights, which often allow a senior employee in one classification to displace a junior employee in a different classification — sometimes across union boundaries, sometimes only within them. Recall lists have to maintain order for years after the RIF, with rehire eligibility tied to original classification, original seniority, and original union membership. We've built RIF workflows that model both civil service order and union bumping logic together, that produce the documentation grievance arbitrators actually look at, and that survive the chain reaction the first bump can trigger across the workforce. RIF configuration accuracy is the difference between a clean reduction and twelve months of grievances.
Frequently asked
Questions we hear
Which HCM and WFM platforms do you work with in public sector?
UKG Pro, UKG Pro WFM, and ADP Workforce Now are where most of our public sector implementation depth sits — they handle the civil service classification, multi-union scheduling, prevailing wage, and certified payroll complexity public agencies actually need. Paylocity shows up occasionally in smaller municipalities and special districts where the workforce model is simpler. Public sector tilts toward UKG and ADP more heavily than the broader HCM market does, and our portfolio reflects that. Our advisory work stays platform-agnostic. Our implementation work goes platform-deep.
How do you handle prevailing wage and certified payroll across multiple jurisdictions?
Many public sector projects carry overlapping prevailing wage regimes — federal Davis-Bacon, state prevailing wage acts, and local prevailing wage ordinances all touching the same workforce on the same project. Each regime has its own rate determinations, fringe benefit calculations, and reporting cadences, and they don't always agree. We design configurations that handle the multi-jurisdictional reality at the rate determination layer, not as a reporting overlay. Certified payroll output reconciles against the rates in effect on the project's start date, per worker, per classification, per week, with the audit trail accountability reviewers actually look at.
What's your engagement shape for municipalities vs. special districts vs. state agencies?
We work all three, with visible depth in municipalities and special districts. Municipalities carry the broadest workforce mix — police, fire, public works, parks, administration, and elected officials — often with multiple bargaining units running alongside civil service systems. Special districts (water, transit, housing, sanitation) carry distinctive characteristics: joint powers structures, multi-jurisdictional funding, and workforce models shaped by the specific function the district performs. State agencies carry their own civil service hierarchies and pension systems, and the engagement shape adjusts accordingly. The common thread is workforce complexity that exceeds what generic HCM was built to handle.
How does your work relate to the vendor's professional services organization?
Vendor professional services teams are good at getting the platform stood up. They're not always set up to handle public sector workforce complexity — civil service classification systems, multi-union contracts that don't simplify, prevailing wage compliance across overlapping jurisdictions, and pension system integration that has to feed actuarial reporting correctly. We work alongside the vendor's professional services team when the engagement structure calls for it, and we work in their place when the client wants public-sector-specific depth on the implementation team. Either way, we own the configurations that have to keep working through the next contract cycle, the next budget appropriation, and the next reduction-in-force.
What about civil service compliance and audit-readiness?
Audit-readiness in civil service work isn't a separate deliverable. It's what you get when classification systems, examination-based promotion processes, reclassification workflows, and seniority calculations are configured correctly to begin with. We design HCM configurations that produce the documentation civil service review boards actually look at — class spec change logs, reclassification audit trails, examination-to-position links, and seniority calculations that hold up under formal review. When the auditor or the review board asks for documentation, the system produces it from the configuration that ran the work, not from a reconstruction after the fact.
Do you handle multi-union contract negotiation cycles?
Contract renegotiation is one of the moments where HCM configurations break quietly — new pay scales, revised seniority rules, changed differential structures, and updated grievance procedures all have to encode into the existing system without disturbing the configurations that aren't changing. Public sector multi-union environments magnify this because contract cycles for different bargaining units rarely align, which means the system is in some state of mid-cycle change most of the time. We support clients through the configuration side of contract cycles — modeling proposed changes against current state, identifying conflicts with existing rule structures, and implementing updates before each new contract's effective date. Negotiation strategy and bargaining are not our practice; configuration accuracy through the change is.
What about public sector pension system integration?
Public sector pension systems work fundamentally differently from corporate retirement plans. CalPERS, IMRF, MERS, and state retirement systems each carry contribution structures, vesting schedules, service credit calculations, and reporting requirements that the HCM has to feed correctly to keep actuarial valuations accurate. OPEB obligations carry their own actuarial inputs. Some agencies replace social security with their pension system entirely, which changes payroll tax treatment and reporting in ways generic HCM doesn't anticipate. We configure pension system integration at the contribution and reporting layer, where the data flows correctly from payroll through to the annual actuarial cycle and the audits that follow it.
Selected work
Featured case studies
- Chicago Housing Authority
Custom Salesforce case management integrated with Yardi property operations: the Chicago Housing Authority
Resident-services case management with Yardi integration for the CHA
Read the case study →
Ready to talk through government & public sector?
Tell us about your operational priority. We'll respond within one business day and route the right people to the conversation.