Family Foundation Grants vs. Federal Grants (SBIR, NIH, NSF): Why the Same Playbook Doesn't Work for Both

A client says "I need help with a grant," and the word does a lot of hiding. If the funder is a family foundation or a small state agency, that sentence probably means: research the funder's priorities, draft a letter of inquiry or a narrative in the funder's own template, build a budget that looks reasonable and adds up, and submit it by whatever deadline the funder posted on its own website. If the funder is the Small Business Innovation Research (SBIR) program, the National Institutes of Health (NIH), or the National Science Foundation (NSF), "help with a grant" can mean something else entirely — a federally defined award instrument, a mandatory registration process that starts weeks before you write a word of narrative, a review conducted by outside scientists instead of a program officer, and a budget that has to satisfy a specific federal cost-principles regulation, not just look defensible.

One visible sign that freelancers run into this mismatch: a thread in the r/SBIR community carries the title "Grant writing takes me FOREVER... How do people do this?" — the kind of frustration that shows up when someone applies foundation-pace habits to a federal mechanism (r/SBIR, title and preview consulted September 2026; we're citing the title as a documented signal of the pain point, not quoting the thread's body). This article lays out the concrete differences — not "the federal process is more complicated" in the abstract, but which specific steps, reviewers, timelines, and rules change — so you can recognize early which kind of job you actually took.

Step one: figure out which instrument you're actually writing for

"Grant" is a legal term with a narrower meaning at the federal level than in everyday nonprofit-sector usage. The Federal Grant and Cooperative Agreement Act of 1977 created three distinct categories that federal agencies use to fund external work: procurement contracts, grants, and cooperative agreements. SBIR.gov's own program-basics training spells out why this matters for SBIR and its sister program STTR specifically: of the eleven agencies that run SBIR/STTR programs, four — the Department of Energy, NOAA, NSF, and USDA — award only grants; five award only contracts, with the training naming the Department of Defense and NASA as the largest of that group; and two (HHS, which includes NIH, and the Department of Education) award both, depending on the specific solicitation (SBIR.gov, "Contracts vs Grants").

The distinction isn't paperwork trivia. Per the same SBIR.gov training, a grant lets the applicant define the scope of work and requires the principal investigator's best effort toward a stated aim, with no legally binding requirement to hit a specific result. A contract is a binding agreement to deliver a specific good or service the government wants, with an inflexible scope and payments tied to deliverables and milestones — "classified work is done as contracts, not grants," the training notes as a sharp illustration of how differently the two instruments are treated. A cooperative agreement sits between the two: like a grant, but with substantial federal involvement in carrying out the project. NIH's own standard-due-dates table shows this distinction inside a single agency — its "U01" activity code is labeled "Research Grants – Cooperative Agreements," a different instrument from the plain "R01" research grant, with its own due dates and expectations (NIH, "Standard Due Dates"). None of this vocabulary exists on the foundation side of the work: a family foundation's award is a grant in the plain-English sense every time, with no separate contract or cooperative-agreement track to identify first.

Registration you'll never touch for a foundation grant

Before a foundation grant, there's no government registry to join — you research the funder, you write the letter of inquiry or narrative, you submit it through the funder's own portal or by email. Before you can even submit to most federal solicitations, there's a registration sequence with its own lead time. Every SBIR or STTR applicant must register on the SBIR/STTR Company Registry, a separate step from registering in the federal government's own System for Award Management (SAM.gov) — SBIR.gov's FAQ is direct about this: "If my company is already registered on SAM, do I also need to register on SBIR.gov? Yes... We will not be rolling out a company registry that integrates with SAM at this time" (SBIR.gov, "Company Registry" FAQ). SAM.gov registration itself isn't instant: the government's own entity-registration guidance states "registration can take up to 10 business days to become active," and once active, it has to be renewed every 365 days to stay valid (SAM.gov, "Entity Registration"). For a freelance grant writer used to a foundation timeline where the LOI itself is the first real step, this is an easy thing to miss until a client says they're "just about to apply" and the registration hasn't even started.

Who actually decides: outside reviewers scoring criteria, not a program officer and a board

On the foundation side, this site's own reporting on rejection patterns and letters of inquiry describes a process built around program officers and a board: Peter Marks, executive director of the L.B. Research and Education Foundation, put it plainly in describing his own foundation's process — funding decisions come from "the board, or program staff on behalf of the board," and for smaller family foundations especially, "grantmaking choices are forged from the preferences of individuals" on that board (National Center for Family Philanthropy, Peter Marks, "Declining Applications and Inquiries: How Funders Can Do Better"). It's a relationship-and-judgment process, and it's exactly what this site's guide to why foundations reject proposals and letter of inquiry guide are built around.

