Why the White House keeps missing its budget deadline

Government Printing Office

When the White House missed its deadline to release a budget on Monday, officials did something a little unusual: They declined to say when the blueprint would be released.

The failure to meet the deadline was not new. Under federal law, the president is required to release a budget for the following fiscal year sometime between the first Monday in January and the first Monday in February. For three years running, President Obama hasn’t submitted the document on time. (And, for three years running, Republicans have pounced on the delay.) Here are the excuses the White House has given each year:

2013: Blame Congress
This year, the White House pushed the blame onto Congress and its inability to avert, ahead of time, the impact of the fiscal cliff, the massive combined tax hikes and spending cuts scheduled to go into effect right around the end of 2012. Jeffrey Zients, director of the White House’s Office of Management and Budget, explained the delay in a Jan. 11 letter to House Budget Committee Chairman and former vice presidential hopeful Paul Ryan.

"As you know, the protracted 'fiscal-cliff' negotiations ... created considerable uncertainty about revenue and spending for 2013 and beyond," Zients wrote. "[B]ecause these issues were not resolved until the American Taxpayer Relief Act was enacted on Jan. 2, 2013, the administration was forced to delay some of its FY 2014 budget preparations, which in turn will delay the budget's submission to Congress."

When asked whether the budget would come before or after the president’s Feb. 12 State of the Union address, White House press secretary Jay Carney on Monday said only, “I don’t have a date for you for when that will happen.”

2012: “Finalize Decisions”
The White House gave a terse explanation for skipping last year’s deadline: “As in previous years, the date was determined based on the need to finalize decisions and technical details of the document,” an administration official told reporters.

In announcing the delay, however, the White House gave the date when the budget would land. It came out, as promised, on the second Monday in February.

2011: Blame Congress: The Prequel
The budget proposal due out in 2011 was also released a week late. At the time, the administration blamed Congress on two counts: for taking six weeks to confirm the White House budget director and for its late approval of legislation to fund the government.

“The administration is scrambling to assemble what could be a pivotal document following a six-week delay in the confirmation of the White House's new budget director,” The Wall Street Journal reported at the time, citing a senior administration official. “The official also cited Congress's late moves to fund government operations for the current fiscal year, which began Oct. 1.”

Stay up-to-date with federal news alerts and analysis — Sign up for GovExec's email newsletters.
Close [ x ] More from GovExec

Thank you for subscribing to newsletters from GovExec.com.
We think these reports might interest you:

  • Sponsored by Brocade

    Best of 2016 Federal Forum eBook

    Earlier this summer, Federal and tech industry leaders convened to talk security, machine learning, network modernization, DevOps, and much more at the 2016 Federal Forum. This eBook includes a useful summary highlighting the best content shared at the 2016 Federal Forum to help agencies modernize their network infrastructure.

  • Sponsored by CDW-G

    GBC Flash Poll Series: Merger & Acquisitions

    Download this GBC Flash Poll to learn more about federal perspectives on the impact of industry consolidation.

  • Sponsored by One Identity

    One Nation Under Guard: Securing User Identities Across State and Local Government

    In 2016, the government can expect even more sophisticated threats on the horizon, making it all the more imperative that agencies enforce proper identity and access management (IAM) practices. In order to better measure the current state of IAM at the state and local level, Government Business Council (GBC) conducted an in-depth research study of state and local employees.

  • Sponsored by Aquilent

    The Next Federal Evolution of Cloud

    This GBC report explains the evolution of cloud computing in federal government, and provides an outlook for the future of the cloud in government IT.

  • Sponsored by Aquilent

    A DevOps Roadmap for the Federal Government

    This GBC Report discusses how DevOps is steadily gaining traction among some of government's leading IT developers and agencies.

  • Sponsored by LTC Partners, administrators of the Federal Long Term Care Insurance Program

    Approaching the Brink of Federal Retirement

    Approximately 10,000 baby boomers are reaching retirement age per day, and a growing number of federal employees are preparing themselves for the next chapter of their lives. Learn how to tackle the challenges that today's workforce faces in laying the groundwork for a smooth and secure retirement.

  • Sponsored by Hewlett Packard Enterprise

    Cyber Defense 101: Arming the Next Generation of Government Employees

    Read this issue brief to learn about the sector's most potent challenges in the new cyber landscape and how government organizations are building a robust, threat-aware infrastructure

  • Sponsored by Aquilent

    GBC Issue Brief: Cultivating Digital Services in the Federal Landscape

    Read this GBC issue brief to learn more about the current state of digital services in the government, and how key players are pushing enhancements towards a user-centric approach.

  • Sponsored by CDW-G

    Joint Enterprise Licensing Agreements

    Read this eBook to learn how defense agencies can achieve savings and efficiencies with an Enterprise Software Agreement.

  • Sponsored by Cloudera

    Government Forum Content Library

    Get all the essential resources needed for effective technology strategies in the federal landscape.


When you download a report, your information may be shared with the underwriters of that document.