What does the stopgap actually do?

The continuing resolution keeps the government open but carries familiar restrictions. It ensures current weapons programs can be funded at fiscal 2026 levels and prevents a situation where civilians are furloughed and troops work without pay, per Breaking Defense's September 1 account. What a continuing resolution cannot do is start new programs or support the spending profile of a budget built on different assumptions, which is the core tension with the Pentagon's fiscal 2027 request.

The same account flags a fiscal cliff built into the arrangement: potential automatic cuts to reconciliation funds if certain money is not spent by October. That deadline matters because the Pentagon's two-track budget — base appropriations plus the mandatory reconciliation tranche — was built assuming both tracks would be enacted and obligating on schedule. A stopgap that freezes the base while the reconciliation money runs into an October spend-by date squeezes the department from both directions.

Where does the request stand?

The request itself is a two-part structure. The Pentagon is betting on a $1.15 trillion discretionary budget request with a further $350 billion coming from the reconciliation process, together adding up to a $1.5 trillion defense budget, while whether Congress can pass the full sum has remained uncertain, with the House yet to pass its version of the FY27 defense appropriations bill after moving it through committee in June, per Breaking Defense's August 27 preview of the fall agenda. That preview also catalogued a long list of unresolved defense funding items awaiting Congress on its return, from the stopgap to supplemental needs.

As of late September 2026, the state of play by measure is the practical scoreboard:

What happens if the reconciliation money fails?

The Pentagon's own comptroller has described the fallback. Jules Hurst told Breaking Defense on September 10, 2026 that if Congress does not pass the full $350 billion reconciliation funding, the department is prepared to work with lawmakers to shuffle key priorities into the base budget, a plan that would require cutting or deferring investment elsewhere or pushing it to fiscal 2028, per that report. Hurst said it was too premature to know exactly what those decisions and trade-offs would require.

His framing of the choice, as quoted in the report, was blunt: the question would be what is more important to have money for in FY27, or whether it can wait for FY28, and he noted that some technological areas are evolving fast enough that some things need money right now while others need more research and development. A shuffle into the base budget is not a free move — every priority moved in displaces a priority already there, and the appropriators, not the comptroller, hold the pen.

Why does a stopgap cost the Pentagon even when it funds everything?

A continuing resolution is often described as harmless because it holds spending flat, but flat is not the same as right. The fiscal 2027 request was built on different priorities than fiscal 2026 law — new starts, production ramps, and the mandatory tranche's investment profile — and none of those can proceed at prior-year levels. A program that was planned to grow is held to its old size, and a program that was planned to end keeps drawing funds until full-year law says otherwise.

The administrative mechanics compound the mismatch. Obligation plans, contract award schedules, and hiring pipelines are all set against the assumption of enacted appropriations, and each month under a stopgap pushes decisions later into a fiscal year that is already underway. The December 11 boundary means the department could operate under prior-year funding for well over two months of fiscal 2027 before either a full-year bill or a longer stopgap resolves the question.

The reconciliation layer makes 2026 unusual rather than typical. Past stopgaps froze one budget; this one freezes the discretionary half of a two-track request while the mandatory half faces an October spend-by cliff. The comptroller's willingness to discuss moving priorities into the base budget is the department planning for the failure of its own preferred structure — a contingency that only exists because the two-track design put so much of the topline on a separate legislative path.

What should watchers track next?

The document calendar from here is short and unforgiving. The stopgap expires December 11, 2026, which sets the outer boundary for enacting full-year appropriations before the department must plan around an entire fiscal year at prior-year funding levels. The House and Senate floor schedules for the defense appropriations bill have not been announced, and the reconciliation bill's fate in the Senate remains the largest single unknown in the $1.5 trillion arithmetic.

The second-order effects are already visible in program offices. Contractors and program managers plan obligations against enacted law, not requests, and a December boundary compresses decision-making across new starts, production ramps, and the priorities Hurst described. When the appropriations question is settled, the practical test will be which of the priorities moved into the base budget survived contact with the allocations, and whether the multiyear production commitments Congress has signaled interest in were funded at levels that let suppliers act on them. Between now and December 11, every marker — the Senate's appropriations schedule, the reconciliation bill's progress, and the October spend-by deadline inside the stopgap — is dated and public, which makes this one budget fight where the scoreboard updates in documents rather than in rhetoric.

