HIGHENDPBN

PBN / GUIDE

PBN handover: access and maintenance

Network ownership starts with control of domains, files and backups. Agree the handover scope before building, not on delivery day.

HIGHENDPBN01DOMAINS02CONTENT03TECHNICAL04HANDOVER
PBN handover: access and maintenance: Confirm ownership → Preserve recovery → Separate one-off and r

Confirm ownership

For each site record registrar, DNS, hosting, CMS and licence ownership. Specify what transfers and what remains a managed service. A shared folder is not a substitute for control of the domain.

Preserve recovery

Receive source files, a database export where applicable, images and startup instructions. Test restoration in a separate environment. Record the build version and backup date.

Separate one-off and recurring work

Builds, registration, hosting, renewals, content updates and support are separate cost lines. Agreements should specify frequency, price and how maintenance can be ended.

The first 30 days

Use a checklist: verify access after handover; recheck pages and backups after a week; review costs and changes after a month. This is a suggested control schedule, not a promise of free maintenance.

Use this procedure as a project checklist. The exact service scope belongs in your agreed brief.