← The session and what comes next
The chosen job. Ready to build.
A build plan names the input, the output and the checks for one recurring job. This sample shows a proposal moving from source notes to an approved draft. It includes the things that stop the job, so a person can see what still needs them.
This is a fictional example. Birch Books, the people and the records below are invented. No client result, measured pass rate or time saving is claimed.
The job on one page
Job: turn a checked discovery call transcript into a proposal draft.
Owner: Jo, the fictional delivery owner. Jo approves scope and the exact version before sending. Lee, the fictional engineer, can stop the job and investigate a failed run.
Starts: an approved transcript and current scope notes are available.
Finishes: the reviewed proposal is sent once to the confirmed contact, with the message reference recorded. This sample stops at the held draft; no real message is sent.
Outside the job: setting prices, making new promises, signing agreements, taking payment and granting client access.
Input to finish
| Step | Who does it | Output |
|---|---|---|
| Validate required source fields | Fixed check | Accepted input or a specific missing-field hold |
| Extract promises and questions | AI drafts | A fact sheet with source references |
| Check facts against source | Jo reviews | Corrected, approved fact sheet |
| Write the proposal | AI drafts | Versioned proposal draft |
| Check scope, recipient and commitments | Jo approves | Approval tied to the exact version |
| Send once and record the reference | Approved sending tool | Confirmed destination and message reference |
The detailed proposal example contains a source excerpt, a checked fact sheet and a complete draft.
The baseline and the success number
For a real job, record the period, number of runs, total person-minutes, corrections and exception count before changing anything. Name the source and the person who reads it. Pick the result you want to improve and agree when to compare it.
In this sample those fields are not measured. Use the cost calculator to estimate today's labour cost from your own inputs. An estimate is not evidence of money saved.
Exceptions stay visible
| Exception | What happens | Frequency |
|---|---|---|
| Start date missing | Hold the date; ask Jo | Not measured |
| Two conflicting scope versions | Stop; Jo chooses the authority | Not measured |
| Contact does not match the approved record | Stop before sending | Not measured |
| Send result uncertain | Inspect destination before retrying | Not measured |
| Draft changes after approval | Cancel approval and request a new check | Not measured |
Count affected runs as well as exception types. One run can contain several exceptions. Keep the denominator and observation period beside any percentage.
The check sheet
These are test cases to run, not test results. Keep the same input set for a later comparison.
| Case | Expected result | Actual result |
|---|---|---|
| Complete source and matching contact | Correct draft ready for review | Not run |
| Missing date | No invented date; visible hold | Not run |
| Conflicting price notes | No chosen price; visible hold | Not run |
| Wrong contact | Sending blocked | Not run |
| Edited approved draft | Earlier approval invalid | Not run |
| Repeated source event | Existing run found; no second send | Not run |
For each actual run, record pass, fail or not run; the reason; source and output versions; and reviewer. Mark a costly mistake separately. Agree the pass line and the costly-mistake rule before use. A high average must not hide a wrong-recipient send.
Permissions, stop and recovery
Read access covers only the approved source folder and contact record. Drafting access does not grant sending access. Jo owns the approval. Lee owns the stop control. Both must know where it is before a real job starts.
Stop new runs if a source changes shape, a contact mismatch appears or the sending result cannot be confirmed. Preserve the input, output and last confirmed action. Check the destination. Correct the cause. Rerun the failed case and nearby cases. Jo approves restarting. Do not delete failed records or retry an uncertain send blindly.
A readable action log
The following is an illustrative sequence, not a record of a real run:
- Source version A accepted for sample run DEMO-01.
- Fact sheet version 1 drafted. Start date missing.
- Jo asked to confirm the date. Run held.
- No approval recorded. No proposal sent.
A real row also needs the time, person or tool, input reference, output reference and reason. Record attempted, confirmed and failed actions separately.
The handover
The owner keeps the instructions, access list, check sheet, action log and recovery steps. The handover records what shipped, what remains held and any support agreed in the scope. It also names the next three candidate jobs without treating them as booked work.
For this fictional business the candidates are client onboarding, monthly reporting and support replies. Each needs its own inputs, owner and checks.
Use the Job Picker to choose a real first job. Read how the work is built and handed over, or join the waitlist.