The renewal application asks what you told this funder last year. The proposal is in a shared drive, the award letter is in the executive director's email, and the final report is on somebody's desktop.
The short answer
Grant files organize by funder first and grant year second, because a funder is a recurring relationship and the question is nearly always what happened with this funder last time. A workflow uses the Read Details from File step to pull the funder, the document type and the date off each document, the Rename step to name it date-first, and the Move step to file it under that funder and year. The Email Attachment trigger matters here, because award letters and reporting templates arrive as attachments from program officers rather than through any system of yours.
Steps this uses
Before and after
As they arrive
After the workflow
Four documents filed by the funder and grant year named on them, rather than by whoever happened to open the email.
Setting it up
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.
When a grant document arrives, read the funder, the document type and the date off it, rename it date-first, and file it under that funder and the grant year it belongs to.
Two levels. A third level by document type puts four files in each of six folders and turns every save into a decision, when the filenames already say what each document is.
The determination letter, the W-9, the audited financials, the board list and the most recent 990 belong in one folder of their own. Every application asks for them and they are identical each time, so copying them into each grant folder only creates a question about which copy is current.
A funder folder should read as a timeline: letter of inquiry, proposal, award letter, interim report, final report. The Rename step writes the date first so the year reads in order without anyone thinking about it.
A budget template or a photo from a program site names nobody. The Ask AI About the File step sends those to review rather than filing them under whichever funder was mentioned most recently.
The reason funder comes before year is that grant work repeats on a multi-year cycle. When a program officer emails, or a renewal opens, the useful question is what you asked this funder for last time, what they funded, and what you told them you did with it. One folder per funder puts that whole history in one place. Filing by program or by year instead scatters a single relationship across the drive and turns every renewal into a search.
Half of grant filing is outbound: the proposal as submitted, the budget as approved, the report as filed. Those are the versions that matter later, because they are what the funder actually holds. Filing the submitted version alongside the funder's replies means the folder carries both sides of the conversation, which is what a renewal or an audit actually needs to see.
It files grant documents under the funder and year written on them. It does not track reporting deadlines, because a deadline lives inside a grant agreement as a sentence rather than as a date on the face of a document, and a workflow reading files cannot maintain a calendar. It does not manage a pipeline or suggest what to apply for next. It makes the documents findable underneath whatever you use to manage the work.
Limits
This workflow fires when a file arrives. It will not go back over the documents already sitting in the folder, so switching it on leaves the existing pile exactly where it is. Working through what is already there is a scheduled run instead, which is a different workflow.
Organize the files you already haveThis 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
One folder per funder, with a folder per grant year inside it, and organizational boilerplate kept once in its own place rather than copied into each grant. Name files date-first with the document type, so a funder folder reads as the history of that relationship.
In one folder of their own, not duplicated into each grant. Every application asks for them and they are the same every time. Keeping a single current copy is what stops last year's audit being submitted by accident.
By funder. Programs are how you think about the work and funders are how the paperwork arrives. A proposal is written to a funder, answered by a funder and reported back to a funder, so the funder is the thread running through every document in the file.
Yes, and it should. The submitted proposal and the filed report are the versions that matter later. Anything uploaded to the watched folder is read and filed the same way an email attachment is, so outbound documents land beside the replies to them.
The proposal, the award and the report, filed where the renewal will look for them.
5 GB free · No credit card required