A website can look finished while the business still does not know who controls the domain, receives enquiries or handles updates. Handover should make those responsibilities usable. This guide focuses on the operating information a business and its developer can agree before a WordPress project is closed.
List the accounts the business depends on
Create an account inventory for the domain, hosting, WordPress administration and any connected services used by the agreed website. Record the responsible business contact and the process for granting access. Keep passwords out of shared proposals and public documentation; use an appropriate account-access or secure transfer method.
Ownership and day-to-day administration are different responsibilities. A developer may manage technical work while the business retains control of its commercial accounts. Record who receives renewal notices and who approves costs. If a third-party licence is involved, clarify whether it belongs to the business, the provider or a separately agreed support arrangement.
Match editing access to the actual job
WordPress supports different roles and capabilities. Its security guidance emphasises suitable access and ongoing maintenance. Translate that into the jobs people need to perform: publishing an article, replacing a project image, updating a service description or administering the site. Avoid distributing administrator access merely because it is the quickest way to begin.
Use a representative editing exercise during handover. Ask the content owner to update a draft, preview it and identify the publishing controls. Review longer headings, image alternatives and category selection where relevant. Training is more useful when it follows the tasks the team will repeat rather than a tour of every settings screen.
Agree backup and update responsibilities
Record what is backed up, where it is held and who can initiate a restore through the agreed hosting or maintenance process. An update procedure should identify the responsible person, the review environment and the customer paths checked afterwards. A file existing somewhere is not enough to explain how the website would be recovered.
Keep maintenance boundaries explicit. Routine updates, content changes, new features and emergency assistance are different kinds of work. Decide which are included and how requests are submitted. This prevents a simple content question from becoming an unclear assumption about unlimited ongoing development.
Write a short operating guide people can use
A practical guide can link the key editing tasks, enquiry-receiving process, support contact and renewal responsibilities. Include the location of the approved project scope so the owner can distinguish delivered functionality from a future idea. Use the business’s real account and role names without exposing credentials.
At the final review, follow an article update and a test enquiry through the intended workflow. Check that the right person can access the relevant controls and explain what happens if something fails. Record remaining issues and their owners instead of treating a visual sign-off as proof that all operating responsibilities are settled.
Your practical checklist
- Identify account owners and renewal contacts.
- Assign access around publishing and administration tasks.
- Document backup, restore and update responsibilities.
- Complete one real editing exercise and enquiry test.
Common questions
Should every staff member have administrator access?
Access should follow the tasks the person needs to perform. Review the appropriate WordPress role and any agreed custom editing controls rather than sharing a single unrestricted account.
Does handover automatically include ongoing maintenance?
Only if that work is included in the agreement. Clarify coverage, contact routes and change responsibilities separately from completion of the initial build.
Official references
Use the current official guidance alongside the planning questions in this article.
Apply this guide to your website
- Custom WordPress development ↗
- Discuss maintenance responsibilities ↗
- Understand scope, reviews and handover ↗
