Nothing locked in, nothing left unexplained
A CMS is complex software, and hosting and development processes can be involved. Without them documented, your team depends on whoever built the site.
We build on open-source Drupal with no vendor lock-in, and we hand over the documentation that lets anyone, including a future provider, take over.
What you get:
- Confidence in what was delivered. Stakeholders can see the quality and completeness of the project.
- A technical team that can work on the site. Documentation covering how it's built and how it runs.
- Freedom to choose. Change provider or bring work in-house without starting from scratch.
Our approach to site handover
Document the content model
The types of content, their fields, and how they relate, so future changes stay consistent.
Write the functional specification
A record of what the site does, including custom functionality and integrations.
Document key systems and build processes
How the site is hosted, developed, and released, so a technical team can work on it in a practical way.
Hand over access and control
Credentials are transferred, not shared. Code, configuration, and content sit in your organisation's control, not tied to our infrastructure or accounts.
Explain it to the people who need it
Stakeholders and technical staff each get what they need. If editor training wasn't part of the project, we can add it. After handover, support and maintenance are available if you want them.
Frequently asked questions
A thorough handover documents the content model, custom functionality, and integrations. It also covers editor training if it wasn't delivered, a clear picture of hosting and support arrangements, and ideally a transition period where the outgoing team can answer questions. Incomplete handovers are a major source of risk when an agency changes provider or brings work in-house.
That all code, configuration, and content are in your organisation's control and not locked to the agency's accounts or infrastructure. That documentation exists for anything custom. That nothing stops a future provider from taking over. And that access has been transferred, not shared.
Yes. The documentation and knowledge transfer are the same whether you move to another supplier or build your own team. The risk of knowledge leaving with the outgoing team is the same either way.
Case studies
