River
Y CombinatorBacked by Y Combinator
FREE TEMPLATE

SF-424 Application Checklist Template

Three documents and three sheets, scheduled backward from the deadline through SAM.gov and Grants.gov so a lapsed registration surfaces before it blocks submission.

Free download  ·  No account needed

Every SF-424 checklist in circulation is a list of documents to gather: the narrative, the budget, the letters, the biosketches. Gathering is the easy half. The SF-424 family itself is published only as a sample, because the real form lives inside a Grants.gov Workspace. The Workspace will not transmit a package at all unless a condition none of those checklists mention is already true: an active SAM.gov registration, checked at the moment of submission rather than at the moment someone last remembers checking it.

2 CFR 25.200 requires every applicant without an exemption to register in SAM.gov before submitting and to keep that registration current with an annual review. Grants.gov enforces the same rule mechanically: the Sign and Submit button only activates when the workspace has an active SAM registration, every selected form has passed, and the closing date has not passed. None of that is graded. It is binary, and a registration that lapsed eleven months into its 365-day cycle fails it exactly as hard as one that was never started.

Cedar Line Community Health discovered this the ordinary way: a grants manager checked SAM.gov status nine days before a Monday deadline and found the registration expired since October. Only four business days were left on the calendar once a federal holiday is subtracted. SAM.gov's own guidance allows at least ten. The point of no return, ten business days back from the deadline, had already passed nine calendar days earlier, and nobody had been watching a date that carried no reminder anywhere. The narrative was finished. The page budget was correct. Neither mattered.

Ten business days, and the date that had already passed

The registration countdown against the deadline, every required form, and each notice requirement mapped to its answer.

Eligibility and Registration Checklist

Illustrative, for a fictional organisation called Cedar Line Community Health. Deadline Monday 2026-11-16, checked 2026-11-09, nine calendar days out.

ItemOfficial minimumResult on 2026-11-09Biz days to deadlineVerdict
UEI assignedNone, one-timeActive since 2021-Clear
SAM.gov registration active10 business daysExpired 2026-10-024Short by 6
Annual information reviewDue yearlySame lapse4Same cause
Grants.gov AOR roleSame day once SAM clearsSuspendedDependsWaiting
SAM exclusions check, signersNone, one-timeNeither listed-Clear
Congressional district on fileNone, a data fieldPre-2024 address-Fix today

Ten business days back from the 16th lands on Friday 2026-10-30. That is the point of no return: the last day a renewal could start and still clear under SAM.gov's own stated minimum. The registration lapsed October 2nd, twenty-eight calendar days before that date, so a renewal started any time in that window would have made the deadline comfortably. Nobody checked until November 9th, nine calendar days after the window had already closed. Four business days were left against a ten-day minimum, a shortfall of six, and no version of moving faster on the narrative closes that gap.

Form Register

Every form and attachment this notice requires, with the status actually true on the check date rather than a target.

Form or attachmentOMB #StatusNote
SF-424 cover4040-0004CompletePopulates UEI and district for the rest of the set
SF-424A budget4040-0006CompleteCrosswalked to the chart of accounts
SF-424B assurances4040-0007CompleteEighteen certified, none excepted
Lobbying certification4040-0013CompleteAbove the $100,000 threshold
Project Narrative-Complete25 of 25 pages
Indirect rate agreement-CompleteCurrent negotiated agreement attached
Key personnel biosketches-CompleteTwo required, both attached
Partner letters of commitment-1 of 2Second signature pending

Eight rows, seven complete, and every one of them is beside the point while the registration row on the other tab reads short by six business days. A perfect form register attached to an inactive registration has nowhere to go.

Requirement to Response Map

The notice's instructions read line by line, including the appendix. Twelve stated requirements, ten answered, two gaps.

RequirementWhere it is answeredStatus
Evaluation plan names who conducts itNarrative section 4Gap: method only, no name
Data management plan, appendix BNot draftedGap: no attachment
Statement of need, data under 3 yearsNarrative section 1Answered
Milestone schedule by quarterNarrative section 2; budget narrativeAnswered
Named partner commitmentLetters of commitment1 of 2 returned
Prior active federal award disclosureSF-424 item 20None disclosed