What did GAO actually find?

In a report published July 17, 2025, GAO identified the government's most critical decades-old systems and graded agency plans to replace them. "Eight of the 11 systems use outdated languages, four have unsupported hardware or software, and seven are operating with known cybersecurity vulnerabilities," the report states, and the 11 legacy systems most in need of modernization are maintained by 10 federal agencies, per the GAO report on critical legacy systems.

The report's most uncomfortable detail is age: the systems on GAO's list span from 23 years old to 60 years old, and the oldest is operated by the Defense Department, per the report's table of systems. On planning, GAO found that only a minority of agencies had modernization plans containing all the elements GAO considers necessary, and at least two agencies, including Defense, had no plan at all for the flagged systems.

Why it matters is not nostalgia but exposure: outdated languages mean shrinking pools of qualified maintainers, unsupported hardware means unpatchable components, and known vulnerabilities in systems supporting missions from tax processing to national security are an auditable, dated risk on the public record.

What did GAO recommend, and to whom?

The July 2025 report's remedies ran to both branches. GAO recommended that Congress consider requiring agencies to develop modernization plans for critical legacy systems, and that the agencies operating the flagged systems complete plans containing the elements GAO defines, according to the report's recommendations section.

The branch matters. Recommendations to agencies depend on management follow-through that history shows is uneven; a statutory requirement converts a suggestion into an audit-ready obligation, which is why GAO escalates some findings to legislators rather than to executives alone.

The report is also a follow-on in a series: GAO has flagged critical legacy systems in earlier products across administrations, and the 2025 edition reads as a progress check in which the systems age faster than the plans mature. Whether Congress adopts the recommendation in authorization or appropriations law is the indicator to watch in the current cycle.

Why do legacy systems persist?

The persistence is structural, not accidental. A legacy system that still processes transactions is a working production asset; replacing it means re-engineering interfaces that dozens of other systems depend on, with no ribbon-cutting and high failure risk. Agencies rationally divert scarce IT budget to keeping the current stack compliant and operational.

Funding mechanics compound this. Large modernizations need multi-year money, while appropriations committees prefer annual control, and a failed high-profile project costs a career. The Technology Modernization Fund was created precisely to break that trap: a revolving fund that lends to agencies for modernization projects, with repayment from realized savings. Its recent trajectory shows the tension.

The result is the pattern GAO has documented across administrations: critical systems identified, plans requested, plans not delivered, and the can kicked to the next budget cycle with another year of runtime on hardware older than the workforce maintaining it.

How is the Technology Modernization Fund funded now?

Thinly, and by transfers. "The White House is not proposing new funding for the Technology Modernization Fund (TMF) in fiscal year (FY) 2027, instead relying on transfer authority to sustain the government's central IT modernization fund," MeriTalk reported on April 7, 2026, noting the proposal lets the General Services Administration, with OMB approval, collect up to $100 million in funding that would otherwise be unavailable for obligation from other agencies, per MeriTalk's report on the TMF proposal.

Congress's counter was modest. "House appropriators included $5 million in total funding for the TMF 'to remain available until expended,'" MeriTalk reported on April 20, 2026, a sum that "would match what Congress ultimately approved for FY 2026 TMF appropriations," per MeriTalk's coverage of the House spending bill.

Is procurement itself the bottleneck?

Partly. Modernization is not only a money problem; it is an acquisition problem. Requirements documents written around the legacy system's quirks, years-long solicitations and vendor lock all slow replacement, and GAO's finding that most agencies lack complete plans points at management capacity as much as dollars.

Transfer authority is itself a procurement-policy choice: sweeping unobligated balances into a central fund moves decisions from agencies to GSA and OMB, which is faster but concentrates both expertise and political risk. Whether that trade pays off depends on project selection discipline that the public record does not yet demonstrate.

What is unknown is stated as unknown: neither the administration nor appropriators have published a full accounting of TMF loan repayments against the new transfer mechanism in the documents reviewed. The testable claim is narrow, that a fund nourished at $5 million a year plus transfers cannot by itself carry eleven mission-critical replacements, several of them in agencies that GAO found had no modernization plan at all.

