Collect What a Grant Report Needs Without Chasing Program Staff
The final report is due Friday and needs participant numbers from one person, receipts from another, and three photographs with signed releases from a program that ended in March.
The short answer
Grant reporting is a collection problem before it is a writing problem, and the people holding the pieces do not work on grants. A file request with a document checklist is what fits: you list what the report needs, send one link, and each item is tracked per person as it arrives, with reminders going only to whoever has not sent theirs. As documents land, the Read Details from File step reads what each one is, and the Rename and Move steps file it under the grant it reports on, so collecting and filing are the same act.
Steps this uses
Before and after
What actually changes
As they arrive
- IMG_0912.jpg
- receipts.pdf
- numbers.xlsx
- release form signed.pdf
After the workflow
- Funders/Hartwell Foundation/2026/Report/2026-09-02-photo-release-signed.pdf
- Funders/Hartwell Foundation/2026/Report/2026-09-03-expenditure-receipts.pdf
- Funders/Hartwell Foundation/2026/Report/2026-09-04-participant-numbers.xlsx
- Funders/Hartwell Foundation/2026/Report/2026-09-05-site-photo.jpg
Four items from three people, uploaded to one link and filed under the grant they report on.
Setting it up
Described once, then it runs
This is the sentence. Send it to the builder and the steps below appear on a canvas, wired and named, for you to change before anything runs.
Ask program staff for the receipts, participant numbers and photo releases a grant report needs, remind anyone who has not sent theirs, and file each document under that grant as it arrives.
Write the checklist once, per report shape
Interim and final reports for the same funder ask for the same things year after year. That list is worth writing once and reusing, rather than reconstructing it out of the grant agreement each time a deadline gets close.
Send one link, not five threads
A file request is a single link the recipient uploads into. The alternative is a thread per person, which is where the version confusion and the "I thought I already sent that" both come from.
Let the reminders be automatic
Completion is tracked per recipient against the checklist, so reminders reach only the people who still owe something. Nobody has to maintain the list of who has responded, which is the part that actually takes the time.
File as it arrives, not afterwards
Each upload is read and filed under the grant it belongs to at the moment it lands. Collecting into a pile and sorting it out later is the same work done twice, and the second pass is the one that gets skipped.
The people holding the pieces do not work on grants
A program coordinator has a job that is not sending you receipts, and your request arrives as one more email in a week that already has too many. That is not a discipline problem. It is what happens when an ask is unstructured, repeats, and has no visible state. A checklist with a link and automatic reminders changes the shape of the ask rather than its volume, which is why it works where a firmer email does not.
Photo releases are the item that sinks reports
Funders want photographs, and photographs of people need consent. The release is signed on paper at the event by somebody who is not thinking about a report due in six months, and then it is in a drawer or it is nowhere. Putting the release on the checklist alongside the photograph is the only reliable way to end up holding both, and it costs nothing to ask for them together.
What it does not do
It asks for a list of documents, tracks what has arrived against that list, reminds the people who have not sent theirs, and files what comes in. It does not write the report, total an expenditure column, or judge whether a receipt is an allowable cost under the grant agreement. Those are decisions with money attached and they belong to a person.
Limits
What to know before you build it
It can work through what is already there
This one runs on a schedule over a folder you point it at, so the documents sitting in it now are read and filed alongside the ones that arrive later. A large backlog is an overnight job rather than an instant one, because each document is read rather than pattern-matched.
It needs a connected account
This workflow reads files out of an email inbox, so it cannot run until that account is connected. Connecting one is on the Max plan, or on any team workspace. There is no version of this particular workflow that runs on the free plan, because the files it organizes never arrive in The Drive AI on their own.
FAQ
Common questions
How do you collect documents for a grant report?
With a checklist of required items and one upload link per person, rather than a thread per person. Completion is tracked per recipient against the list, so reminders go only to whoever has not sent theirs, and each document is filed under the grant as it arrives.
Can it tell me what is still outstanding?
Yes, and that comes from the file request checklist rather than from the workflow. A workflow acts on a file when it arrives and cannot look at a folder and know what should have been in it. The checklist holds the required items and tracks completion per recipient, which is what makes the outstanding list possible at all.
Does this work for subrecipient documentation?
The mechanics are the same: a list of what each subrecipient owes you, one link each, tracked separately. Whether what they send satisfies your pass-through obligations is a compliance judgement and is not something a workflow decides.
What happens to documents that arrive by email anyway?
They are handled the same way. The Email Attachment trigger picks up an attachment somebody sent instead of using the link, and it is read, renamed and filed under the same grant. People will always reply to the email, so the flow has to accept both routes.
Ask once, then stop chasing.
A checklist per report, reminders to whoever has not sent theirs, and everything filed on arrival.
5 GB free · No credit card required