Pro sample · available now · no purchase
From meeting to follow-through.
A connected four-step pack for non-technical professionals and small-team leads. Use each reviewed output as the next input.
Result: an agenda, an action register, a follow-up draft and a factual weekly update.
Requirements: non-sensitive notes and an approved text chat assistant. No plugin or paid slide tool is required.
Saves stay in this browser. Cross-device syncing is planned.
1. Prepare an agenda
Copy the prompt, replace the placeholder, then compare the output against your input before continuing.
Prompt
Using only the facts below, draft an agenda with: goal, discussion questions, decisions needed and missing information. Do not assign owners or durations. Mark proposals explicitly. Facts: [paste facts]
Illustrative input → output
Input
Goal: agree the FAQ review process. Attendees: Sarah and team lead. Known blocker: no review owner. No duration agreed.
Output
Goal: agree the FAQ review process. Discuss: What review is needed? Who can review? Decision needed: assign a review owner. Missing: meeting date and duration. Proposed agenda only; no agreement assumed.
2. Build an action register
Copy the prompt, replace the placeholder, then compare the output against your input before continuing.
Prompt
From the notes, output an action register: Owner | Action | Date as written | Agreement. Keep questions out of agreed actions. Do not turn relative days into calendar dates without context. Add open questions. Notes: [paste notes]
Illustrative input → output
Input
Sarah: I will send the FAQ draft by Wed. Team lead: I will review it Thursday. Publish Friday? No decision.
Output
Sarah | Send FAQ draft | Wed | Explicit commitment Team lead | Review FAQ | Thursday | Explicit commitment Open question: Is Friday publication agreed? No decision recorded. Exact dates need confirmation.
3. Draft the follow-up
Copy the prompt, replace the placeholder, then compare the output against your input before continuing.
Prompt
Draft a brief follow-up using only this action register. Preserve names, dates and uncertainty. Include confirmed actions and open questions separately. Do not add deadlines, promise attachments or send anything. Register: [paste the reviewed register]
Illustrative input → output
Input
Sarah | Send FAQ draft | Wed | Explicit commitment Team lead | Review FAQ | Thursday | Explicit commitment Open question: Friday publication?
Output
Subject: FAQ review follow-up Sarah will send the FAQ draft by Wed. The team lead will review it Thursday. Publication on Friday is still an open question. Please confirm the publication decision and the exact dates for the commitments above.
4. Update the weekly report
Copy the prompt, replace the placeholder, then compare the output against your input before continuing.
Prompt
Create a weekly update from the notes: completed, pending decisions, metrics available, missing information. Do not equate an agreed action with completed work; only notes of completion count. Do not invent impact or percentages. Notes: [paste this week’s actual progress]
Illustrative input → output
Input
Sarah sent the draft Wed. Team lead reviewed it Thursday. Friday publication remains undecided. No usage metrics available.
Output
Completed: Sarah sent the draft Wed; team lead reviewed it Thursday. Pending decision: Friday publication. Metrics: Not available. Missing: publication decision, exact dates and any outcome evidence.
Review before using.
- A proposed publication date is not an agreed deadline.
- A committed action is not proof of completion.
- Do not infer metrics, saved time or business impact.
- Remove personal and confidential details; follow your employer's tool policy.
Compatibility: plain text for general chat assistants. Output and availability vary by tool and plan.
Evidence: illustrative examples reviewed for fidelity, not recorded external AI executions. Model-specific testing is pending.
Reviewed: 18 September 2026.