[Day 13 of 30] Turn Meeting Notes Into a Team Decision Log With Tasks
One meeting becomes one shared truth and clear next steps for everyone.
The situation
You already have a PMS on your computer and, if you followed Day 12, a shared backbone in GitHub. Still, most meetings leave you with a messy transcript or scattered notes. Decisions are buried, owners are unclear, and each person retypes their own version into their PMS. You want one decision log the whole team can trust and clean tasks that land in each person’s system without another hour of admin.
The 1% upgrade
Use one prompt that takes your meeting notes or transcript and turns it into:
A clean decision log for the shared backbone, with Decision, Owner, Deadline, Rationale, Risks or Assumptions.
A quick sanity check that calls out missing context, conflicts, and fuzzy ownership.
Draft tasks for each participant that they can paste into their PMS with the right context.
Copy-paste prompt
You are my meeting decision editor for a small team.
Input:
- Raw notes or transcript from one meeting.
3) Propose tasks for each participant so they can add them to their personal PMS.
Under the heading “Tasks by Person”, group by person or role.
For each task include:
- Person:
- Task:
- Related_decision:
- Source_context: 1 short sentence that will remind them which meeting or topic this came from.
4) When you cannot be sure about a person or role, still do your best guess from the notes, mark it as “(please confirm)” next to the Person, and also list it under Fuzzy_ownership in the Sanity Check so the user can correct it quickly.
Steps:
1) Build a concise Decision Log for this meeting.
Format as a markdown list under the heading “Decision Log”.
For each decision include:
- Decision:
- Owner:
- Deadline:
- Rationale:
- Risks_or_assumptions:
2) Run a sanity check on the decision log.
Under the heading “Sanity Check”, list:
- Gaps: what information is missing to make these decisions safe.
- Conflicts: any decisions that contradict each other or past work.
- Fuzzy_ownership: any items where the owner is not clearly a single person or role.
3) Propose tasks for each participant so they can add them to their personal PMS.
Under the heading “Tasks by Person”, group by person or role.
For each task include:
- Person:
- Task:
- Related_decision:
- Source_context: 1 short sentence that will remind them which meeting or topic this came from.
Rules:
- Be concrete and short. No fluff.
- Prefer one owner per decision and per task.
- If something is unclear, call it out explicitly in Sanity Check and still propose your best guess instead of staying silent.
Now wait for my input, I will paste only the raw notes or transcript in this format:
Notes:
“”“[paste raw notes or transcript here]”“”
Example output
Decision Log
Decision: Move forward with Option B for the reporting dashboard, limited to the compliance use case in Q2. Owner: Maria, Product Deadline: 2026-03-28 Rationale: Fastest path that reuses existing components and unlocks the next compliance audit. Risks_or_assumptions: Assumes data team can expose the three new fields on time.
Decision: Pilot the new daily summary email with the compliance team only. Owner: Alex, Ops Deadline: 2026-04-05 Rationale: Smaller surface area and clear success metrics before rolling out to the whole org. Risks_or_assumptions: Assumes compliance team will provide a list of 10 pilot users by Monday.
Sanity Check
Gaps: No clear metric defined for “pilot success” on the daily summary email. Decide on open rate or number of issues caught.
Conflicts: Timeline for data fields and dashboard launch are both set for end of March, this may overload the same people.
Fuzzy_ownership: Follow up on legal review for the new email content, owner was not explicitly named.
Tasks by Person
Person: Maria, Product Task: Write a short spec for Option B of the reporting dashboard, including the three new data fields and the Q2 scope. Related_decision: Move forward with Option B for the reporting dashboard. Source_context: Weekly compliance sync on reporting and audit prep.
Person: Alex, Ops Task: Collect a list of 10 pilot users from the compliance team and confirm they agree to receive the new daily summary email. Related_decision: Pilot the new daily summary email with the compliance team only. Source_context: Weekly compliance sync on reporting and audit prep.
10-minute action
Take real notes or a transcript from your last meeting with at least one decision. Paste only the notes into the prompt, let the AI infer people and roles from context, and skim the Sanity Check section for any “(please confirm)” markers. Save the Decision Log section into your shared PMS backbone, for example in a decisions/ or meetings/ folder in the GitHub repo from Day 12. Then, for each person in the Tasks by Person section, paste their tasks into their PMS or ask them to paste the tasks themselves so their local system stays in sync with the shared log.
What to do next
Take the next meeting on your calendar that usually produces fuzzy outcomes, run this prompt on the notes, and send the Decision Log to the team with one question: “What did I miss or mis-assign here?” The replies will both correct the log and show you how much alignment you were actually losing before you had a shared decision log.