From a loose brief to a usable website handoff

“Build a better website” is an understandable request, but it leaves almost every decision open. A useful project record narrows the task: who is visiting, what they need to do, what will be checked and who will maintain the result. This guide uses a fictional repair workshop to show how those decisions fit together.

01 / Make the brief small enough to finish

Cedar Workshop needs a visitor to request a repair assessment. The first version does not need a customer portal, online payments or a booking calendar. Its main job is to explain the service and collect enough information for a reply.

When a new feature is suggested, ask whether it helps the agreed visitor task.

Visitor task: Decide whether the workshop handles the repair, then send a short assessment request.
Initial scope: Service description, accepted repair types, enquiry form and a confirmation message.
Outside this version: Payments, customer accounts and live appointment availability.

Put this in the project brief before discussing colours or page sections. When a new feature is suggested, ask whether it helps the agreed visitor task. Record changes to scope instead of quietly allowing the project to expand.

02 / Turn each promise into a check

The launch review should describe an observable result. “The form works” is too broad. Split it into submission, confirmation, delivery and reply. Those are separate steps and can fail independently.

1. Submit one clearly marked test enquiry with the receiving owner’s agreement.
2. Read the confirmation and check that it makes no promise the business cannot keep.
3. Have the owner confirm arrival in the intended inbox.
4. Reply to the test address and confirm that the reply arrives.

If you can observe only the confirmation, record only that part as verified. Leave delivery and reply as unverified until someone checks them. The workbook is a record of your review; it does not perform these checks automatically.

03 / Preserve the difference between a finding and a guess

Suppose the enquiry confirmation appears, but the owner has not checked the inbox. That is an incomplete check, not proof of an email failure. If the owner checks and cannot find the test, write down the exact test time, visible result and receiving address in the private project record. Keep personal addresses out of public screenshots.

Finding: Confirmation displayed after the marked test submission. Receiving owner could not locate that test message.
Impact: Enquiry delivery is not yet verified for launch.
Next action: Investigate the delivery path and repeat the same test.
Recheck: Record the new result and date after the change.

A clear issue record lets another person continue the investigation without treating an assumption as a diagnosis. For more detail, read how to write a product issue someone can fix.

04 / Give the owner a task, not just a document

For Cedar Workshop, the handoff exercise is changing a service description and checking it on the public page. Ask the owner to perform that change using the instructions. If the owner cannot find the editing control, improve the instructions while you are still together.

Record who owns the website account, where recovery instructions are kept, which issues remain open and what support is included. Do not put passwords, recovery codes or payment information into the workbook. Those belong in an appropriate private credential system.

Save the record before you close it

The paid workbook opens as a self-contained HTML file in a desktop browser. It has 21 fields across the four sections above. Entries are not automatically saved. Use its JSON export to keep a copy before closing, then restore that copy when you return.

1. Unzip the download and open the HTML workbook.
2. Complete the relevant fields using your own project details.
3. Export a JSON copy and store it with the project.
4. Reopen the workbook and restore that copy to check your saved work.

Use a project name and date in your saved filename so you can recognise the latest copy. The file stays useful only if the next owner can find it. Shared copies should contain the minimum information needed for the handoff.

Choose the format that fits

The free toolkit includes editable Markdown worksheets, a CSV issue log and a fictional worked example. The paid workbook combines four sections into one browser-based workspace with JSON save and restore. It was listed at CA$9, one-time, on 23 September 2026; check the store for the current total and terms. Digital download; no consulting or certification included.