Try it yourself

Give a team one reusable AI workflow

Turn a week’s scattered notes into an update the next person can use. Try it for the team or its coordinator.

You can read the complete example below without JavaScript. The choices and editable worksheet need JavaScript. You can select the text by hand.

Practice with a made-up workshop team. The examples are already written; no live AI.

Who’s reading?

From notes to a useful update

Step 1 / 3

Example response

A faithful first draft, still hard to scan

We ran 16 of 20 planned sessions in the week of 5–9 October. Four did not run because Room B was awaiting inspection, and their new dates are not agreed. We completed five repairs, leaving seven requests open after three new requests arrived. We have 20 pairs of gloves and plan to need 30 next week. Mira is asking about ten more; Tuesday 13 October is the earliest expected arrival, with order and delivery unconfirmed. On Monday 12 October, Sam will check Room B and prepare replacement-date options, and Mira will confirm supplier availability. Jo will decide whether the plan needs to change if gloves remain uncertain.

How to ask for this

Turn the source notes into a short update for the whole workshop team. Keep the facts and unknowns. This first authored version puts everything in one paragraph.

Why this works: The information is useful, but results, open issues and actions all compete in one paragraph. The next request changes the shape so people can find their part.

Explore the fictional source notes

A weekly operations update

This fictional community workshop has a useful week of notes and several loose ends. Turn them into an update the team can read, then a handoff the next coordinator can use.

Cedar Workshop · week of 5–9 October 2026

T1Sessions

Twenty sessions were planned; sixteen ran. Four did not run because Room B was awaiting an inspection. Their new dates have not been agreed. These notes do not establish whether Room B is ready to reopen.

T2Repair queue

The week began with nine repair requests. Five were completed and three new requests arrived. Seven requests remain open: 9 − 5 + 3 = 7. The team has not yet assigned dates for those seven requests.

T3Supplies

There are twenty pairs of gloves in stock. Next week’s plan calls for thirty pairs. Mira has asked the supplier about another ten pairs. The supplier said Tuesday 13 October is the earliest expected arrival, but has not confirmed the order or delivery.

T4Next decisions

Sam will check the Room B inspection status on Monday 12 October and bring possible replacement session dates to the next team check-in. Mira will ask the supplier to confirm availability on Monday. Jo must decide whether to change next week’s plan if gloves cannot be confirmed. No one should assume Room B or the extra gloves will be available.

T5People and handoff

Mira gathers the weekly notes and prepares the internal update. Sam supplies the session and repair figures and the Room B follow-up. Jo coordinates the next week’s plan and decisions. The team uses an internal channel for the shared update; Mira carries open items into the next week’s notes. This example contains no participant names or private case details.

Back to the example

Your one-page weekly-update recipe

Agree on one useful job, audience and rhythm: for example, a weekly update that helps the workshop team know what happened and what comes next.
Gather dated notes under results, open issues and next actions. Use the tools and information your organization allows, and leave out private case details.
Ask for the same short structure each week. Supply the notes and name the reader; ask for one line per action with an owner and next checkpoint.
Have the named people improve their part: the coordinator makes it readable, the operations owner checks the figures, and the plan owner adds decisions. Keep unknowns visible.
Share the agreed update in the intended internal channel. Keep its source notes and carry open items into next week. Give the next coordinator the questions they need to ask.

What makes this reusable

A fixed structure saves readers from learning a new format every week. Results, open issues and next actions each answer a different question.
A useful handoff names the next person and what they need to collect. The same source notes can support both a team message and a coordinator’s checklist.
Finish with a short check of counts, dates and uncertain statements. This authored example shows a method; it reports no measured time saving or real team outcome.

Take the complete example

The text includes the source notes and every step for the selected reader. Copy it or select it by hand. Printing includes this pack too.

Complete example text

Practice with a made-up workshop team. The examples are already written; no live AI.

A weekly operations update

This fictional community workshop has a useful week of notes and several loose ends. Turn them into an update the team can read, then a handoff the next coordinator can use.

Cedar Workshop · week of 5–9 October 2026