The evaluation gap is invisible on a read-through: section 4 reads as complete, states a method, and never names a person. It is the same failure mode as the registration date nobody was watching, in miniature and inside the narrative rather than outside it.

What is in the pack

01

Eligibility and Registration Checklist

SAM.gov and Grants.gov status checked against today's date, with the business days available to the deadline computed against the official minimum rather than assumed.

02

The point of no return, computed

Ten business days back from the deadline, landed on a real calendar date, so a lapsed registration is caught while it is still fixable rather than after.

03

Form Register

Every form and attachment this specific notice requires, with the OMB number, who it applies to, and a completion status that is actually true today.

04

Requirement to Response Map

Every requirement the notice states, including the ones buried in an appendix or a footnote, mapped to the exact document and section that answers it.

05

Assurances and Certifications Note

SF-424B's eighteen assurances reduced to the handful genuinely worth checking for a given applicant, including a named debarment and exclusions check.

06

Project Narrative shell

The five standard sections, built to hand off to the funder's own page-budget arithmetic once a full draft exists rather than guessing at length.

How it works

  1. 1

    Send the notice and today's status

    The full notice with its submission instructions and every appendix, the deadline with its time zone, and the organization's actual current SAM.gov and Grants.gov status, not a remembered one.

  2. 2

    Count backward from the deadline

    Business days to the deadline, and ten business days back from it for the point of no return, against the calendar and published federal holidays rather than a rule of thumb.

  3. 3

    Build the register while registration clears

    Form Register and Requirement to Response Map get built in parallel with any registration fix in progress, since neither depends on SAM.gov's own processing time.

  4. 4

    Finish the narrative against a confirmed gate

    Draft or refine the five sections, then hand the draft to the notice's own criterion weights for the page allocation, once submission itself is no longer in question.

Frequently asked questions

We renewed SAM.gov last year. Why would it lapse now?

Because SAM.gov registration is active for exactly 365 days from the last renewal, not indefinitely once completed. A renewal done in early October 2025 lapses in early October 2026, with no reminder that reaches everyone who assumes the organization is 'already registered.' Checking the actual expiration date on SAM.gov's own record is the only reliable answer.

Can we ask for extra time if SAM.gov is the problem?

Only the awarding agency can grant that, and it is discretionary rather than automatic. 2 CFR 25.110 permits an exception for exigent circumstances, decided by the federal agency, not one an applicant can invoke by requesting it. Treat the ten-business-day minimum as real rather than as a starting point for negotiation.

Does completing every form early protect us?

No, and that is the finding this pack is built around. A complete, correctly filled Form Register attached to a workspace with a lapsed SAM.gov registration still cannot reach the agency: the Sign and Submit button itself will not activate without an active registration. Registration and the form set are independent gates, and both have to clear.

What is the difference between this and the grant proposal pack?

This pack works the form set and the registration prerequisites: whether the package can physically be submitted. The grant proposal pack works the narrative itself, sizing each section against the notice's published criterion weights. Use both on a federal notice: this one first, since a narrative has no value if nothing can transmit it.

Our SF-424B assurances look fine. Is there anything to actually check?

Usually only two: whether any signer or named key person appears on SAM.gov's own exclusions list, and whether federal funds have touched any lobbying activity this year. Most nonprofit applicants certify both without exception, but that has to be confirmed by asking, not assumed because nothing has gone wrong before.

Does this pack submit the application?

No. The Authorized Organization Representative signs and clicks Sign and Submit inside Grants.gov Workspace, under a false-statements warning attached to SF-424B. This pack produces the figures, the register and the map that make that click a formality rather than a discovery.

What happens after the award is made?

The notice's terms become the award's terms, and tracking what every active award actually obliges the organization to do is separate, ongoing work that starts the day the award is signed, not the day the application was submitted.

Find out if your registration will actually clear in time

Send the notice, its deadline, and your organization's real SAM.gov status. The first thing back is the business-day count and the date it stopped being fixable.

Check my registration gap