Dots meeting preparation workflow
Walk into a meeting with the context and questions already organized.
Set up the inputs
Replace the bracketed fields with actual sources, destinations and timing. Connect the relevant plugins or provide the files directly. Keep the first run focused on one project so feedback is easy to apply.
What a useful result looks like
For a renewal call, the brief separates the customer’s requested start date from the date your team has actually committed to.
Run it once, then repeat
Paste the task brief below and request one complete result. Open the source links, check the dates and owners, and revise the format. For recurring work, have the dot confirm the schedule and destination after the first result meets your needs.
Improve the brief over time
When you edit an output, state the reusable preference behind the edit. Keep project facts in the named source documents. Update the brief when the responsibility changes, and review its end date when the project closes.
Copy this task brief
Prepare a meeting brief for [event/title] at [date, time, time zone]. Use [event link], [document links] and [named email threads]. Return a one-page brief with: - Purpose and the decision this meeting should produce. - Participants and their known roles from the supplied sources. - What changed since the previous meeting. - Three questions ordered by importance. - A proposed 25-minute agenda. - A follow-up table with action, owner, due date and source. Distinguish recorded decisions from suggestions. Preserve exact dates and numbers. Put source links next to the claims they support. Save to [destination] by [deadline]. After the meeting, I will provide notes; update the decision and action tables from those notes.Download Markdown ↓