Agency consolidation promises savings through eliminated overhead, but the mechanism rarely pays out on schedule. The Government Accountability Office has repeatedly found that mergers generate transition costs first — moving offices, rewriting personnel systems, reconciling information technology — and savings later, if at all. In a 2018 review of federal reorganizations, the GAO reported that agencies often could not quantify expected savings at all, because no baseline cost accounting existed before the merger began. That is the rule, not the exception: the merger is announced with a round number, and the audit arrives years later with an asterisk.
What actually happens in a merger?
A consolidation moves through predictable stages, and each one carries a bill. First comes the statutory or executive authority — either Congress writes the new agency into law, or an administration uses existing authority to realign components. Then the machinery-of-government work begins: payroll systems must be merged, procurement shops combined, and competing job classifications reconciled. The Office of Personnel Management rules on transfers, and employees whose functions overlap enter reassignment or reduction-in-force processes that take months to complete. Only after the dust settles does anyone measure whether overhead actually fell.
The measured results are sobering. When the Department of Homeland Security was assembled from 22 components in 2003, it was the largest government reorganization since 1947 — and DHS's own inspector general and the GAO spent the following decade documenting duplicated business systems and unresolved management structures. A 2005 DHS management review, followed by GAO reports through the 2010s, found the department still operating multiple financial and human-resource systems long after the merger was supposed to produce savings.
Why do the savings fail to materialize?
Three mechanisms eat the projected savings. First, transition costs are real and immediate: severance, retention incentives for people with institutional knowledge, IT migration, and physical moves. Second, consolidated agencies tend to keep both legacy systems running in parallel — the expensive duplication the merger was meant to remove — because turning one off before the replacement works is a risk no manager will own. Third, the political clock runs out. A merger launched in year one of an administration is expected to show savings by year three, but the honest timeline is closer to a decade, and mid-course corrections quietly restore the structures that were cut.
When do mergers work?
Consolidations succeed when the functions are genuinely duplicative and the seam is clean. The 1996 consolidation of disparate Treasury bureaus' support functions into shared service centers, for all its stumbles, eventually standardized payroll and personnel processing that no bureau could have afforded alone. The pattern in the successful cases: a narrow, measurable back-office function; a forced migration deadline with an actual decommissioning date; and a funded transition budget stated up front, so the savings claim could be audited against a baseline.
Compare that with the failures: broad cultural mergers of agencies with different missions, announced with savings estimates but no transition budget, no decommissioning dates, and no named owner accountable for the post-merger audit. The difference is not ambition. It is whether the merger plan contains a number that can be checked later.
What should reformers check before proposing one?
A workable consolidation proposal answers four questions before the first press release. How much will the transition cost, over how many years, and from which appropriation? Which legacy systems get decommissioned, on what dates? Who owns the savings target and reports progress to Congress? And what happens to statutory functions that cannot legally move without new legislation? Proposals that skip these answers are not reform plans; they are announcements.
FAQ
Do agency mergers ever reduce costs?
Yes, in narrow back-office consolidations with forced decommissioning dates and audited baselines. Broad multi-mission mergers rarely produce measurable savings within a decade.
How long does a federal agency merger take?
Realistically five to ten years, including systems migration and workforce transitions. DHS was still consolidating management systems more than a decade after its 2003 creation.
Who audits whether a merger saved money?
The Government Accountability Office and the agency's own inspector general, against cost baselines that should be set before the merger begins.
For more context, read Shared Services Centers: What Twenty Years Actually Delivered.
For more context, read pendleton act 1883.
For more context, read Buyouts or Layoffs: The Two Machines of Federal Downsizing.