A practical workflow · NonProfit Radar
How to compare a NOFO amendment without losing your working notes
A revision can change the meaning of a task even when its sentence stays the same. Preserve both source versions, review the effects and record which decisions you have checked again.
Published and sources checked . Agency instructions govern your application.
1. Follow the specific opportunity’s updates
Start at the official opportunity, using its number to confirm that you have the correct program and cycle. Record where amendments appear and who will check them. A copy in a shared folder can remain unchanged while the agency’s source moves on.
Grants.gov makes an important distinction: saved-search subscriptions do not notify you about opportunity-package changes, such as modified application forms. A subscription to a selected opportunity includes packages being added, modified or deleted. These official subscriptions require a Grants.gov account. Choose the relevant Grants.gov subscription.
Use alerts as a prompt to revisit the official documents. They are not a substitute for opening the current source before submission. Save the agency’s amendment or change notice alongside the revised announcement; it may explain what changed and which applicants or dates it affects.
2. Preserve a readable baseline before replacing anything
Save the existing source files, current checklist, task notes and any earlier comparison. Identify this set as the version you worked from. A useful folder name includes the opportunity number and retrieval date; the source inventory should also preserve any revision date actually printed by the agency.
Download the new material from the official source into a separate version folder. Record the URL, filename, revision label, retrieval date and the amendment’s stated scope. If two downloads have the same filename, that alone tells you nothing about whether their contents match. Keep both until you have compared them.
Check that you are comparing the same document’s revisions. A general application guide and a program-specific notice are different sources, even if they contain similar headings. Likewise, an addendum may supplement a notice instead of replacing it. Follow the agency’s statement of what the new document changes.
3. Compare the effect on your application
A text comparison can point to passages worth reading. It cannot decide whether a change matters to your organization. Work through changed passages in the original layout and trace each one to your tasks, attachments, budget assumptions and unanswered questions.
| What you observe | What to check next |
|---|---|
| An instruction was added | Identify who it applies to, any exception, the required evidence and a new owner or task. |
| A passage disappeared | Check whether it moved or is still imposed by another governing source before removing the task. |
| A definition or condition changed | Revisit every decision that used it, including items whose own wording stayed the same. |
| A date, limit or form changed | Read the full label and context. Recheck the relevant stage, time zone, attachments and dependencies. |
| Only layout seems different | Compare the original pages. New line breaks or extraction order can look like substantive edits. |
Recheck cross-references, table headings and neighboring paragraphs. For example, a revised definition of “eligible project” can affect an unchanged narrative task. A requirement disappearing from a suggestions list may reflect extraction differences; verify the original source before concluding that the agency removed it.
4. Keep the old evidence and the new decision together
Give each material change a log entry. Record the old source and locator, new source and locator, exact excerpts, affected checklist items and your decision. Add who reviewed it and when. Separate what the agency changed from what you changed in your plan.
Illustrative example: a later deadline
Suppose a fictional amendment moves the final submission deadline but says nothing about a separate registration step. Record the new final deadline and its source. Keep the registration question open until you check its governing instruction. Do not shift every date merely because one deadline moved.
This example is a planning scenario, not an announcement or agency rule.
A useful status is “needs recheck” until the new evidence supports a decision. If an item remains applicable, preserve its owner and useful notes while recording the new review. If it becomes inapplicable, retain the reason and old evidence in the change log instead of erasing the history.
5. Update working files, assignments and calendars deliberately
When using NOFO Workspace, save the current project before changing sources. Replace a source for a revision of that document; add a separate source for an additional document. Both operations reset review states across the project so earlier checks need attention against the changed source set.
Source replacement compares excerpts and retains task notes for unchanged items when they match unambiguously. Download the separate amendment comparison to preserve the previous source and removed notes. The regular project download contains the current version. Save both before replacing another source or leaving the workspace.
After reviewing the effects, update owners, dependencies and internal planning dates. Reissue exports with a clear version label. An exported checklist or previously imported calendar event does not update itself. Check your calendar for obsolete entries before importing revised planning tasks; a second import may leave both versions visible.
6. Check the current application package before submission
Revisit the official package and forms as well as the announcement. Grants.gov says that applicants must use updated forms when a grantor modifies them; its application workspace alerts users to form updates. Read Grants.gov’s form-update guidance. A revised task list alone does not update an official application package.
Finish the change review with a short handoff: which source version is current, which tasks changed, who owns them, what remains unresolved and when someone will recheck the official source. Keep superseded exports recognizable so a teammate does not continue from an old checklist.
If you already submitted, read the specific agency instructions for the amendment and any correction or resubmission process. Ask the designated agency contact when those instructions do not resolve your situation. An amendment does not, by itself, establish permission to submit again or extend every related deadline.