Audit beginner Works with: Any AI

Meeting Follow-Up Workflow Audit

Table output Has example

Check whether decisions become actions.

The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.

Audit how meetings produce actions. Notes and action lists from three recent meetings, with what was completed afterwards: [MEETING_RECORDS]. Who attends and who owns follow-up: [ATTENDEES_OWNERS]. Tools used: [TOOLS].

Check whether decisions are recorded, actions have owners and dates, notes are sent quickly, items are tracked to closure, and meetings repeat the same discussions.

Return a table with Meeting, Decisions, Actions closed and Gap, a template for notes, and a rule for when a meeting is not needed.

Also suggest a three-line format for notes, a place where actions live that everyone can see, and a ritual of reviewing last meeting's actions at the start of the next one. Include advice on meetings that could be replaced by a written update. Further, suggest a standard place for the notes and a reminder to owners two days before each action is due.

Close with the one change you would make first if I had only thirty minutes, and explain why it beats the alternatives in effect and in risk.

Fill in before use

Optional: type your details and the prompt above updates. Nothing is saved or sent.

Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.

Record review (invented, three meetings)
Meeting 1: 9 actions listed, 6 with an owner, 3 with a date; 4 completed.
Meeting 2: notes sent after 6 days; 2 decisions unclear.
Meeting 3: 70% of time spent on a topic discussed in meeting 1.
Pattern: decisions recorded as discussion, not outcomes.
Template for notes: Decisions (what, who decided); Actions (owner, date); Parked topics.
Rule: notes within 24 hours; start each meeting by reviewing last actions (5 minutes). When not to meet: if it is an update, send a written one.

• audit