NIH and NSF run a structurally different process. At NIH, most applications go through a Scientific Review Group — commonly called a study section — which NIH itself defines as a panel "composed primarily of non-federal scientists who have expertise in relevant scientific disciplines and current research areas." A Scientific Review Officer assigns "at least three reviewers to assess each application," each reviewer scores it on defined criteria using a 1-to-9 scale, and the panel as a whole discusses and scores the application at a formal review meeting before anyone at NIH makes a funding decision (NIH, "First Level: Peer Review"). Notably, NIH's SBIR and STTR applications (the R43/R44 and R41/R42 activity codes) go through this same peer-review structure, on their own dedicated review cycle — it isn't a lighter-touch process just because the applicant is a small business rather than a university lab.

NSF's process runs in parallel but isn't identical: program officers first check a proposal is complete, then identify external reviewers — "the review may be conducted by ad hoc reviewers, a panel of experts, or a combination of both" — who score the proposal against two Board-approved criteria, intellectual merit and broader impacts, before NSF staff weigh that input alongside other portfolio considerations to reach a funding decision (NSF, "How We Make Funding Decisions"). In both cases, the reviewers are outside subject-matter experts scoring against published, numbered criteria — not a program officer's discretionary read of fit, and not a vote among board members who also set the foundation's overall giving priorities.

Fixed cycles instead of "whenever the funder is ready"

Foundation deadlines vary by funder — this site's letter of inquiry guide already documents cases from a three-page limit to a five-page one, and from rolling review to fixed annual cycles, all set independently by each foundation. Federal mechanisms, in the cases covered here, run on published, structured calendars. NIH's Standard Due Dates page lays out three receipt cycles a year for most activity codes, with SBIR/STTR applications specifically due September 5, January 5, or April 5 depending on the cycle, followed by a defined "Scientific Merit Review" window (October–November, February–March, or June–July) and an Advisory Council round roughly two to five months after that (NIH, "Standard Due Dates"). How long the whole thing takes end to end, per NIH's own institute-level guidance: "it typically takes between 8 and 20 months after the due date to get an award," with about 8 months typical after a standard Advisory Council review, a rare 5 to 6 months for the small share of applications that get an expedited second-level review, and up to 20 months possible for awards decided near the end of a fiscal year (NIAID, "Timeline for Funding Decisions"). NSF states a narrower internal goal for the decision itself — "NSF strives to be able to tell applicants whether their proposals have been declined or recommended for funding within six months" of submission (NSF, "How We Make Funding Decisions") — though award negotiation and start-date logistics add time after that decision. Either way, a freelance writer quoting a client on "we'll hear back in a month or two," a reasonable estimate for plenty of foundation cycles, is quoting the wrong universe of time for these programs.

The budget has to satisfy a federal cost-principles regulation, not just look reasonable

A foundation budget mainly has to convince a program officer and a board that the numbers are honest, proportionate to the request, and tied to the activities described in the narrative — this site's guide to grant budget narratives covers what that looks like in practice. A federal grant or cooperative agreement budget has to do that and satisfy a specific regulation: 2 CFR Part 200 (the "Uniform Guidance"), whose applicability section states plainly that its cost-principles subpart "applies to grants and cooperative agreements" (with a short list of narrow exceptions), while contracts awarded under the Federal Acquisition Regulation follow a different rulebook — "in cases of conflict... the terms and conditions of the contract and the FAR prevail" instead (eCFR, 2 CFR 200.101, Applicability). NSF's own budget-preparation guidance ties this together for a proposer directly: it requires a written "budget justification, up to 5 pages long" documenting every line item, states that the same 2 CFR 200 cost principles govern what's allowable, and requires organizations without a federally negotiated indirect cost rate to submit a separate indirect cost rate proposal if they want to charge more than the 15% de minimis rate (NSF, "Preparing Your Proposal Budget"). That 15% de minimis figure and the cost-principle details behind it — what counts as equipment, how indirect costs get calculated — are the same federal numbers this site's budget narrative guide walks through in full; the difference on a federal proposal is that they're not optional background knowledge, they're the regulation the budget will actually be checked against.

A quick way to tell what you actually took on

Before drafting anything, a few questions separate a foundation-style engagement from a federal one:

• Does the opportunity come from a federal agency's own funding announcement (a Notice of Funding Opportunity, a Broad Agency Announcement, an SBIR/STTR solicitation) rather than a foundation's own website or a foundation database listing?
• Does the solicitation mention SAM.gov registration, a Unique Entity ID, or (for SBIR/STTR specifically) the SBIR.gov Company Registry as a prerequisite?
• Does it use terms like "cooperative agreement," "Phase I/Phase II," "principal investigator," or a specific activity code (R01, R43, U01, and similar) rather than a foundation's usual "letter of inquiry" or "full proposal" language?
• Does it name a peer-review panel, study section, or external reviewer process, rather than a program officer's recommendation to a board?
• Does it list fixed, recurring receipt dates set by the agency (several times a year, the same dates every cycle) rather than a single deadline the funder set for this round?
• Does the budget section reference 2 CFR 200, federal cost principles, or a negotiated indirect cost rate agreement, rather than simply asking for a total project budget?

A "yes" to two or more of these is a strong signal you're in federal-mechanism territory, with its own registration steps, review process, timeline, and budget rules — not a bigger or stricter version of a foundation grant, but a different kind of engagement with different homework before you write a single sentence of narrative.