- What NOT-OD-25-132 Actually Says
- The Six-Application PI Limit, Explained
- AI Detection and Post-Award Consequences
- Compliance FAQs for Research Offices
- Compliance Steps Before the Next Submission Cycle
- Implications for the Wider Research Ecosystem
The National Institutes of Health has put research offices on notice: proposals that look like they were written by a machine, and principal investigators who submit an implausible volume of them, will now be treated as a fairness problem rather than a productivity feature. NIH AI policy grant applications is the subject of NOT-OD-25-132, “Supporting Fairness and Originality in NIH Research Applications,” issued 17 July 2025 and effective for applications with due dates on or after 25 September 2025. The notice does two distinct things at once — it restricts the use of generative AI in drafting applications, and it caps the number of applications any one principal investigator (PI) can submit per year — and research administrators need to treat them as two separate compliance obligations, not one.
What NOT-OD-25-132 Actually Says
NIH’s position is narrower than “no AI allowed.” The notice states that applications must reflect the original ideas and scientific contributions of the investigators, and that NIH will not accept applications that are substantially developed by AI. That is a materiality threshold, not a blanket prohibition on tools — spell-checkers, reference managers, and light editorial assistance are not the target.
The stated concern is specific: NIH flags plagiarism, fabricated or non-existent citations, and other misleading content generated by large language models as the practical harms it is trying to prevent, not AI use in the abstract. Applications judged to fall foul of this standard can trigger a research misconduct review and enforcement action, including referral to the Office of Research Integrity, disallowance of costs, or termination of an award already made.
NIH published the policy as a companion pair: the formal Guide notice (NOT-OD-25-132) and an accompanying Extramural Nexus explainer, “Apply Responsibly,” released two weeks later on 31 July 2025. A supporting FAQ page clarifies edge cases such as how applications are counted and which activity codes are exempt.
The Six-Application PI Limit, Explained
The second, less-discussed half of the notice caps submissions. An individual PI or Program Director — including each PI listed on a Multiple PI application — may submit a maximum of six new, renewal, resubmission, or revision applications within a defined NIH Council Round. NIH has said the cap was prompted by evidence that a small number of investigators, aided by AI drafting tools, were submitting dozens of applications in a single round, in some cases reportedly more than 40, straining the peer-review system disproportionately relative to the scientific contribution.
| Council Round | Applications counted toward the cap |
|---|---|
| 2026 Council Round | Due dates 25 September 2025 through 7 May 2026 |
| 2027 Council Round | Due dates 25 May 2026 through 7 May 2027 |
Two activity types are explicitly carved out: T-series training grants and R13 conference grants. The limit applies only to the PI/PD role — an investigator can still appear as a co-investigator, senior/key personnel, or a PI on a subaward across as many applications as the science supports, without those roles counting against their own six-application ceiling.
- Counts toward the cap: new, renewal, resubmission, and revision applications where the individual is listed as PD/PI or Multiple PI.
- Does not count toward the cap: T-activity-code training grants, R13 conference grants, and any application where the individual’s role is co-investigator or subaward PI rather than the lead PD/PI.
- Counting trigger: institutional guidance (e.g., UCSF’s Office of Sponsored Research) indicates an application is counted toward the limit once it passes administrative review, prior to peer review — so late withdrawals after that point may still occupy a slot.
PIs are responsible for tracking their own running total through eRA Commons; NIH does not promise to intercept a seventh application before submission, and rejection at that stage disrupts a funding cycle an institution cannot easily recover.
AI Detection and Post-Award Consequences
The most consequential detail for research offices is timing: NIH’s review for AI-substantiality is not confined to the submission window. The notice makes clear that detection can occur at the post-award stage — after funds have already been drawn down — and that a finding of substantial AI authorship at that point is treated with the same seriousness as post-hoc discovery of plagiarism or fabricated data.
That reframes the risk calculus for institutions. A proposal that clears peer review and receives an award is not retroactively safe; institutional research integrity offices should treat AI-authorship disclosures and certifications as live documents that could be tested years into a project period, not a one-time submission checkbox.
Compliance FAQs for Research Offices
What is NOT-OD-25-132?
NOT-OD-25-132 is an NIH Guide notice, “Supporting Fairness and Originality in NIH Research Applications,” issued 17 July 2025. It bars grant applications substantially developed by AI and, separately, caps most PIs at six NIH applications per year, effective for due dates from 25 September 2025.
How many grants can one PI submit to NIH per year?
A maximum of six new, renewal, resubmission, or revision applications per PD/PI or Multiple PI, counted per NIH Council Round rather than the calendar year strictly. T-series training grants and R13 conference grants are exempt from the count entirely.
Does NIH ban all use of AI in grant writing?
No. NIH restricts applications “substantially developed by AI” — content that is not the applicant’s original scientific thinking — rather than incidental editing or drafting assistance. The concern is plagiarism, fabricated citations, and misleading content, not tool use itself.
What happens if AI use is detected after an award is made?
NIH can pursue a research misconduct review, refer the case to the Office of Research Integrity, and take enforcement action including disallowance of costs or termination of the award — even after funding has already begun.
Compliance Steps Before the Next Submission Cycle
Research offices working toward the 2027 Council Round have a defined window to close process gaps. Practical steps that institutional sponsored-programs and research-integrity functions are adopting:
- Add an explicit AI-originality certification to internal routing and sign-off forms, distinct from the existing research-misconduct and conflict-of-interest attestations.
- Track each PI’s running six-application count centrally rather than relying on individual faculty to self-monitor eRA Commons, particularly across multi-department or multi-PI proposals.
- Flag applications naming the same PI as PD/PI on more than six efforts early in the planning cycle, and confirm which, if any, qualify for the T-code or R13 exemption before assuming a conflict exists.
- Brief investigators that post-award AI-authorship findings carry the same institutional exposure as post-award data-integrity findings — this is not solely a pre-submission compliance question.
- Coordinate with departmental research administrators (the audience ARMA, NCURA, and EARMA serve) so that the cap is applied consistently across schools and centres within one institution, since NIH counts at the individual-PI level regardless of departmental structure.
Implications for the Wider Research Ecosystem
NOT-OD-25-132 sits inside a broader pattern: funders are converging on the idea that AI-assisted productivity gains in proposal writing are not neutral if they change who gets reviewed and how thoroughly. The six-application cap is, functionally, a peer-review capacity-protection measure as much as an integrity measure — NIH is acknowledging that AI tools changed submission economics faster than its review infrastructure could absorb.
For research administration more broadly, the notice is also a signal that funder-side AI governance is arriving as binding operational policy, not aspirational guidance, and that institutions without a documented AI-in-proposals policy of their own are now exposed to funder-level enforcement they cannot pre-empt internally. Institutions that build durable certification and tracking workflows now — rather than treating this as a one-off notice to file away — will be better positioned as other US and international funders publish comparable AI-authorship and submission-volume rules over the next funding cycles.