Keep a Decision and Commitment Log
By the end of this recipe you'll have a running log where every decision your team makes and every commitment someone takes on is captured as an entry — with what was decided, who owns it, when, and where it came from — so nothing important dies in a scrollback. Decisions get made in a channel at 4pm on Thursday and are forgotten by Monday; "I'll handle it" is said in a meeting and never tracked. Because your chat, meetings, and boards all live in one workspace, Copera AI has the context to sweep those conversations and turn them into a log you can actually trust.
Readiness: Available now — ask Copera AI to build your log on demand today, and add a meeting automation for hands-free capture. The version where a named teammate keeps the log current on its own is rolling out in early access.
What it does
Your decision log is a board — a running list where each row is one decision or commitment. A row carries:
- What was decided (the headline) and the full rationale in its description.
- Type — a Decision the team made, or a Commitment someone took on.
- Owner — who's accountable.
- Date — when it was decided.
- Source — the channel, meeting, or thread it came from.
- Due date and Status — for commitments, so you can chase follow-through.
There are two ways to fill it, and you'll likely use both:
- Ask Copera AI on demand — the primary, flexible way. Point it at a channel, a meeting, or your whole workspace and it sweeps for the decisions and commitments, then adds a row for each. Run it at the end of a week, after a big meeting, or any time you think "wait, what did we actually agree on?"
- An automation for meetings — always-on capture. The moment a call finishes transcribing, an automation extracts the decisions and logs them, so recurring meetings feed the log without anyone lifting a finger.
A board beats a flat document here: you can filter commitments by owner, sort by what's due next, and instantly see what's still open — a scrolling doc can't do any of that.
Build it yourself
The log is a board, so set that up once, then feed it. The fastest, most flexible way to fill it is to just ask Copera AI (the next section — this is the primary path). The automation below adds hands-free capture for meetings, which are the single richest source of decisions.
Set up the log (one time)
Make a board with a table where every row is one decision or commitment. You can build it by hand, or ask Copera AI: "Create a Decision Log board."
Add Decision (the title), Type (single-select: Decision, Commitment), Owner (a people column), Date decided (date), Source (text or link — which meeting or channel it came from), Due date (date, for commitments), and Status (single-select: Open, Done, Revisited). Put the full context and rationale in each row's description so a decision is never just a one-liner without its "why."
Capture meeting decisions automatically
Meetings are where most real decisions happen, and Copera already transcribes them and surfaces the key decisions. Turn that into log entries with one automation.
On your Decision Log board, add an automation with a Transcription complete trigger, scoped to the meeting channel where decisions get made (or run it across every meeting).
Add a Load meeting context step so the next step has the transcript's summary, decisions, and details to work from.
Add an AI → Extract step that pulls structured fields out of the conversation: the decision or commitment, whether it's a Decision or a Commitment, the owner, and any due date mentioned.
Add a Create row action that writes one row per extracted item into the Decision Log — mapping the decision, type, owner, and due date into their columns, stamping Date decided to now, and setting Source to the meeting. Mark the rows with an "AI-created" status so they're easy to review.
Add a Post channel message or Send notification action to tell the team the decisions from the call are logged, with a link to the board.
This automation captures meeting decisions the moment a call ends. For decisions made in chat, in a document, or anywhere else, the on-demand sweep below is the way — it's the flexible catch-all that reads across sources whenever you ask.
Or just ask Copera AI
This is the primary way to run your log. An automation watches one source; Ask Copera AI reads across your workspace on demand — it can search your chat, read a meeting's decisions, and read a document you point it at, then write the entries for you. Open Ask Copera AI and describe what you want:
"Look through our Product channel for the decisions and commitments we made this week. For each one, add a row to my Decision Log board with what was decided, whether it's a decision or a commitment, who owns it, today's date, and the source. Put the full context in each row's description."
Copera AI searches your chat and workspace for the relevant discussion, pulls out the decisions and commitments it finds, and creates a row for each on the board. It works from search, so name the channel and the time frame in your request, and skim the review cards — it surfaces the decisions it can find, and you're the final check. With the default Ask before acting permission mode, it shows a review card for each row before anything is saved, so you approve exactly what enters the log. It always acts as you and within your permissions — it can only read what you can already see.
Point it at any source the same way: "Read the decisions from this morning's leadership meeting and log them," or "Add the commitments from the launch planning doc to my Decision Log." See What Copera AI Can Do for the full list of what it can read and create.
Make it a standing teammate
AI teammates are rolling out gradually. When one is available in your workspace, a named teammate — call it "Scribe" — can keep this log current on its own: it reads your channels and meeting notes as decisions happen and adds each one to the log under its own identity, no prompting required. Until then, everything in this guide works today — ask Copera AI to sweep for decisions on demand, and let the meeting automation capture calls hands-free.
Tips
Turn commitments into follow-through. Add a second automation to the board: a Date reached trigger set to a few days before the Due date that sends the Owner a notification. Now every commitment in the log actively chases itself instead of quietly slipping.
Agree on one keyword. Ask your team to write a marker like "DECISION:" or "COMMITMENT:" when they lock something in a channel. It makes the decision unmistakable in the moment — and far easier for you or Copera AI to find when you sweep for them later.
Run the sweep on a rhythm. End of every week and right after big meetings, ask Copera AI to sweep for decisions. Pair it with your weekly reflection so reviewing what was decided becomes a standing habit, not a scramble.
Set a spend cap on the meeting automation. Because it runs after every call and uses AI to extract decisions, give the automation a per-automation spend cap so it can never run past a budget you choose, and watch the usage dashboard to see where credits go.
Frequently Asked Questions
Can Copera AI capture decisions made in our chat channels?
Yes, on demand. Ask it to sweep a channel's recent discussion and it searches your chat and workspace, pulls out the decisions and commitments it finds, and adds each as a row to your Decision Log board with the owner, date, and source. With the default Ask before acting mode, it shows a review card for each row before it's saved.
Where does the decision log live in Copera?
As a board. Each decision or commitment is one row, with columns for what was decided, its type, the owner, the date, the source, a due date, and a status. Because it's a board and not a flat document, you can filter commitments by owner, sort by due date, and see what's still open — and the full rationale lives in each row's description.
Can Copera log decisions from meetings automatically?
Yes. Build an automation that triggers when a meeting finishes transcribing, loads the transcript, extracts the decisions and commitments with their owners, and creates a row for each in your Decision Log — so every call's outcomes are captured without anyone typing them up.
Can I be reminded about commitments before they're due?
Yes. Because the log is a board, add a Date reached automation that notifies the owner a few days before a commitment's due date — turning the log from a record of good intentions into something that drives follow-through.
Does the AI save decisions without me reviewing them?
Only if you choose that. With the default Ask before acting permission mode, Copera AI shows a review card for every row before it's created, so you approve exactly what goes into the log. It also acts as you and within your permissions — it can only read what you can already see.
Related
- What Copera AI Can Do — the full, honest list of what Ask Copera AI can read and create
- Ask Copera AI — the conversational assistant that sweeps your workspace and writes the entries
- Automations — the trigger, action, and AI-step reference behind the meeting-capture flow
- AI Summaries — how Copera surfaces decisions and action items from a transcript
- Turn Every Meeting Into Assigned Tasks — the sibling recipe for turning calls into tracked work
- What You Can Build with Copera AI — the full playbook