[T1] Sessions
Twenty sessions were planned; sixteen ran. Four did not run because Room B was awaiting an inspection. Their new dates have not been agreed. These notes do not establish whether Room B is ready to reopen.

[T2] Repair queue
The week began with nine repair requests. Five were completed and three new requests arrived. Seven requests remain open: 9 − 5 + 3 = 7. The team has not yet assigned dates for those seven requests.

[T3] Supplies
There are twenty pairs of gloves in stock. Next week’s plan calls for thirty pairs. Mira has asked the supplier about another ten pairs. The supplier said Tuesday 13 October is the earliest expected arrival, but has not confirmed the order or delivery.

[T4] Next decisions
Sam will check the Room B inspection status on Monday 12 October and bring possible replacement session dates to the next team check-in. Mira will ask the supplier to confirm availability on Monday. Jo must decide whether to change next week’s plan if gloves cannot be confirmed. No one should assume Room B or the extra gloves will be available.

[T5] People and handoff
Mira gathers the weekly notes and prepares the internal update. Sam supplies the session and repair figures and the Room B follow-up. Jo coordinates the next week’s plan and decisions. The team uses an internal channel for the shared update; Mira carries open items into the next week’s notes. This example contains no participant names or private case details.

The whole workshop team

A faithful first draft, still hard to scan

Turn the source notes into a short update for the whole workshop team. Keep the facts and unknowns. This first authored version puts everything in one paragraph.

We ran 16 of 20 planned sessions in the week of 5–9 October. Four did not run because Room B was awaiting inspection, and their new dates are not agreed. We completed five repairs, leaving seven requests open after three new requests arrived. We have 20 pairs of gloves and plan to need 30 next week. Mira is asking about ten more; Tuesday 13 October is the earliest expected arrival, with order and delivery unconfirmed. On Monday 12 October, Sam will check Room B and prepare replacement-date options, and Mira will confirm supplier availability. Jo will decide whether the plan needs to change if gloves remain uncertain. [T1, T2, T3, T4]

The information is useful, but results, open issues and actions all compete in one paragraph. The next request changes the shape so people can find their part.

Named edits that make the update easier to use

Keep the same facts. Group them as results, what needs attention and next actions. Show how Mira, Sam and Jo make the wording useful for their teammates.

Mira, update coordinator: put the week and two results first: 16/20 sessions ran; five repairs completed. Give the remaining seven requests their own place instead of burying them inside the arithmetic. [T1, T2, T5]

Sam, operations: group the four sessions needing new dates with the Room B check. Put the Monday owner and follow-up beside the issue so teammates can see what happens next. [T1, T4, T5]

Jo, next-week planning: make the glove gap visible as 20 available against 30 planned. Put Mira’s supplier question and Jo’s plan decision in the action section. Keep “earliest expected” beside Tuesday so the team can plan with that uncertainty. [T3, T4, T5]

The human edits improve order, emphasis and ownership. No new fact is needed to make this draft more useful.

A weekly update the team can scan

Apply the structure and edits. Use a short results section, open issues and one line per next action. End with the next coordinator’s handoff.

WEEK OF 5–9 OCTOBER
Results: 16 of 20 planned sessions ran. Five repairs were completed.
Still open: seven repair requests and new dates for the four sessions that did not run while Room B awaited inspection. [T1, T2]

SUPPLIES TO RESOLVE
Gloves: 20 pairs available against 30 planned for next week. Ten more are expected no earlier than Tuesday 13 October; the supplier has not confirmed the order or delivery. [T3]

NEXT ACTIONS
Sam — check Room B’s inspection status on Monday 12 October and bring replacement-date options to the next check-in.
Mira — ask the supplier to confirm availability on Monday.
Jo — decide whether to change next week’s plan if the gloves remain unconfirmed. [T4]

NEXT UPDATE
Mira carries forward the seven open requests, the four sessions needing dates and the glove question. Sam supplies the updated operational figures; Jo supplies any plan decision. [T1, T2, T3, T5]

A teammate can find the result, the issue and the person handling it. The final example also tells the next coordinator what to collect, without pretending any message was sent.

Your one-page weekly-update recipe

