The NIH Grants Policy Statement: What It Actually Requires From Your Institution

The NIH Grants Policy Statement (GPS) is not background reading — it is incorporated by reference into every NIH Notice of Award, which means its provisions are enforceable terms of the award itself, on the same footing as anything typed into the notice. That matters most at the point research offices tend to underestimate it: the GPS does not just describe how a grant works in general terms, it sets specific, document-level conditions that have to be satisfied — in writing, before money moves — whenever a NIH-funded project sends part of its work, and part of its budget, to another institution.

This page works through what the GPS actually requires at that moment: who it legally binds, what has to exist on paper before a subaward can be executed, who has to sign it, and how those requirements sit alongside the separate HHS Grants Policy Statement that governs other Public Health Service agencies. It does not re-cover NIH’s page-limit, appendix, FCOI-threshold, or inclusion-reporting rules — CASRAI already has dedicated pages for each of those, linked below — because folding them in here would dilute the one thing this page is trying to do well: explain the GPS’s subaward-execution and signature requirements in enough depth to actually use.

Last verified 2026-08-26. NIH’s own grants.nih.gov domain blocked direct automated fetching throughout this research (a recurring pattern, not specific to this page), so section numbers and effective dates below are corroborated across multiple secondary sources — university sponsored-programs offices, the Federal Register, and COGR — rather than a single primary-source quote. Where a detail is genuinely load-bearing for your institution’s compliance posture, confirm the current wording directly against grants.nih.gov/policy-and-compliance/nihgps before relying on it.

Tip: try code CASRAI at checkout for 15% off, if the offer is currently active for this program — codes vary by vendor and aren’t guaranteed.

What is the NIH Grants Policy Statement and who does it apply to?

The GPS is NIH’s single consolidated reference document for the terms and conditions attached to its grants and cooperative agreements — administrative requirements, allowable-cost rules, reporting obligations, and the mechanics of the award relationship, all in one place, published and periodically revised by the NIH Office of Policy for Extramural Research Administration (OPERA). NIH revises it through dated Guide notices rather than on a fixed calendar; the most recent full edition was released via NOT-OD-26-057 (March 25, 2026), consolidating NIH policy notices in effect as of March 17, 2026 and covering updates to research security, subawards, and prior-approval requirements, superseding the prior April 2024 edition.

The critical point for a research office is who the GPS binds. It is not primarily a document for the principal investigator — it is a condition of award accepted by the grantee institution. The institution, through its Authorized Organizational Representative (AOR), is the party that legally accepts the GPS’s terms when it accepts the award, and the institution is the party NIH holds accountable if those terms aren’t met — including the terms governing what has to happen before any of that money can legally be passed to a subrecipient. A PI who signs off on a subaward’s technical scope has not, by that signature alone, satisfied the institution’s obligations under the GPS; that requires a separate, specific set of documents executed at the institutional level, covered below.

HHS Grants Policy Statement vs. the NIH GPS — what’s the difference?

These are two separate documents, and conflating them is a real, recurring mistake in research offices that handle both NIH and non-NIH Public Health Service funding.

NIH explicitly maintains its own GPS rather than deferring to the HHS-wide document — the two are not interchangeable, and a subaward agreement drafted under the wrong one will cite the wrong terms and conditions. If your institution manages awards from both NIH and, say, HRSA or SAMHSA, check the prime notice of award before assuming which GPS governs a given subaward — don’t assume based on the funding agency’s parent department alone.

What the GPS requires before a subaward can be executed

This is the operational core of the GPS’s subaward provisions, laid out primarily in GPS Section 15 (“Subawards”), and it’s stricter than many research offices treat it in practice. Three things have to exist, in writing, before a subrecipient is authorized to begin work and before subaward funds can be drawn against:

1. A fully executed written subaward or consortium agreement. The GPS requires the recipient institution to enter into a formal written agreement with each subrecipient — signed by an authorized representative of both institutions — that documents the negotiated scientific, administrative, financial, and reporting arrangements specific to that piece of the project. NIH updated its guidance on what these agreements must contain via NOT-OD-23-182 (announced in the Federal Register on June 5, 2023, effective October 1, 2023), which tightened expectations around what terms a compliant written agreement has to spell out. A subrecipient is not supposed to start incurring costs against the award before this document is fully signed.
2. Current institutional certifications. Uniform Guidance at 2 CFR 200.415(b) — incorporated into the GPS by reference for domestic awards — requires the subrecipient to submit a signed certification whenever it applies for funds, requests payment, or submits a financial report, substantially to the effect that the report is true, complete, and accurate, with civil and criminal penalties attached to a false certification. The GPS’s subaward guidance expects the terms of this certification requirement to be written directly into the subaward agreement itself, not left as an unstated assumption.
3. A subrecipient risk determination. Before finalizing terms, the pass-through institution is expected to have assessed the subrecipient’s risk profile (prior audit findings, programmatic experience, financial systems) closely enough to set monitoring terms proportionate to that risk — see CASRAI’s subrecipient risk assessment guide for the mechanics of that step specifically.

In practice, this means a subaward isn’t “in progress” from a GPS-compliance standpoint until all three of those exist as executed, dated documents — not verbal agreement between PIs, not a purchase order, not an email confirming scope. That’s the gap that turns into an audit finding: work starts on the strength of a PI-to-PI handshake while the paperwork catches up weeks later, and the institution has, for that period, authorized subaward spending without the written agreement the GPS requires to exist first.

Who has to sign a subaward agreement under NIH terms?

Signature authority sits at the institutional level on both sides, not with the investigators:

