CASRAI Dictionary

Tag: era commons

  • NIH R21 Eligibility vs R01: What ESIs Need to Know

    NIH R21 eligibility and R01 eligibility both extend to early-stage investigators (ESIs), postdoctoral fellows, and established faculty alike — the two mechanisms do not gate applicants by career stage. What differs is project readiness: the R21 is built for exploratory, high-risk ideas without preliminary data, while the R01 requires a mature, hypothesis-driven research plan and carries a funding advantage reserved specifically for ESIs.

    An NIH R21 is an Exploratory/Developmental Research Grant Award capped at two years and $275,000 in total direct costs, designed to seed early-stage or high-risk research rather than fund a fully developed programme.

    What does NIH R21 eligibility actually require?

    NIH R21 eligibility has no formal career-stage restriction. Any individual with the skills, knowledge and resources to carry out the proposed research may serve as principal investigator, provided their institution is eligible to receive NIH funding. There is no minimum degree requirement and no exclusion for early-career applicants.

    What R21 eligibility does require is fit with the mechanism’s purpose. Under NIH’s activity code guidance, the R21 supports the “early and conceptual stages” of a project — pilot studies, novel methodology development, or high-risk/high-reward ideas — rather than confirmatory or fully powered research. Reviewers are explicitly instructed not to penalise applications for lacking extensive preliminary data, which is the R21’s defining structural feature.

    • Project period: up to two years, non-renewable.
    • Budget: up to $275,000 in total direct costs across the two years, with no more than $200,000 in any single year.
    • Research Strategy section: limited to six pages, versus twelve for an R01.
    • Standard receipt cycles: three per year (mid-February, mid-June, mid-October), with no letter of intent required.

    How does R01 eligibility differ?

    NIH R01 eligibility is likewise open to any qualified investigator regardless of career stage — but the R01 is calibrated for a different kind of readiness. It funds a “mature, hypothesis-driven” research plan, typically over three to five years, and in practice reviewers expect substantial preliminary data even though NIH policy does not formally mandate it.

    The critical eligibility distinction for early-career applicants is not who may apply, but how ESI applications are treated once submitted. NIH’s Early Stage Investigator policy defines an ESI as a PI within ten years of completing a terminal research degree or postgraduate clinical training who has not yet successfully competed for a substantial NIH independent research award. Many NIH institutes and centres extend more favourable payline consideration to ESI R01 applications specifically — a benefit that does not extend to R21 submissions, according to NIH’s own Early Stage Investigator Policy guidance published via the NIH Office of Extramural Research.

    R21 vs R01: eligibility and structure at a glance

    The table below summarises the practical differences that matter most when an early-stage investigator is deciding which mechanism to pursue.

    Feature R21 (Exploratory/Developmental) R01 (Research Project Grant)
    Career-stage restriction None None
    ESI payline advantage Not applicable Applies at most participating institutes
    Preliminary data Not required; reviewers instructed not to penalise its absence Not mandated, but expected in practice
    Project period Up to 2 years Typically 3–5 years
    Direct costs Up to $275,000 total; $200,000 cap per year No fixed statutory cap; modular budgets commonly requested up to $250,000/year
    Renewable No Yes
    Research Strategy page limit 6 pages 12 pages
    Receipt cycles 3 per year, no letter of intent 3 standard NIH due dates per year

    Which track should an early-stage investigator choose?

    The eligibility rules alone will not decide this — the strategic calculus does. Because the ESI payline advantage applies only to R01 applications, an ESI with a genuinely mature research plan and defensible preliminary data is usually better served applying directly for an R01, where the same percentile score is judged against a more favourable cutoff than either an established investigator’s R01 or the ESI’s own R21 would receive.

    An R21 remains the right eligibility route when an ESI is pivoting into a field with no track record, testing a high-risk method, or needs seed data before a competitive R01 can be written. Importantly, holding an R21 does not by itself end ESI status — an investigator can use an R21 to generate pilot data and still submit a subsequent R01 as an ESI, provided they have not already held a substantial independent NIH award.

    The risk to watch is what grant strategists sometimes call the R21 trap: two years and $275,000 rarely generate enough momentum to avoid a funding gap once the award ends, given the R21’s non-renewable structure. Early-stage PIs should map the R21’s fixed end date against their institution’s next R01 cycle before committing to the exploratory route.

    Where do U01s and other NIH activity codes fit?

    NIH activity codes extend well beyond R21 and R01. The R-series alone includes the R03 (small grant, descriptive/pilot work), R15 (Academic Research Enhancement Award, for institutions with a lower NIH funding history), and R34 (planning grant). Career-stage-specific mechanisms sit in the K-series (career development awards), while the F-series covers individual fellowships.

    The U01 sits outside the R-series entirely: it is a cooperative agreement, not a research grant. The defining difference in a u01 vs r01 grant comparison is programmatic involvement — a U01 gives the NIH programme officer substantial scientific and technical involvement in the project, whereas an R01 PI retains full independent direction. Some funding opportunities offer parallel R01/U01 tracks, in which case the choice depends on whether the institution is comfortable with NIH staff having a defined role in study design.

    Institutional sign-off: what research administrators need before submission

    Eligibility to apply is only half the picture — eligibility to submit runs through the institution. Every NIH application is transmitted via eRA Commons, and no PI submits directly: a Signing Official (SO) at the applicant institution must authorise and route the application through Grants.gov and eRA Commons on the organisation’s behalf.

    This has direct implications for R21-vs-R01 planning that pure eligibility guidance tends to omit. R21 budget justifications are typically quicker to process, given the hard $200,000 annual cap and six-page Research Strategy, but institutions still require the same internal sign-off chain: department or dean-level approval, cost-sharing review where applicable, and SO certification in eRA Commons ahead of the mechanism-specific deadline. First-time PIs should confirm their institution’s internal routing deadline — commonly five to ten business days before the NIH receipt date — regardless of activity code, since a missed internal sign-off blocks submission even when the PI is otherwise fully eligible.

    Answer-first Q&A

    What is an R21 NIH grant?

    An R21 is NIH’s Exploratory/Developmental Research Grant Award, intended to fund the early and conceptual stages of a research project. It supports pilot, high-risk or methodologically novel work without requiring extensive preliminary data, and is capped at two years and $275,000 in total direct costs.

    What is the difference between R01 and R21?

    An R01 funds a mature, hypothesis-driven research programme typically over three to five years with reviewer expectations of solid preliminary data, while an R21 funds exploratory or high-risk ideas over a maximum two years with no such expectation. Only R01 applications receive the ESI payline advantage.

    What is the R21 funding limit?

    The R21 budget cap is $275,000 in total direct costs across the full two-year project period, with no more than $200,000 permitted in any single year. This limit is fixed by NIH’s activity-code guidance and applies regardless of the awarding institute or centre.

    What are the NIH R21 cycles?

    NIH runs three standard R21 receipt cycles a year — mid-February, mid-June and mid-October — for most participating institutes. No letter of intent is required, and applicants may submit new R21 applications at any of these three annual deadlines.

    Implications for first-time PIs

    For institutions supporting first-time PIs, the R21-vs-R01 eligibility decision is best framed as a readiness audit, not a career-stage filter: both mechanisms are open to ESIs, but only the R01 carries the payline consideration NIH built for that population. Research administrators advising early-career faculty should pair mechanism selection with an honest look at preliminary data and the institution’s internal sign-off timeline, so a two-year R21 realistically bridges to a fundable R01 rather than lapsing. Framed this way, eligibility becomes a planning tool rather than a gate — and research administration teams are well placed to run that audit alongside the PI.

  • NIH Matchmaker: Find Peers and Study Sections

    NIH Matchmaker is a free text-similarity search tool built into NIH RePORTER that lets a researcher paste an abstract or specific aims page and instantly see the most similar NIH-funded projects, the institutes that funded them, the activity codes used, and the study sections that reviewed them. For grant offices and research administrators, this turns a guessing exercise — “who else works in this space, and who will review us?” — into a data-driven five-minute check before a proposal is submitted.

    NIH RePORTER (Research Portfolio Online Reporting Tools Expenditures and Results) is the National Institutes of Health’s public database of funded projects, publications and patents, maintained by NIH’s Office of Extramural Research. Matchmaker is one of several search modes inside it, alongside keyword-based Advanced Search and the Center for Scientific Review’s separate Assisted Referral Tool (ART). Most institutional grant offices know Advanced Search well and have never opened Matchmaker — which is exactly the gap this guide closes.

    What is NIH Matchmaker?

    NIH Matchmaker is the text-similarity search feature of NIH RePORTER, NIH’s public grants database. Rather than requiring a researcher to guess the right keywords, Matchmaker accepts a block of free text — typically a project abstract or specific aims section — and returns a ranked list of previously funded NIH projects with comparable scientific content.

    The tool sits inside the same interface as RePORTER’s project search and requires no eRA Commons login to run a search; it is open to the public, including institutional grant administrators who are not themselves the principal investigator (PI) on a proposal. That distinction matters, because eRA Commons access is only required later, at submission and progress-report stage, not for discovery searches.

    How Matchmaker works: text in, peers out

    A user pastes text — up to roughly 15,000 characters — into the Matchmaker search box on reporter.nih.gov. The system parses the terms and concepts in that text and compares them against NIH’s full corpus of funded project abstracts, returning matched projects ordered by a relevance (“match”) score rather than by exact keyword overlap.

    This is the practical advantage over Advanced Search: a researcher does not need to know NIH’s internal vocabulary for their field. A specific-aims paragraph written in plain scientific prose is enough to surface funded peers, even where the terminology differs from what NIH’s controlled taxonomy would predict.

    • Paste an abstract, aims page, or project summary directly — no query syntax required.
    • Results are grouped visually by NIH institute or centre (ICO) and by activity code.
    • Each matched project links through to its full RePORTER project record, including funded amount and PI.
    • The report also breaks matched projects down by the study section that reviewed them.

    Matchmaker vs Advanced Search vs ART

    NIH RePORTER offers three distinct discovery routes, and institutional grant offices routinely default to only one of them. Each serves a different question.

    Tool Input Best for Owner
    NIH RePORTER Advanced Search Boolean/field queries (PI name, institution, keyword, fiscal year, activity code) Locating a known project, PI, or institution’s funding history NIH Office of Extramural Research
    NIH Matchmaker Free text (abstract, aims page, summary) Finding comparably-funded peers and likely study sections for a new proposal NIH Office of Extramural Research
    Assisted Referral Tool (ART) Free text (similar to Matchmaker) Getting a suggested study-section assignment directly from the reviewing body NIH Center for Scientific Review (CSR)

    Matchmaker and ART both use text-similarity matching and often surface overlapping study sections, but ART sits with CSR — the body that actually makes final review assignments — while Matchmaker is a general discovery layer inside RePORTER. Using both, rather than either alone, is the more defensible approach for a formal study-section request in a cover letter.

    Reading a Matchmaker report: activity codes and study sections

    A Matchmaker report is only useful if the reader can interpret two recurring elements: activity codes and study sections. Activity codes are NIH’s two- or three-character classification of grant mechanism, and they appear on every matched project.

    • R01 — the standard NIH research project grant, typically 3-5 years.
    • R21 — exploratory/developmental research, shorter and smaller than an R01.
    • R03 — small grant for limited-scope, short-duration projects.
    • K99/R00 — the Pathway to Independence award for early-career transition.
    • U01 — cooperative agreement with substantial NIH programmatic involvement.
    • P01 — multi-project program project grant.

    Study sections are the peer-review panels convened by CSR to evaluate applications by scientific discipline. A Matchmaker report shows which study sections reviewed the matched, already-funded projects — direct evidence of where NIH has previously sent similar science for review. That evidence is more current and more granular than the study-section descriptions published on CSR’s own roster pages, because it reflects actual assignment outcomes rather than a panel’s stated scope.

    Common questions

    How do I find the right NIH study section using Matchmaker?

    Paste your specific aims or abstract into Matchmaker and review the study-section breakdown of your top-matched projects. The study sections appearing most frequently among close matches are the strongest evidence-based candidates to request in your cover letter, though CSR makes the final assignment.

    Use NIH RePORTER’s Advanced Search, not Matchmaker, for PI-name lookups. Advanced Search offers a dedicated PI/co-PI field alongside institution, fiscal year, and activity-code filters, returning an exact list of a named investigator’s funded NIH awards.

    Why does NIH Matchmaker return no results or seem broken?

    Matchmaker requires JavaScript enabled and a modern browser session; RePORTER displays a “please enable it to continue” message otherwise. Empty results usually mean the pasted text is too short or too generic — a full abstract or aims paragraph performs far better than a single sentence.

    What is the difference between NIH Matchmaker and NIH RePORTER Advanced Search?

    Advanced Search matches exact fields you specify (name, keyword, code); Matchmaker matches the meaning of a pasted text block against funded abstracts. Use Advanced Search when you know what you’re looking for, and Matchmaker when you need to discover unknown peers or likely reviewers.

    What this means for grant offices

    Most pre-award workflows at institutional research offices still rely on Advanced Search and word-of-mouth knowledge of “who funds this” — Matchmaker replaces guesswork with a documented, repeatable evidence trail that can sit in a proposal’s internal review file. Running a Matchmaker check before a PI submits is a five-minute addition to any pre-submission checklist, and it produces two concrete deliverables: a short list of comparably-funded peers worth citing or contacting, and a defensible, evidence-based study-section recommendation for the cover letter.

    For research administrators managing portfolios across multiple PIs, running Matchmaker at the department or centre level — pasting a synthesis of several related aims pages — can also surface funding-landscape gaps: institutes or activity codes with strong topical overlap that a department has not yet approached. As NIH RePORTER continues to be positioned by NIH’s Office of Extramural Research as the primary public window into its funded portfolio, tools like Matchmaker are becoming a standard, not optional, part of pre-award due diligence — and grant offices that build it into their checklists now will have a documented edge over those still relying on Advanced Search alone.

  • U01 vs R01 Grant: NIH Governance Difference

    A U01 is an NIH cooperative agreement in which programme staff are substantially involved in shaping the research; an R01 is a standard NIH research grant in which the principal investigator retains full scientific autonomy. The mechanisms otherwise fund similar science — the deciding factor is governance, not topic or budget size.

    The u01 vs r01 grant question comes up constantly among early- and mid-career investigators comparing Funding Opportunity Announcements (FOAs), and among research administrators advising faculty on which activity code to target. A cooperative agreement is defined by NIH as an assistance mechanism used “when there will be substantial Federal programmatic involvement with the recipient during performance of the anticipated activity” — that single distinction cascades through eligibility, budgeting, and day-to-day project management.

    What is the core difference between a U01 and an R01?

    The R01 Research Project Grant is NIH’s oldest and most common mechanism. It funds a discrete, investigator-defined research project, and once awarded, NIH’s role is largely to fund and monitor rather than direct the work. The National Institute on Aging (NIA) describes the R01 as a “Traditional Research Project,” in contrast to the U01, which it labels a “Cooperative Agreement Award” supporting “a discrete, specified, circumscribed research project … performed by the named investigator(s) in cooperation” with NIH staff.

    A U01 is legally a cooperative agreement, not a grant, even though it funds a similarly scoped project. That distinction is not cosmetic: cooperative agreements carry a statutory expectation of agency involvement that grants do not.

    How does NIH programme staff involvement work under a U01?

    Under a U01, an NIH programme official is typically named as a substantive collaborator, not just an administrative contact. This can include contributing to protocol design, setting go/no-go milestones, participating in data and safety monitoring, and helping steer scope changes mid-project.

    Investigators applying for U01s should expect:

    • Milestone-based progress reviews built into the award terms, sometimes with continued funding contingent on meeting them
    • Direct scientific input from NIH staff on study design, particularly for multi-site or clinical trial work
    • Coordination requirements when several U01 sites report to the same NIH programme, common in consortium-style initiatives
    • A Request for Applications (RFA) or targeted Program Announcement as the usual entry point, rather than an open-ended, investigator-initiated submission

    By contrast, R01 applicants who bring their own hypothesis and preliminary data face no equivalent programmatic partnership; NIH’s involvement is confined to peer review, award administration, and standard progress reporting.

    What are the funding, duration, and eligibility differences?

    Budget mechanics diverge sharply between the two codes. NIH’s modular budget policy — which caps direct-cost requests at $250,000 per year before a detailed line-item budget is required — applies to standard R01 applications. U01 cooperative agreements are generally excluded from modular budgeting and require a full, detailed budget justification regardless of size, reflecting the closer NIH oversight built into the mechanism.

    Eligibility rules, however, converge in one important respect. NIH’s own activity-code guidance for the U01 states that Early Stage Investigator (ESI) status is assessed the same way across both: “If all the PD/PIs on an R01 (or R01-equivalent, including U01) application have ESI status on the date an application is submitted,” it is treated as an ESI application. In other words, U01s count as R01-equivalent awards for ESI and early-career funding calculations.

    Feature R01 (Research Project Grant) U01 (Cooperative Agreement)
    Legal instrument Grant Cooperative agreement
    NIH staff role Funding and oversight only Substantial scientific/programmatic involvement
    Typical entry point Investigator-initiated or open FOA Targeted RFA or Program Announcement
    Budget format Modular budget up to $250,000/year direct costs Detailed budget required regardless of size
    Duration Up to 5 years, renewable Set by the specific FOA, often milestone-gated
    ESI/early-career treatment Standard R01 ESI rules Treated as R01-equivalent for ESI status
    Best suited for Hypothesis-driven, independent research with strong preliminary data Multi-site studies, clinical trials, projects needing NIH coordination

    When should an investigator choose a U01 over an R01?

    An R01 fits a self-contained research question that one lab, or a small collaborating team, can execute without external coordination. A U01 fits work that genuinely benefits from NIH’s coordinating role: harmonising protocols across multiple clinical sites, aligning data standards across a consortium, or delivering a resource (a dataset, an assay, a trial infrastructure) that NIH programme staff have a direct stake in shaping.

    Investigators should read the specific FOA before assuming either code applies by default. Institutes vary in how they deploy U01s — some use them almost exclusively for multi-site clinical trials, others for resource-building initiatives like biobanks or shared data platforms.

    Answer-first Q&A: U01 vs R01

    What is the difference between U01 and R01?

    A U01 is a cooperative agreement requiring substantial NIH programmatic involvement in project design and milestones. An R01 is a standard research grant where the principal investigator retains full scientific control. Both can fund comparable science; the difference is governance, not scope, budget cap, or scientific ambition.

    What is a U01 grant?

    A U01 is NIH’s Research Project Cooperative Agreement activity code. It funds a specified project performed “in cooperation” with named NIH staff, who contribute to protocol decisions and monitor milestones. U01s are commonly used for multi-site trials, consortia, and resource-development projects requiring active NIH coordination rather than pure investigator autonomy.

    What are the different types of R01 grants?

    R01s vary mainly by FOA type rather than a separate code: investigator-initiated (parent) R01s, R01s issued against targeted RFAs, and R01-equivalent activity codes NIH groups for reporting purposes. All share the same modular budget and independent-investigator structure; the variation lies in the announcement, not the underlying mechanism.

    Is R01 a big deal?

    Yes — NIAID and other institutes describe the R01 as the mechanism for “mature research projects that are hypothesis-driven with strong preliminary data,” providing up to five years of support. It remains NIH’s most prestigious and most commonly awarded research project grant, widely treated as a benchmark of independent investigator status.

    What this means for research administration teams

    For research administration offices, the U01-versus-R01 distinction changes pre-award workload, not just post-award reporting. U01 applications typically demand earlier engagement with NIH programme staff, detailed (non-modular) budget justification regardless of award size, and internal processes for tracking milestone-contingent continuation funding — all of which should be flagged to investigators well before a targeted RFA deadline.

    Sponsored-programmes teams that treat a U01 like a slightly larger R01 risk under-scoping the administrative burden: cooperative agreements typically require more frequent NIH check-ins, closer subaward coordination on multi-site awards, and budget justifications that a modular R01 submission would never need.

    The bottom line

    Choosing between a U01 and an R01 is ultimately a governance decision as much as a funding one. Investigators who need full scientific autonomy over an independently conceived project should target an R01; those whose work depends on NIH coordination — multi-site trials, shared infrastructure, consortia — should expect, and plan for, a U01’s cooperative-agreement structure. Reading the specific FOA, not the activity code alone, remains the only reliable way to confirm which governance model applies to a given opportunity.

  • 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.