Grant Monitoring: How to Track New Grants and Application Updates

To track U.S. federal grants, use Grants.gov subscriptions to discover new or modified opportunities, subscribe to individual postings when you need to follow their revisions, and check application status after submission. A saved-search alert does not tell you when forms inside an opportunity package change. After an agency retrieves your application, Grants.gov stops providing status updates; use the awarding agency’s system. NIH applicants should check both Grants.gov and eRA Commons rather than relying on email alone.

This guide covers federal opportunities because the workflow below is based on Grants.gov and NIH guidance. State, local, foundation, and other non-federal funders may use different portals and alert systems. Follow the instructions in the current funding notice and the awarding agency’s portal for each application.

1. Choose the right kind of grant alert

Grants.gov offers three useful opportunity subscription types. You can use more than one, depending on whether you want broad discovery or updates about particular postings.

Subscription	Useful for	What to know
All new opportunities	Broad discovery across recently forecasted or posted opportunities.	Expect a broad set of messages; use saved searches if you need tighter criteria.
Saved searches	Alerts for opportunities matching your search criteria.	These alerts do not report changes to application forms inside an opportunity package.
Selected opportunities	Following a specific posting you may apply to.	Subscribe from that opportunity’s page to receive updates when the opportunity or its package changes.

Grants.gov describes its opportunity updates as a nightly email digest for posted or modified opportunities. The saved-search limitation matters: a matching-opportunity alert is not a package-form revision alert. For the subscription options and caveat, see Grants.gov Manage Subscriptions.

2. Build a useful saved search

Sign in to your Grants.gov account and open Search Grants.
Start with the applicant’s eligibility and funding mechanism, then narrow by topic, agency, opportunity status, and relevant dates. Grants.gov search offers keyword and facet filters; use only the filters that reflect your actual organization and program.
Review the results before saving. If the list is too broad, add criteria; if it is too narrow, remove a constraint that is not essential.
Save the search with a descriptive name, such as “Community health, eligible nonprofits” or “Agency name, research grants.”
Open Connect and Manage Subscriptions, then enable saved-search updates for the searches you want in the digest.
Periodically open View Results for each saved search. Confirm the results still match your program and adjust criteria if they have drifted.

Grants.gov’s help page explains how to create, edit, review, and delete saved searches: Subscribe to Saved Searches. Saved searches help discover matches; they do not replace reading the funding notice.

3. Treat forecasts as planning signals

A forecast describes a planned opportunity that does not yet have an official posted Funding Opportunity Announcement (FOA). Use it to begin planning, but do not treat it as a promise that the opportunity will open. Grants.gov says a forecast is not guaranteed to become an FOA. When the final notice appears, verify the eligibility rules, application package, required forms, deadline, and submission instructions before committing resources. See Grants.gov Forecast Tab help.

4. Follow a specific opportunity and its revisions

Open the View Grant Opportunity page for the posting you may pursue.
Subscribe to updates for that selected opportunity. This is the subscription intended to notify you when the specific opportunity or its package is updated.
Check the official page, version history, and package documents when an update arrives. Identify what changed and whether it affects eligibility, forms, attachments, instructions, or the deadline.
If you use Workspace, watch for its updated-form alert and confirm that the workspace contains the current forms before completing or submitting the application.
Record the version and date you reviewed. If the revision is consequential, assign an owner to confirm the team is working from the current package.

Outdated application forms can prevent successful submission. Grants.gov explains selected-opportunity subscriptions and package changes on its Manage Subscriptions page. This independent change log is a practical safeguard based on the documented update and form risks; it is not a required Grants.gov template.

5. Keep a small opportunity monitoring log

A shared spreadsheet or project record can make alerts actionable, especially when several people review the same opportunities. Track:

Opportunity number and official source page.
Current notice version and the date your team reviewed it.
Forecast, posted, modified, or closed status.
Eligibility decision and the person who verified it.
Deadline, including its stated time zone.
Required forms and attachments, plus any package revision to review.
Next action, owner, and due date.

Keep the official notice as the authority. The log is for coordination and should point back to the current source rather than reproduce instructions that may change.

6. Track an application after submission

Save the Grants.gov tracking number. A successful Workspace submission receives a system-generated number. Keep the confirmation PDF and record the number with the opportunity number, submission date, and applicant contacts.
Check status in Grants.gov. Sign in and open Check Application Status, or use Track My Application if you do not see the link. Search by the available criteria and date range. Access can depend on your organization role and whether you worked on the application.
Read the status and any errors. Grants.gov statuses distinguish stages such as waiting to be received, received and awaiting validation, validated, rejected with errors, received by the agency, and agency tracking number assigned. If rejected, read the errors, correct the application, and complete a successful resubmission under the applicable notice and deadline rules.
Download and verify the submitted package. Keep a copy and review the assembled documents so you can confirm what was submitted. Grants.gov describes downloading the application ZIP from Workspace when the application is in an eligible status.
Follow the agency handoff. “Agency Tracking Number Assigned” is the last status Grants.gov tracks. Once the agency retrieves the application, use the agency’s portal and internal number, if it provides one. The absence of an agency number does not itself mean the agency failed to receive or process the application.

See the official instructions for Check Application Status and Tracking Numbers and Notes.

7. NIH applicants: check Grants.gov and eRA Commons