What should watchdogs track next?

Three indicators will tell the story over the coming cycle. First, whether GAO's recommendation landscape changes: if the next update shows agencies producing complete plans, the pressure worked; if the same systems reappear, the finding aged into wallpaper. Second, whether the transfer authority is actually executed and at what scale, since authority to collect up to $100 million is not the same as collection. Third, whether any of the flagged systems, particularly the oldest Defense Department entry, moves from operation to retirement with a dated transition plan.

For agencies, the practical reading of 2025-2026 is that central seed money has effectively evaporated and modernization must be funded from operating budgets, meaning the legacy problem now competes directly with daily service delivery in every appropriations hearing that follows.

What is Schedule Policy/Career?

Schedule Policy/Career is a new excepted service schedule — a category of federal positions outside the competitive hiring and removal rules — created by Executive Order 14410, published in the Federal Register on June 10, 2026. The order states its premise in its first section: "Officials in confidential, policy-determining, policy-making, and policy-advocating roles (policy-influencing positions) play particularly important roles" in helping the President execute the laws, and "ensuring that such employees can be removed for misconduct or poor performance is essential to protecting democratic self-government by an elected President."

The order explicitly builds on Executive Order 13957 of October 2020 — the Trump-era first term order that created Schedule F, rescinded in 2021. The June 2026 version revives the concept with implementing machinery attached: positions whose occupants shape policy can be moved out of the competitive service, where adverse actions carry full Merit Systems Protection Board (MSPB) — the independent board that reviews federal personnel actions — appeal rights, and into the excepted service, where those protections are narrower.

What does the September 2026 MSPB rule do?

On September 3, 2026, the MSPB published a final rule amending 5 CFR Part 1201, docket OPM-2025-0012, titled Determining the Appropriate Penalty for Federal Employees Charged With Misconduct. The rule changes "the Board's review of the reasonableness of an agency's chosen penalty in misconduct-based adverse actions appealed to the Board" — in plain terms, the Board will no longer defer to the penalty an agency selected, but will review it on its own standard.

The direction matters as much as the mechanism. For four decades the Board applied the framework from its 1981 Douglas decision, which required balancing the aggravating factors against the employee's record and the leniency precedent in the agency's own penalty table. That balance functioned as a brake on removals. The 2026 rule shifts the balance point: agencies gain wider latitude to impose severe penalties, and employees appealing a misconduct removal face a Board that no longer starts from the assumption the agency's choice was reasonable.

How do the competitive and excepted services now compare?

The two changes work on different halves of the personnel system, and the comparison shows how they interlock.

Read together, the table shows the strategy: the June order reduces how many policy employees reach the appeal stage at all, and the September rule changes what happens to those who do.

What are the arguments on each side?

The administration's argument is accountability and democratic control: elected presidents cannot execute the law if career staff in policy roles cannot be managed, and the order says as much in its purpose section. Supporters also note that excepted service schedules have always existed — Schedules A, B, and C predate this debate by decades — and that the order targets policy-influencing positions rather than the civil service wholesale.

The counterargument is institutional: competitive hiring and removal protections exist to prevent a spoils system, and career expertise in policy roles is what survives transitions. Federal employee groups and oversight watchers have warned that making policy staff removable at will pressures exactly the employees whose job is to give candid written advice. Both arguments now run through the MSPB's new penalty posture, where the practical meaning of "removable" gets tested case by case.

What does this mean for the Pentagon's own civilians?

The Department of Defense runs one of the largest civilian workforces in government, and its policy, acquisition, and intelligence-support staffs sit squarely in the population the June order defines as policy-influencing. A defense policy analyst who drafts positions on weapons programs, or a requirements officer who shapes what the department buys, does exactly the kind of work the order's language targets. How many defense positions are designated — and whether the national security workforce is carved out or included — will be visible in the implementing actions agencies publish.

The MSPB rule reaches defense civilians directly, because department misconduct appeals go to the same Board as every other agency's. A removal case from a defense components agency decided under the new penalty standard will shape how aggressively the department uses discipline, and the Board's published decisions are the record to watch.

What happens to employees already in the pipeline?

