ALI REHMAN · BLANK WORKSHEET

Website handover acceptance

Use your browser’s Print / Save as PDF option, then complete the worksheet privately. This file does not submit, upload or save your answers.

No secrets here. Do not enter passwords, API keys, recovery codes, customer records or links that grant access. Use restricted evidence references and a separate approved credential vault. Even a completed account inventory is private.

Website / business

Transition scope / what is not changing

Receiving representative / authority

Outgoing operator / agreed role

Check date / environment

Agreement / evidence location reference

1. Confirm account control

V Verified · P Pending · B Blocked · N/A Not applicable, with a reason. Start untested items as Pending. A sent invitation is not verified control.

Area	Provider, owning organisation, receiving role and renewal responsibility	Check result, status, date and restricted evidence reference
Domain registrar Registration, recovery, renewal
Authoritative DNS Web, mail and verification records
Hosting / deployment Correct production project and billing
CMS users and roles Business administrator and routine editor
Email / forms Mailbox, sender and enquiry owner
Search / analytics Existing properties, verified and inherited access

RECEIVING-SIDE EVIDENCE

2. Verify what was delivered

Test in a protected environment using approved data and recipients. Staging and sandbox payment mode do not automatically stop real emails, fulfilment or connected jobs. Never test recovery by overwriting newer live orders.

Deliverable / check	What is available / check performed / environment	Result, status, evidence reference and verifier/date
Agreed files and content Sources, media, custom work and exclusions
Licences and subscriptions Permitted use, renewal owner, required replacements
Routine content editing Approved draft edit, preview and reversal
Build / protected preview If applicable: source, runtime, commands and dependencies
Backup access and coverage Matching files/database, storage, date and retention
Isolated restore What was restored and which workflows were tested
Form / booking / checkout Approved controlled result, recipient and limitations
Handover instructions Editing, support, recovery and escalation

A content XML export is not a complete WordPress backup. A repository transfer is not proof that hosting, recovery and deployment access are complete.

CONTROLLED OFFBOARDING & ACCEPTANCE

3. Close without hiding open items

Receiving administrator and recovery route verified before routine removal of old access.
Retained support users have named roles, approval and a review date.
Machine credentials, deploy keys and integrations reviewed; shared secrets rotated with dependency checks.
Search Console verification paths and inherited Analytics roles checked without removing unrelated service access.
Renewals, updates, backup checks, support hours and emergency responsibility assigned.

Pending / blocked item and business effect	Next action, responsible person and target date	Agreed limitation / workaround / decision owner

Acceptance note: We verified the items marked Verified using the recorded evidence. Pending and Blocked items remain assigned to the named people. This record covers the agreed transition only.

Scope accepted / conditions / reference to the agreed approval process:

Receiving representative / decision date

Next review / support contact reference

A name written here is not independent identity verification, a legal signature service, a security audit or proof of unperformed tests. Use the approval process in your agreement.