Skip to content
Aurora

The Sharing Playbook

How to prepare files for a grant review

Build a grant review pack where the figures match, the supporting files fit and you keep a record of what you submitted. Includes a free worksheet.

Nonprofit Projects · Aurora Datarooms

Archive Date Published
Four organizers prepare bicycles and tools for a repair workshop in a bright community hall.

Get The Free Worksheet

Start a grant review pack with the funder's questions, the reporting period and the documents needed to support each answer. Check that the figures use the same dates and definitions, then share the files each reviewer needs. Keep a copy of the submitted report and its supporting files so later corrections are easy to explain.

A small nonprofit has run a series of community repair workshops. Its coordinator has session notes, a spending spreadsheet, photos and an attendance list. The funder asks how many people took part. One spreadsheet says 90 and another says 42. Both figures may be right: one counts visits, while the other counts individual people. Sending the whole folder would leave the reviewer to work that out.

Read the request before collecting more files

Open the award agreement, the reporting instructions and the latest message from the funder. Write down the reporting period, deadline, required form and submission destination. Ask the funder about anything that is unclear before spending time on the wrong format.

For US federal awards, Grants.gov explains that reporting schedules, requirements and systems can vary by grant. Your own award instructions are the starting point. Grants.gov's post-award guidance.

Foundation processes can change too. NewAlliance Foundation directs recipients funded after May 2023 to its application portal for final reports, while its older reporting format applies to earlier awards. An old form found through search may therefore be the wrong one to use. NewAlliance's final-report instructions.

Agree who prepares the pack, who checks the figures and who can submit it. In a small team, one person may handle more than one role. A shared room can help with preparation or follow-up when the funder accepts it; it does not replace a required submission portal or form.

Give each answer a clear meaning

Before choosing attachments, write a short answer to each question. Beside every number, record what it counts, its date range and where it came from.

For the repair-workshop example, the team's working list could look like this:

QuestionAnswer to checkSupporting fileCheck before sharing
What happened this quarter?12 workshops held from July through SeptemberSession summaryExclude the canceled session still shown in the planning calendar.
How many people took part?42 individual participants; 90 total attendancesParticipant-count summaryState that repeat visits are included in 90. Explain how individual participants were counted.
How was the grant used?Spending for this grant and reporting periodGrant spending summary and requested receiptsCheck dates, totals and the grant's share of any joint cost with the person responsible for the accounts.
What changed for participants?Feedback collected after the workshopsFeedback summaryState how many people replied and when. Explain any gaps.

These numbers describe a worked example. Use the definitions requested by your funder. If you cannot confidently count individual people, explain what you can count and ask how to report the gap. Don't turn total attendances into a claim about unique participants.

Keep the free grant-review worksheet beside your draft report. It has a place for the counting method, reporting period, files and unresolved questions.

Separate the activity from the result

Running a workshop is an activity. Attendance shows participation. A participant's feedback may help describe what they gained, within the limits of what was asked and who replied.

For example, eight feedback responses from the final workshop don't describe everyone who attended the full program. Label that summary with the session, response count and question asked. Keep any broader claim in the report tied to information you actually collected.

Photos can help a reviewer understand the setting or activity. They won't explain the spending calculation or show how many distinct people took part. Choose attachments for the question they answer, and use photos only where you have permission to share them.

Prepare copies for the people reviewing them

The working folder may contain participant names, contact details, donor records, staff notes and files from another grant. Check what the reviewer needs before granting access to that folder.

A program officer might need the progress report, participant-count summary and selected supporting material. A finance reviewer might also need the spending breakdown and requested receipts. Use the funder's actual request to decide the split; some reviews will need the same pack for everyone.

Where a summary is accepted, send the summary and keep the underlying records in the controlled working location. If the funder requires identifiable or sensitive source records, agree the recipients and transfer method with the person responsible for those records. Do not remove information required for the review without resolving that requirement.

When making a sharing copy, check the whole file. Spreadsheets can contain hidden sheets, comments and links to other workbooks. PDFs can include attachments or text beneath a visual cover. Use a suitable export or redaction tool, reopen the resulting file and check it before sharing. Aurora controls file access; it does not redact the contents for you.

Keep the report and its attachments together

Use filenames that show the project, reporting period and purpose. Keep a short list linking each report answer to its attachment. If a receipt is missing or a total is still being checked, name the person following up and the expected date. Tell the funder about unresolved items when the reporting instructions require it.

Before submission, check the final report against the files once more. Make sure the same period, participant definition and spending total appear wherever you use them. Keep the completed report, exact attachments and submission confirmation in your agreed records location.

If a correction is needed later, record what changed and follow the funder's correction process. A file silently replaced behind an old link can leave the reviewer unsure which version supported the submitted answer.

Use Aurora to organize a shared review

You can keep the project files in one Aurora library and choose which files appear in each room. One room could hold the general progress pack, while a second contains the supporting financial files for a separate reviewer. Groups and individual permissions refine access within each room; they cannot expose a file excluded from that room.

Replacing a shared source file makes its current version available in the rooms that share it when reviewers reopen or refresh it. Downloaded copies do not update. Keep the submitted pack separately from files you continue to revise, and tell reviewers when a correction affects an answer.

For a small trial task, use three sample documents with no real participant data: a progress summary, a count summary and a spending summary. Create one library and two rooms, then check which sample files each room contains. This fits the current 30-day Starter trial and its two-room allowance.

Try Aurora with a sample review.

For a larger collection, the guide to helping reviewers find the right files explains how to add section references and reading routes.

Grant review worksheet

Free to use and adapt. Keep your completed worksheet in your own project files.

Download Worksheet (.md)

Use this alongside the funder's actual reporting instructions. Complete the answer-and-file list, resolve inconsistent dates or definitions, then check the copies you plan to share.

Reporting details

  • Project and grant reference:
  • Reporting period:
  • Funder's current instructions and form:
  • Deadline, time and timezone:
  • Required submission destination:
  • Pack prepared by:
  • Figures checked by:
  • Person authorized to submit:
  • Submission confirmation and exact submitted-files location:

Answer and file list

Funder's questionDraft answerPeriod and counting methodSupporting file and sectionCheck or gap, person and due date
Activities completed
Participation
Grant spending
Results and feedback

These are starting examples. Replace them with the questions your funder asks. Keep attendance counts separate from individual participant counts. For feedback, record how many people responded, the question asked and the collection date.

Sharing copies

FileReviewer and reason neededSharing copy or original requiredSensitive content checkedAccess checked
  • Review hidden sheets, comments, linked workbooks and embedded attachments where present.
  • Reopen any export or redacted copy and check what the recipient can read.
  • Resolve required sensitive-record transfers with the responsible person and the funder.
  • Keep unrelated projects, donor lists and internal working notes outside the shared pack unless required.

Submission and correction record

Sent date and timeReport and attachment versionsDestination and confirmationLater correction and how the funder was told

Final check: the report and attachments use the same period, definitions and checked totals. Keep unresolved questions visible. Follow the funder's required format, submission process and retention instructions.

Sources