Both documents raise transition questions the texts themselves only partly answer. For employees moved into Schedule Policy/Career, the order's implementing provisions govern conversion terms — whether tenure, appeal rights, and time-in-service carry over — and affected employees' remedies will run through whatever administrative process the schedule provides, which is narrower than competitive service protections. For pending appeals, the MSPB rule applies to cases decided under the new regulation, and how the Board treats misconduct appeals filed before the effective date is a threshold question its early decisions will settle.

Unions and merit-system watchers have a further concern: the interaction of the two changes could concentrate removal power at exactly the career layer where institutional memory lives. The counterweight they point to is statutory — the merit system principles and prohibited personnel practices remain law, and the Office of Special Counsel, the agency that investigates prohibited personnel practices, keeps its jurisdiction regardless of which service an employee sits in. Whether that counterweight suffices is the live question of the next several years.

What should readers watch next?

Three documented markers: how many positions agencies actually move into Schedule Policy/Career — the Federal Register's June 10, 2026 publication runs to more than 200 pages of implementing detail; how the MSPB's penalty decisions cite the new rule in its first months; and whether Congress legislates, since the civil service rules the order amends are themselves codified law Congress can rewrite. What is settled on paper as of September 2026 is direction, not destination: the system is tilting toward removal, and the docketed cases will show how far it goes.

What did GAO actually find?

The report, Defense Management: DOD Needs to Review Its Defense Agencies and Field Activities for Efficiency and Effectiveness (GAO-26-107781), states plainly that DOD "has not recently met statutory requirements to review and report on the efficiency and effectiveness of its defense agencies and DOD field activities." Between April 2023 and September 2024, the department reviewed four of the 27 organizations but, per GAO, "did not finalize the reports based on its reviews or submit the reports to Congress as required."

GAO traced the failure to process, not to a single office. DOD lacked formalized guidance, such as a written instruction, when it ran the reviews. A May 2026 memorandum assigned responsibilities and deadlines, but GAO noted that an earlier memo had already failed to ensure the reviews were completed. The watchdog also found the department "did not clearly define measures to be used for its most recent DAFA reviews," which prevented any meaningful judgment about efficiency or effectiveness.

Why do these reviews matter to Congress?

Defense agencies and DOD field activities — known as DAFAs — are the Pentagon's shared-service and support organizations, and the law requires each to be examined on a fixed cycle. GAO's report states that "DOD is required to conduct reviews of each DAFA's efficiency and effectiveness at least once every 4 years." When the reviews lapse, committees lose their main documented instrument for judging whether agencies such as the Defense Logistics Agency are duplicating work done elsewhere.

GAO identified concrete overlap in two training areas: leader development programs at the Defense Human Resources Agency, the Defense Logistics Agency, and Washington Headquarters Services, and sexual assault prevention and response training developed separately by DOD and the military services. The department "has not assessed if there are negative effects on efficiency or effectiveness resulting from this overlap," the report says.

Where does this fit in GAO's wider Pentagon ledger?

The September report lands on top of a large backlog of unimplemented watchdog guidance. A GAO letter published July 28, 2026 and covered by Legis1 found the Department of Defense "has 53 unimplemented priority recommendations among 1,567 open GAO recommendations overall." Of the 79 priority recommendations in the previous annual letter, the department implemented 17, GAO dropped 16 from the priority list, and seven were added — netting out to 53.

GAO designates recommendations as priority items when acting on them could yield major savings, improve decision-making, or curb mismanagement. The open priority items span military readiness, weapons acquisition, and financial management — a reminder that the DAFA review failure reported in September 2026 is one entry in a much longer accountability ledger that Congress, not the department, keeps tallying.

What Does the Order Actually Create?

The document establishes an advisory commission to design a NASA-led federal academy. In the order's language, the commission "shall advise and assist the President regarding proposals to establish the United States Space Academy (Space Academy), a proposed NASA-led Federal academy dedicated to combining rigorous technical education with leadership development, discipline, and a durable commitment to public service," per the Federal Register text. The policy rationale opens with first principles: "Space is a critical domain for American national security, economic growth, scientific discovery, and technological innovation."

NASA's own release frames the action in workforce terms: the order was signed "to strengthen the nation's space workforce and develop the next generation of space leaders," and "the proposed academy would focus technical education with leadership development, discipline, and a commitment to public service," per an August 28, 2026 agency announcement.

