Meeting Follow-Up Action Plan Loop

By Juan Beltrán — personal website on AI and digital growth for complex B2B industries.

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 Task: What should happen after this meeting, and who owns it? 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 Useful setup: Paste meeting notes, attendees or roles, decisions made, open questions, deadlines, dependencies, and tone for the follow-up. Why this matters: Use this after meetings that produced many ideas but not enough ownership, sequencing, or accountability. Business problem: Meetings create motion but not accountability when decisions, dependencies, and owners are not converted into visible follow-up. 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. Workflow: 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. Quality bar: - Use only the context in this chat. - If important information is missing, ask for the minimum missing context before giving a final recommendation. - Separate facts from assumptions. - Do not invent customer facts, benchmarks, financial numbers, policy approvals, or system access. - Keep the answer useful for Transformation Lead. Output: A follow-up note with decisions, actions, owners, dependencies, risks, and a polite email draft. - BLUF recommendation or draft. - Evidence from my context. - Assumptions and missing information. - Risks, objections, or failure modes. - Recommended next action, owner, and stop condition. Evidence checklist: - Decision - Action - Owner - Date - Dependency - Risk - Follow-up draft 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