1. Agree on one useful job, audience and rhythm: for example, a weekly update that helps the workshop team know what happened and what comes next.

2. Gather dated notes under results, open issues and next actions. Use the tools and information your organization allows, and leave out private case details.

3. Ask for the same short structure each week. Supply the notes and name the reader; ask for one line per action with an owner and next checkpoint.

4. Have the named people improve their part: the coordinator makes it readable, the operations owner checks the figures, and the plan owner adds decisions. Keep unknowns visible.

5. Share the agreed update in the intended internal channel. Keep its source notes and carry open items into next week. Give the next coordinator the questions they need to ask.

What makes this reusable

• A fixed structure saves readers from learning a new format every week. Results, open issues and next actions each answer a different question.

• A useful handoff names the next person and what they need to collect. The same source notes can support both a team message and a coordinator’s checklist.

• Finish with a short check of counts, dates and uncertain statements. This authored example shows a method; it reports no measured time saving or real team outcome.

Adapt the recipe for your team

Fill in this worksheet with a non-sensitive example. It assembles your instructions; it does not produce an AI response. You can use the brief in an approved tool of your choice.

Your text stays in this page’s state; this lesson does not save or send it. Refreshing clears it. Copy anything you want to keep. Leave out personal or confidential data, and follow your organization’s rules in any other tool.

Your assembled brief

Recurring job and rhythm:
[To be supplied]

Readers and the people contributing each part:
[To be supplied]

Allowed source notes and open questions:
[To be supplied]

Reusable structure and next-person handoff:
[To be supplied]

Use only the supplied notes. Draft the update for the named readers in the agreed structure, then add a short handoff for the next coordinator. Keep results, open items and estimates distinct. Ask for missing owners or dates rather than inventing them. I will check and edit the wording before sharing.

Take the complete example

