Board Packets, Agendas and Minutes Filed by Meeting Date
A new board member asks what was decided about the building lease. The answer is in minutes that were emailed as a draft, approved at the following meeting, and never saved anywhere in their approved form.
The short answer
Board records organize by meeting, one folder per meeting date, because a decision is anchored to the meeting that made it. A workflow uses the Read Details from File step to pull the meeting date and the document type off each document, the Rename step to name it date-first, and the Move step to file it under that meeting. The distinction that matters is draft against approved: the approved minutes are the record, and the Ask AI About the File step can route the two differently so a draft never sits where the record should be.
Steps this uses
Before and after
What actually changes
As they arrive
- minutes draft.docx
- packet.pdf
- agenda v2.docx
- treasurer report.xlsx
After the workflow
- Board/2026-03-19/2026-03-19-agenda.docx
- Board/2026-03-19/2026-03-19-board-packet.pdf
- Board/2026-03-19/2026-03-19-treasurers-report.xlsx
- Board/2026-01-22/2026-01-22-minutes-approved.docx
Four documents filed under the meetings they belong to, with January minutes landing in January even though they were approved in March.
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.
When a board document arrives, read the meeting date and the document type off it, rename it date-first, and file it under that meeting. Keep approved minutes separate from drafts.
A folder per meeting, named by date
ISO dates, so the year reads in order. Everything from one meeting in one place: agenda, packet, financial reports, anything circulated for a vote, and the approved minutes of the meeting before it.
Separate the draft from the record
Draft minutes and approved minutes are different documents that usually arrive with the same name. The approved version is the one that answers questions years later, and it should not be sitting beside three drafts of itself.
Keep the standing documents out of the meetings
Bylaws, the conflict of interest policy, signed disclosure forms and the current roster are not meeting documents. They belong in a governance folder of their own, because the question asked about them is what is current rather than what was circulated in March.
Gate the filing of the record
The Ask a Person to Approve step earns its place on minutes specifically. Filing a draft as the approved record is the one mistake in this flow that is genuinely expensive to discover later.
Minutes are approved at the next meeting, which is where filing goes wrong
The minutes for the March meeting are adopted in May. If they are filed under the meeting that adopted them, every future question about a March decision looks in the wrong folder. The date on the minutes is the date of the meeting they record, not the date they were signed off, and reading that date off the document is what puts them where anyone would look.
These are the records outsiders actually ask for
Auditors ask for minutes. Funders ask for a board roster and a conflict of interest policy. A bank opening an account asks for the resolution authorising it. Each of those is a two minute request if the records are filed by meeting and the standing documents are current in one place, and each is a bad afternoon if they are spread across four inboxes and a shared drive.
What it does not do
It files board documents under the meeting they belong to and keeps the approved record apart from drafts. It does not run a board portal, collect votes, or track attendance and quorum. It does not know by itself whether minutes were adopted, which is exactly why the approval step is there: a person says so, and the workflow files accordingly.
Limits
What to know before you build it
It runs on new files, not your backlog
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 haveIt 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 should board meeting documents be organized?
One folder per meeting, named with the meeting date in ISO form, holding the agenda, the packet, the financial reports and the approved minutes for that meeting. Standing governance documents such as bylaws and the conflict of interest policy live separately, because the question asked about them is always what is current.
Where do approved minutes go if they are adopted at a later meeting?
Under the meeting they record, not the meeting that adopted them. The date on the document is the anchor. Filing them by adoption date is the most common way a set of board records becomes hard to search.
Should draft minutes be kept at all?
Keeping them is harmless if they are clearly named as drafts and are not sitting where the record should be. What causes trouble is a folder holding four files called minutes with no way to tell which one the board actually adopted.
Does this handle committee minutes too?
Yes, with the same shape, though committee records usually deserve their own folder rather than being mixed into the board meetings. A committee and the board are different bodies, and the questions asked of their records are different.
One folder per meeting.
Filed by the date on the document, with the approved record kept apart from the drafts.
5 GB free · No credit card required