Build a federal grant source register another reviewer can use

A consultant handing an application to a colleague needs more than a folder called “final.” The next person needs to know which notice, attachments and instructions informed the work, where those files came from and which questions remain open. A short source register makes that handoff inspectable.

The register described here is a suggested working method, not an agency form or a determination that the application has every required document. Adapt it to the opportunity and your organization's records practices.

Separate discovery from the source set

Start with the opportunity number and official page. Grants.gov's opportunity-page guidance distinguishes the synopsis or forecast, version history, related documents and application package. Treat each area as a place to inspect. A synopsis copied into a spreadsheet does not stand in for the documents it describes.

For NIH opportunities specifically, NIH's download guidance 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. Record the announcement you actually downloaded; a search result alone does not identify your working copy.

Give each file a stable identity

Use one row per source, including a separate row for an amendment or incorporated guide. A compact register can contain these fields:

• Source ID: a short local label, such as S01, that stays attached to the same source.
• Document role: main notice, application guide, attachment, amendment or another stated role.
• Official location: the page or document URL from which you obtained the file.
• Local copy: the exact filename and its location in the shared project folder.
• Issued or revised date: the date printed or stated by the agency, or “not stated.”
• Retrieved date: when you downloaded this copy.
• Review state: unread, under review, reviewed for this working version or needs recheck.
• Open point: a missing item, unclear relationship or question, with an owner.

Keep the agency's date and your retrieval date separate. Downloading a document today does not make it a new agency revision. Likewise, two downloads with the same filename may contain different text.

Record relationships without guessing precedence

Some material replaces an earlier file; other material adds instructions alongside it. Put the agency's stated relationship in the register, with a locator to the statement. If the relationship is unclear, retain both sources and write down the question. Do not assume that the newest timestamp automatically resolves a conflict.

For a linked guide, capture the applicable edition if it is stated. If the notice refers to a section you cannot locate, keep an unresolved entry rather than checking the source off because a similarly titled PDF exists.

Make the handoff reproducible

Here is an illustrative register note, not a real opportunity instruction:

S03 is an addendum downloaded from the official page. Its heading identifies it as an addition to S01. The budget worksheet mentioned in section 2 has not been located. Jordan will check the official documents and record the result before budget review.

This note identifies the evidence, what is unknown and the next action. It does not turn a missing worksheet into an assumption that no worksheet is required.

Before handoff, ask the receiving reviewer to open one cited file from the register and locate one referenced instruction. Fix ambiguous filenames, unavailable folder permissions and mismatched page labels while the original reviewer is still available.

Preserve the working set

Keep the register with the original files and the exported checklist that used them. Label the set with the opportunity number and your working revision. When a source changes, preserve the earlier set and mark affected work for recheck.

A saved NOFO Workspace project can retain imported text and notes, but it does not replace the original PDF or automatically collect linked documents. Save those originals in your own project folder. The useful outcome is a handoff another reviewer can follow, including the gaps they still need to resolve.