This is the system I built for my team so nobody has to be the person who remembers everything. After our weekly meeting, it turns the conversation into tracked action items, files them in one shared sheet, and messages each person their tasks, then nudges them before anything's due. I set it up once. It runs on its own every week.
Here's exactly how it's wired, so you can build your own.
Takes an afternoon to build, about 20 minutes if you only do Part A. You need: a transcript tool, an AI with connectors, a spreadsheet, a team chat. You end with: meetings that file their own follow-ups.
What you'll need
- Granola (or another meeting transcript tool), records and transcribes your meeting.
- Claude (or ChatGPT) with connectors + scheduled tasks, this is the engine that reads, sorts, writes, and messages. No Zapier, no developer.
- Google Sheets, the one shared tracker everyone trusts.
- Slack (or Teams), where people get their tasks.
Part A: Build the tracker first (10 minutes)
Make a Google Sheet with a Tracker tab and these columns:
Date Raised | Action Item | Owner | Due Date | Status | Notes | Meeting Link | Confidence
Add a second Lists tab with your team's valid owners, the actual people who can own a task. This one detail matters: it stops the AI from turning someone who was just mentioned in the meeting into an owner.
Part B: Connect your AI to your tools
In Claude (or ChatGPT), turn on connectors for your transcript source, Google Sheets, and Slack. This is what lets it act, read the meeting, write rows, send messages, instead of just talking about it.
Part C: The weekly task (the core of it)
Set up a scheduled task to run right after your weekly meeting. Give it this job:
Now, every week, the meeting turns itself into assigned, tracked tasks. Nobody takes notes. Nobody chases.
What good extraction looks like. Run it by hand once and compare against this shape:
Action Owner Due Conf
Send revised quote to Bianca Marcus Fri 29 high
Book the venue for the offsite Priya none high
Look into the booking software Priya none low
^ said as "someone should probably look at that" -
flagged low, no due date offered
UNASSIGNED - posted to channel:
"We need to sort out the returns process"
^ everyone agreed, nobody volunteered
That last block is the part people don't expect and it's the most valuable thing on the page. The commitments nobody claimed are exactly the ones that die, and they're invisible in normal meeting notes because they sound handled at the time.
Part D: The daily nudge task
Set up a second scheduled task to run each morning. Keep this one read-only:
Nudging before the due date, not after, is the part that actually changes behavior.
The power move: point it at the last three months
Once the tracker has some history, stop using it only for what's next and ask what it says about you:
The answer is usually the same and still lands: items raised without a due date don't get done, and one or two categories of work quietly slide every single month. That's not a people problem you fix by nudging harder, it's a capacity problem or a priority problem, and you can't see it until something's been counting.
Run it quarterly. It takes two minutes and it's the closest thing to a free management consultant you'll get.
The gotcha worth knowing
The write step is the fussy one. Connections to Google Sheets can quietly go stale, and then rows silently stop saving. Build in a safety net: tell the task that if it can't write to the sheet, it should message the rows to you to paste in manually, so a broken connection never means a lost meeting. Check the sheet actually updated for the first couple of runs.
(Scheduled tasks run inside your AI app, it needs to be open, or they'll run the next time you open it. Good to know so you're not wondering why Monday's sync didn't fire.)
Start manual first
Before you schedule anything, run the Part C prompt by hand once, right after a meeting. Watch it pull the action items and confirm they're right. Once you trust the extraction, then put it on a schedule. Automating a process you don't yet trust just automates the mistakes.
When it goes sideways
"It invented an owner." Someone got named in passing and it assigned them work. That's what the valid-owners list is for — if it's still happening, add: "If the transcript doesn't clearly show a person agreeing to do it, leave Owner blank and mark it unassigned. Never infer an owner from who was being talked about."
"Due dates are wrong." People say "next week" and "end of month," not dates. Give it your anchor: "Today's date is in the transcript header. Convert relative dates to real ones and put the original wording in Notes so we can check."
"The same task appears three weeks running." It's re-extracting things that were only discussed, not re-committed. Add: "Before writing a row, check the Tracker for an open item with the same meaning. If it exists, don't duplicate it - add a note that it came up again." Repeat appearances are useful data, so keep the note.
"Everyone ignores the Slack nudges." Two usual causes. Either the nudges go to a channel instead of a DM, which makes them everybody's and therefore nobody's — or there are too many, because low-confidence items are being nudged like commitments. Only nudge high-confidence items with due dates.
"It works but nobody trusts the sheet." Somebody has to correct it in public for the first month. If the owner column is wrong and nobody fixes it, the tracker becomes fiction and everyone quietly returns to their own notes.
Make it yours
- No Slack: send the same messages by email, or have it post one summary in your group chat. The nudge matters, the channel doesn't.
- Client meetings instead of team meetings: swap valid-owners for a two-name list (you and the client), and add a column for what you owe them. Chasing yourself is the point.
- Solo: you still want this. The tracker becomes your commitment list, and the daily nudge replaces the "I know I said I'd do something" feeling on Wednesday nights.
- Regulated or sensitive work: keep the write step manual. Extraction is the time-saver; automatic writing to a shared sheet is the risky part, and you can have the first without the second.
Do this next
Start this week: build the tracker (Part A) and run the extraction by hand once. That alone will save you the post-meeting scramble, and it's the foundation everything else runs on.
Next guide: The Small-Team Action-Item Template — the fill-in-the-blank version of this, if you'd rather copy a structure than design one.