Build a grant audit trail that connects decisions, figures and source records. Preserve versions, test a budget amendment and identify missing evidence.
Build a grant audit trail by linking each material decision, transaction and reported result to its source, the responsible person and the relevant date or version. Preserve changes and approvals so another reviewer can reconstruct what happened. A folder of documents is useful evidence, but it is not a complete trail unless the relationships and decisions are also recorded.
By Sopact Academy · Reviewed September 12, 2026. This lesson combines cited public guidance with practical workflow recommendations. Figures and teaching scenarios are illustrative unless explicitly identified as a published case.
Grant Intelligence · Chapter 20 · Communicate
Bring: one grant’s agreement, amendments, financial support, reporting record and a decision from chapter 19.
Leave with: an evidence index and a reconstruction test. The example below is fictional; apply the requirements of your particular award and organization.
Start with the questions a reviewer must be able to answer: who approved the award, what terms applied, which changes were authorized, what was paid or spent, and how the reported results were checked.
The scope depends on your role. A grantmaker’s disbursement record is different from the recipient’s expenditure record. Keep both where appropriate, but do not treat the payment of a grant as proof of the recipient’s use of those funds.
For U.S. federal awards, 2 CFR 200.302 describes financial-management requirements including award identification and records supported by source documentation. That is a specific regulatory context, not a universal checklist for every private grant.
Use stable organization and grant IDs, then connect the records that belong to each grant. Give amendments, report obligations and transactions their own identifiers when needed. A person should not have to match filenames by memory.
| Stage | Evidence to index | Decision or relationship to preserve |
|---|---|---|
| Selection | Application, criteria and review record | Authorized award decision and rationale |
| Agreement | Signed agreement and approved budget | Applicable terms and version |
| Change | Amendment request and approval | What changed, when and under whose authority |
| Financial activity | Relevant Finance records and supporting documents | Grant allocation, period and accounting basis |
| Reporting | Submission, source evidence and clarification | Accepted version and review outcome |
| Closeout | Final review and unresolved-item record | Authorized closure or remaining obligations |
Not every grant needs the same packet. Agree the evidence requirements with the responsible Finance, compliance and program owners before collecting extra documents from recipients.
A useful change record identifies the prior value, the new value, the reason, the date and the person responsible. Keep the source approval when a change affects grant terms or reporting.
Separate a correction from an amendment. Correcting a mistyped date is different from approving a later deadline. Both may change a field, but they mean different things to a reviewer.
Do not describe a record as immutable unless the system’s actual controls establish that property. Confirm version history, permissions, export behavior and retention in your implementation. A visible history panel alone does not prove that every relevant change is preserved.
A fictional $50,000 award originally allocates $30,000 to delivery and $20,000 to equipment. An authorized amendment moves $5,000 from equipment to delivery. The total award remains $50,000.
The current budget is now $35,000 for delivery and $15,000 for equipment. If a reviewer sees only that current version, they cannot tell whether it was the original plan, a correction or an approved change.
| Record | Information | Evidence link |
|---|---|---|
| Budget version 1 | Delivery $30,000; equipment $20,000 | Original agreement |
| Change request | Move $5,000 to delivery | Request and stated reason |
| Approval | Authorized reviewer approves the change | Approval record and date |
| Budget version 2 | Delivery $35,000; equipment $15,000 | Approved amendment |
The trail explains the change without claiming anything about actual expenditure. To review spending, connect the appropriate Finance records and apply the approved budget version for the relevant period.
An assistant can help locate evidence, identify missing references and draft an index. Record those outputs as analysis. A flag is not a final finding, and a generated explanation is not an approval.
If a reviewer accepts, rejects or modifies an AI-assisted finding, keep the rationale and supporting source. Preserve the question and source scope when they are needed to understand the result.
Use a focused instruction:
Build an evidence index for [grant] and [review scope] from the supplied authorized records. For each material decision or figure, identify the source, date, version and recorded approver where available. Separate an AI-generated observation from a recorded human decision. List missing links and conflicting versions without inventing approvals or declaring compliance. Do not change or publish the records.
Choose one figure and one decision. Ask a colleague who did not prepare the packet to trace each back to its source. They should be able to explain the applicable version and identify unresolved questions.
Check more than whether a hyperlink opens. Does it open the right document? Is the relevant page readable? Can the reviewer distinguish the final approval from a draft? If access is denied, is there an authorized way to obtain the evidence?
Record the result of the test and fix the specific gap. Adding more files is not always the answer; sometimes the missing item is the relationship between an existing file and the decision.
Use a documented retention schedule based on the applicable award, legal requirements and organizational policy. Do not apply a single number of years to every grant or delete records just because a project is closed.
For example, NIH’s retention guidance distinguishes reporting situations and includes exceptions involving unresolved claims or audit matters. It also addresses integrity of electronically stored records. Check the rules applicable to your own award rather than copying the example as a universal policy.
Match access to the reviewer’s role and purpose. A board summary, an external audit packet and a public impact report may require different detail and different permissions.
Watch the explainer · 6 minutes 7 seconds
This Sopact video explains why sources, definitions and audience context matter even when the numbers are clean. Apply that lesson when preparing a review packet: connect each reported figure and recorded decision to its source, version and remaining questions.
Watch on YouTube if playback is unavailable · Browse the video library
Lead with the scope, period and preparation date. Include a short index linking decisions, figures and relevant source records. Show unresolved matters, the owner and the next step.
Preserve the version that was actually reviewed or submitted. A live dashboard may update later; that does not establish what a reviewer saw at the earlier meeting.
In a configured Sopact workflow, connected records can help organize the evidence as it arrives. Check the actual history, access and export capabilities before committing to a particular audit process. The software supports preparation; the responsible reviewer determines whether the evidence is sufficient.
Use the budget example, but remove the approval record. Ask another person to reconstruct the change. The correct result is an unresolved authorization question, not a newly generated approval.
Then restore the approval with a date and verify that the amended budget points to it. Check that the original remains available and that the total still reconciles to $50,000.
Pass condition: the reviewer can trace the change and explain what is still unknown. Neither an AI summary nor a current value substitutes for the missing evidence.
It is a connected record of material grant decisions, transactions and reported results, with their sources, dates, versions and responsible people. It should let another reviewer reconstruct what happened.
Not by itself. The record also needs to show how documents relate to a grant, figure or decision and which version applied.
No. Connected records can support review, but an audit is a separate process. Do not label data audited merely because it has source links.
Preserve the history required for the review and retention process. Distinguish corrections from approved amendments and keep the applicable source approvals.
Use the requirements applicable to the award and organization, including relevant exceptions and holds. There is no single retention period that should be assumed for every grant.
AI can help organize and inspect authorized evidence, but it must not invent missing approvals or certify compliance. Verify the system’s actual history and access controls and the sufficiency of the evidence.
Continue to chapter 21 on grant compliance reports. The evidence index supports the report, but each reporting requirement still needs its own definitions, scope and review.
For clear presentation, use the impact report writing ebook and example reports. Return to the Grant Intelligence course for the full sequence.
Bring one grant decision and its evidence. Explore how to keep the source, version and review history connected.
Explore Applications & Grants →