Which Agencies Sit on the Commission?

The composition reaches well beyond NASA, pulling in the budget office and the Pentagon's senior leadership. The NASA Administrator chairs; the Assistant to the President for Science and Technology and the Assistant to the President for Economic Policy serve as vice chairs; the NASA Deputy Administrator is executive director. Additional seats, per the order published by the White House, include the Secretary of War, the Assistant to the President and Chief of Staff, the Director of the Office of Management and Budget, the Assistant to the President for National Security Affairs, and the Secretary of the Air Force.

What Happens Next?

The deadline is fixed: "Within 120 days of the date of this order, the Commission shall submit to the President through the APST and the APEP a report proposing key details," the order states. NASA's release says the report is expected to cover "governance framework, service obligations for graduates," among other items. Whether those service obligations become a military-style commitment, and whether Congress appropriates money for any academy the commission proposes, remain open questions the order does not answer; the 120-day clock, which runs from August 28, is the only dated commitment on the record.

Why Does a Space Academy Need This Much Interagency Machinery?

The membership list answers a question the title raises: an academy that produces both civil servants and warfighters cannot be designed by one agency. NASA chairs the commission because the order describes a NASA-led institution, but the Secretary of War and the Secretary of the Air Force hold seats because the order's own policy language charges the nation with preparing the next generation of astronauts, scientists, engineers, operators, entrepreneurs, civil servants, and warfighters, per the Federal Register text. The Office of Management and Budget's seat exists because any eventual academy will need an appropriations line.

The model invites comparison with the federal service academies, which Congress established by statute and funds through annual appropriations. Executive Order 14423 does not follow that route: it commissions a study. The practical difference is that nothing in the order obligates a single dollar or admits a single student, and the entire proposal can be revised or shelved when the 120-day report lands. Readers tracking the effort should watch two documents after the deadline, the commission's report and any subsequent budget request, either of which will say more about the academy's fate than the order itself.

What did GAO find?

GAO's central finding is methodological: the savings arithmetic cannot be checked from what the site publishes. "DOGE was not transparent regarding methodologies used to calculate savings," the report states, noting DOGE "did not use its stated methodology to calculate the majority of savings associated with the contracts reported as terminated," and "did not provide sufficient information to verify the method used to calculate 96 percent of DOGE-reported savings" on grants, per the GAO report page. On leases, the report found the Wall of Receipts overstated savings from terminations by more than $80 million.

Some claims were attributed to actions that predate the office or never occurred. Of 264 leases listed for termination, 108 — about $15.3 million of the claimed $53.5 million — had already been slated for termination before DOGE existed, the report states. The recommendation that followed is directed at transparency rather than accounting: GAO recommended that the U.S. DOGE Service prominently display known data quality issues and limitations on the site.

What did GAO recommend, and what happens now?

One recommendation, one addressee. GAO's finding that the Wall of Receipts "does not provide sufficient information on data quality issues or limitations" produced a recommendation to the Executive Office of the President, via the U.S. DOGE Service, to display the site's known limitations prominently. The recommendation remains open as of the report's release, which means the audited party has not yet documented the action. Open recommendations of this kind routinely become questions at subsequent oversight hearings, where agencies report completion or explain the delay.

The audit's scope bounds what it can say. GAO reviewed savings data posted from February 17, 2025, when posting began, through July 7, 2026, and checked contract claims against federal procurement records and grant claims against federal spending databases. Findings about methodology and verification apply to that window; the report does not forecast totals beyond it, and the full site continued to change after the review closed.

Why does a Pentagon contract anchor the audit?

The Defense Department example is the report's most concrete case. In coverage of the findings, Federal News Network reported on August 7, 2026 that "The Department of Government Efficiency touted that it saved $110 billion across federal contracts, grants and leases," and that "96% of DOGE's claimed savings on federal grants cannot be verified," with some posted savings "already being phased out before DOGE was established," per the Federal News Network report. GAO's own review tracked savings data against federal procurement and spending databases.

The report does not conclude that no savings occurred. What GAO concluded is that the public record, as posted, does not support the posted figures — a distinction that matters for Congress as it weighs the office's legacy and for agencies inheriting the contracts in question. The recommendation to the Executive Office of the President remains open as of the report's release.