• At the pass-through (prime recipient) institution: the Authorized Organizational Representative (AOR) — the same signing authority who accepted the original NIH award — or another institutional official specifically delegated that authority (commonly someone in the sponsored programs or research administration office).
• At the subrecipient institution: its own equivalent authorized official — often also called an AOR, Signing Official, or Institutional Official depending on the institution’s internal terminology — never the subrecipient’s PI acting alone.

This is precisely the bottleneck that makes multi-institution subaward execution slow in practice: a single subaward agreement typically needs a real signature from an authorized official at each institution, sometimes alongside a PI countersignature confirming the technical scope, before it’s complete. On a project with five subrecipients, that’s a minimum of five to ten separate signatures, from officials at different institutions, often in different time zones, before a single dollar can legally move — and the traditional route (print, sign, scan, email, repeat with tracked changes) is exactly the kind of multi-week bottleneck a compliant office runs into every time a new multi-site award comes in.

This is the specific point where electronic signature tools like Sign.Plus earn their place in a research office’s workflow — not as a general convenience, but because the GPS’s own requirement (a fully executed, signed agreement, from named authorized officials at each institution, before funds flow) is a routing-and-signature problem at its core, and that’s a narrower, more solvable problem than the compliance requirement itself might suggest. A tool that can route a single subaward document to the AOR at your institution, then automatically forward it to the subrecipient’s authorized official, track who has and hasn’t signed, and return a fully executed, audit-ready copy with a verifiable signature trail, addresses exactly the bottleneck described above — without changing anything about what the GPS actually requires.

See how Sign.Plus handles multi-institution signing →

What does the GPS require for subrecipient monitoring?

Executing the agreement is the start of the obligation, not the end of it. Once a subaward is in place, the GPS incorporates the Uniform Guidance’s ongoing monitoring requirement at 2 CFR 200.332: the pass-through entity has to evaluate each subrecipient’s risk of noncompliance (with statutes, regulations, and the terms of the subaward itself) for purposes of determining the appropriate monitoring level, and then actually monitor the subrecipient’s activities throughout the period of performance — reviewing financial and programmatic reports, following up on audit findings (including Single Audit findings under 2 CFR Part 200 Subpart F where applicable), and verifying the subrecipient is meeting the performance goals in the agreement. CASRAI’s subrecipient monitoring checklist walks through that ongoing obligation in the depth it deserves; this page’s scope stops at the execution step because that’s the gap the GPS’s own subaward language most specifically addresses and the one research offices most often treat as informal.

How often does NIH update the Grants Policy Statement?

There is no fixed revision cycle. NIH updates the GPS through individual Guide notices as policy changes arise, then periodically republishes a full consolidated edition that folds the accumulated notices into one document — the pattern behind the current NOT-OD-26-057 edition. Subaward-specific mechanics get updated the same way: NOT-OD-23-182 revised the written-agreement guidance in 2023, and a more recent notice, NOT-OD-26-062 (“Prior Approval Requirement for Changes to Domestic Subawards”), addresses when a change to an existing domestic subaward needs NIH’s advance sign-off — a distinct question from initial execution, and one worth checking directly against the live notice if you’re modifying rather than creating a subaward.

Because notices supersede each other outside the calendar rhythm most research offices plan around, the practical habit that holds up is checking the GPS’s own “What’s New” or notice-history page each time a new subaward cycle starts, rather than relying on institutional guidance that may cite a prior edition’s section numbers.

Where CASRAI already covers the individual GPS provisions

The GPS is a long document, and this page deliberately does not re-explain the parts of it CASRAI already covers elsewhere in depth:

• NIH Financial Conflict of Interest — the $5,000 SFI threshold and institutional FCOI process under 42 CFR Part 50 Subpart F
• NIH Application Page Limits and Format Requirements
• NIH Appendix Policy — what may and may not be included
• NIH Inclusion Enrollment Report — completing the form
• Subaward Agreement Negotiation — the general (agency-neutral) mechanics of getting to signature
• Pass-Through Entities, Subrecipients, and the Subaward Statement of Work

If you landed here looking for one of those specific provisions, those pages go deeper than this one does on purpose. This page’s job is narrower: the GPS’s subaward-execution and signature requirements specifically, which none of the pages above cover as their primary focus.

Frequently asked questions

What is the NIH Grants Policy Statement and who does it apply to?

It’s NIH’s consolidated terms-and-conditions document for its grants and cooperative agreements, incorporated by reference into every Notice of Award. It binds the grantee institution (via its Authorized Organizational Representative), not the PI individually — see CASRAI’s NIH GPS dictionary entry for the underlying definition.

HHS Grants Policy Statement vs. the NIH GPS — what’s the difference?

They’re separate documents from separate issuing offices. The HHS GPS governs most other HHS operating divisions (CDC, HRSA, SAMHSA, AHRQ, ACF); NIH maintains its own GPS and is explicitly excluded from the HHS-wide version. Check which one governs based on the actual awarding operating division, not the parent department.

What does the GPS require for subrecipient monitoring?

Ongoing risk-based monitoring under 2 CFR 200.332 — evaluating subrecipient risk, tracking financial and programmatic reports, and following up on audit findings for the life of the subaward. See the subrecipient monitoring checklist for the full obligation.

Who has to sign a subaward agreement under NIH terms?

An authorized institutional official at each institution — the AOR or equivalent Signing Official — not the PI alone. Most agreements also carry a PI countersignature confirming technical scope, but that never substitutes for the institutional signature the GPS requires.

How often does NIH update the Grants Policy Statement?

On no fixed schedule — via dated Guide notices as changes arise, periodically consolidated into a full edition (most recently NOT-OD-26-057, March 2026). Subaward-specific notices, like NOT-OD-23-182 and NOT-OD-26-062, can update between full editions.

Try Sign.Plus for subaward signatures →