# Useful — personal workflow practice

Edition 1 / 3 October 2026 / Original fictional exercise / Prepared for rehearsal

One task: turn repair-job notes into a clear customer update without turning estimates, questions or missing information into promises. Practise a brief, a checked revision and an independent repeat. This written pack does not book a session, send messages, use an AI integration or record course completion.

Use paper, a document template or an existing approved AI tool. You do not need to buy a plan. These are fictional names and notes; do not substitute private customer records without the appropriate permission. The printable HTML is read-only; write on a printed copy or copy these Markdown worksheets into your own document.

## Before session one

Chosen method/tool and access needs: [not recorded]
Current method for the task: [not recorded]
Current quality problem: [not recorded]
Current time: [not recorded — identify measured or estimated]
What a useful result must preserve: [not recorded]

## A — guided source / 3 October 2026

A1. Marlow Bench is a fictional furniture-repair workshop. Ira is the fictional customer for bench job MB-14.
A2. The workshop inspected one loose joint on 3 October. Repair work has not started.
A3. The workshop proposed replacing the joint. Customer approval is still needed.
A4. The supplier estimated AUD 48 for the part only. This is not a total repair quote or a confirmed customer charge.
A5. The part arrival date has not been confirmed.
A6. The workshop will give Ira another update on 6 October, even if the part date is still unknown.
A7. No completion or collection date has been agreed.
A8. This update should ask whether Ira approves the proposed repair. No reminder, email or booking is to be sent by this exercise.

Task: draft a warm customer email of 60–120 words. Use only A1–A8. Explain what is known, what is pending and what the customer needs to decide. Keep the update date separate from the repair/collection date. Prepare a draft only.

My four-line brief:
- Task: [not recorded]
- Source/context: [not recorded]
- Useful format: [not recorded]
- Facts, boundaries and unknowns: [not recorded]

## A — inspect this deliberately flawed draft

> Hi Ira, your approved repair is underway. The part has arrived and your total bill is AUD 48. Your bench will be finished on 5 October, so collect it that day. We have booked your collection. Thanks, Marlow Bench.

This is an authored teaching draft, not an actual AI output. Find every unsupported promise or changed fact before reading the revision below. Name its source note and your correction.

My checking record — claim / source ID / supported or unsupported / correction:
1. [not recorded]
2. [not recorded]
3. [not recorded]
4. [not recorded]
5. [not recorded]
6. [not recorded]

My own corrected draft: [not recorded]
Help received, if any: [not recorded]

## A — one authored revision

> Hi Ira, we inspected the loose joint on bench job MB-14. We propose replacing the joint and need your approval before repair work starts. The supplier’s AUD 48 estimate covers the part only; it is not a total repair quote. Part arrival is unconfirmed, so no completion or collection date is agreed. Please let us know whether you approve the proposed repair. We will update you on 6 October even if the part date is still unknown. Thanks, Marlow Bench.

This is one acceptable wording, not the only answer. It keeps inspection separate from starting the repair (A2), asks for approval (A3/A8), keeps the part estimate separate from the total price (A4), states unconfirmed arrival and completion (A5/A7), and preserves the 6 October update (A6). Review the meaning, not whether your wording matches.

## B — independent practice between sessions / 6 October 2026

Start a new document or conversation so the old draft is not your source. Use this new snapshot:

B1. This is a fresh snapshot of the same fictional bench job MB-14. Use B1–B7 for the new update.
B2. Ira approved the proposed joint replacement on 5 October.
B3. On 6 October the supplier withdrew the earlier AUD 48 part estimate. A new estimate is pending; no total repair price is agreed.
B4. The supplier now estimates part arrival on 9 October. Arrival is not confirmed.
B5. Repair work has not started. No completion or collection date is agreed.
B6. Ira asked, “Can I collect it on 9 October?” This is a question, not an agreed appointment.
B7. The workshop will give Ira another update on 10 October, whether or not the part has arrived.

Task: draft a new 60–120 word customer email. Answer the collection question honestly, reflect the approval and withdrawn estimate, and preserve the agreed next-update date. Do not copy promises from A. No messages or bookings are sent.

My brief: [not recorded]
My first draft: [not recorded]
What changed from A — with source IDs: [not recorded]
My checks and corrections: [not recorded]
My final draft: [not recorded]
What I could not resolve: [not recorded]
Help received and approximate active time: [not recorded — identify estimates]

Bring the source, first/final drafts and this checking record to session two. If you cannot use your chosen tool, use paper or a document and record the access issue. Do not change billing or buy a subscription to complete the exercise.

## Take your method with you

When I use this task: [not recorded]
Permitted source and owner: [not recorded]
Method/tool chosen and why: [not recorded]
My reusable brief or steps: [not recorded]
Facts I always check: [not recorded]
When notes conflict or information is missing: [not recorded]
Who approves sending, and what I do not automate: [not recorded]
Where I keep the source, output and known working guide: [not recorded]
My own explanation of the method: [not recorded]
Next independent attempt: [not recorded]

The proposed Workflow sprint is two 60-minute sessions, a written task guide and one clarification email within seven days of session two. Final scope and terms need founder confirmation before sale. A new task, extra call or implementation needs a separate agreement. This practice pack creates no booking or support contract.