What did the House actually approve?

The bill folds the renaming provision into the annual National Defense Authorization Act, alongside a request for $1.15 trillion in national security spending and a pay raise of 5 to 7 percent for service members depending on rank, per Federal News Network's account of the July 22 vote. The measure passed on a sharply partisan tally of 216-212, with Democrats objecting to steep Pentagon spending increases and several social policy riders included in the bill.

The renaming itself began as an executive action. A September 2025 executive order directed agencies to begin using the historic name where possible, and the department has since rebranded signage and web properties. As Military.com reported, the House vote converts what began as a symbolic discussion about language into an active legislative question with implications for military policy, government operations, and federal spending.

How does a reorganization actually take effect?

Whether the change is a rename or a full restructuring, the path runs through the same institutions, and the current bill illustrates each step:

1. An executive order sets policy direction — the September 2025 order directed executive agencies to use the new name where possible.
2. Agencies implement what they can administratively: signage, websites, internal documents, and correspondence.
3. Congress legislates the parts that require statute, because a department created by law can only be renamed or restructured by law.
4. Both chambers must pass matching language, and differences must be reconciled in conference before a final bill reaches the president.
5. Appropriations follow, since every structural change — from IT systems to facility signage worldwide — carries a cost Congress must fund.

The bill now sits at step four. The Senate must approve its own version of the NDAA, and lawmakers from both chambers would then need to reconcile differences, per PBS NewsHour's July 22 coverage. No date for Senate action had been announced as of mid-August 2026.

What comes next for the name change?

The practical stakes are larger than letterhead. Renaming touches information technology systems, references in treaties, and signage at facilities worldwide; congressional aides' estimates of the total cost have ranged well above $100 million and, in some accounts, could approach $2 billion, per Military.com's reporting. For comparison, renaming nine military bases that carried Confederate names cost $62 million.

The department has not said publicly how it would sequence the change if the provision survives conference. What the record documents is procedural: administrative rebranding is fast, but a legal rename waits on the Senate, a conference committee, and a presidential signature.

What do the first proposed rules cover?

The first batch touches the skeleton of the regulation. FAR Case 2026-001 proposes revisions to FAR parts 1, 2, 4, 33, 39, 40, 52, and 53, covering the framework of the regulation, definitions, contracting forms, and the clauses that carry the rules into every contract. Its companion, FAR Case 2026-002, covers parts 6, 7, 10, 18, 26, 37, and 41 — including part 6, which governs competition requirements, and part 37, which covers service contracting.

The issuing bodies are the Office of Federal Procurement Policy, the Department of Defense, the General Services Administration, and NASA, collectively the FAR Council, per the Federal Register notice for FAR Case 2026-001. Both notices carry the same architecture: twelve proposed rules that collectively will streamline the FAR in its entirety.

Both notices state that the rules implement an executive order that "directs the elimination of excessive acquisition regulations to stop the inefficient use of American taxpayer dollars." The stated method is organizational — reorganizing FAR parts into phases of acquisition and simplifying the text into plain language where possible, rather than changing statutory requirements, which the rulemaking cannot do.

What is the overhaul actually trying to do?

The initiative traces to Executive Order 14275 and the push to return the FAR to its "statutory roots" — keeping only what federal law requires and cutting non-statutory rules accumulated over decades. For contracting officers at defense and civilian agencies, the practical consequence would be a restructured regulation whose parts map to acquisition phases rather than the historical layering of repeated amendments.

The scale is unusual. A full rewrite of the FAR has not been attempted in the regulation's modern history, and doing it through twelve coordinated proposed rules means agencies must track which parts of the regulation are stable, which are in proposal, and which are governed in the meantime by class deviations already issued across the government. The notice for FAR Case 2026-002 confirms the same twelve-rule structure and the same comment deadline of July 23, 2026.

What happens next in the process?

With the comment period for the first four rules closed, the council is now in the review phase before final rules are issued. The remaining proposed rules in the twelve-rule sequence were still pending as of August 12, 2026, and the council has not published a schedule for the final versions. Under the Administrative Procedure Act, each final rule must respond to public comments before it takes effect.

