Action-item closure
Tracks every action someone agreed to until it is done, handed to somebody else, or explicitly dropped.
Finished meeting, create one task per action item in the notes with an owner and a date, then post the list for review.
The job, and what good looks like.
A meeting ends with six actions, three of which get done and three of which disappear. Nobody can tell which is which, so the same task is added again next week and the team believes work is moving when it is not. The workflow makes every action a record with three fields: owner, date, and state. The state is one of open, done, handed off, or dropped, and dropped is a real answer that stops the item from coming back. Actions are captured once, in one place, within a day of the conversation, because the format matters more than where it happened. Anything agreed verbally in a corridor or a DM gets the same entry. One weekly pass lists everything open past its date and asks the owner for one of the three closing moves. An item handed to somebody else changes hands in the same pass, so the trail shows where it went and who is holding it now. A person still decides who owns an item nobody claimed, whether a silent item is finished or simply forgotten, and what a missed date actually means. The measure is simple: no action stays open past its date without a reason.
When it is handled
- Every action has one owner
- Stale items surfaced within a week
- Fewer duplicate tasks
Works with tools like
- Linear
- Asana
- Slack
- Notion
Ready-made automations. Pick the one that fits.
Each one is a plain-language document. Run it as it is, or change the timing, the rules and the tools to match your team.
Action Items From Meeting
Finished meeting, create one task per action item in the notes with an owner and a date, then post the list for review.
After every meeting ends
Action Owner Check
New actions page, flag every item missing an owner or a date and ask in the channel for a name before the next meeting.
When a meeting note is added to the actions page
Open Action Reminder
Every Friday at 9am, list open actions older than a week and remind each owner to close, reassign, or drop them.
Every Friday at 9:00am
You stay in charge.
At every step.
It sorts and reminds. You decide what to do.
- It never replies for you
Digests and reminders come to you. Anything that would send a message waits for your OK.
- Undo what you don't want
Every step is recorded, and a file it changed can be put back.
- Only what you connect
Each automation reaches only the inbox, calendar and notes you give it.
Action Items From Meeting
Approve before it files the ticket and posts in Slack?
Before you download.
- Where does it run?
- On your Mac or Windows computer, in the background. It keeps working after you close its window, and only reaches the folders and apps you connect for each automation.
- How does it connect to our CRM and other tools?
- Through each app's own connection where it offers one, signed in once by you, or by using the app in a browser the way you would. Each automation gets only the connections you give it, and the tools a page names are examples you can swap for your own.
- Does it run when my computer is asleep?
- It keeps your computer awake while a job runs and just before a scheduled one. While the computer is closed or off, nothing runs; when it wakes, it checks the inbox, calendar and other sources it watches for anything that arrived meanwhile.
- How does my team use it?
- Each person who runs automations installs the app. Keep a project in a shared folder, such as Google Drive or a network drive, and teammates can open it and follow every run, while one person owns it and runs it.
- Do I need anyone technical to set it up?
- No. Download the app, add an automation in plain words, and connect only what that job needs. Nothing runs until you switch it on.
Already have tools for this? Here is the difference.
Built-in rules in your email and calendar
Filing messages by sender or subject.
They can't read what a message asks for, or follow up on it.
Flowchart automation tools
Connecting apps if you build and maintain the flow.
Every exception becomes another branch.
AI chat assistants
Summarizing when you ask.
Nothing happens until you remember to ask.
AUTOMATE.md
Your routine, written in plain words. It runs on its own, follows your rules, handles the exceptions a flowchart can't, and asks you when it matters. The file stays yours, whichever AI model runs it.
Related workflows.
Meeting notes
Turns a recorded call into a written record with the decisions, the open questions, and the owners.
2 automations
Decision log capture
Records what was decided, what was rejected, and when the decision should be looked at again.
3 automations
Project updates
Collects one written status from every active project each week and surfaces the blockers nobody has raised.
1 automation
Start with one job.
Make it your own.
macOS — coming soon- 1
Get the app
It runs on your computer, next to your files.
- 2
Add the automation
Paste the instructions into the app, or save them as a file next to your work.
- 3
Try it, then turn it on
Run it once and check the result. It only runs on its own once you switch it on.