Handover · 21 Nov 2026 · 7 min read
Website documentation: what to ask a developer to hand over
A finished website without documentation is a risk waiting for a bad day. Here is what to request and how to check it before the final payment.
The short answer
A website handover pack should record what was built, where it lives and how to run it. It should include account and ownership details, access arrangements, platform and plugin lists, backup and update routines, how content is edited, a record of tracking and integrations, and known issues. Check it by asking someone new to use it.
Why website documentation is worth asking for
Website documentation is the written record of how your site is put together and how to look after it. It matters most on the day something goes wrong, or the day the person who built the site is no longer available. Without it, the business depends on one person's memory, and finding out what a site needs can cost more than building it did.
Developers do not always offer it, and clients do not always ask. Documentation takes time to write, and it can feel like an extra at the end of a project. It is better to treat it as part of the deliverable, agreed in the brief at the start. Our guide to writing a website brief for a developer shows where to put it, and the earlier the request, the easier it is for the developer to collect the details as they work.
Think of documentation as insurance with two uses. It lets you change supplier without panic, and it lets a new member of staff get up to speed. It does not need to be long. A clear, short pack that is accurate beats a thick one that nobody can follow.
What should a handover pack include?
The following list covers what most small business sites need. Not every item applies to every site, so tick off the ones that do and ask about anything that is missing.
| Area | What to ask for |
|---|---|
| Ownership | Who is the registrant of the domain, who holds the hosting account, who owns the code and designs, and who owns any paid licences |
| Overview | The platform, theme and framework used, with versions, and a plain description of how the site is structured |
| Access | A list of every system the site uses and who can sign in, without the passwords themselves in the document |
| Content | How to edit pages, add posts, change menus and manage media, with short written steps or screenshots |
| Plugins and services | Every plugin, extension and third-party service, what it does, whether it is paid and when it renews |
| Hosting and domain | The host, the plan, the server settings that matter, DNS records and the renewal dates |
| Backups and updates | What is backed up, how often, where copies are kept and how to restore one, plus the update routine |
| Tracking and integrations | Analytics and tag set-up, forms and where they send messages, payment and email connections |
| Design assets | Logo files, fonts, colours, images and design files in their original form |
| Known issues | Open problems, workarounds, things deliberately left undone and ideas for later |
Ownership comes first because everything else depends on it. If the developer holds the domain or the hosting in their own name, no other document makes up for it, and our guide to who should own your domain, hosting and code explains how to correct that. For sites with technical depth, ask also for the code repository, an explanation of how to build and deploy the site and a list of the settings or environment values needed.
Where should logins be stored?
Not in the documentation itself, and not in an email or a chat message. Passwords written into a handover document travel wherever the document goes, and are hard to take back. The document should say which accounts exist and who can sign in, and a separate, secure system should hold the credentials.
A password manager designed for businesses is the usual answer. It lets you share access to specific items with named people, record who changed what and remove access in one place when someone leaves. Check the current documentation of whichever one you use for how sharing and recovery work. Where a service supports it, use separate named accounts for each person instead of one shared login, and turn on two-step sign-in. Shared logins make it impossible to tell who did what, and they cannot be removed from one person without changing everything for the rest.
Keep a recovery route. Someone in the business should hold the master access to the password manager, and the recovery details should be stored safely offline or with a second trusted person. If a single developer's vault holds everything, you have moved the problem, not solved it. Include a note in the pack naming where credentials live, who administers them and how to request access. The same principle applies to analytics accounts, and our guide on who should hold the keys to analytics explains it in detail.
How do I check the documents are enough?
The test of documentation is whether someone who was not involved can use it. Before you accept the handover, try these checks.
- Ask a colleague who has never worked on the site to follow the content editing steps and publish a small change.
- Pick three tasks that might arise, such as restoring a backup, adding a new user and finding where contact form messages go, and see whether the pack explains each.
- Compare the list of plugins and services with what is actually installed, and ask about any that are missing.
- Confirm that you can sign in to the domain, hosting, analytics and any other account yourself, using your own details.
- Ask what would happen if the developer were unavailable tomorrow, and see whether the answer is covered in writing.
- Check that dates are listed: renewals, licence expiries and the date the document was last updated.
Treat gaps as a normal part of the process. Few first drafts are complete. Ask the developer to fix them, and agree how long that will take, ideally before final payment. A short session where the developer walks you through the site by screen share, which you record, is a useful companion to the written pack. Many questions answer themselves when someone explains the site aloud.
If your site is going live with a big event or launch, ask also what happens under unusual load. Our guide to handling traffic spikes on your website lists what to plan, and an event website often needs these notes more than most.
Keeping documentation alive
Documentation is only useful while it is true. A pack written at launch will be out of date within months as plugins change, staff come and go and services are added. Treat it as a living document. Give it an owner, put it in a shared place, and update it when something significant changes. A short change log at the top makes it clear what is current.
Agree who updates it. If an agency maintains your site, make the update part of the service, and ask to see it at regular intervals. If you maintain the site yourself, add a documentation check to your routine. A yearly review, with a calendar reminder, is a realistic minimum.
Include the people side, too. List who is responsible for what, who to contact for hosting problems, who approves content and who decides about budget. When a supplier changes, keep the old documentation, and ask the new supplier to review it and fix errors. Testing is part of the picture as well: a record of the browsers and devices checked, as described in our guide to cross browser and device testing, helps the next person know what was covered.
Putting it in the contract
The easiest time to get documentation is before the work starts. Ask for it in the brief or the agreement, say what it should contain, and state that final payment depends on its delivery and your check. A developer who does this routinely will have a template and will not mind. One who resists is giving you information.
Say in the agreement that the business owns the finished work, the content and the designs, and that the code is handed over in a usable form. The wording of contracts and intellectual property differs by country, so ask a qualified lawyer to review yours.
Finally, set up something to watch the site once it is handed over, such as uptime monitoring with alerts, and record it in the pack. If you are planning a new build and want documentation, access and ownership handled properly from the start, the website development service at Liftup Technologies is a place to begin the conversation.
Related guides
- Website development
- Event website what it needs
- Handling traffic spikes on your website what to plan
- How to write a website brief for a developer
- Browser and Device Testing: What to Check Before Launch
- Website Uptime Monitoring: How to Set Up Alerts
Questions and answers
What should a website handover pack include?
Ownership details for the domain, hosting and code, a description of the platform and structure, a list of accounts and who can use them, steps for editing content, every plugin and service with renewal dates, backup and update routines, tracking and integrations, design files and known issues.
Where should website logins be stored?
In a business password manager with named access and two-step sign-in, not in the handover document, email or chat. The document should say which accounts exist and who administers them. Make sure someone in the business holds the recovery access.
How do I check the handover documents are enough?
Ask someone who was not involved to follow the steps, such as editing a page, restoring a backup and finding where form messages go. Confirm you can sign in to every account yourself and compare the plugin list with what is installed.
Should I ask for the source code?
Where the site is custom built, yes, along with instructions for building and deploying it. For a standard platform, you need the theme, plugin and settings details more than raw code. Ask your developer what applies.
When should I ask for documentation?
At the start, in the brief or agreement, so the developer can collect details as they build. Asking at the end often produces a rushed document. Make final payment depend on delivery and on your check.
How often should documentation be updated?
Whenever something significant changes, and reviewed at least once a year. Name an owner and keep it in a shared place so it does not go out of date unnoticed.
Tell us what you are building.
A short call, a written plan and a fixed quote. No obligation.