NIH applications pass through Grants.gov and NIH’s eRA systems. Check Grants.gov for its submission and validation stages, then check eRA Commons for NIH-side status, errors, warnings, and the assembled application information available to your role. NIH guidance encourages proactive status checks; email is a notification channel, not a dependable substitute for checking the systems directly.

Keep the Grants.gov tracking number from the submission confirmation.
Sign in to eRA Commons and open the Status module. The view and available searches depend on your Commons role.
For a recent submission, review the pending or recent eSubmission status and inspect any errors or warnings.
Confirm that the assembled application and required information are correct during the applicable review window described by NIH and the funding notice.
Resolve actionable errors using current NIH and opportunity instructions. Warnings may not stop processing, but review them to decide whether they reveal a real issue.
After the application advances beyond submission processing, use the appropriate NIH or awarding-agency status area for later review and award progress.

Primary guidance: eRA Commons Status module, how signing officials check submission status, and status for principal investigators. NIH workflows and correction rules can depend on the opportunity and the submission circumstances, so use the current notice.

8. Troubleshooting common monitoring problems

Problem	Likely reason	What to do
No matching alerts arrive.	The saved search may be too restrictive, not subscribed, or producing no matches; messages may also be filtered by email settings.	Open Manage Subscriptions, verify the saved search is enabled, review its results, broaden criteria if appropriate, and check spam or mail rules.
A form changed, but no saved-search alert arrived.	Saved-search alerts cover matching opportunities, not changes to forms inside the package.	Subscribe to the specific opportunity and inspect its package and version history. Check Workspace for updated-form alerts.
A forecast disappears or never becomes a posted notice.	A forecast is a plan, not a guarantee that an FOA will be issued.	Keep it in a planning queue and wait for the official posted notice before treating requirements or dates as final.
Check Application Status is not visible.	Your Grants.gov role or access may not expose the page, or you may need the public tracking route.	Try Track My Application and confirm your organization role with the relevant administrator. Consult the Grants.gov status help page.
The application is rejected or has errors.	Validation or agency processing found an issue that blocks progress.	Read the specific errors in the portal, correct the application, and follow the notice’s current correction and resubmission rules. Do not assume a warning is harmless without reviewing it.
Grants.gov stops showing new progress.	The agency has retrieved the application; Grants.gov says its tracking ends at the agency handoff.	Check the awarding agency’s system and use its internal tracking number if provided. Lack of that number alone does not establish nonreceipt.
NIH email is missing or differs from the portal.	Messages may be delayed, filtered, or sent to contacts listed for the submission.	Check Grants.gov and eRA Commons directly, inspect contact details and junk folders, and contact the appropriate service desk if the portal indicates a problem.

9. Make monitoring reliable without creating alert fatigue

Use a small number of purpose-built saved searches instead of one broad keyword search for every program.
Assign someone to triage the digest and route relevant notices to program owners.
Keep selected-opportunity subscriptions for active applications and check the package after a revision notice.
Put deadlines in a shared calendar with the time zone and a separate internal review deadline.
Check portals directly at important milestones, especially near submission deadlines and during post-submission validation.
Store the tracking number, confirmation PDF, final submitted copy, and agency handoff details in an access-controlled project location.

The official services described here are online portals and email alerts; the reviewed sources do not establish a universal alert frequency beyond the Grants.gov nightly digest description. Do not interpret a lack of new email as proof that a notice, package, or application status has not changed.

Or skip the browser setup

If your grant workflow also needs clean screenshots of public opportunity pages or documentation, ScreenshotNeo is a website screenshot API and MCP server. The direct answer for grant alerts and application status remains Grants.gov and the awarding agency’s system; ScreenshotNeo captures web pages and does not replace those portals.

One GET request returns an image or PDF. See the ScreenshotNeo API documentation.

curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://www.grants.gov/ -o grants-page.webp

import requests

r = requests.get(
    "https://api.screenshotneo.com/v1/shot",
    params={"access_key": "YOUR_API_KEY", "url": "https://www.grants.gov/"},
    timeout=90,
)
r.raise_for_status()
open("grants-page.webp", "wb").write(r.content)

const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://www.grants.gov/' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);
if (!res.ok) throw new Error(`Screenshot request failed: ${res.status}`);
await import('node:fs/promises').then(fs => fs.writeFile('grants-page.webp', Buffer.from(await res.arrayBuffer())));

Cookie banners, newsletter popups, and chat widgets are removed before the shot.
Bot checks, blank pages, and failed loads are never billed.
An MCP server lets AI agents take screenshots.
1,000 screenshots a month are free with no card; paid plans start at $5 for 3,000.

Frequently asked questions

Can I monitor grants outside the federal government with Grants.gov?

This workflow is for U.S. federal opportunities listed through Grants.gov. State, local, foundation, and other funders may have separate portals, mailing lists, and status systems. Check each funder’s official instructions.

Does a saved search alert me when application forms change?

No. Grants.gov says saved-search updates do not notify you about modified forms inside an opportunity package. Follow the specific opportunity and review its package.

Does an agency tracking number mean the application was awarded?

No. It is an agency identifier, and “Agency Tracking Number Assigned” is a tracking stage. Use the awarding agency’s system for later review and award decisions.

Should I wait for an email before checking my status?

No. Check the official status portal directly, particularly for NIH submissions, where eRA Commons provides NIH-side status information.

Are forecast deadlines final?

No. Verify the final posted announcement and its current instructions, forms, eligibility, and deadline.