How do I turn a useful idea into a client resource I can review?

Name the person’s task and the question the packet should answer before choosing a format.

Mark the exact unsupported or unclear sentence. Explain the defect so you can check whether the revision fixed it.

Keep the original request, source facts and correction beside the final draft. Those make the next client resource easier to inspect.

# Build Along: Make and Revise One Client Resource

Current companion, prepared November 8, 2026, for the April 22, 2026 class. The exercises are editorial practice; no particular attendee outcome is claimed. No verified recording was located.

Specify the reader and the job, collect the facts, and ask for a complete first draft. Mark what is inaccurate or unclear, revise against the source, and test the final packet on a phone and in print. Save the request and the correction with the asset.

## Specify

Write a three-sentence brief for fictional agent Morgan Reed’s first-meeting packet. Name the reader, the question it answers and what a useful result looks like.

Check: One packet, not an entire CRM or marketing program.

My input:
Observed result:
Correction and next action:

## Collect source

Use the supplied process facts: discuss goals, explain the search workflow and collect next questions. Add only permitted source material you can inspect.

Check: No invented mortgage terms, market facts, legal advice, testimonials or guarantees.

My input:
Observed result:
Correction and next action:

## Brief

Ask for a one-page preparation checklist and an accompanying draft email. Include the relevant source facts, style examples and instructions for missing information.

Check: Explicitly say unknown facts must be asked about or omitted.

My input:
Observed result:
Correction and next action:

## Generate

Generate the complete draft and its structure. Keep the packet editable so you can mark corrections before anyone receives it.

Check: First output is clearly a draft; no automatic send or public host.

My input:
Observed result:
Correction and next action:

## Annotate and revise

Mark one inaccurate, unclear or unsupported passage. Explain the specific defect, request a revision and compare the new passage with the source.

Check: Compare version two against source and acceptance checklist, not aesthetic preference alone.

My input:
Observed result:
Correction and next action:

## Test and save

Check the packet on a phone and in print. Read its next step aloud, test its links and save the source, request, correction and final review state together.

Check: All placeholders removed from the usable draft; links work; audience can identify the next step. Request approval separately before delivery.

My input:
Observed result:
Correction and next action:

## Save the working record
Source, owner and date:
Exact version:
What passed:
What failed or remains unknown:
Permission needed before external use:
Next review date:

Use only the fictional process notes I supply to draft a one-page first-meeting buyer preparation checklist and an accompanying email for review. Name the reader, job and success checks first. Include the full structure. Ask about missing facts or omit them; do not invent mortgage terms, market numbers, legal advice, credentials or testimonials. Mark the weakest passage, propose one source-based correction and show the revised version. Do not send, host or publish.

No. Choose a useful asset with a clear reader and job. The practice here produces a meeting packet and draft email.

No. This April 22 Build Along also covers non-code assets. The separate April 8 class focuses on specifying and testing a small tool.

No. Use the fictional source facts or a permitted, appropriately minimized case.

Review facts, placeholders, permission and the intended recipient first. Preparing a class exercise does not authorize a send.

Neither was recovered for this occurrence. The new workbook is a current companion to the registered build-loop slide, with the historical URL and class identity preserved.