# Grants.gov vs. NIH eRA Commons Grants.gov is the government-wide portal where you find federal funding opportunities and submit applications, while NIH eRA Commons is the National Institutes of Health's internal system where registered institutions and investigators track, correct, and administer applications after they reach NIH. A quick rule of thumb: you use Grants.gov to discover an opportunity and get your application in the door, and you use eRA Commons to confirm NIH received it, fix compliance errors, and manage the award afterward. If you are applying to NIH, you will almost always touch both systems. If you are applying to another federal agency, Grants.gov may be your only stop. This guide explains the difference between Grants.gov and eRA Commons in plain language, compares them side by side, walks through how they cooperate on a real NIH application, and covers the planning habits and common mistakes that separate smooth submissions from rejected ones. ## Why Two Systems Exist Federal grant-making involves two distinct jobs. The first job is intake at the government-wide level. Grants.gov was built as a single storefront for every federal grant-making agency, so a researcher at a small college can search for opportunities from NIH, NSF, the Department of Energy, and dozens of other agencies in one place, and can submit an application through one standard process rather than learning a separate portal for each agency. The second job is agency-level administration. Once an application leaves Grants.gov and arrives at NIH, NIH needs its own systems to verify investigator credentials, route the application through peer review, track the status through the review and award cycle, and manage post-award actions such as name changes, extensions, and reporting. That is eRA Commons. The electronic submission and review world has been steadily digital for years, and reviewers of the modern regulatory and grant ecosystem have argued that these transactional systems still lag behind what modern cloud technology could deliver, which is one reason agencies continue to redesign them [1]. A useful analogy comes from manuscript publishing. Submitting to a journal typically means one portal for submission and a second internal workflow where editors assign reviewers and track decisions. Grant submission works the same way. Grants.gov is the front door. eRA Commons is NIH's back office. ## What Grants.gov Is Grants.gov is managed by the U.S. Department of Health and Human Services on behalf of the entire federal government. Its core functions are search, eligibility checks, and application intake. On Grants.gov you can: 1. Search funding opportunity announcements (FOAs) across all federal agencies using keywords, eligibility type, and funding category. 2. Download the application package associated with a specific FOA, which contains the required forms such as the SF-424 family of forms. 3. Complete and submit that package through Grants.gov Workspace, either as an individual applicant working with your institution's authorized representative or through a team workspace with role-based access. 4. Receive submission confirmations and tracking numbers that prove your application entered the federal system before the deadline. Two registration requirements matter for Grants.gov. Your institution needs a Unique Entity Identifier (UEI) issued through SAM.gov, the federal System for Award Management, and it needs an active SAM.gov registration. These are institution-level registrations. Your individual Grants.gov account, by contrast, is often tied to your institution through a linked account, and the person who actually submits is the Authorized Organization Representative (AOR), not necessarily the principal investigator. Grants.gov does not review your science. It validates the application package for completeness and format and passes it along to the receiving agency. ## What NIH eRA Commons Is NIH eRA Commons is an online interface where NIH interacts with applicants and grantees throughout the life of an application and award. It is administered by NIH's Office of Extramural Research through its eRA (electronic Research Administration) program. Key functions of eRA Commons include: 1. Issuing eRA Commons usernames to individuals. Every principal investigator on an NIH application must hold an active eRA Commons ID, and that ID must be listed in the application credentials section before submission. 2. Housing the Signing Official (SO) and Authorized Organization Representative (AOR) roles, which are institutional officials empowered to submit applications to NIH and conduct official business. 3. Tracking application status. After Grants.gov intake, NIH assigns each application a number, checks it against the funding opportunity's requirements, and posts assembled application images and status updates in eRA Commons. 4. Supporting Just-in-Time (JIT) information requests, where NIH asks for certifications and other materials after peer review but before award. 5. Managing post-award actions, including No-Cost Extensions requested by the grantee and annual progress reports submitted through the Research Performance Progress Report (RPPR) module. 6. Providing tools such as xTRACT for preparing training data tables and the Internet Assisted Review (IAR) site where reviewers handle assigned applications. One structural detail causes frequent confusion. eRA Commons is not open for self-registration by individuals. An institution must first be registered in eRA Commons, and then an institutional administrator (the Signing Official or an Accounts Administrator) creates the individual account. If you are at a new or very small organization, this registration chain has to be complete before your application can be submitted and processed. ## Grants.gov vs. NIH eRA Commons: Side-by-Side Comparison | Feature | Grants.gov | NIH eRA Commons | |--|--|--| | Who runs it | HHS on behalf of the federal government | NIH Office of Extramural Research | | Scope | All federal grant-making agencies | NIH only | | Main job | Opportunity search and application intake | Application tracking, compliance checking, award administration | | Who registers | Institutions (SAM.gov and UEI) and individuals (linked accounts) | Institutions first, then individual investigators created by institutional administrators | | What you submit through it | The complete application package (SF-424 forms) | Nothing directly for most new applications. You track, view, correct, and administer | | What you see | Confirmation your application was received by the federal system | NIH-assigned application number, assembled image, status, review outcomes, award data | | Used by | Applicants to any federal agency, at any career stage | NIH investigators, Signing Officials, admins, and peer reviewers | | Common entry point | Searching FOAs and downloading packages | Creating an eRA Commons ID and checking status after submission | | Failure mode | Rejection for late or incomplete submission | Application cannot be processed because the PI lacks an ID or forms are missing | ## How the Two Systems Work Together on an NIH Application A typical NIH R01 sequence shows exactly where each system belongs. Here is the flow from idea to award. 1. **Find the opportunity.** You locate the FOA on NIH's site or through a Grants.gov search. The FOA lists the due dates and points back to the NIH Guide notice. 2. **Prepare and plan.** Grant proposal planning starts months ahead of the deadline. Well-run laboratories set internal due dates weeks before the agency deadline because assembling a competitive application involves multiple documents, approvals, and routing steps. Reviews of regulatory and submission processes across biomedical contexts consistently show that applications succeed or fail on preparation discipline as much as on content [2]. 3. **Register everyone.** Your institution confirms its SAM.gov registration and UEI. You obtain your eRA Commons ID from your institutional administrator. The AOR confirms authority to submit on behalf of your organization. 4. **Assemble the application.** Most institutions assemble NIH applications in ASSIST (the Application Submission System and Interface for Submission Tracking), NIH's own preparation tool, or in the institution's system-to-system software, rather than in Grants.gov Workspace. ASSIST is linked to your eRA Commons credentials and can validate against NIH-specific requirements. 5. **Submit through Grants.gov.** The AOR submits, Grants.gov validates the package, and then NIH pulls the application in and runs its own compliance checks. 6. **Verify in eRA Commons.** Within a few business days, the application appears in the PI's and AOR's eRA Commons status screen with an NIH application number. This is the moment to check the assembled image and the error/warning list. Warnings do not stop processing. Errors do. 7. **Peer review happens.** Applications that pass compliance move to scientific review groups. Peer review is the mechanism the research community relies on to judge merit, and guidance on navigating review successfully emphasizes understanding the process itself, not just producing good science [3]. Practical advice on surviving review, such as responding precisely to reviewer concerns and respecting the reviewer's role, transfers directly from manuscript review to grant review. Review communities have also developed codes of practice covering reviewers, editors, and authors, and the same principles of preparation and professional conduct apply to study section service [4]. 8. **Council and award.** After review and advisory council placement, NIH issues the summary statement (the "pink sheet") in eRA Commons, handles Just-in-Time requests there, and the AOR accepts the notice of award through the Commons. 9. **Administer the award.** Progress reports, No-Cost Extensions, and prior-approval requests flow through eRA Commons for the life of the grant. The dividing line is clean. Grants.gov hands the application from you to NIH. eRA Commons hands information back to you and manages everything after. ## When to Use Grants.gov ![Decision path asking whether you are submitting or administering, leading to Grants.gov for intake and eRA Commons for NIH tracking and awards.](/article-images/illustrations/grants-gov-vs-era-commons-which-system-task.webp) Use Grants.gov when you are doing any of the following: 1. **Searching broadly.** You want to see federal opportunities across agencies, not just NIH. Grants.gov search is the fastest way to scan the whole federal portfolio for your topic and eligibility category. 2. **Checking eligibility.** FOAs list eligible applicant types. If you are at a small nonprofit, a tribal organization, or an independent hospital, Grants.gov search plus the eligibility filters quickly shows which opportunities you can pursue. 3. **Applying to a non-NIH agency.** If your opportunity is from NSF, USDA, DOE, or another agency that uses Grants.gov for intake, this is your submission route. Each agency then handles review and administration in its own systems. 4. **Submitting as an individual applicant where permitted.** Some opportunities allow individuals to apply directly, and Grants.gov supports those registrations. 5. **Needing proof of on-time submission.** The Grants.gov tracking number and timestamp are the official record that your application entered the system before the deadline. When deciding between grants.gov or era commons for a given task, ask one question. Am I submitting, or am I administering? Submission intake lives on Grants.gov. Administration lives at the agency, which for NIH means eRA Commons. ## When to Use NIH eRA Commons Use eRA Commons when you are doing any of the following: 1. **Getting your investigator ID.** Anyone listed as a senior or key person on an NIH application needs an eRA Commons ID. Start this before you draft anything, because a missing ID at submission causes processing problems. 2. **Tracking status.** After submission, the Commons is where you confirm NIH received the application, view the assembled image, and follow status changes from "received" through "reviewed" and beyond. 3. **Responding to NIH requests.** Just-in-Time requests, other support questions, and certain compliance items arrive as Commons notifications that route to your AOR and inbox. 4. **Handling post-award business.** The RPPR, No-Cost Extension requests, and grantee-side prior approvals are managed through Commons modules. 5. **Reviewing as a peer reviewer.** If NIH appoints you to a study section, you receive and score assigned applications through the Internet Assisted Review module within eRA Commons. 6. **Acting as an institutional official.** Signing Officials and AORs use the Commons to submit, view, and manage every application and award belonging to their institution. ## Grant Proposal Planning Around Both Systems ![Timeline of grant preparation from twelve to sixteen weeks out through the days after submission, with registration and ID checks early.](/article-images/illustrations/grants-gov-vs-era-commons-planning-calendar.webp) Because the two systems have separate registrations, validations, and lead times, your planning calendar should treat them as parallel tracks. Strong grant proposal planning looks like this: 1. **Twelve to sixteen weeks before the deadline:** Identify the FOA, confirm eligibility, and check that your institution has current SAM.gov and eRA Commons registrations. New institutional registrations can take weeks. 2. **Eight to twelve weeks before:** Secure your eRA Commons ID if you do not have one. Confirm the AOR knows the submission is coming and agree on an internal deadline. 3. **Four to eight weeks before:** Draft the science, budget, and administrative components. If your project involves human participants, begin IRB preparation in parallel. IRB review is a separate institutional process with its own documents and timelines, and guidance for new researchers emphasizes starting early and working through the required steps methodically [5]. The same advice recurs across research settings. Start the submission early, be patient, and identify what can be expedited [6]. Practical IRB guidance divides the work into planning before drafting documents, care while drafting, and follow-up after submission, a structure that maps neatly onto grant preparation [7]. 4. **One to two weeks before:** Complete internal routing and approvals, run validations in ASSIST or Grants.gov, and plan to submit several days ahead of the deadline. 5. **Within days of submission:** Check Grants.gov confirmation, then check eRA Commons for the assembled image and any errors. If you are building these habits as part of a research [grant writing](/knowledge/molecular-biology/grant-writing) course or a formal training program, note that most courses teach the science of the application but leave systems logistics to mentors and research administrators. Budgeting time for the two portals is a logistics habit you have to build deliberately, because no amount of scientific quality rescues an application rejected for late or incomplete submission. ## Common Mix-Ups Between the Two Systems The difference between Grants.gov and eRA Commons generates a predictable set of errors. Here are the ones that matter most. 1. **Treating Grants.gov as NIH's portal.** Grants.gov is shared infrastructure for the whole government. It knows nothing about NIH-specific requirements such as the eRA Commons ID or NIH-specific attachments. NIH runs those checks after intake. 2. **Assuming a Grants.gov confirmation means NIH accepted the application.** Grants.gov confirmation only proves federal intake. The application still has to clear NIH compliance checks, which you verify in eRA Commons. A warning or error posted in the Commons needs action even though Grants.gov said your submission was fine. 3. **Trying to self-register in eRA Commons.** Individuals cannot create their own accounts. The institutional administrator creates them. Asking the AOR or department administrator early avoids a scramble. 4. **Confusing ASSIST with Grants.gov Workspace.** ASSIST is NIH's application preparation system. Grants.gov Workspace is the generic federal tool. Both can produce a submittable package, but ASSIST integrates NIH-specific validation, which is why most institutions assembling NIH applications use ASSIST or system-to-system software. 5. **Submitting on the deadline day.** NIH postmark deadlines are real, and the days before them are when both systems see peak traffic. Applications submitted late are rejected, and a rejected application cannot simply be re-stamped as on time. 6. **Looking for review outcomes in Grants.gov.** Summary statements, scores, and council outcomes appear only in eRA Commons. Grants.gov is done with your application once it is delivered. 7. **Forgetting that IRB approval is separate from both systems.** Grant submission and IRB approval are parallel tracks, not sequential ones in all cases. For applications involving human subjects research, IRB approval is a prerequisite that the institution manages directly, and starting the IRB process early is the single most repeated recommendation in IRB guidance [7]. ## Worked Scenarios ### Scenario 1. A first-time postdoc applying for an NIH fellowship A postdoc at a university plans an F31 fellowship application. Her mentor has an eRA Commons ID. She does not. Her first step, eight weeks before the deadline, is emailing her department administrator to request an eRA Commons account, which the institutional Signing Official creates. She drafts the application with her mentor, the administrator assembles it in ASSIST under the correct FOA, and the AOR submits through Grants.gov two days early. Three days later she logs into eRA Commons, sees her application number, and confirms every component, including her own eRA Commons ID in the credentials, appears in the assembled image. Her Grants.gov job was essentially to exist as a form component. Her eRA Commons job begins the moment NIH receives the application. ### Scenario 2. A researcher at a small nonprofit applying to a non-NIH agency A program director at a small conservation nonprofit finds a Department of Energy opportunity through a Grants.gov search. His organization has an active SAM.gov registration, so no NIH involvement exists at all. He downloads the package into Grants.gov Workspace, invites colleagues to complete forms, and his AOR submits. Because the opportunity is not NIH, eRA Commons never enters the picture. If a reviewer later asks about human or animal subjects, his institution handles the ethical review directly, since separate ethical approval processes govern research that involves human participants regardless of the funder [5]. ### Scenario 3. An international institution applying for a Fogarty grant A researcher at an institution outside the United States is named on an NIH application led by a U.S. university. The U.S. institution holds the registration and submits through Grants.gov. The international collaborator still needs an eRA Commons ID, which the U.S. applicant institution can arrange for foreign component key personnel. The collaborator tracks her part of the application through her own Commons login even though her institution never touched Grants.gov directly. This split, where one institution submits and multiple institutions track, is one of the clearest illustrations of the difference between Grants.gov and eRA Commons. ### Scenario 4. A department administrator handling a rejected submission An application arrives at Grants.gov before the deadline but fails NIH compliance checks in eRA Commons because a required attachment is missing. The administrator sees the error notification in the Commons, corrects the application, and resubmits within the correction window NIH allows after the deadline for fixable errors. The Grants.gov submission timestamp preserved the application's eligibility. The eRA Commons error list is what made the fix possible. Neither system alone could have resolved the situation. ## Common Mistakes and Limitations 1. **Starting registrations too late.** SAM.gov registration, UEI issuance, and eRA Commons account creation each have their own processing timelines. Every one of them can be started the day you decide to apply, at zero cost in scientific effort. 2. **Assuming the AOR and PI are the same person.** The AOR is an institutional official with authority to commit the organization. PIs draft and verify. AORs submit. Confusing the two roles delays routing and creates deadline risk. 3. **Skipping the assembled image check.** The assembled image in eRA Commons is what reviewers will see. Errors stop the application. Warnings may indicate problems a reviewer will notice. Checking the image is a five-minute task that prevents avoidable rejections. 4. **Equating submission readiness with scientific readiness.** A technically valid submission can still receive an unfavorable review. Review quality depends on preparation, clarity, and the fit between the application and the opportunity, and the discipline that good reviewers and editors apply in manuscript review applies in grant review as well. Manuscript submission guidance similarly stresses aligning content with the funder's or journal's scope and requirements before submission [8]. 5. **Planning only around the deadline, not the whole pipeline.** The application deadline is one milestone in a pipeline that includes review, council, Just-in-Time, and award. Planning backward from the deadline is necessary. Planning forward from the award start date is what keeps the project on schedule. 6. **Assuming both systems behave the same across agencies.** Grants.gov intake rules are shared. Everything after intake is agency-specific. An applicant moving from NIH to NSF must learn a new post-submission landscape, just as a researcher moving between regulatory jurisdictions encounters different review processes and timelines [2]. 7. **Individual limits.** Every institution administers these systems slightly differently. Your department administrator, research office, and AOR are the authoritative source for internal deadlines and routing requirements. When a specific application raises questions about eligibility, human subjects oversight, or institutional policy, resolve them with your research office rather than assuming the general rule applies. ## Frequently Asked Questions ### Do I need both Grants.gov and eRA Commons to apply for NIH funding? Yes, in nearly every case. The application is submitted through Grants.gov (usually via ASSIST), and NIH tracks and administers it in eRA Commons. You also need an eRA Commons ID listed in the application before submission. ### Can I submit my NIH application directly in eRA Commons? No. New applications are submitted through Grants.gov or, for many institutions, through NIH's ASSIST tool, which itself delivers the application through the federal intake process. eRA Commons is for tracking, corrections, and administration. ### What is the difference between Grants.gov and eRA Commons in one sentence? Grants.gov is the government-wide front door for finding and submitting federal grant applications, and eRA Commons is NIH's internal system for tracking, reviewing, and administering those applications after they arrive. ### Which system do I use for non-NIH federal agencies? Grants.gov. Other agencies use Grants.gov or their own submission systems for intake and have their own administration tools, so eRA Commons is irrelevant outside NIH. ### How long does eRA Commons registration take? There is no fixed published processing time that applies to every case, but account creation requires your institution to be registered first and requires action by an institutional administrator, so build in several weeks of buffer and never request the ID on deadline week. ### Where do I see my application's score and summary statement? In eRA Commons. Scores, critiques, summary statements, council outcomes, and notices of award all appear in the Commons status screens, never in Grants.gov. ## Sources 1. [Digital Innovation in Medicinal Product Regulatory Submission, Review, and Approvals to Create a Dynamic Regulatory Ecosystem-Are We Ready for a Revolution?](https://pubmed.ncbi.nlm.nih.gov/34109196/) 2. [Navigating Global Regulatory Frameworks: A Review of Submission Frameworks, Approvals and Timelines Across the FDA, EMA and MHRA](https://doi.org/10.22270/ijdra.v14i3.918) 3. [A Critical Assessment of the Peer Review Process in Life: From Submission to Final Decision](https://pubmed.ncbi.nlm.nih.gov/37511978/) 4. [Towards codes of practice for navigating the academic peer review process](https://doi.org/10.1016/j.erss.2022.102675) 5. [Navigating the Institutional Review Board Process.](https://pubmed.ncbi.nlm.nih.gov/35225497/) 6. [Navigating Institutional Review Boards.](https://pubmed.ncbi.nlm.nih.gov/38388120/) 7. [Institutional Review Board Insights: Tips for Submission to the Institutional Review Board.](https://pubmed.ncbi.nlm.nih.gov/40840914/) 8. [Navigating the Publication Process: Recommendations for Submitting a Manuscript to Rural Special Education Quarterly](https://doi.org/10.1177/87568705251355206)