A BETTER WAY TO SHARE THE WORK
Turn meeting notes into a decision record people can act on
Capture what changed, why it changed, and what happens next—not everything everyone said.
New to creating with an agent? The request will guide it through the task. Bring your notes; you don’t need to write HTML.
What makes a meeting decision record different from meeting notes?
Meeting notes describe the conversation. A decision record tells readers what was actually decided, why, who owns the next action, and what remains unresolved. An agent can draft that structure from supplied notes, but participants should verify commitments and ambiguity before the reviewed HTML record is shared.
01 / SEE THE DIFFERENCE
From a discussion recap to an actionable record
A fictional product-planning meeting. The decisions, owners, and timing illustrate the format rather than describe a real team.
We talked about the pilot, discussed documentation, and agreed there is more work to do. Marketing also had some questions.
- Decision
- Limit the first pilot to the reporting workflow. Broader onboarding is not included in this pilot.
- Rationale
- The team wants to review one complete workflow before expanding scope. This postpones feedback on the other workflows.
- Action
- Design owner: prepare a sample report for the next review. Due date was not recorded and requires confirmation.
- Still open
- Who will recruit pilot participants? No owner was confirmed in the notes.
- Not a decision
- A public launch was suggested but not approved. Do not treat it as a scheduled commitment.
Open a complete fictional HTML example, with its source notes →
Create my meeting decision record02 / MAKE IT YOURSELF
Start with the evidence. Shape the page around the reader.
Sort statements by their status
Ask the agent to separate decisions, proposals, questions, and background. A suggestion, silence after a suggestion, or a positive comment is not sufficient evidence of agreement. If the notes are ambiguous, mark the item for confirmation. This classification matters more than making the meeting sound productive.
Preserve the reason for the choice
For each confirmed decision, include the scope, rationale, and a material tradeoff from the supplied discussion. Explain which options were deferred or rejected only when that is recorded. Avoid assigning motives to participants. A useful rationale helps a future reader understand the conditions under which the choice made sense.
Make the next actions specific
Write each action as an observable deliverable with its confirmed owner and due date, if agreed. Keep a missing date visible instead of choosing one. Separate actions from desired outcomes: prepare a sample is an action; improve adoption is a goal. Link to the existing task record when one is supplied.
Confirm before distributing
Have the appropriate participants verify decisions and commitments. Remove private discussion, unnecessary personal information, and restricted links. Lead the HTML page with what changed, then actions and unresolved issues. Apply your saved style if available without letting color imply approval. Share after review, and clearly label later corrections or superseding decisions.
03 / TRY THIS PROMPT
Copy this into your agent. Add your source material.
Use the conversation where you already did the work, or start one with your notes. Replace the placeholders and supply any missing context; only attach information you are allowed to share with your agent.
Get the ready-to-copy creation request for guided questions, this task, and a draft review before anything is published.
Turn the supplied meeting notes into a concise decision record as static HTML. Lead with confirmed decisions and what changed. For each decision include its scope, recorded rationale, and important tradeoffs. Then list agreed actions with the exact owner and due date when supplied, followed by unresolved questions. Keep proposals separate from decisions. Do not infer agreement from silence, invent commitments, assign missing owners, or create deadlines. Mark ambiguous items for participant confirmation. Link to supplied authoritative task or decision records where appropriate. Remove confidential discussion and unnecessary personal details. Apply my saved artifact style if available, with readable headings and restrained emphasis. No scripts or forms. Return a review draft; wait for approval before publishing or changing access.
04 / BEFORE YOU SEND
A polished page still needs your judgment.
- Does each decision have clear evidence of agreement in the notes or participant confirmation?
- Are proposals and unresolved questions visibly separate from confirmed decisions?
- Have owners and dates been verified instead of inferred by the agent?
- Does the record respect confidential discussion and point to the team’s authoritative records?
When HTML fits
A compact handoff for people who attended and colleagues who need the outcome without reading a transcript.
When another format fits better
A replacement for required formal minutes, legal records, approvals, or task tracking. A published action list does not assign or synchronize tasks in another system.
FROM DRAFT TO A LINK
Make it clear. Make it yours. Then share it.
Keep creating and revising in the agent you already use. With a compatible connection, share/artifacts publishes the reviewed HTML so you do not have to rebuild it in another editor. Ask your agent to use your saved artifact style for headings, color, and tone; review the result before sending it.
Choose who should be able to open the page and verify the returned link. For corrections to the same deliverable, update the existing artifact without changing its link. Publish a separate artifact when the old edition needs to remain available.
These are static pages, not live apps: no scripts, forms, or automatic data refresh. Source collection and scheduling depend on your agent and its available tools, not on share/artifacts.
Make this with my agentQuestions before you start
Should I include the full transcript?
Usually the decision record should stand on its own. Link to an approved transcript only when readers need it and are permitted to access it. Do not publish a transcript simply because an agent used it as source material; it may contain unrelated or confidential discussion.
What if no decision was made?
Say so. A useful record can state the question, the options discussed, what information is missing, and the agreed next step if there is one. Do not manufacture a conclusion to fill the template. An honest open question is more actionable than false certainty.
How should a later decision be recorded?
Keep the original context understandable and mark the earlier decision as superseded, with a date and a link to the new record when available. For a correction, explain what changed. Do not silently rewrite history when readers may have acted on the earlier version.