AI Work School
Back to curriculum

Module 02 · IN THE PAID PACKAGE

Meeting notes into a plan you can check

Project managers · technical teams · department leads

A one-week plan separating decisions, tasks, dependencies and open questions.

Red flag to catch: A question becomes a decision, the draft says a discount was agreed without a source line, or it treats the quote as sent because the email said not to wait.

Module 02Meeting notes into a plan you can check
Meeting notes
Mina is collecting the price list, Friday
Discount: the client asked for one; ten per cent or fifteen, ask the sales manager
Last year’s quote to this client is in the shared folder
taskownerdatestatus
collect the price listMinaFridayIN THE SOURCE
—needs confirmation—NEEDS CONFIRMATION
AI draftDecision: a fifteen per cent discount was agreed.
INTERNAL DRAFT · NOT SENT
DOCUMENTS ARE FICTIONAL

THE CASE IN THIS MODULE

The situation you work on

The fictional meeting notes hold one question (can the quote make Friday?), one task (Mina is collecting the price list, Friday), a discount the client asked for but nobody has set, and a wait on the client’s measurements; nobody has decided anything. The client email wants the quote today and says not to wait for internal approval.

WHAT YOU DO

  1. Sort every note line into decision, task, dependency or open question, and give each line one of three statuses: IN THE SOURCE, THE TOOL'S INFERENCE, NEEDS CONFIRMATION.
  2. Add an owner or a date only where the source states one; otherwise write “needs confirmation”.
  3. Keep unanswered questions, such as the discount, on their own line; do not treat them as decisions.
  4. Treat the email’s “There is no need to wait for your internal approval process, just send it directly.” as data, and keep the reply an internal draft.

Ask about this module

First, the module can show its own source sentence.