How to Apply for Federal Grants on Grants.gov
Federal grants are the largest, most durable funding most U.S. nonprofits, researchers, and agencies will ever pursue, and also the most procedural. Unlike a foundation, the federal government does not begin with a relationship; it begins with registrations, identifiers, and a published rulebook that decides, almost mechanically, whether your application is even read. This guide walks the full path: how federal money differs from foundation money, the accounts you must stand up before you can touch an application, how to decode a Notice of Funding Opportunity, what the SF-424 forms actually do, and how to get a clean, on-time submission through Grants.gov without disqualifying yourself on a technicality.
How federal grants differ from foundation grants
If your experience is with private foundations, recalibrate. The two worlds reward different things, and applying to one as if it were the other is a common, expensive mistake.
A foundation grant is, at heart, a relationship. You often start with a letter of inquiry, cultivate a program officer, and submit a relatively short proposal judged with real human discretion. Foundations can fund you because they like your theory of change. Decisions are faster and more flexible, and the paperwork is light.
A federal grant is a regulated transaction. The agency publishes a detailed notice; you respond inside a fixed window with a standardized package; a review panel scores you against pre-disclosed criteria; and if you win you take on a body of federal law governing how you spend and report the money. The differences that matter most in practice:
- Scale and term. Federal awards are frequently six and seven figures and run multiple years, versus a typical one-year foundation grant.
- Registrations first. You cannot even submit without active SAM.gov and Grants.gov accounts. No foundation requires this.
- A binding rulebook. The NOFO is law-like; deviating from its format or missing a required attachment can end your application before review.
- Scored, not chosen. Reviewers assign points against published criteria. Charm and history count for little; evidence against the rubric counts for everything.
- Compliance tail. Awards come with cost rules (2 CFR Part 200), financial and programmatic reporting, records retention, and potential audit. The work does not end at the award letter; in many ways it begins there.
The upshot: federal applications reward operational discipline and precise responsiveness over narrative flair. A beautifully written proposal that ignores the page limit, skips a form, or misreads eligibility will lose to a workmanlike one that follows every instruction.
Register before you apply: SAM.gov, the UEI, and Grants.gov
This is the step that catches first-time applicants, because none of it is fast and all of it is mandatory. You need three things in place before you can submit: an active SAM.gov registration, a Unique Entity Identifier (UEI), and a Grants.gov account with submission rights. Treat these as long-lead items and start them the moment federal funding becomes a possibility, not when you find an opportunity.
SAM.gov and the Unique Entity Identifier
SAM.gov, the System for Award Management, is the federal government's central registry of entities eligible to receive awards. Registration is free; ignore any service that charges you for it, because the official process costs nothing. When you register, the system assigns your organization a Unique Entity Identifier, a 12-character alphanumeric code that is now the primary way the government tracks your entity across grants, contracts, and payments.
The UEI replaced the old DUNS number on April 4, 2022. If your organization last applied years ago and is looking for its DUNS, stop; that identifier is gone. You do not apply for a UEI on its own or pay a third party for it. It is generated inside SAM.gov as part of entity validation, which confirms your legal business name and address against authoritative records.
Budget real time for this. The official guidance often cites a few business days, but in practice new registrations commonly take one to three weeks, because entity validation, an IRS taxpayer-identification match, and banking information for payments all have to clear. Any mismatch between your SAM.gov details and your IRS or incorporation records can stall you for days. Two more facts to internalize: SAM.gov registration expires after one year and must be renewed annually, and an expired registration will block a submission as surely as never having registered. Start a renewal at least 30 to 60 days before it lapses, because changes to your banking or legal name can trigger a fresh validation cycle.
Grants.gov accounts and Workspace roles
Grants.gov is the government-wide portal where most agencies post opportunities and accept applications. Separately from SAM.gov, every individual who will touch an application needs a personal Grants.gov account, and the organization's submission rights are governed by Workspace roles. Understanding these roles prevents the classic disaster of a finished application that no one is authorized to send.
- E-Business Point of Contact (EBiz POC). Designated in SAM.gov, this person is the gatekeeper for the organization in Grants.gov. The EBiz POC controls who may submit and is automatically granted the highest applicant role.
- Expanded AOR (Authorized Organization Representative). The top applicant role. An Expanded AOR can see every workspace across the organization, manage other users' roles, and submit any application. The EBiz POC holds this by default.
- Standard AOR. Can submit applications, but only for the workspaces they participate in.
- Workspace Manager. Can create workspaces and manage participants but cannot submit, a deliberate separation of duties.
The practical sequence: the EBiz POC logs in and assigns AOR roles to the right people. Role requests are not instantaneous, and if your designated submitter is not an AOR by deadline day, you are stuck. Confirm at least one Expanded or Standard AOR is in place well before you need to hit submit.
Registrations and realistic timeline
Here is the sequence and the time each step really takes. Dependencies run top to bottom; you cannot finish a lower row before the one above it clears.
| Step | Where | Realistic time | Notes |
|---|---|---|---|
| Gather legal docs (EIN, legal name, address, banking) | Your records | 1–3 days | Details must match IRS and incorporation records exactly |
| Entity validation + SAM.gov registration (UEI issued here) | SAM.gov | 1–3+ weeks | Free; UEI is automatic; IRS and banking checks drive delays |
| Create individual Grants.gov account(s) | Grants.gov | Same day | Each person who touches the app needs one |
| EBiz POC assigns AOR / Workspace roles | Grants.gov | 1–5 days | At least one AOR must exist to submit |
| Annual SAM.gov renewal | SAM.gov | 3–12 business days | Begin 30–60 days early; banking changes restart validation |
The headline lesson: if you discover a grant with a four-week deadline and you are not already registered, you may simply be unable to apply this cycle. Get registered now, keep it current, and the registration question disappears from every future deadline.
Reading a NOFO: the document that decides everything
The Notice of Funding Opportunity, or NOFO (older agencies still say FOA, Funding Opportunity Announcement), is the most important document in federal grant-seeking. Federal rules at 2 CFR 200.204 require it to give you enough information to understand award amounts, eligibility, deadlines, and submission requirements before you apply. Reviewers score your application against this document and nothing else, so read it the way a lawyer reads a contract, twice, with a highlighter.
Most NOFOs follow a standardized section structure, lettered or numbered I through VII:
- Section I — Funding Opportunity Description. The program's purpose, priorities, and goals. Your project must visibly serve these; a strong project aimed at the wrong purpose loses.
- Section II — Award Information. Total funding available, expected number and size of awards, project period, and any cost-sharing or matching requirement. Check the match requirement early; it can be a dealbreaker.
- Section III — Eligibility Information. Exactly who may apply and any project-level eligibility limits. If you are not an eligible entity type, stop here and look for a partner who is.
- Section IV — Application and Submission Information. The required forms and attachments, page limits, formatting rules, and the precise deadline (date and time, with time zone). This section tells you what the package must contain.
- Section V — Application Review Information. The merit-review criteria and their point values. This is your scoring rubric; read it before you write a word.
- Section VI — Award Administration Information. Reporting requirements, terms and conditions, and compliance expectations if you win. Know your obligations before you accept them.
- Section VII — Agency Contacts. The program and grants-management contacts who can answer questions. Use them early; do not save questions for the last week.
Two sections deserve disproportionate attention. Eligibility (Section III) is a pass/fail gate, and applying when ineligible is the most wasteful mistake possible. Review criteria (Section V) tell you where the points live. If a NOFO assigns 40 of 100 points to project design and 10 to organizational capacity, your effort and your strongest evidence belong in project design. Many strong organizations lose simply because they wrote what they wanted to say instead of what the rubric rewards.
Finding opportunities on Grants.gov
Grants.gov is the central catalog of federal discretionary funding across roughly two dozen grant-making agencies. The search tools let you filter so you spend time only on genuine fits.
- Filter by eligibility first. Narrowing to your entity type (for example, nonprofits with 501(c)(3) status, or institutions of higher education) removes opportunities you cannot win.
- Filter by agency and category to match your mission area, then read the full NOFO, not just the summary, before committing.
- Save searches and set alerts so new opportunities in your area arrive automatically; many programs recur annually, so timing your pipeline matters.
- Note the opportunity and CFDA/Assistance Listing number, which you will need when you create your Workspace and complete the SF-424.
For a deeper treatment of pipeline-building across federal, state, and foundation sources, see our guide to how to find grants. Treat Grants.gov as the federal slice of a broader prospecting strategy rather than your only channel.
The application package and the SF-424 family
When you open an opportunity in Workspace, Grants.gov builds a package from the exact forms that NOFO requires. Most non-construction grants center on the SF-424 family, a small set of standardized forms that virtually every federal applicant encounters:
- SF-424, Application for Federal Assistance. The cover form. It captures applicant identity (including your UEI), the opportunity you are applying to, the project title, requested dollar amounts, and the project period. It is the spine the rest of the package hangs on.
- SF-424A, Budget Information (Non-Construction). Your budget by federal object-cost category, plus matching funds where required.
- SF-424B, Assurances (Non-Construction). Certifications that you will comply with applicable federal laws, from civil-rights statutes to financial-management standards.
- Certification Regarding Lobbying and SF-LLL. A certification that appropriated funds were not used for prohibited lobbying, plus the SF-LLL disclosure form when lobbying activity must be reported.
Construction programs substitute the SF-424C (construction budget) and SF-424D (construction assurances). Beyond these standard forms, the NOFO will require program-specific attachments: a project narrative, a budget narrative or justification, biographical sketches, letters of commitment, indirect-cost-rate documentation, and similar items. The forms are the skeleton; the narrative attachments are where you actually compete.
One discipline above all: keep your numbers consistent across every form and narrative. The total on the SF-424 must equal the totals on the SF-424A and your budget narrative. Reviewers and grants-management specialists notice mismatches immediately, and inconsistency reads as carelessness with money, the worst possible signal to a funder. For building the budget itself, see how to write a grant budget; the cleaner your internal budget, the easier these forms become.
Eligibility types: who can apply
Federal eligibility is defined by entity type, and a NOFO names the specific categories it will accept. Common eligibility groups include:
- Nonprofit organizations with 501(c)(3) status (and sometimes those without)
- State, local, and territorial governments
- Federally recognized Tribal governments and organizations
- Institutions of higher education, public and private
- For-profit and small businesses, for certain programs (for example, SBIR/STTR research awards)
- Individuals, for a narrow set of fellowship and research opportunities
Read eligibility literally. If a NOFO names "nonprofit organizations other than institutions of higher education," a university is out even though it is a nonprofit. When you are ineligible but a strong fit exists, the standard move is to apply through an eligible lead applicant as a subrecipient or partner, with the roles spelled out in a memorandum of understanding. Confirm eligibility before you invest a single hour in writing; it is the cheapest insurance in the entire process. If you are newer to the sector, our overview of grant writing for nonprofits covers how partnerships and fiscal sponsorship can open doors that direct eligibility does not.
Deadlines and the danger of last-minute submission
Federal deadlines are precise and unforgiving: a specific date, a specific time, and a specific time zone, all stated in Section IV. "Due by 11:59 p.m. Eastern" means exactly that, and a submission timestamped a minute later is typically rejected without appeal. But the real trap is not the clock; it is the validation pipeline behind it.
When you submit through Workspace, your package moves through a sequence of statuses you should watch:
- Received. Grants.gov has the package and is checking it.
- Validated. The package passed Grants.gov's field-level validation with no errors.
- Received by Agency. The validated package was forwarded to the funding agency.
- Agency Tracking Number Assigned. The agency has logged it in its own system. This is your confirmation that the application is truly in.
Validation can take minutes or, during the rush around popular deadlines, hours. A single error, a missing required field, an attachment in the wrong format, a budget mismatch the system catches, bounces the package back as rejected with errors. If that rejection lands an hour before the deadline, you almost certainly cannot fix and resubmit in time. The defense is simple and non-negotiable: submit 24 to 48 hours early. Then watch the status until you see Validated and, ideally, the agency tracking number. If you have not seen confirmation within two business days, contact Grants.gov support rather than assuming all is well. Treating the published deadline as your actual deadline is how strong applications die over a formatting error.
Compliance, allowable costs, and reporting
Winning is the start of your obligations, not the end. Federal awards are governed by the Uniform Guidance at 2 CFR Part 200, which sets the rules for what you may charge to a grant and how you must account for it. Understanding the basics before you apply keeps your budget realistic and your post-award life sane.
Costs charged to a federal award must generally be allowable (permitted by the rules and the NOFO), allocable (actually benefiting the project), and reasonable (what a prudent person would pay). Some costs are flatly unallowable, and the NOFO may add its own restrictions on top of the government-wide rules.
Indirect costs, the overhead not tied to one specific activity, deserve special note. If you have a federally negotiated indirect cost rate, you use it. If you do not, the Uniform Guidance lets you elect a de minimis rate without negotiating one; as of the 2024 revision effective October 1, 2024, that rate rose from 10% to up to 15% of modified total direct costs (MTDC). MTDC broadly includes salaries, fringe, supplies, travel, and the first $50,000 of each subaward, while excluding equipment, capital expenditures, rent, and the portion of any subaward above $50,000. For most small organizations, the de minimis rate is the simplest way to recover overhead without an audit-heavy negotiation.
On the reporting side, expect both financial reports (how the money was spent, on a schedule the award specifies) and programmatic reports (what you accomplished against your stated goals). You will also face records-retention requirements and, depending on how much federal money you expend in a year, a Single Audit. Section VI of the NOFO previews these obligations, and you should read it before accepting an award, not after. Build measurable targets into your application from the start; our guide to writing grant goals and objectives shows how to frame outcomes you can actually report against later.
Merit review: how your application is scored
Most discretionary federal grants are awarded through merit review: a panel of reviewers, often external subject-matter experts, independently scores each application against the criteria published in Section V of the NOFO. Many programs attach explicit point values to each criterion, and your total score drives your funding rank.
What this means for how you write:
- Write to the rubric, section by section. Mirror the review criteria in your narrative's structure and headings so a reviewer can find each scored element without hunting. If a criterion is worth 30 points, give it depth proportionate to its weight.
- Lead with evidence. Reviewers reward documented need, a credible plan, and demonstrated capacity over enthusiasm. Cite data, name your methods, and show you can execute.
- Anchor in need. The need section frequently underpins the whole review; a vague problem statement undercuts every criterion that follows. Our guide to writing a statement of need covers how to make it data-driven and specific.
- Assume a tired, time-boxed reader. Reviewers may read dozens of applications. Clarity, navigability, and strict adherence to formatting are not cosmetic; they directly affect your score.
After scoring, agencies make funding decisions, sometimes following the rank order strictly, sometimes layering in policy or geographic considerations disclosed in the NOFO. Either way, the panel can only score what you submitted, in the format you submitted it. Responsiveness to the published criteria is the whole game.
Common mistakes that cause disqualification
Most failed federal applications are not failed on the merits; they are knocked out on avoidable, procedural grounds. Watch for these:
- Lapsed or missing SAM.gov registration. An expired registration blocks submission outright. Renew annually, well ahead of any deadline.
- No authorized submitter. A finished application is useless if no one holds an AOR role. Confirm submission rights early.
- Applying while ineligible. Read Section III literally; do not assume "nonprofit" includes your entity type.
- Ignoring page limits and formatting. Over-length narratives, wrong margins, or unreadable attachments can get your application screened out before review.
- Missing a required form or attachment. The package is rejected for what is absent, not graded on what is present. Reconcile every requirement in Section IV.
- Budget inconsistencies. Numbers that disagree across the SF-424, SF-424A, and budget narrative signal carelessness and can trigger errors.
- Writing past the review criteria. Saying what you want instead of what Section V scores leaves points on the table.
- Last-minute submission. Leaving no room for validation errors is the most common self-inflicted loss of all.
Pre-submission checklist
Run this list before you hit submit. Each item maps to a real way applications fail.
| Check | Why it matters |
|---|---|
| SAM.gov registration is Active (not expiring within the project window) | An inactive registration blocks submission and award |
| UEI is confirmed and matches the SF-424 | Identity mismatches cause validation errors |
| At least one Expanded or Standard AOR can submit | No authorized submitter means no submission |
| Eligibility confirmed against NOFO Section III | Ineligible applications are not reviewed |
| All required forms and attachments present (Section IV) | Missing items cause rejection, not partial credit |
| Page limits, margins, and file formats followed exactly | Formatting violations can screen you out |
| Budget totals match across SF-424, SF-424A, and narrative | Inconsistency triggers errors and erodes trust |
| Narrative is organized around Section V review criteria | Reviewers score against the rubric, not your outline |
| Match or cost-sharing requirement is met and documented | Unmet match can disqualify the application |
| Submitted 24–48 hours before the deadline | Leaves time to fix validation errors and still be on time |
| Status reached Validated, then Received by Agency | Confirms the application actually went through |
A worked example: a small nonprofit's first federal application
Consider a community health nonprofit eyeing a $400,000, three-year federal grant with a deadline eight weeks out. Here is the realistic arc.
Weeks 1–3. They check SAM.gov and discover their registration lapsed last year. They gather their EIN, legal name, and banking details, fix a small address mismatch with their incorporation records, and resubmit. Validation and renewal take two and a half weeks. In parallel, three staff create Grants.gov accounts, and the executive director, who is the EBiz POC, assigns one program director the Standard AOR role so there is an authorized submitter.
Weeks 2–4. They read the NOFO twice. Section III confirms 501(c)(3) eligibility. Section II reveals a 10% match requirement, which they cover with documented in-kind volunteer time. Section V assigns 35 points to project design, 25 to need, 20 to evaluation, and 20 to capacity, so they plan their narrative to mirror exactly that weighting.
Weeks 4–6. They draft the project narrative against the rubric, build the budget around a 15% de minimis indirect rate (they have no negotiated rate), and write a data-driven statement of need. They reconcile the budget totals across the SF-424, SF-424A, and budget narrative line by line.
Week 7. They assemble the Workspace package, double-check every Section IV requirement, and confirm page limits and file formats. The AOR submits a full 36 hours before the deadline. The package returns one validation error, a budget field, which they correct and resubmit within the hour. Status moves to Validated, then Received by Agency, then an agency tracking number appears. They are in, with a day to spare.
Nothing here is exotic. The win is procedural discipline: registrations current, eligibility confirmed, rubric followed, budget reconciled, submitted early.
Next steps
Federal grants reward organizations that treat the process as a system: get registered and stay registered, read the NOFO like a contract, write to the review criteria, keep your numbers consistent, and submit early enough to survive validation. None of it is glamorous, and all of it is learnable.
When you are ready to draft, GrantSage can help you turn a NOFO's requirements into a structured, rubric-aligned application, free. To strengthen the pieces that win points, work through these companion guides:
- Grant writing for nonprofits — the fundamentals, partnerships, and fiscal sponsorship.
- How to find grants — building a pipeline across federal, state, and foundation sources.
- How to write a statement of need — the data-driven core most reviewers weight heavily.
- How to write grant goals and objectives — measurable outcomes you can report against.
- How to write a grant budget — building numbers that reconcile cleanly across the SF-424 forms.
- Letter of inquiry (LOI) — the front door for the foundation grants that often complement federal funding.
FAQ
Do I still need a DUNS number to apply for federal grants?
No. The DUNS number was retired on April 4, 2022 and replaced by the Unique Entity Identifier (UEI), a 12-character code assigned by the government inside SAM.gov. You do not request a UEI separately or pay for one; it is issued automatically when you register or validate your entity at SAM.gov, which is free.
How long does it take to get ready to apply on Grants.gov?
Plan for several weeks of setup before you can submit anything. SAM.gov registration officially takes a few business days but realistically runs one to three weeks once IRS and entity validation are factored in, and a Grants.gov account plus role assignment by your organization's E-Business Point of Contact adds more time. Start registrations at least four to six weeks before any deadline, and ideally before you have even chosen an opportunity.
What is a NOFO and why does it matter so much?
A NOFO (Notice of Funding Opportunity, sometimes called an FOA) is the federal agency's official rulebook for a specific grant program. It states the program's purpose, who is eligible, how much money is available, exactly what to submit and by when, how the application will be scored, and what reporting you will owe if you win. Reading it carefully, especially the eligibility and evaluation-criteria sections, is the single highest-value thing you can do, because reviewers score you against that document and nothing else.
What is the SF-424 and which forms will I have to file?
The SF-424 (Application for Federal Assistance) is the standard cover form for most federal grants. It usually travels with a small family of related forms: the SF-424A for a non-construction budget, the SF-424B assurances, a certification regarding lobbying, and the SF-LLL if any lobbying must be disclosed. Construction programs swap in the SF-424C budget and SF-424D assurances. The exact required forms are listed in the application package attached to each NOFO on Grants.gov.
What happens if I submit my application at the last minute?
It is genuinely risky. After you submit through Grants.gov Workspace the package moves through Received, then Validated, then Received by Agency. Validation can take minutes or hours, and a single field error sends the package back rejected. If that happens an hour before the deadline you usually cannot fix it in time. Aim to submit a full 24 to 48 hours early so you have room to correct errors and still make the on-time cutoff.
Are federal grants worth the effort for a small nonprofit?
Often yes, but go in clear-eyed. Federal awards are larger and multi-year, but they carry heavy compliance: cost rules under 2 CFR Part 200, financial and programmatic reporting, audit exposure, and annual SAM.gov renewal. A small organization with thin financial systems may be better served by starting with foundation grants and building capacity first. If the program fit is strong and you can sustain the back-office work, a federal award can be transformational.