The fastest way to understand eRA Commons is to follow one NIH grant through the system. An application starts in a wider federal portal, lands in eRA Commons for review and award management, and stays there for progress reports, no-cost extensions, and closeout. Researchers who check only their email can miss deadlines that live inside the portal.
The system is operated by the National Institutes of Health's Office of Extramural Research. It gives grant applicants, signing officials, principal investigators, and NIH staff a single record for each application and award. It does not replace Grants.gov; it receives what Grants.gov sends and becomes the NIH-specific workspace.
For any researcher named on an NIH application, an eRA Commons account is required infrastructure, not an optional extra. That includes principal investigators, co-investigators, postdoctoral fellows, graduate students on training grants, and lab staff who help with reporting.
Who Uses the Portal, and What It Actually Does
Principal investigators use eRA Commons to check application status, read priority scores and summary statements, and submit progress reports. Signing officials at research institutions use it to submit institutional portions of applications, request no-cost extensions, and manage user accounts. Trainees and fellows use the xTrain module for appointment forms and termination notices.
Administrative assistants and lab managers can be set up as delegates with limited access to specific tasks. The Commons also carries several institutional roles: signing official, administrative official, and financial conflict of interest roles, among others. Each role has separate permissions, and submitting under the wrong role can delay an action.
What the system does not do is write or format the science. Application preparation still happens in a lab's own document workflows, and initial submission goes through Grants.gov or NIH's ASSIST submission system. Once the application reaches NIH, the Commons becomes the source of record.
A Typical Timeline From Submission to Award
The status screen reads as a sequence. When an application is first submitted through Grants.gov and processed by NIH, the PI sees a status indicating that the application has been received. That line changes as the application moves into peer review and then to the NIH council that considers the application.
After review, the priority score appears in the Commons. The summary statement, which contains the reviewers' written critique, usually is posted in the portal before it reaches the inbox through a grants office. A PI who checks the Commons directly can read those assessments earlier.
If the application is likely to be funded, a Just-in-Time request appears. Council review follows, then the Notice of Award, and finally the award account becomes active. Each step is reflected as a status update in the portal. For first-time applicants, learning to read that status screen matters more than memorizing grant terminology.
Setting Up an Account, Step by Step
Individual researchers cannot sign themselves up for eRA Commons. The institution must first complete its own chain of registrations. That chain starts with a Unique Entity Identifier from SAM.gov, continues through an active SAM registration and a Grants.gov registration, and ends with an institutional eRA Commons registration. The institution's signing official then creates accounts for people who need them.
NIH's eRA help documentation describes the sequence for researchers: contact your office of sponsored research or grants administrator, ask to be added in eRA Commons, receive a temporary invitation or password, and then sign in through eRA Commons online help to complete your profile. Since September 2021, sign-in requires a Login.gov account with two-factor authentication. A researcher with an old Commons username and password must still link that account to Login.gov to get past the front door.
After the first login, fill in the public profile immediately: name, degrees, employment, and contact details. The profile connects to NCBI's My Bibliography for publication tracking, and it accepts an ORCID iD. Keeping that profile current prevents bad data from creeping into a biosketch or progress report.
Core Tasks Researchers Do in eRA Commons
Tracking application status. After an application is submitted, the PI can see status changes in the Commons. The record moves from received through peer review, council review, and eventually to award or not funded. The priority score and summary statement are posted in the portal when available. Checking the Commons directly is faster than waiting for an email, especially for PIs who submit through a central office.
Just-in-Time information. NIH sends Just-in-Time requests only to applications that are likely to be funded. The PI then uploads other support, certification of IRB or IACUC approval, and training-related documents in response. Submitting before the JIT request is unnecessary and can clutter the record.
Research Performance Progress Reports. Annual RPPRs, interim RPPRs, and final RPPRs are submitted through the Commons. The PI or a delegate fills in sections; the signing official submits. NIH's RPPR page describes the required sections and deadlines. A delayed progress report holds up non-competing continuation funding.
No-cost extensions and prior approval requests. Many no-cost extensions are initiated in the Commons by the PI and submitted by the institution. This is also where some prior approval requests go, depending on the grant mechanism. The exact route varies by award, so checking the Notice of Award terms is the first move.
xTrain for training grants. On institutional training awards such as T32s, appointment forms and termination notices for trainees are processed through the xTrain module. Graduate students and postdoctoral fellows on those grants may need their own accounts to submit forms on time.
Common Compliance Tasks After Funding
Funding does not end the Commons work. Publications arising from the award are managed through My NCBI's My Bibliography, linked to the eRA Commons profile. That is how NIH tracks compliance with its Public Access Policy, and a final RPPR can be delayed if publications are not linked and compliant.
Institutional officials use the Commons to verify that human subjects and animal welfare approvals are current, and to submit the invention statements and closeout documents that finish an award. A researcher who treats the Commons as a pre-award-only tool will run into exactly these post-award deadlines.
Recent Changes and Why They Matter
The sharpest change in daily use is the Login.gov requirement, which brought two-factor authentication to every Commons session. In practice, that means a researcher needs a phone or authenticator available, and old shared-lab Commons credentials no longer match how NIH handles access.
On the institutional side, DUNS numbers stopped being the identifier for federal awards. Since April 2022, the government uses the Unique Entity Identifier from SAM.gov. Institutions that have not updated their profiles can stall a new Commons registration or an award setup.
NIH has also kept the Commons tied to other research infrastructure: ORCID iDs and My Bibliography are visible from the profile, and the data feeds into SciENcv for biosketches. That means a poorly maintained Commons profile can show up in grant application documents, not just in administrative screens.
Practical Advice for First-Time Researchers
- Apply for an eRA Commons account the day you start on a grant application, not when an R01 is due. Institution offices can take several days to process account requests, especially in high-volume weeks in late December and late January.
- Set up Login.gov and two-factor authentication before you travel. Some NIH systems require a second factor for every session, and replacing a lost device while a progress report is due creates avoidable stress.
- Link ORCID and My Bibliography immediately. This saves duplicate data entry and keeps your publication list aligned with NIH systems on future applications.
- Use a delegate account for lab staff who need to upload documents but should not have full PI-level access. Delegates can be given permissions for specific modules.
- Read the eRA Commons status screen more than your inbox around deadline weeks. The status screen is the authoritative record when an application has moved to review, when a summary statement is posted, and when a no-cost extension is approved.
Most errors in eRA Commons are not technical failures; they are role problems and timing problems. A signing official submitting under the wrong role, a delegate without permission, a JIT response sent before the request, or a progress report missing publication links are the common patterns. Fixing those early means less urgency later.
Photo by Brett Jordan on Unsplash