CASRAI Dictionary

Tag: NIH grants policy statement

  • NIH Activity Codes Explained: A Grants Administrator’s Field Guide

    NIH activity codes are the three-character alphanumeric labels — R01, U01, K08, F31, P01 and dozens more — that NIH assigns to every grant mechanism to signal its purpose, its funding structure, and how much NIH staff are involved in running it. Reading a funding opportunity announcement (FOA) correctly starts with decoding this one code, because it determines eligibility, budget caps, review criteria, and reporting obligations before a single word of the science is assessed.

    An NIH activity code is defined by NIH’s Office of Extramural Research as the three-character identifier — for example R01, U01 or K08 — used to differentiate the research, training, career-development, and infrastructure programs NIH supports. This guide is a field reference for research administrators who need to tell these codes apart quickly and correctly the first time they open an FOA.

    What are NIH activity codes?

    An activity code is the three-character segment of an NIH grant number — the “R01” in 5R01HL123456-04 — that identifies the specific award mechanism. According to NIH’s Office of Extramural Research, activity codes are grouped into nine major letter series: F (fellowships), K (career development), N (research contracts), P (program projects and centers), R (research grants), S (research-related programs), T (training grants), U (cooperative agreements), and Y (interagency agreements).

    Each letter series carries a distinct relationship to NIH. R-series and U-series codes both fund discrete research projects, but the NIH Grants Policy Statement defines a cooperative agreement (U) as involving “substantial programmatic involvement” from NIH staff, whereas a grant (R) involves minimal day-to-day NIH direction. That distinction, not the science itself, often separates an R01 mechanism from a U01 mechanism for an identical research question.

    How do you read a full NIH grant number?

    The activity code is only one segment of a full NIH award number. A typical number — 5 R01 HL123456-04A1 — breaks down into six parts, and administrators who can parse all six avoid the most common FOA-reading errors: misidentifying a resubmission as a new application, or a supplement as a competing renewal.

    Segment Example Meaning
    Application/Type code 5 Type 5 = non-competing continuation; Type 1 = new; Type 2 = competing renewal; Type 3 = administrative supplement
    Activity code R01 The award mechanism (research grant, cooperative agreement, fellowship, etc.)
    Institute/Center code HL The primary NIH Institute or Center funding the award (HL = NHLBI)
    Serial number 123456 A unique project identifier assigned once by the Center for Scientific Review and retained for the project’s life
    Support year 04 The current year of the current project period
    Suffix code A1 Marks a resubmission (A1) or supplement/allowance variant (e.g. S1)

    The application-type digit matters as much as the activity code itself for compliance purposes: under NIH Grants Policy Statement section 2.3.4, a Type 3 administrative supplement adds funds within the existing scope of a peer-reviewed project without new peer review, while a Type 2 renewal is a fully competing application judged against the current review cycle.

    R01 vs U01: research grant or cooperative agreement?

    The R01 is NIH’s oldest, most-used mechanism: an investigator-initiated, discrete project, typically funded three to five years with minimal ongoing NIH direction. The U01 funds a comparably discrete project structured as a cooperative agreement, so NIH scientific staff have a defined, substantial role in decisions — common for multi-site clinical trials and coordinated consortia.

    Feature R01 (Research Project Grant) U01 (Research Cooperative Agreement)
    NIH programmatic role Minimal Substantial, defined in the Notice of Award
    Typical use Single-site, investigator-driven project Multi-site trials, coordinated consortia
    Budget ceiling No universal cap; modular budgets over $250,000/year direct costs require detailed justification Set per FOA, often larger due to coordination costs

    Smaller mechanisms sit alongside the R01. The R21 Exploratory/Developmental Research Grant supports high-risk, early-stage work, generally capped around $275,000 in direct costs across a two-year period under NIH’s standard parent R21 announcement. The R03 Small Grant is smaller still — typically limited to $50,000 per year over a maximum two-year period — and suits pilot data or secondary analysis rather than a full research programme.

    K awards vs F fellowships: career development or training?

    Both series fund people rather than research questions, but at different career stages. An F fellowship (Ruth L. Kirschstein National Research Service Award, e.g. F31 predoctoral or F32 postdoctoral) funds a mentored training experience for someone moving toward independence, with a stipend set annually under NIH’s NRSA stipend schedule.

    A K award (e.g. K01, K08, K23, K99) instead funds “protected time” — salary support plus research funds — for building an independent research programme, usually under mentorship. Per NIH’s K-award guidance, most mentored K mechanisms require at least 9 person-months (75% effort) committed to the career development plan, well above what F fellowships require of trainees.

    • F31/F32: mentored training, stipend-based, no independent PI status yet
    • K01/K08/K23: mentored career development, salary support, ≥75% effort commitment
    • K99/R00: two-phase “K99 mentored, R00 independent” transition award for postdoctoral researchers moving to faculty positions
    • K24/K05: non-mentored, for established investigators taking on new mentoring or research roles

    What do P-series and other codes cover?

    The P series funds large, multi-project programmes rather than single studies. A P01 (Research Program Project) supports several interrelated projects sharing a central scientific theme; a P30 or P50 Center grant funds shared infrastructure (“cores”) that serve multiple investigators. These mechanisms require an overarching administrative core and are among the most complex awards for a research administration office to manage, since sub-project budgets, personnel, and reporting must roll up into a single Notice of Award.

    Less common codes still matter operationally. The PF5 code, for instance, denotes NIH’s Collaborative International Research Project mechanism, created specifically to let NIH track federal fund expenditure at foreign components and satisfy federal oversight requirements when a US award involves an overseas site — a detail administrators handling international collaborations need to check before assuming standard R-series rules apply.

    Common questions administrators ask

    What is an R01 activity code?

    The R01 is NIH’s standard, investigator-initiated research project grant mechanism. It funds a discrete, PI-defined project in the applicant’s area of expertise, typically for three to five years, with minimal day-to-day NIH programmatic direction once the award is made.

    What is the difference between R01 and R03?

    An R01 funds a substantial, often multi-year research programme with no fixed budget ceiling under standard review; an R03 Small Grant funds a narrowly scoped project — pilot data, secondary analysis, or a small self-contained study — capped at roughly $50,000 in direct costs per year over a maximum two-year period.

    What is a Type 3 NIH grant?

    “Type 3” is not an activity code but an application-type digit: it designates an administrative supplement — additional funds added to a currently active, peer-reviewed award to cover unforeseen costs within the existing project scope, without a new competing peer review.

    What is the NIH PF5 activity code?

    The PF5 code identifies NIH’s Collaborative International Research Project mechanism, structured so NIH can track expenditure of federal funds at foreign components of a US-led award and meet federal reporting and oversight obligations for international sites.

    What this means for grants administration teams

    Getting the activity code wrong at intake has downstream costs: a proposal built to R01 assumptions but submitted under a U01 FOA can miss data-sharing plans, milestone structures, or steering-committee provisions that only apply to cooperative agreements. Pre-award teams should build activity-code verification into their FOA-intake checklist rather than relying on a PI’s assumption about “what kind of grant this is.”

    Eligibility, effort requirements, and budget caps are activity-code-specific, not investigator-specific — the same researcher can be eligible for a K08 at one career stage and ineligible at the next as the code’s own rules change. Teams supporting research administration functions should treat the activity code, not the topic area, as the first eligibility gate in pre-award review.

    Looking ahead

    NIH periodically retires and introduces activity codes as funding priorities shift. The current list on grants.nih.gov is the authoritative, continuously updated source and should be checked against any FOA before submission, since codes cited in older institutional guidance can lapse. Training staff on the full six-part grant number, not the activity code alone, gives a durable framework that survives individual codes being added or retired.

  • NIH Grants Policy Statement: What It Requires of Institutions

    The NIH Grants Policy Statement (NIHGPS) is the master terms-and-conditions document for every NIH award: institutions that accept NIH funding are bound by its rules on cost allowability, effort reporting, prior-approval triggers and audit obligations, applied alongside the government-wide cost principles in 2 CFR Part 200. Research administrators use it as the single reference point for what a grant actually obliges a recipient organisation to do.

    The NIH Grants Policy Statement is defined by NIH as the document that “makes available, in a single document, the policy requirements that serve as the terms and conditions of NIH grant awards.” It is not optional guidance — by accepting a Notice of Award, an institution agrees to comply with it unless the notice itself states otherwise.

    What is the NIH Grants Policy Statement?

    The NIHGPS is NIH’s consolidated statement of the terms and conditions attached to every grant, cooperative agreement and, where applicable, contract-adjacent award it issues. It is organised into three parts: general information about NIH and the award lifecycle, the substantive terms and conditions that bind recipients, and a directory of NIH contacts for compliance questions. Institutions do not negotiate these terms award-by-award; the current NIHGPS edition applies by reference from the date on the Notice of Award.

    Because the NIHGPS is revised periodically rather than rewritten from scratch, most institutional research offices track it as a living reference — checking each Notice of Award against the edition in force, since older awards can remain subject to the NIHGPS version current on the date they were issued.

    How does the NIHGPS relate to 2 CFR 200?

    The NIHGPS does not operate in isolation. It sits beneath, and explicitly incorporates, the Office of Management and Budget’s Uniform Guidance at 2 CFR Part 200 — the government-wide cost principles, administrative requirements and audit rules that apply to all US federal grants, not just NIH’s. The NIHGPS then layers NIH-specific interpretation and additional conditions on top of that baseline.

    There is also a departmental layer in between: the HHS Grants Policy Statement, issued by the Department of Health and Human Services, sets terms common to all HHS operating divisions. NIH’s own document tells recipients to consult the HHS Grants Policy Statement for department-wide matters and the NIHGPS for anything NIH-specific — the two are complementary, not duplicative.

    Document Issuing body Scope
    2 CFR Part 200 (Uniform Guidance) Office of Management and Budget Government-wide cost principles and audit requirements for all federal awards
    HHS Grants Policy Statement Department of Health and Human Services Department-wide terms across all HHS operating divisions
    NIH Grants Policy Statement National Institutes of Health NIH-specific terms and conditions layered on the two frameworks above

    What must institutions do to comply?

    Three compliance areas generate the most work for research administration offices: cost allowability, effort reporting, and the award terms that trigger prior approval.

    Cost allowability

    Costs charged to an NIH award must be allowable, allocable, reasonable and consistently treated, per the cost principles in 2 CFR 200 Subpart E, as applied through the NIHGPS. Institutions are expected to maintain financial management systems capable of tracking costs at the individual-award level and reconciling them through periodic Federal Financial Reports.

    Effort reporting

    Where NIH funds pay any part of a researcher’s salary, the institution must certify that the proportion of effort charged reflects the effort actually devoted to the project, consistent with the compensation-for-personal-services standard at 2 CFR 200.430. NIH also applies an annual salary cap, set against Executive Level II of the federal executive pay scale, that limits the salary rate chargeable to NIH awards regardless of an individual’s actual institutional salary.

    Award terms and prior approval

    The NIHGPS lists specific actions that require NIH’s prior written approval before an institution can proceed — commonly a significant change in project scope, a change of principal investigator, a no-cost extension beyond the automatic first extension, or the addition of a foreign component. Institutions that expend federal awards above the Single Audit threshold — raised to $1,000,000 under OMB’s 2 CFR 200 revision effective for fiscal years beginning on or after 1 October 2024 — must also arrange an annual Single Audit.

    • Maintain auditable, award-level financial records under 2 CFR 200 cost principles
    • Certify effort for NIH-funded personnel and apply the current salary cap
    • Seek prior approval for scope changes, PI changes, extensions and foreign components
    • Comply with human subjects, animal welfare, research misconduct and conflict-of-interest policies
    • Report inventions arising from NIH funding under Bayh-Dole Act procedures
    • Meet NIH data-sharing and public-access requirements for funded research outputs

    What changed for FY2026?

    NIH published a revised NIHGPS effective March 2026, applicable to awards issued for Fiscal Year 2026. Research offices should treat each Notice of Award as the definitive marker of which NIHGPS edition governs that specific award, since NIH does not retroactively apply every revision to awards already in force. Comparing the March 2026 edition against the prior version — rather than assuming continuity — is the safest institutional practice each cycle.

    Answer-first Q&A

    Who can apply for an NIH grant?

    Most NIH programmes do not require applicants to hold a specific degree or US citizenship; eligibility is set at the level of the individual funding opportunity. Institutions, not individuals, are the formal recipients of NIH awards, and it is the institution that assumes NIHGPS compliance obligations on behalf of its research staff.

    Can non-US citizens apply for NIH grants?

    Yes. Non-US institutions and researchers can serve as recipients or principal investigators for most NIH mechanisms, though some programmes impose citizenship or residency conditions stated explicitly in the funding opportunity notice. The NIHGPS applies equally to foreign and domestic recipient organisations once an award is made.

    What are the NIH guidelines referenced in grant compliance?

    “NIH guidelines” typically refers to specific technical policies — such as those governing recombinant DNA research — that sit alongside, but are distinct from, the NIHGPS. The NIHGPS is the umbrella terms-and-conditions document; specialised guidelines are incorporated into it by reference where relevant to a given award.

    What is a Type 3 NIH award?

    A Type 3 award is an administrative supplement: additional funds provided during a current project period to cover increased costs within the existing, peer-reviewed scope of work. It cannot extend the award beyond its current end date and is governed by the same NIHGPS terms as the parent award.

    What this means for research administration offices

    For grants and contracts offices, the practical implication is that NIHGPS compliance cannot be delegated to a single reading at award setup. Cost allowability rules, effort-reporting certification cycles and prior-approval triggers recur throughout an award’s life, and each NIHGPS revision can shift specific thresholds or procedures without changing the document’s overall structure. Institutions that build compliance checklists against the current NIHGPS edition — cross-referenced to 2 CFR 200 and the HHS Grants Policy Statement — reduce the risk of disallowed costs and audit findings.

    This layered structure (OMB, HHS, NIH) is a useful model for research administrators more broadly: understanding how a funder-specific policy statement incorporates broader federal cost and audit frameworks is a transferable skill across other US federal sponsors, not just NIH. CASRAI’s research administration content covers this compliance-mapping approach across funders.

    Looking ahead

    NIH continues to revise the NIHGPS on a rolling basis rather than a fixed annual schedule, and institutions should expect further alignment with OMB’s evolving Uniform Guidance, particularly around audit thresholds and data-sharing expectations. Research administration offices that treat the NIHGPS as a living compliance map — rather than a document read once at onboarding — are best positioned to absorb each revision without disruption to active awards.

  • eRA Commons Guide: Roles, JIT, RPPR & Closeout

    eRA Commons is the web-based portal that NIH, its grantee institutions, and federal partner agencies use to manage every administrative stage of a National Institutes of Health award — registration, application tracking, Just-in-Time (JIT) requests, annual progress reporting (RPPR), and closeout. For a research administrator handling a first NIH award, eRA Commons is where institutional roles are assigned, documents are routed for signature, and compliance deadlines are tracked from submission through final closeout.

    eRA Commons (Electronic Research Administration Commons) is defined by NIH’s own policy documentation as “an online interface where grant applicants, recipients and Federal staff at NIH and grantor agencies can conduct their research administration business,” according to the NIH Grants Policy Statement (NIHGPS), Section 2.2. It is distinct from ASSIST, which is used to prepare and submit the application package, and from NIH RePORTER, the public database used to search awarded projects.

    What is eRA Commons?

    eRA Commons is NIH’s system of record for post-submission grant administration. Once an application enters the system, applicants, recipient institutions, and NIH programme and grants management staff use eRA Commons to check status, view summary statements, respond to information requests, and file every required report through award closeout.

    The portal sits inside NIH’s broader Electronic Research Administration (eRA) suite, which also includes ASSIST (application preparation), xTrain (training-grant appointments), and xTRACT (personnel data tables for training awards). eRA Commons is the hub that connects these modules to a single institutional profile and a single set of user accounts.

    Who needs an eRA Commons account, and what are the roles?

    Every eRA Commons account carries one or more institutional roles, and the functions a user can perform are determined entirely by that role assignment. NIH separates administrative roles (which cannot be combined with scientific roles) from scientific roles such as Principal Investigator. The core roles are:

    Role Who holds it Key authority
    Signing Official (SO) Institutional authorised representative Registers the institution, submits applications, JIT, RPPRs and closeout documents
    Administrative Official (AO) Central or departmental research office staff Reviews applications before SO submission; cannot submit to NIH
    Account Administrator (AA) Central research administration office Creates and manages Commons accounts on the SO’s behalf
    Business Official (BO) Training-grant administrator Manages xTrain appointments and termination notices
    Principal Investigator (PI) Named PD/PI on the award Initiates RPPRs; can delegate submission, status and xTrain access
    Financial Status Reporter (FSR) Sponsored programmes finance staff Submits the Federal Financial Report (FFR)
    FCOI / FCOI_ASST / FCOI_VIEW Conflict-of-interest office Manages or views Financial Conflict of Interest disclosures

    One person can hold several administrative roles at once (an SO is often also the FSR), but administrative and scientific roles cannot combine on one account — an SO who is also a PI needs two separate Commons accounts.

    How does eRA Commons registration work?

    Institutional registration is an SO-led, one-time process, separate from creating individual user accounts. Per the NIH Grants Policy Statement, Section 2.2.1, organisations registering in eRA Commons for the first time should allow two to four weeks to complete the registration process — a lead time new research offices routinely underestimate when planning their first submission.

    1. The institution submits its organisational registration, including its Employer Identification Number (EIN) and banking (DUNS/UEI) details.
    2. NIH’s eRA Commons help desk verifies the institutional profile (IPF).
    3. The SO creates individual accounts for AOs, AAs, PIs and other staff, assigning roles as needed.
    4. Users complete their personal profile, including an ORCID iD where applicable, before submitting or being named on an application.

    What is Just-in-Time (JIT), and when is it required?

    Just-in-Time (JIT) is the point in the pre-award process, after peer review but before a funding decision, when NIH requests additional information it does not need to evaluate scientific merit but does need before issuing an award. JIT typically covers other support pages, updated IRB/IACUC approval dates, and other financial certifications, and is submitted through eRA Commons rather than as part of the original application.

    Only the SO can submit JIT information, though this is often delegated to the PI or an ASST-role user. Institutions that treat JIT as a low-priority formality create the single biggest avoidable delay between award recommendation and the Notice of Award (NoA).

    How do RPPR submission and grant closeout work?

    The Research Performance Progress Report (RPPR) is the standard mechanism NIH uses to monitor scientific and financial progress on a funded award. A PI initiates the annual RPPR in eRA Commons; the SO (or a PI delegated with submission authority) then routes and submits it. Non-competing continuation funding for the following budget period depends on timely RPPR submission.

    At the end of the project period, three closeout documents are due through eRA Commons: the Final RPPR, the Final Federal Financial Report (FFR), and the Final Invention Statement (FIS). Under federal closeout requirements referenced throughout the NIH Grants Policy Statement, recipients must submit all required closeout reports within 120 calendar days of the period-of-performance end date. Missing this window can trigger late-closeout flags that affect an institution’s standing on future awards.

    • Final RPPR — scientific progress and outputs for the full project period
    • Final FFR — expenditure reconciliation, submitted by the FSR role
    • Final Invention Statement — disclosure of inventions conceived or reduced to practice under the award

    How does eRA Commons differ from ASSIST and NIH RePORTER?

    Research administrators new to NIH awards often conflate eRA Commons with the tools used to find or apply for funding. The three systems serve different stages of the award lifecycle and should not be used interchangeably:

    System Purpose Typical user
    eRA Commons Post-submission tracking, JIT, RPPR, closeout, account/role management SO, AO, AA, PI, FSR
    ASSIST Prepares and submits the application package to Grants.gov/eRA AOR, PI, grants administrator
    NIH RePORTER (with Matchmaker) Public search of already-funded projects, publications and patents; Matchmaker suggests similar funded abstracts or reviewers Prospective applicants, policy analysts, the public

    A related but separate reference point is NIH’s system of activity codes (for example R01, K award, or U-series mechanisms), which classify the type of grant mechanism and appear throughout eRA Commons screens and the NIH Grants Policy Statement, but are defined by NIH’s Office of Extramural Research rather than by eRA Commons itself.

    Frequently asked questions

    What is eRA Commons used for?

    eRA Commons is used to track application status, submit Just-in-Time information, file annual and final RPPRs, and complete closeout documentation for NIH and select other federal research awards. It is the single portal linking an institution’s Signing Official, administrative staff and Principal Investigators to one shared award record.

    How do I get an eRA Commons ID?

    An individual eRA Commons ID is created by the institution’s Signing Official or Account Administrator, not self-registered by the user. A Principal Investigator should hold only one Commons ID for their entire career, which is then affiliated or unaffiliated with institutions as they move between them.

    What is the difference between eRA Commons and ASSIST?

    ASSIST prepares and submits the grant application; eRA Commons tracks it afterward and manages everything from peer-review outcomes through closeout. Institutions use ASSIST once per submission cycle but use eRA Commons continuously for the life of the award.

    Who can submit an RPPR in eRA Commons?

    The Signing Official has default authority to submit an RPPR, but can delegate that authority to the Principal Investigator for that specific report. Once delegated, the PI becomes the individual who legally binds the institution for that submission.

    Implications and outlook for research administrators

    For institutions handling their first NIH award, the practical risk is rarely the science — it is role assignment and deadline tracking inside eRA Commons. Registering two to four weeks ahead, assigning SO/AO/AA roles deliberately, and calendaring the 120-day closeout window are the three highest-leverage administrative actions a new research office can take.

    Institutions that treat the portal as a compliance system rather than a submission afterthought see fewer JIT delays and fewer late-closeout findings. Research administrators reviewing adjacent reporting standards can consult the CASRAI CRediT contributor roles reference, which some NIH-funded institutions now request alongside RPPR publication lists.

  • NIH’s March 2026 Grants Policy Statement: What Every Institution’s Research Office Needs to Do Now

    The National Institutes of Health has issued a March 2026 revision to the NIH Grants Policy Statement (NOT-OD-26-057), and research offices outside the United States are not exempt from its reach. Any UK or international institution holding a subaward, consortium agreement, or direct NIH grant now has a compliance clock running: the most consequential change — a new prior-approval requirement for subawards — takes effect from 1 June 2026.

    For research administrators, this is not a routine annual refresh. The revised NIH grants policy statement 2026 tightens subrecipient monitoring, reinforces the NIH Data Management and Sharing (DMS) Policy, and, less visibly but just as significantly, hardens expectations around how contributor roles are documented on funded outputs. Institutions that treat this as a US-only administrative update will find themselves scrambling when their next competing renewal or Just-in-Time submission is flagged for missing subaward documentation.

    This explainer sets out what changed, why it matters for research grant administration beyond NIH’s own borders, and the concrete steps a research office should be taking this quarter.

    What NOT-OD-26-057 Actually Changes

    The headline change in the March 2026 NIH Grants Policy Statement revision is the introduction of a prior-approval step before a recipient institution may issue certain subawards under active NIH grants. Historically, subaward issuance sat largely within a recipient’s own delegated authority once the parent award was in hand, subject to standard federal subrecipient monitoring obligations under 2 CFR 200 (the Uniform Guidance). From 1 June 2026, awardee institutions must obtain NIH sign-off before finalising subawards that meet the thresholds specified in the revised policy — a shift that mirrors the agency’s broader push, visible across recent Notices, to get earlier visibility into where federal research funds ultimately flow.

    For UK universities and research institutes that sit downstream as subrecipients on US-led NIH awards, this changes the practical timeline of collaboration. A subaward that might previously have been executed within weeks of a parent award’s Notice of Award could now be delayed pending NIH’s prior-approval review. Research offices coordinating multi-country consortia — a common pattern in genomics, infectious disease, and clinical trials networks — need to build this lag into project start dates and budget-period planning, and should flag it explicitly to principal investigators who are used to faster subaward turnaround.

    Data Management and Sharing: Convergence, Not a New Burden

    The revised Grants Policy Statement does not introduce a new data-sharing regime; instead, it folds the existing NIH Data Management and Sharing Policy more tightly into the core policy document, making DMS plan compliance an explicit, cross-referenced condition of award rather than a companion policy institutions could treat as separate. In practice, this means DMS plans are now read alongside the Grants Policy Statement’s subaward and reporting provisions as a single compliance package, which raises the stakes for institutions whose data plans have been thin or templated.

    The same logic applies to the NIH open access policy lineage — the NIH Public Access Policy that governs deposit of peer-reviewed manuscripts arising from NIH funding. The 2026 revision continues to align expectations around timely deposit, persistent identifiers, and machine-readable metadata with the broader global shift toward open science, echoed in UKRI’s own open access policy and the cOAlition S Plan S principles. Institutions with NIH-funded outputs should treat manuscript deposit compliance and DMS plan fidelity as two halves of the same reporting obligation, not separate boxes to tick.

    Contributor Roles and the Attribution Layer

    A quieter but structurally important element of the revised policy is its reinforcement of contributor-role transparency in reporting and progress reports involving multiple investigators and subrecipient teams. Where an award spans several institutions, NIH’s expectation is that reporting clearly distinguishes who did what — an expectation that maps naturally onto the contributor role taxonomy first published as CRediT.

    CASRAI originated the CRediT contributor role taxonomy in 2014. The standard is now stewarded by NISO as ANSI/NISO Z39.104-2022, and its fourteen roles — from Conceptualization and Methodology through to Writing – Original Draft and Writing – Review & Editing — give research offices a ready-made, internationally recognised vocabulary for exactly the kind of multi-institution attribution NIH’s revised reporting language is asking for. Institutions that already require CRediT statements on manuscripts arising from grant-funded work, and that track contributor roles at the ORCID-linked researcher level, will find it far easier to produce the kind of granular reporting the 2026 policy anticipates than those relying on ad hoc author-order conventions.

    This is a useful moment for research offices to check whether their internal reporting templates for multi-site NIH awards actually capture contributor roles in a structured way, or whether that information exists only informally between collaborating PIs.

    What This Means for Research Administrators

    The combined effect of the subaward prior-approval rule, the tighter DMS/open-access linkage, and the contributor-attribution expectations is a policy environment that rewards institutions with mature research administration policy 2026 infrastructure and penalises those still managing NIH compliance manually. Concretely, research offices should:

    • Map every active and pipeline NIH subaward against the new prior-approval thresholds, and rebuild subaward issuance timelines to account for the review step from 1 June 2026.
    • Audit existing DMS plans against the revised Grants Policy Statement language, not just the standalone DMS Policy text, to close any gaps in how the two are cross-referenced.
    • Confirm that manuscript deposit workflows tied to the NIH Public Access Policy are functioning ahead of any competing renewal or annual progress report.
    • Introduce or reinforce CRediT-based contributor statements in multi-institution reporting, using ORCID identifiers to anchor role attribution at the individual level.
    • Brief PIs directly — subaward delays and reporting changes affect project planning, not just the compliance office, and PIs are often the last to hear about policy notices like NOT-OD-26-057.

    Bodies such as NCURA, EARMA, and ARMA have all flagged the growing complexity of cross-border federal compliance as a priority area, and institutions should look to these networks — alongside INORMS — for shared templates and peer benchmarking rather than building compliance responses in isolation. Investment in structured research administration training on the revised Grants Policy Statement, delivered before the June deadline, will do more to prevent downstream delays than any last-minute scramble once subawards start stalling in review.

    Looking Ahead

    NIH’s March 2026 revision is best read as part of a broader convergence: funder policies, open science mandates, and structured attribution standards are increasingly expected to interlock rather than operate as parallel compliance streams. Research offices that align their subaward management, data-sharing infrastructure, and contributor-role reporting now — rather than treating each as a separate policy silo — will be far better placed not only for this revision, but for the funder policy changes that are likely to follow it as NIH, UKRI, and other major funders continue to tighten the links between funding, data stewardship, and verifiable attribution of research contributions.