# Client project handover

Version 1, 29 October 2026. Copyable service-project template and fictional worked example. This is an operational record; it does not replace the contract, transfer intellectual property or establish legal acceptance by itself.

## Copy and fill in

- Project / client:
- Handover version and date:
- Delivery owner / receiving owner / approver:
- Agreed scope and exclusions (link the agreement):
- Delivered items (version, location, check result, approver):
- Open issues (impact, owner, next action, due date):
- Access transfer (system, recipient, role, verified date; no secrets):
- Maintenance and support boundary (what, who, until when):
- Recurring costs / renewals / account owner:
- Approval request (what is being accepted, by whom, by when):
- Actual response and next checkpoint:

## Worked example: Juniper website refresh

All entries below are fictional. In your copy, replace every assumed date and result with evidence.

- Packet v1, 20 November 2026. Delivery owner: Alex. Receiving owner: Casey. Approver: Rowan.
- Scope: five pages in the existing CMS, two revision rounds, handover guide and training call. Ecommerce and copywriting excluded. CR-01 (sixth page) deferred on 11 November; no added page is included here.
- Deliverables: Home, Services, About, Work and Contact, build v1.3; guide v1.0. Insert actual private links, with access checked for Casey. Example checks: mobile/desktop review completed and contact form delivery confirmed by Alex on 19 November. Attach the actual check record before using this claim.
- Approval: Rowan's response is pending. Request review of build v1.3 and the listed exceptions by 23 November. No response is not approval.

| Open item | Impact | Owner | Next action / target |
| --- | --- | --- | --- |
| Client team photo missing | About page retains the approved placeholder | Casey | Supply licensed image by 23 Nov; Alex confirms whether replacement is within agreed support |
| Sixth page request | Outside original five-page scope | Rowan | Decide whether to request a separate quote at the 27 Nov check-in |

## Access transfer

Invite Casey to the client's own CMS account using a named account and the appropriate role. Ask Casey to sign in and confirm the required actions work. Record that confirmation and its date. Revoke temporary studio access only after the handover and any agreed support need are resolved. Never paste a password, API key, recovery code or private login link into the packet.

Confirm who owns the domain, hosting subscription, analytics property and form inbox. Record renewal dates and the client's billing owner without storing payment-card data. A list of URLs alone does not transfer ownership.

## Support and acceptance

Illustrative support boundary: questions and fixes to agreed deliverables until 4 December; new pages and ongoing content updates require a separate agreement. Copy the actual terms from your signed agreement instead of adopting this example blindly.

Draft message: "Rowan, please review build v1.3 and this handover packet. The team photo is the only listed delivery exception; the sixth page remains a separate request. Please confirm acceptance or list the changes needed by 23 November. Casey, please confirm that you can access the CMS and guide. We will record both responses and the owner of any remaining work."

Before closing the project, save the actual responses. If acceptance is withheld, keep the relevant task open and record the next action. Do not replace a missing response with an assistant-generated approval.