Federal shared services promised that payroll, human-resources processing, and financial management would consolidate into a few centers serving everyone, with savings too obvious to lose. The record is mixed in a specific, measurable way. The Treasury's two shared-service providers and the Interior Business Center process personnel actions for a substantial share of the government, and standardization of those transactions genuinely reduced per-transaction costs — the Office of Management and Budget reported steady migration to shared providers through the 2010s. But the GAO's inventory of government-wide management reports kept finding the same structural gap: agencies with heavily customized legacy systems could not migrate without modernization projects of their own, so the agencies that most needed the savings were the ones that could least afford to switch.
This article publishes information about government administration, not advice on any specific procurement or migration decision.
How the model was supposed to work
FIX
What the record shows
Three findings repeat across GAO reviews. First, cost savings exist but concentrate in uncomplicated agencies: those with standard payroll profiles and no exotic statutory reporting requirements. Second, the marketplace never fully formed — providers operated without published, enforceable service-level agreements in the early years, and customer agencies had limited recourse when service degraded, a problem GAO flagged repeatedly before the Unified Shared Services Management Office standardized templates. Third, the exit of providers destabilized the market: when the Treasury's HR line of business offerings contracted and NASA's shared-services center repositioned, customer agencies faced forced re-migrations whose transition costs consumed years of projected savings.
Why agencies stay on legacy systems anyway
The blocker is not preference; it is appropriations math. Migrating a payroll system requires funding for integration, data cleanup, and parallel running — money that must be found in the year it is spent, while the savings arrive on someone else's watch. Without a central transition fund, an agency chief financial officer is asked to pay a certain cost now for an uncertain benefit later, and rationally declines. The result is the equilibrium documented in OMB's own IT dashboard reporting: a core of migrated agencies, a band of agencies permanently mid-migration, and a tail of legacy systems whose annual operating cost exceeds migration cost only when measured over a decade no budget cycle covers.
What a working version would need
The evidence points to four requirements. Publishable service-level agreements with financial remedies, so customers have leverage. A central transition fund, so migration costs are not paid from the mover's own budget. Standard data schemas set by the referee office, so switching providers becomes possible at all. And a decommissioning discipline: each migration ends with a legacy system actually turned off, with the date recorded. Where those four existed, consolidation held; where they were missing, agencies drifted back to doing it themselves.
FAQ
What is a federal shared service center?
A government-operated provider — run by Treasury, Interior, or Agriculture, among others — that processes payroll, HR, or financial-management transactions for other agencies as a paid service.
Did shared services save the government money?
Yes for agencies with standard needs: per-transaction costs fell and duplicate systems were retired. Agencies with customized legacy systems often found migration costs exceeded the savings horizon.
Who referees the federal shared-services marketplace?
The Unified Shared Services Management Office within OMB, created to set standards, contracts, and migration guidance for administrative shared services.
For more context, read Agency Mergers: Why Consolidations Rarely Save Money.
For more context, read pendleton act 1883.
For more context, read Performance-Based Budgeting: Why the Numbers Rarely Bind.