The $4 Billion Competition Everyone Wrote Off Just Came Back With a 12-Day Fuse. HUD's CoC NOFO Is Live Again and Closes September 30.

Six weeks ago, the FY2026 Continuum of Care competition did not exist. A federal judge in Rhode Island had vacated the Notice of Funding Opportunity in its entirety, HUD's own website told applicants it could not accept submissions, and several thousand homeless-services projects were staring at a procedural vacuum with no replacement notice and no timeline.

It exists again. On September 16, 2026, the U.S. Court of Appeals for the First Circuit granted HUD an emergency stay pending appeal of the district court's vacatur. HUD reopened the e-snaps portal on Friday, September 18, and set a new federal submission deadline of September 30, 2026 at 8:00 PM ET.

That is roughly $4 billion in competitive funding, restored, with twelve days on the clock — and ten days left as of this writing.

If you lead a Continuum of Care, staff a collaborative applicant, or hold a CoC subaward, stop reading the litigation coverage and open e-snaps. Then come back, because the strategic picture underneath this deadline is genuinely unusual and it changes what you should be doing after you submit.

What actually happened, in order

The sequence matters because each step constrains the next.

August 7, 2026. The U.S. District Court for the District of Rhode Island, in the consolidated cases State of Washington, et al. v. HUD (1:26-cv-00439) and National Alliance to End Homelessness, et al. v. HUD (1:26-cv-00436), held that HUD's issuance of the FY2026 CoC NOFO violated the Administrative Procedure Act. The defect was procedural: HUD had made a sweeping policy shift — reserving roughly $1.3 billion, close to a third of available CoC funding, as a set-aside tilted toward transitional and service-intensive housing models — without the notice-and-comment process such a change requires. The court vacated the NOFO in full. We covered that ruling and its implications in detail in A Federal Judge Just Erased the Entire FY2026 CoC Competition.

Mid-August. HUD appealed and asked the district court for an emergency stay so the competition could proceed during the appeal. The district court denied it.

September 16, 2026. HUD took the same request to the First Circuit and won. The appeals court granted the emergency stay, reportedly finding that HUD had made a strong showing that it is likely to succeed on the merits and that further delay would create funding gaps in programs that cannot absorb them.

September 18, 2026. HUD reopened e-snaps for CoC Consolidated Applications, Project Applications, and CoC Priority Listings, and announced that the added twelve days exist specifically so CoCs can finalize and submit.

September 30, 2026, 8:00 PM ET. New federal deadline. Note that this is also the last day of FY2026, which is not a coincidence and is not an accident of scheduling.

What the stay decides — and what it doesn't

This is where a lot of the field is getting the risk calculus wrong.

A stay pending appeal is not a ruling on the merits. It is a preliminary judgment about whether the appellant is likely to win and whether the harms of waiting outweigh the harms of proceeding. The First Circuit has said HUD is likely to prevail. It has not said HUD has prevailed. The appeal is still live, both sides are still briefing, and the underlying question — whether a $1.3 billion reallocation away from the Housing First framework required notice-and-comment — remains open.

The practical consequence: the FY2026 competition is proceeding under a legal posture that could still be reversed. Applications submitted by September 30 will be scored and, presumably, awarded. Whether those awards are durable depends on an appellate panel that has not yet issued a merits decision.

Plan accordingly. That does not mean hedging your application — you apply, and you apply as if the money is real, because it is. It means that internally, your board and your finance team should understand that FY2026 CoC awards carry a tail risk that ordinary awards do not, and that any commitments you make in reliance on them (leases, hires, match pledges) should be structured with that in mind where you have the flexibility to do so.

The two changes buried in the reopening

HUD reinstated the NOFO substantively unchanged. There is no rewrite, no new scoring, no revised set-aside. But two operational changes ship with the reopening and both have teeth.

1. Applicant notification compressed from 15 days to 7. CoCs that had not yet notified project applicants of their selection — or non-selection — for the CoC Priority Listing may do so now, and the required notification period has been shortened from 15 days to 7. This is the single most consequential technical correction in the package. In a normal year, the 15-day window is the procedural spine of local appeal rights: it is the time in which a rejected project applicant learns its status and can contest a local ranking decision. Cutting it in half inside a twelve-day competition compresses that process to near-nothing.

