Back to the libraryWorkflow cluster / 02

Work updates that say what changed, what matters, and what happens next.

Practical AI writing workflows for project updates, first drafts, and follow-up messages that preserve context, ownership, and open questions.

How to use these guides

Write toward a reader's next decision.

These guides help turn working notes into clear communication. They keep the difference between a draft, an agreement, a request, and a confirmed next step visible.

Start with the task that already has enough context to inspect. Treat the generated output as a working surface, keep uncertainty visible, and use the related guide only when it helps the next human decision.

Suggested order

Read from raw notes to a responsible send.

Each step uses the output of the previous step as its starting point. Stop when the reader, decision, and next action are clear.

Path progress0/8 checks · 0%
Check each item as you go
01 / FRAME

Give the task a brief

Input: audience, context, constraints, and desired output.

Output: a reviewable brief with missing facts visible.

Start with brief-first prompting
02 / DRAFT

Shape the project update

Input: the brief plus dated progress notes, risks, decisions, and one ask.

Output: an update separating progress, risk, decision, and next step.

Draft a clear update
03 / FOLLOW UP

Confirm what was agreed

Input: confirmed notes, owners, dates, and unresolved questions.

Output: a follow-up that does not turn suggestions into commitments.

Write the follow-up
04 / DECIDE

Make the request clear

Input: rough notes, options, evidence, recipient, and the decision needed.

Output: a decision-ready email with a specific request.

Prepare the decision email
Start from records you can inspect. Make owners, sources, and limits visible. Review before a draft becomes a commitment.
Filed in this topic
Writing8 min read
Verified field noteReviewed 4 Sep 2026

Turn rough notes into a decision-ready email

Use AI to organize a messy update into context, options, a clear request, and the details a recipient still needs to confirm.

BoundaryUse when you can name the reader and goal.

EverydayOpen record