Practice with a made-up workshop team. The examples are already written; no live AI. A weekly operations update This fictional community workshop has a useful week of notes and several loose ends. Turn them into an update the team can read, then a handoff the next coordinator can use. Cedar Workshop · week of 5–9 October 2026 [T1] Sessions Twenty sessions were planned; sixteen ran. Four did not run because Room B was awaiting an inspection. Their new dates have not been agreed. These notes do not establish whether Room B is ready to reopen. [T2] Repair queue The week began with nine repair requests. Five were completed and three new requests arrived. Seven requests remain open: 9 − 5 + 3 = 7. The team has not yet assigned dates for those seven requests. [T3] Supplies There are twenty pairs of gloves in stock. Next week’s plan calls for thirty pairs. Mira has asked the supplier about another ten pairs. The supplier said Tuesday 13 October is the earliest expected arrival, but has not confirmed the order or delivery. [T4] Next decisions Sam will check the Room B inspection status on Monday 12 October and bring possible replacement session dates to the next team check-in. Mira will ask the supplier to confirm availability on Monday. Jo must decide whether to change next week’s plan if gloves cannot be confirmed. No one should assume Room B or the extra gloves will be available. [T5] People and handoff Mira gathers the weekly notes and prepares the internal update. Sam supplies the session and repair figures and the Room B follow-up. Jo coordinates the next week’s plan and decisions. The team uses an internal channel for the shared update; Mira carries open items into the next week’s notes. This example contains no participant names or private case details. The whole workshop team A faithful first draft, still hard to scan Turn the source notes into a short update for the whole workshop team. Keep the facts and unknowns. This first authored version puts everything in one paragraph. We ran 16 of 20 planned sessions in the week of 5–9 October. Four did not run because Room B was awaiting inspection, and their new dates are not agreed. We completed five repairs, leaving seven requests open after three new requests arrived. We have 20 pairs of gloves and plan to need 30 next week. Mira is asking about ten more; Tuesday 13 October is the earliest expected arrival, with order and delivery unconfirmed. On Monday 12 October, Sam will check Room B and prepare replacement-date options, and Mira will confirm supplier availability. Jo will decide whether the plan needs to change if gloves remain uncertain. [T1, T2, T3, T4] The information is useful, but results, open issues and actions all compete in one paragraph. The next request changes the shape so people can find their part. Named edits that make the update easier to use Keep the same facts. Group them as results, what needs attention and next actions. Show how Mira, Sam and Jo make the wording useful for their teammates. Mira, update coordinator: put the week and two results first: 16/20 sessions ran; five repairs completed. Give the remaining seven requests their own place instead of burying them inside the arithmetic. [T1, T2, T5] Sam, operations: group the four sessions needing new dates with the Room B check. Put the Monday owner and follow-up beside the issue so teammates can see what happens next. [T1, T4, T5] Jo, next-week planning: make the glove gap visible as 20 available against 30 planned. Put Mira’s supplier question and Jo’s plan decision in the action section. Keep “earliest expected” beside Tuesday so the team can plan with that uncertainty. [T3, T4, T5] The human edits improve order, emphasis and ownership. No new fact is needed to make this draft more useful. A weekly update the team can scan Apply the structure and edits. Use a short results section, open issues and one line per next action. End with the next coordinator’s handoff. WEEK OF 5–9 OCTOBER Results: 16 of 20 planned sessions ran. Five repairs were completed. Still open: seven repair requests and new dates for the four sessions that did not run while Room B awaited inspection. [T1, T2] SUPPLIES TO RESOLVE Gloves: 20 pairs available against 30 planned for next week. Ten more are expected no earlier than Tuesday 13 October; the supplier has not confirmed the order or delivery. [T3] NEXT ACTIONS Sam — check Room B’s inspection status on Monday 12 October and bring replacement-date options to the next check-in. Mira — ask the supplier to confirm availability on Monday. Jo — decide whether to change next week’s plan if the gloves remain unconfirmed. [T4] NEXT UPDATE Mira carries forward the seven open requests, the four sessions needing dates and the glove question. Sam supplies the updated operational figures; Jo supplies any plan decision. [T1, T2, T3, T5] A teammate can find the result, the issue and the person handling it. The final example also tells the next coordinator what to collect, without pretending any message was sent. Your one-page weekly-update recipe 1. Agree on one useful job, audience and rhythm: for example, a weekly update that helps the workshop team know what happened and what comes next. 2. Gather dated notes under results, open issues and next actions. Use the tools and information your organization allows, and leave out private case details. 3. Ask for the same short structure each week. Supply the notes and name the reader; ask for one line per action with an owner and next checkpoint. 4. Have the named people improve their part: the coordinator makes it readable, the operations owner checks the figures, and the plan owner adds decisions. Keep unknowns visible. 5. Share the agreed update in the intended internal channel. Keep its source notes and carry open items into next week. Give the next coordinator the questions they need to ask. What makes this reusable • A fixed structure saves readers from learning a new format every week. Results, open issues and next actions each answer a different question. • A useful handoff names the next person and what they need to collect. The same source notes can support both a team message and a coordinator’s checklist. • Finish with a short check of counts, dates and uncertain statements. This authored example shows a method; it reports no measured time saving or real team outcome.

All example responses

Example response

A faithful first draft, still hard to scan

How to ask for this

Turn the source notes into a short update for the whole workshop team. Keep the facts and unknowns. This first authored version puts everything in one paragraph.

Why this works: The information is useful, but results, open issues and actions all compete in one paragraph. The next request changes the shape so people can find their part.

Example response

Named edits that make the update easier to use

Mira, update coordinator: put the week and two results first: 16/20 sessions ran; five repairs completed. Give the remaining seven requests their own place instead of burying them inside the arithmetic.

Sam, operations: group the four sessions needing new dates with the Room B check. Put the Monday owner and follow-up beside the issue so teammates can see what happens next.

Jo, next-week planning: make the glove gap visible as 20 available against 30 planned. Put Mira’s supplier question and Jo’s plan decision in the action section. Keep “earliest expected” beside Tuesday so the team can plan with that uncertainty.

How to ask for this

Keep the same facts. Group them as results, what needs attention and next actions. Show how Mira, Sam and Jo make the wording useful for their teammates.

Why this works: The human edits improve order, emphasis and ownership. No new fact is needed to make this draft more useful.

Example response

A weekly update the team can scan

