How to review a federal NOFO and build a source-linked checklist

1. Collect the governing sources

A notice of funding opportunity (NOFO) is your starting document. Create a source inventory before making tasks: the official opportunity page, full announcement, attachments, amendments, referenced application guides and the relevant application package. Give each source a short name so your notes can refer to it consistently.

Grants.gov separates opportunity information into a synopsis or forecast, version history, related documents and package information. Follow those document and package links instead of treating a directory summary as the application instructions. See Grants.gov’s opportunity-page guidance.

Record the opportunity number, official URL, downloaded filename, visible revision date and the date you retrieved it. If a revision date is absent, write “not stated.” A retrieval date describes your copy; it does not prove that the agency issued a new version that day. Keep the original files together with your checklist.

For an agency-specific example, NIH directs applicants to the full announcement in the Documents section, to select the latest update when several versions appear, and to check again before applying. NIH’s download instructions are a useful reminder to verify the actual announcement, not just a search result.

2. Build a requirement record, then write the task

Read the sources in full. For each instruction that may affect your application, keep the evidence separate from your interpretation. A short task such as “get letters” is useful only if you can recover whose letters, what they must contain and any limits.

Exact evidence

Copy enough of the instruction to include its subject, condition, limit and exception. Keep the original wording.

Source locator

Record the source version, PDF page and printed section or attachment. Add imported-text line numbers separately if you use them.

Applicability

Write why it applies, why it does not, or what still needs an answer. An unanswered question stays unresolved.

Next action

Describe the work, its owner, your planning date and the evidence that will show the action is finished.

Use review areas as prompts: applicant eligibility, project scope, dates, budget and cost sharing, attachments, format limits, submission steps and review criteria. Your notice may add others. A scoring criterion deserves a writing or evidence plan; it is not automatically a mandatory attachment. Keep those types distinct in your notes.

3. Keep the condition and exception beside the instruction

Look for words such as “if,” “unless,” “only,” “except,” “must” and “may.” Do not stop the excerpt at the first sentence if the next sentence narrows it. A required attachment for one applicant can be unnecessary for another. Preserve that distinction before assigning work.

If the documents appear to conflict, keep both excerpts and their versions. Record the question and consult the designated agency contact or published clarification. Do not silently resolve the conflict by choosing the shorter or more convenient instruction.

4. Check the original page, especially tables

Extracted text is a reading aid. A table row can lose its column heading; a bullet can lose the sentence that introduces the list; a condition can continue on the next page. Open the original PDF and check those relationships before treating an excerpt as a task.

For a table requirement, record the row label and the relevant column heading along with the value. Distinguish mandatory limits from suggested lengths. PDF page numbers may differ from printed page numbers, so label both. Never call an imported line number an original page number.

If a scan has no usable text, keep reading the source and make checked manual notes. If you use software suggestions, compare them with the whole source and add omitted items. A short list, or a list where every suggested item is checked, does not establish that you captured every requirement.

5. Turn reviewed evidence into assigned work

Give each applicable item an owner and a concrete next action. “Confirm partner letter names the project and signatory” is easier to hand off than “letters.” Record a location for the finished attachment or decision evidence so review does not depend on someone’s memory.

Copy the official deadline’s date, time, time zone and source into a separate record. Then choose internal planning dates for drafting, review and submission. Do not infer a time zone from your computer settings or turn an ambiguous date into a confirmed deadline. Keep different application stages separate when the notice specifies them.

In NOFO Workspace, calendar exports use the planning dates you enter as all-day tasks. They do not capture an official submission time or synchronize after you edit the project. Save your project file as you work; a browser session is not your filing system.

6. Review the source set and the actual submission

Before handing off, revisit the inventory: is there a newer notice, an amendment, a linked guide you have not read or a changed form? For each item, distinguish “source reviewed” from “action completed.” Retain unresolved questions with a named next step instead of converting uncertainty into a check mark.

Keep submission evidence separately from your planning checklist. Grants.gov’s “Received” status means the application is awaiting validation; “Validated” makes it available for the agency to download. Grants.gov also instructs applicants to download the submitted package and verify its contents when the status permits it. Use the official status and download guidance.

Record the tracking number, observed status and saved package location, then follow the agency’s instructions for later tracking. Your checklist documents your review and work. The application still goes through the official submission process.