Skip to main content

One task, start to finish

Turn messy leadership meeting notes into a one-page team update.

Northfield Supply Co. is a fictional company.

The raw notes

  • Leadership meeting, Tuesday Oct 14. Present: Dana (ops), Marcus (sales), Priya (finance), Lee (IT), Sam (HR)
  • Warehouse move to the new Dayton site is now planned for Nov 3, not Oct 20. Dana owns the move plan, due to Marcus and Priya by Friday Oct 17.
  • Priya: budget for the move is tight and final numbers are still pending from the vendor. Do not share the vendor quote outside this group. Confidential.
  • Marcus wants to pause the new customer portal launch until after the move. Lee thinks it can launch on schedule, Dec 1. No decision. Revisit next week.
  • Sam: open enrollment starts Nov 10. Sam sends a reminder to all staff by Oct 31.
  • Lee: two people had VPN trouble last week. Not urgent.
  • Side notes: break room fridge left open again. Marcus is thinking about a new coffee vendor.

Plan

Purpose
Everyone knows what was decided and who owns what by Friday.
Limits
No pricing or vendor quotes. No customer names. Nothing marked confidential.
Audience
All staff. They need clear decisions and dates they can act on.
Needs
The raw meeting notes, and last month's update as a style example.

Prompt

Persona
You are an internal communications lead at a mid-size distribution company.
Request
Turn the meeting notes below into a one-page team update.
Objective
A reader should know what was decided, who owns each action, and what happens by Friday.
Material
[Paste the meeting notes here]
Parameters
Use only what is in the notes. Do not invent facts, dates, or names. Flag anything unclear as "Needs clarification." Leave out pricing and customer names.
Template
Three headings: Decisions, Actions (owner and date), Open questions. Plain language, under 250 words.

Proof

Find the four problems

Here is what an AI produced. None of it looks wrong at a glance. Compare it with the notes.

Team update · Week of Oct 14

Decisions

  • The warehouse move to the Dayton site is scheduled for October 20.
  • The customer portal launch is paused until after the move.

Actions

  • Dana: send the move plan to Marcus and Priya by Friday, Oct 17.
  • Sam: send the open enrollment reminder to all staff by Oct 31.

Open questions

  • Customers have been asking for the new portal for months. Should launch timing change?
  • Is the VPN issue affecting more people?

Compare the update with the raw notes above. When you have found four problems, check your answers.

Bring Plan, Prompt, Proof to your team

A hands-on workshop where everyone builds, checks and keeps a real piece of work.

For teams