Source, ownership, and access
We make ownership clear for the company or client’s domain, hosting account, business profiles, and people authorised to approve changes. A working public URL is not enough on its own; the receiving owner also needs to know who can maintain the site and recover access.
We keep credentials, recovery codes, private keys, and customer information out of public pages and shared screenshots. Access is granted by role wherever the relevant provider supports it.
Acceptance checks
We validate the pages and interactions included in the agreed scope: responsive navigation, contact paths, product links, documentation, page summaries, missing-page recovery, and installation or offline behaviour where applicable. Visual review and functional testing are separate checks, and we record any validation that remains incomplete.
We open important addresses directly and refresh them. We review the published result on a phone and a desktop before treating the handoff as complete.
Documentation and support
Our handoff explains how the visitor-facing experience is organised, how an update is reviewed, where to check its published result, and how to report an issue. Documentation reflects the actual delivery rather than a generic workflow copied from another project.
Maintenance after delivery
We clarify which updates are included and who manages future content, releases, domain renewal, and provider settings. Ongoing monitoring, a support queue, and a service-level agreement are not implied unless they are expressly included in the agreement.