WEEK OF 5–9 OCTOBER Results: 16 of 20 planned sessions ran. Five repairs were completed. Still open: seven repair requests and new dates for the four sessions that did not run while Room B awaited inspection.

SUPPLIES TO RESOLVE Gloves: 20 pairs available against 30 planned for next week. Ten more are expected no earlier than Tuesday 13 October; the supplier has not confirmed the order or delivery.

NEXT ACTIONS Sam — check Room B’s inspection status on Monday 12 October and bring replacement-date options to the next check-in. Mira — ask the supplier to confirm availability on Monday. Jo — decide whether to change next week’s plan if the gloves remain unconfirmed.

NEXT UPDATE Mira carries forward the seven open requests, the four sessions needing dates and the glove question. Sam supplies the updated operational figures; Jo supplies any plan decision.

How to ask for this

Apply the structure and edits. Use a short results section, open issues and one line per next action. End with the next coordinator’s handoff.

Why this works: A teammate can find the result, the issue and the person handling it. The final example also tells the next coordinator what to collect, without pretending any message was sent.

Example response

A rough handoff with all the facts

Start next week with seven open repair requests and four sessions needing replacement dates. This week 16 of 20 sessions ran and five repairs were completed. Room B is awaiting an inspection check from Sam on Monday 12 October. Mira will ask about availability for ten more glove pairs on Monday; we have 20 and plan to need 30. The earliest expected arrival is Tuesday 13 October, but order and delivery are unconfirmed. Ask Jo whether the next-week plan changes if the gloves stay uncertain. Mira gathers the next notes, Sam supplies operational figures and Jo supplies plan decisions.

How to ask for this

Turn the same notes into a handoff for next week’s update coordinator. This first authored version is a paragraph rather than a repeatable structure.

Why this works: The paragraph contains the handoff, but the next person must extract it again. A reusable set of headings can do that organizing work once.

Example response

Turn the handoff into a repeatable shape

Mira: separate this week’s results from next week’s starting position. Carry the seven repair requests, four undated sessions and ten-pair glove gap into the next source packet.

Sam: write the Room B follow-up as a question with an owner and date: “Sam, what is the inspection status after Monday’s check, and what replacement dates can we propose?” Keep an unanswered question visible until the next note supplies the answer.

Jo: keep the plan decision beside the supply question: “If the gloves remain unconfirmed, what changes next week?” Use the same results / open issues / next actions headings in the next update so readers know where to look. The headings are an editorial choice for this example.

How to ask for this

Reorganize the handoff as starting position, questions for owners and next update. Show the useful edits without changing any fact.

Why this works: Changing the reader changes the job: the team needs a readable update; the next coordinator needs a starting position and questions to gather.

Example response

A handoff the next coordinator can reuse

STARTING POSITION Seven repair requests remain open, with dates unassigned. Four sessions need replacement dates; Room B’s inspection status is still to be checked. Gloves: 20 available, 30 planned, ten-pair gap. This week’s results were 16/20 sessions run and five repairs completed.

QUESTIONS FOR MONDAY 12 OCTOBER Sam — what did the Room B inspection check establish, and which replacement dates can we propose? Mira — can the supplier confirm the ten pairs? Tuesday 13 October is currently only the earliest expected arrival; order and delivery remain unconfirmed. Jo — if the gloves are still unconfirmed, what changes in the plan?

NEXT UPDATE Mira collects those answers and carries forward anything still open. Sam supplies the next session and repair counts. Jo supplies plan decisions. Reuse three headings: Results / Open issues / Next actions. End each action with its owner and next checkpoint. Check the finished wording against the dated notes before sharing in the team’s internal channel.

How to ask for this

Apply the edits. Give the coordinator a starting position, named questions and the structure to reuse next week.

Why this works: The handoff is now something another person can pick up. The structure repeats, while the facts and decisions change each week.

About this example

Original fictional source material created for this lesson by the SimpleDirect® team. Editorial review: 12 October 2026. These responses were not produced by an AI service. You can adapt this example pack.

Try another way to work

Continue with another complete example and a worksheet you can reuse.

Continue learning