Meeting Follow-Up Action Plan Loop

By Juan Beltrán, Industrial B2B AI Transformation Executive.

What should happen after this meeting, and who owns it? Use this after meetings that produced many ideas but not enough ownership, sequencing, or accountability. Meeting Follow-Up Action Plan Loop Decision to make: What should happen after this meeting, and who owns it? Decision owner: Meeting owner or project lead. Working-session setup: - Timebox: 20 min working session - People in the room: Process owner, frontline representative, delivery owner, and affected manager. - Preparation: Light prep: bring the notes or draft already in front of you. Context: [Paste your notes, excerpts, draft, meeting transcript, CRM fields, proposal text, public research, or examples here.] Context I should provide: - Meeting notes - Attendees or roles - Decisions made - Open questions - Deadlines - Dependencies - Desired tone Safety boundary: - Use only information I provide in this conversation. - Do not infer personal, confidential, regulated, pricing, customer, employee, or supplier facts. - If the material belongs in an approved enterprise environment, tell me before analyzing it. Instructions: Act as an operating cadence assistant. Turn the meeting notes below into decisions, actions, owners, dependencies, risks, and a concise follow-up email. Mark anything unclear instead of inventing owners or dates. Run the session in this order: 0. Inspect the context. If a missing fact could materially change the recommendation, ask no more than five focused questions and wait. If I ask you to continue, mark each missing fact as unknown. 1. Extract decisions: List decisions made, deferred, or unclear. 2. Extract actions: Turn discussion points into actions with owner, date, dependency, and expected output. 3. Flag risks: Identify blocked items, unclear ownership, or dependencies that could stall. 4. Draft follow-up: Write a concise follow-up message in the requested tone. 5. Create the check-in list: List the items to verify before the next meeting. Evidence rules: - Separate supplied facts, interpretations, assumptions, and unknowns. - Reference the exact note, excerpt, metric, or example supporting every material claim. - Show the strongest credible counterargument to the recommendation. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Do not turn missing evidence into a confident recommendation. - Keep the answer useful for Transformation Lead. Output contract: A follow-up note with decisions, actions, owners, dependencies, risks, and a polite email draft. Return: 1. BLUF: the decision, recommendation, or draft in plain language. 2. Evidence table: claim, supplied evidence, confidence, and gap. 3. Assumption ledger: what is assumed and how to verify it. 4. Counterargument: the strongest reason the recommendation may be wrong. 5. Decision record: decision status, accountable owner, next action, and due date or trigger. 6. Evidence still needed: only the gaps that could change the decision. 7. Stop condition: state when the work is complete and when it must pause. Evidence checklist: - Decision - Action - Owner - Date - Dependency - Risk - Follow-up draft Human operating ritual: - Send the follow-up while the meeting is still fresh. - Replace group ownership with named ownership. - Ask for corrections quickly. Do not use this loop when: Do not use it when nobody in the room owns the workflow or can change the operating conditions. Stopping condition: Stop when every action has an owner or is explicitly marked unresolved.

Canonical URL: https://juanbeltran.ch/operating-loops/meeting-follow-up-action-plan-loop