Decision log capture

Records what was decided, what was rejected, and when the decision should be looked at again.

macOS — coming soonSee the 3 automations
More / AUTOMATE.md

Note tagged as a decision, draft an entry with the options considered, the reason, the owner, and a review date, and file it in the decision log.

Ready-made: Decision Log Draft

The job, and what good looks like.

Decisions get made in a meeting, agreed in a chat thread, and forgotten by the next sprint. When the direction changes, the argument starts over, because nobody can point to the call that was made, the options that were dropped, or the reason it went that way. The log fixes that at the moment of the decision instead of later from memory. Every decision worth arguing about gets four fields: what was decided, the options considered and dropped, the reason, and the date to revisit it. The entry is written while the people who made it are still in the room, and the owner of the decision confirms the wording before it is filed. Keep the log searchable by topic rather than by date, so a new joiner can read why the obvious option was rejected. When a review date arrives, mark each entry as holding, changed, or reversed, and link a reversal to the entry it replaced. Reversals are the most useful rows in the log, because they show what changed and what the team believed before. A person still decides whether a conversation was a decision at all, and signs off on the reason.

When it is handled

  • Decisions searchable by topic
  • Reversals traced to the original call
  • Fewer restarts in chat

Works with tools like

  • Notion
  • Coda
  • Obsidian
  • Slack

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.

Decision Log Draft

Note tagged as a decision, draft an entry with the options considered, the reason, the owner, and a review date, and file it in the decision log.

When a meeting note is tagged as a decision

Decision Row Update

Decision marked final, add a row with the date, the owner, and the reason, then post the link in the decisions channel.

When a decision is marked final in a doc

Unlogged Decision Ask

Today's meetings with a decision in the notes, ask in the decisions channel for the reason and the owner's name before the thread closes.

30 minutes after a meeting with a decision in its notes

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.

Decision Log Draft

Approve before it updates the record?

ReviewApprove

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

Action-item closure

Tracks every action someone agreed to until it is done, handed to somebody else, or explicitly dropped.

3 automations

Knowledge base freshness review

Checks that internal documentation still matches how the team works and retires what no longer applies.

3 automations

Start with one job.
Make it your own.

macOS — coming soon
  1. 1

    Get the app

    It runs on your computer, next to your files.

  2. 2

    Add the automation

    Paste the instructions into the app, or save them as a file next to your work.

  3. 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.

macOS — coming soon