Grants.gov Now Lets You Start an Application Before You Are Allowed to Submit One. That Gap Is Where Deadlines Go to Die.
September 3, 2026 · 6 min read
Granted Research Team · Editorial policy
The federal grants portal is in the middle of a multi-year rebuild, and 2026 is the year that rebuild is half-finished. Search has moved. Submission has not. The two systems now disagree with each other about what you are allowed to do — and the disagreement is not symmetric. The new system is more permissive than the old one, and the old one is the one that decides whether your application counts.
That asymmetry is the whole story, and it produces a specific failure mode that will cost some organizations a deadline this fall.
The change that creates the trap
Simpler.Grants.gov now lets you begin filling out an application before your SAM.gov registration is active.
On its face this is a genuine improvement, and it removes a real bottleneck. SAM.gov activation can take one to two weeks and sometimes stretches longer. Under the old sequence, an organization that discovered an opportunity with a three-week fuse could lose most of that window waiting for a registration to clear before it could even open the forms.
Here is what did not change. Submission eligibility still requires, in sequence:
- An active SAM.gov registration producing a valid UEI, renewed annually
- A Grants.gov account linked to that organization's UEI
- Authorized Organization Representative role authorization for the person hitting submit
- Organizational verification completed
You can start. You cannot submit. And an applicant reading "you no longer have to wait for SAM.gov" as "SAM.gov is less urgent" will build a complete, polished, entirely unsubmittable application and discover the problem at the worst possible hour.
The distinction between you can start and you can submit only has protective value if you internalize it weeks before the deadline, which is precisely when it feels least urgent.
What has actually shipped
The modernization is run under HHS and has been moving steadily. The verified timeline:
December 2025 — Simpler Search became the default search experience, replacing the legacy tool. User profiles and a permissions system launched. An activity dashboard for tracking submissions went live.
February 2026 — Expanded search filters, including posted-date windows of 3, 7, 14, 30, and 60 days. Application download capability and simplified application URLs. Protections against incomplete form submissions and restrictions on post-submission alterations — aimed directly at one of the most common causes of rejected applications. Accessibility improvements for keyboard and screen-reader users.
March through May 2026 — Category filters added progressively. Consistent breadcrumb navigation and agency contact data fixes in April. Organization-level opportunity saving with email notifications in May, which is the underrated feature on this list: it lets a team share a watchlist rather than depending on one person's saved searches.
July 2026 — Navigation streamlining.
Throughout 2026 — A redesigned budget form developed with a co-design group of actual applicants, piloted to add clearer instructions and auto-calculation. Budget forms are among the largest single sources of application errors, so this is the pilot worth watching.
There is also a public read-only REST API for opportunity data, rate-limited to 60 requests per minute and 10,000 per day. API traffic already accounts for more than 13 percent of total search volume — a striking number that says a meaningful share of federal opportunity discovery has already moved from humans clicking to systems querying.
What has not shipped
The application workflow. This is the part that matters most and is furthest from done.
The Simpler Application Workflow Pilot ran with partner agencies including the Department of the Interior, the Bureau of Reclamation, and the National Park Service. Its success criteria were deliberately modest: at least ten users completing submissions through the Simpler UI in production, support for at least five different forms, and conversion of applications into PDF and XML formats compatible with existing Grants.gov systems. The pilot is complete. It was UI-only — programmatic submission was explicitly deferred.
The form repository currently holds roughly 15 commonly used forms. The scaling target is 35 percent of Grants.gov competitions by the end of 2026, and full replacement of legacy Grants.gov as the standard experience in 2027.
Read those two numbers together and the shape of the next fifteen months is clear. At best, roughly two of every three competitions will still run on legacy submission through the end of this year. And critically:
No legacy retirement date has been published. Neither the Simpler.Grants.gov roadmap nor its release notes commit to a date on which the classic application system stops working. "2027" is a target for the new system becoming standard, not an announced shutoff for the old one.
For applicants this is good news operationally — nothing is being yanked out from under you — and bad news planning-wise, because you cannot schedule a migration against a date that does not exist. You have to run both.
The five traps in the two-system year
1. Start is not submit. Covered above. It is first because it is new, it is the one that sounds like a simplification, and it is the one that will actually cost somebody a deadline.
2. Half the money you care about never touches Grants.gov submission at all. This is the trap that predates the modernization and gets worse during it. NIH takes applications through ASSIST. NSF takes them through Research.gov. DOJ takes them through JustGrants. All three post opportunities on Grants.gov. None of them are where you finish. We have written before about the DOJ two-portal deadline structure, where a Grants.gov step and a JustGrants step carry different dates — miss the first and the second is unreachable. Improvements to Simpler.Grants.gov do not touch any of this.
3. A corrected resubmission after the deadline is late. If your first submission throws a validation error at 11:52 p.m. and your corrected version lands at 12:04 a.m., you filed late. The original on-time attempt does not preserve your position. Agency-specific late policies sometimes provide relief, but the default is unforgiving, and the new incomplete-form protections reduce this risk without eliminating it.
4. SAM.gov lapses silently. Registration renews annually and does not announce itself. Nothing on the application side flags a pending expiration until you cannot submit. Put the renewal date in an organizational calendar with a 60-day warning, owned by a role rather than a person.
5. Maintenance windows disable submission. Scheduled downtime takes submission offline entirely, and windows have landed near month-end deadline clusters before. Check the Grants.gov maintenance calendar before committing to a same-day submission plan — and as a matter of policy, do not have a same-day submission plan.
Worth noting alongside these: the Grants.gov mobile app was retired in 2025. If any part of your workflow assumed it, that assumption is dead.
Why this fall specifically
Timing makes all of this sharper than it would normally be.
The government is operating under a continuing resolution through December 11, 2026, which triggers the new-starts prohibition and a rate of operations near 20 percent of prior-year totals. As we laid out separately, that means agencies hold NOFOs back through the fall and release a compressed wave after full-year appropriations pass.
A compressed NOFO wave with normal-length response windows is exactly the condition under which registration problems become fatal. When you have five weeks between posting and deadline, a two-week SAM.gov delay is an annoyance. When agencies are pushing a backlog through short windows, it is disqualifying.
Which produces an unusually clean recommendation for October and November: the quiet months are the registration months.
What to do
Treat registrations as standing infrastructure, not as tasks triggered by an opportunity. SAM.gov active and current. UEI verified and linked. At least two people holding AOR authorization — single-point-of-failure AOR access is how organizations miss deadlines when someone leaves or takes vacation in late September.
Verify per solicitation where submission actually happens. Do not infer it from where you found the opportunity. Read the NOFO's submission section, identify the system, and confirm you have credentials in that system. This is a five-minute check that prevents the most expensive category of error.
Use organization-level opportunity saving. The May 2026 feature lets your team share a watchlist with email notifications rather than routing discovery through one person's account. Adopt it.
Set your internal deadline 72 hours early and defend it. Every trap on the list above is survivable with three days of margin and fatal without it.
Read release notes quarterly. The platform publishes them, they are short, and the pace of change through 2027 means the workflow you learned in the spring may not be the workflow you face in the winter.
The modernization is real, it is well-run, and it will end up better than what it replaced. But a half-migrated system is not a simpler system — it is two systems with a seam in the middle. Right now the seam runs directly between the screen that says you can begin and the server that decides whether you finished.