If you are a collaborative applicant, send those notifications today if you have not already. Every day you wait is a day of exposure on a rejected applicant's procedural claim against you, not against HUD.

If you are a project applicant who has not received notification, ask for it in writing, now, with a timestamp. Do not wait for it to arrive.

2. A rental assistance waiver. HUD issued a waiver of 24 CFR 578.51(b) permitting private nonprofit applicants, recipients, and subrecipients receiving FY2026 CoC NOFO funds to administer rental assistance directly. In the ordinary rule, rental assistance administration runs through public housing agencies or governmental entities. This waiver removes that intermediary for FY2026 funds.

This is quietly significant and it is easy to under-use. For nonprofits in jurisdictions where PHA capacity is a bottleneck — or where the PHA relationship has been the friction point in program design — the waiver opens project structures that were previously off the table. If your original application was shaped around a PHA administering the rental assistance line, you have a narrow window to reconsider whether that is still the right structure. Most CoCs will not have time to rework this before September 30, and that is fine. Note it for the post-award period and for FY2027.

The Los Angeles wrinkle

One further complication worth tracking: CA-600, the Los Angeles-area geographic designation, has had its designated status questioned, with a hearing scheduled for September 22, 2026. Geographic designation is the foundation on which every project application in a CoC rests — if the designation is unsettled, the downstream applications inherit that uncertainty.

If you are in the Los Angeles region, your submission strategy should assume the worst case and file as though the designation holds. Conditional filings and wait-and-see postures do not survive a hard federal deadline.

The fight that actually matters is on October 13

Here is what most of the field is missing while it scrambles against September 30.

On September 11, 2026, HUD published a notice seeking public comment on incentives for activities under the CoC program — explicitly including transitional housing with supportive services and recovery-oriented housing models. Comments are due October 13, 2026.

Read that in sequence with the litigation. The district court did not hold that HUD's policy direction was unlawful. It held that HUD had not run notice-and-comment before imposing it. A comment period on exactly the policy direction at issue is the textbook cure for exactly that defect.

In other words: HUD is simultaneously defending the FY2026 NOFO on appeal and building the administrative record that would make a substantially similar FY2027 NOFO immune to the same challenge. Whichever way the First Circuit rules, the October 13 docket is where the shape of next year's competition is being decided.

The National Association of Counties has said it intends to comment and to publish a template for counties that wish to do the same. If your organization has a view on the set-aside, on renewal priority, or on how transitional and permanent supportive housing should be weighted, October 13 is your leverage point, and it is a far cheaper one than litigation.

The sequence to run this week

1. Confirm your e-snaps access today. Portal access problems are the most common cause of missed CoC deadlines and they are the slowest to resolve. Do not discover an account issue on September 29.
2. Send or confirm Priority Listing notifications immediately. The window is 7 days, not 15, and it runs against you.
3. Reconcile your Consolidated Application, Project Applications, and Priority Listing as a set. The reopening did not reset internal consistency requirements. A Priority Listing that does not match the project applications it ranks is a scoring problem, not a clerical one.
4. Build in a 48-hour buffer. Target September 28 for submission. The deadline is 8:00 PM ET on September 30 and it will not move again.
5. Calendar October 13 for the comment period, and assign it to someone who is not currently buried in the application.
6. Brief your board on the tail risk. The stay is preliminary. Say so plainly now rather than explaining it later.

The broader lesson

For most of August, the operating assumption across the homeless-services field was that FY2026 was gone and the program would run on the renewal floor Congress built into the Consolidated Appropriations Act, 2026 — the directive to renew expiring projects, with additional triggers if awards were further delayed. That floor is still there, and it is still the reason this episode has been survivable.

But the reversal itself is the durable lesson. In the current environment, a vacated NOFO is not a dead NOFO, and a restored NOFO is not a safe NOFO. Both states are provisional, both can flip on a single order, and the interval between them can be two days of notice and twelve days of runway.

The organizations that will submit comfortably on September 30 are the ones that kept their application packages assembled through the pause instead of standing down when the deadline disappeared. That is now the baseline competence the federal grants environment demands: build it, keep it current, and be ready to file on a week's notice in either direction.