For agencies and vendors, the open question is how quickly the model class deviations already in day-to-day use converge with the formal rule text. Where a deviation and a final rule diverge, contracting officers will need updated guidance before the rewritten FAR becomes operational, and contracts awarded under the old text remain governed by the clauses in place when they were signed.

What does the rule actually change?

Two things change at once: where appeals go, and how they are decided. Under the final rule, OPM replaces the MSPB as the adjudicative agency for RIF appeals and applies a uniform, record-based process. The final text specifies that only an employee furloughed for more than 30 days, separated, or demoted by a RIF action taken under 5 CFR part 351 may appeal that action to OPM.

The rule also clarifies the appellant's burden of proof, requires production of the complete agency record, and preserves collateral statutory remedies. It applies prospectively, so RIF actions already appealed before the effective date follow the older track. OPM's published abstract states the revisions are intended to improve timeliness, consistency, and cost-effectiveness while maintaining administrative review.

How did the rule get here?

The final rule completes a rulemaking that began with a proposed rule published February 10, 2026, with public comments open through March 12, 2026. The proposal stated that OPM expected the transfer of appeal rights to promote efficiency and reduce costs to agencies carrying out RIF actions, which the notice said may be necessary to eliminate duplicative functions or align agency workforces with new priorities.

The final rule answers those comments in several places, including the clarification of which actions are appealable and a revision of the merits standard. Employees and agencies now operate under a single regulatory framework administered inside OPM rather than before the board.

Why does it matter for the federal workforce?

RIF procedures govern how agencies shrink or restructure their workforces: retention registers, bump and retreat rights, and appeal routes for affected employees. Moving the appeals forum from an independent quasi-judicial board to the personnel agency itself is the most consequential civil-service procedural change of the year, and it lands as agencies continue workforce restructuring across government.

For defense and security agencies, which employ large civilian workforces under the same Title 5 rules, the practical effect is procedural: appeals of RIF furloughs, separations, and demotions filed on or after September 2, 2026 go to OPM under the record-based process described in the final rule published August 3, 2026. How the new process performs will show up in case timelines, which OPM has committed to publishing under the rule.

What Does the Bill Text Actually Provide?

It is a rate-for-operations extension. Section 101 of the Senate text appropriates such amounts as may be necessary for projects and activities conducted in fiscal 2026, under the authority and conditions of the prior-year appropriations acts. Section 106 then sets the clock, making funds available until whichever occurs first: enactment of a full appropriation, enactment of the relevant FY2027 appropriations act without the activity, or December 11, 2026.

The structure means agency budgets neither grow nor shrink in the stopgap's base case; they continue, with the listed exceptions and anomalies spelled out in the text.

Why Does the December 11 Date Matter?

Because it is a hard wall, not a target. Every appropriation extended by the act — across all twelve appropriations divisions, from defense to transportation — lapses on that date unless Congress has enacted the relevant full-year bill. A week-long government shutdown in 2018-19 and the 43-day lapse of October 1 to November 12, 2025 both began exactly this way: a funding deadline arriving with no enacted appropriations in place. The December 11 choice sets the next cliff after the midterm elections rather than before them.

What Restrictions Ride Along for Defense?

Continuing resolutions carry standard limitations that matter to the Pentagon. The Senate text preserves the customary bars on starting new projects and on initiating multiyear procurements using advance procurement funding for economic-order-quantity buys unless specifically appropriated later.

• No new starts: activities not funded in fiscal 2026 cannot be initiated or resumed.
• No new multiyear procurement starts without specific appropriation.
• Funds remain available only through the December 11 deadline.

Why Is Congress Doing This in August?

Because none of the twelve FY2027 appropriations bills had been completed before the fiscal year's final weeks, and last year demonstrated the cost of missing the deadline: the October 1 to November 12, 2025 shutdown, the longest in U.S. history, furloughed roughly 900,000 federal employees. Passing the stopgap in August, before the election-season calendar compresses, is the Senate's insurance against a repeat.

What Happens Next?

The House must agree to the Senate amendment, and differences between the chambers' versions would have to be resolved before the measure can go to the President. A final signed law would push the real appropriations fight into the lame-duck period before December 11. Readers tracking agencies should watch two dates: House action in September, and the December 11 expiry written into Section 106 of the GovInfo record.