Illustrative page set
- Home: offer, service area and primary action.
- Services: maintenance and seasonal tidy-ups.
- About: approved story and permitted imagery.
- Contact: agreed inquiry route and expectations.
AFTER THE DESIGN / ILLUSTRATIVE HANDOVER
A website should
come with
clear ownership.
This sample pack shows the questions a handover should answer: what was built, what can be edited, who owns the accounts and who handles the next request.
Open the sample pack ↓SITECCO / SAMPLE DOCUMENT SETWillow
Garden Care
Garden Care
01 Scope & acceptance
02 Everyday editing
03 Access & ownership
04 Care & responsibilities
FICTIONAL EXAMPLE · NOT A SERVICE AGREEMENT02 Everyday editing
03 Access & ownership
04 Care & responsibilities
READ BEFORE USING
A sample handover guide.
Willow Garden Care is an invented business. This is a proposed structure for a future project handover, not a delivered client pack. Scope, charges, revisions, support hours, response times and ongoing services would need a separate written agreement. None are promised here.
Showing sample scope and acceptance.
SAMPLE 01 / SCOPE & ACCEPTANCE
Know what is included.
Before acceptance
- Owner approves copy, imagery and claims.
- Check navigation and layouts on agreed devices.
- Confirm where each form or booking action goes.
- Record outstanding issues and decisions.
Not implied
A design example does not include live scheduling, payment processing, ongoing edits, legal review or a support plan. These need explicit scope and any required provider setup.
Decision record
For a real project, list each deliverable, approval owner, acceptance check and unresolved item. Record dates when agreed—not invented dates or assumed sign-offs.
SAMPLE 02 / EVERYDAY EDITING
Small changes, made deliberately.
- Find the right source.How you update your website is part of the plan. This example shows the handover information; a content editor would be selected and set up separately.
- Change content before layout.Update the approved text, service area or permitted image. Keep heading structure and meaningful link labels. Avoid pasting private customer records into the site.
- Preview before publication.Check desktop and phone widths, spelling, image cropping, links and any related pages. A saved local edit is not a published change.
- Keep a recovery copy.Record what changed and retain the previous approved version. Agree who can publish and how a mistake will be rolled back before launch.
Know where to make changes.
A real handover should identify the selected editor, source repository or hosting dashboard, the exact editable sections, image guidance and publication steps. This sample contains no account logins or production instructions.
SAMPLE 03 / ACCESS & OWNERSHIP
The business keeps the keys.
Business-controlled registration
Record the registrar, account owner, renewal responsibility and recovery contact. Do not assume design work transfers a domain.
Document access and portability
Agree who owns and can access the site files, hosting account, backups and deployment history; document any platform or license constraints.
Client-owned provider accounts
Booking, payment and email providers require separately authorized setup. The business controls its account and operational settings; grant only the access needed.
No passwords in the handover
Use an agreed secure access-sharing method, record who has access, and remove unneeded permissions. Keep recovery codes and payment credentials out of source files and chat.
These are proposed ownership principles, not evidence that any account has been created, transferred or connected.
SAMPLE 04 / CARE & RESPONSIBILITIES
Make the gaps visible.
Business owner
Approves business information and claims; answers inquiries; manages customer commitments, provider accounts and renewal decisions.
Project provider, if agreed
Delivers the approved scope and documents changes. Maintenance, monitoring, additional edits and issue response require defined arrangements.
Third-party platforms
Operate their own services under their own terms. Availability, charges and provider changes are not controlled by this showcase.
Before calling a site “supported”
- Name the contact channel and the person responsible.
- Agree what counts as a defect versus a new request.
- Define coverage, response expectations and any charges.
- Agree how urgent incidents, backups and recovery are handled.
- Document what happens when an arrangement ends.
A HANDOVER READINESS CHECK
Ready means understood.
Try this illustrative checklist. Checks live only on this page and do not record acceptance or notify anyone.
0 of 4 sample checks reviewed.
GOOD QUESTIONS BELONG IN THE PLAN
Start before the handover.
Capture your goals now. Keep ownership, content and ongoing responsibilities part of the conversation.
Preview your website plan →Explore website essentials