BENCH & PAPER / SAMPLE 01 · ILLUSTRATIVE REPORT
A delivery reply
with the right boundaries.
A fictional furniture-shop pilot. The replies below were written to demonstrate the review format. No named model was run, and no time savings or tool ranking are claimed.
1. The task and current method
The owner answers delivery enquiries by reading the email, checking the diary and confirming the installation cost. The proposed change is to help draft the first reply while keeping checks and approval with the owner.
Material for a real pilot: 5–10 authorised, anonymised examples, the delivery rules, and an agreed definition of a useful answer.
2. One reply, reviewed
Customer request: “Could you deliver and install the shelves by Friday?” No postcode, availability or installation price is supplied.
Draft without the rules
“Yes, we can deliver and install your shelves by Friday. Installation is included.”
Draft using the context
“Thanks for getting in touch. What is the delivery postcode? I’ll check availability and the installation cost before confirming a date.”
| Business check | Without rules | With context |
|---|---|---|
| Asks for the postcode | Missing | Present |
| Waits for a diary check | Promises Friday | Date unconfirmed |
| Uses a confirmed price only | Invents “included” | Price unconfirmed |
3. Sample recommendation
Use the instructions to draft. Keep availability, price and sending with a person.
The second authored reply meets the three checks in this example. It is not evidence that a particular tool will behave reliably on new enquiries. The business context and review checklist provide a starting structure for testing.
- Keep
- The existing diary and the owner's final approval.
- Add
- A reusable context file, drafting instructions and a short review checklist.
- Do not automate yet
- Sending, scheduling, price confirmation or payment.
4. What the real comparison records
Your report compares the current method with the agreed tool options on the same examples. Each record identifies the tool/model, date, settings, context version, exact output, rule failures, edits needed, review time and cost. Test time includes checking and correction, not just draft generation.
The chosen setup is explained against your priorities. If no option gives a useful improvement over the current method, the recommendation says so. Ongoing subscriptions and API charges are identified separately from the pilot fee.
The accompanying CSV includes this illustrative review and five unrun test scenarios. Blank fields are deliberately unmeasured.
5. Handover and limitations
You keep the business context, reusable instructions, test sheet, report and usage guide. One clarification revision is included in the pilot. Changes to business rules, tool versions or the scope may require new tests.
A small sample cannot establish reliability for every customer request. Continue human review; pause use if the setup repeatedly breaks a critical rule. Connecting email, calendars or other systems needs a separate scope.