Skip to content
Godwin LawsonBUILDING WITH PURPOSE

Web Development

What Should a Website Developer Hand Over When Your Project Is Finished?

What Should a Website Developer Hand Over When Your Project Is Finished?

A website developer should hand over the access, materials, instructions and support information agreed for your project. Depending on the scope, this can include website accounts, domain and hosting arrangements, custom code, permitted design assets, licence details, backups, training and renewal records.

The exact package depends on what was commissioned and the ownership or licence terms. A custom website, a managed subscription service and a site built with third-party software do not necessarily have identical handover arrangements.

Agree those arrangements before development starts, then use a checklist to confirm them when the project closes.

Start with the agreed scope

Review the proposal and delivery record. Identify the pages, functions, content, integrations and training included. Record any approved changes and outstanding work.

A handover should make it possible to distinguish delivered work from unresolved issues. Do not rely on a vague statement that the site is complete when an important enquiry route or required integration has not been checked.

For organisations commissioning educational websites, my guide to choosing a school website developer includes ownership and delivery questions to address at appointment.

1. A clear record of accounts and access

Identify the relevant domain registrar, hosting provider, website administration, business email and external services. Record the authorised account owner and the appropriate contact for each one.

Access should reflect responsibilities. A staff member publishing announcements may need a different role from the person maintaining software. Where the provider manages a service, document how your organisation requests changes and how that arrangement can end.

Use a secure handover process. Do not ask the developer to post credentials in a public document or a general group conversation. Confirm recovery arrangements without circulating private recovery material unnecessarily.

2. Domain, hosting and renewal information

Know which domain the website uses, who controls the account, when it renews and who pays. Make the same checks for hosting and business email.

If the provider registered a service on your behalf, clarify the agreed ownership and management arrangement. The important point is that your organisation understands the relationship and can maintain continuity.

Item Useful handover record
Domain Provider, authorised owner, renewal date and responsibility
Hosting Plan, billing period, managed responsibilities and support route
Business email Service owner, administration arrangements and renewal terms
Paid software Licence owner, permitted use, renewal cost and effect of expiry
External integrations Account owner, purpose, billing and ongoing dependencies

3. Website files and custom development materials

For a project where file or code handover is agreed, confirm what is included and how it can be used. Custom development may need source code, configuration instructions and deployment documentation to be maintainable by another competent provider.

Third-party themes, plugins, stock assets and hosted services can have their own licence conditions. Do not assume a bespoke project fee transfers unrestricted rights to every dependency.

If the website is a managed service rather than a conventional build, clarify export, transfer and termination options before commissioning it. Substantial contractual questions should be resolved in the written agreement with suitable advice where needed.

4. Content and asset records

Identify approved text, photographs, videos, logos, downloadable documents and other materials delivered with the site. Keep track of the source and permitted use where rights or consent matter.

Editable design files may be useful when included in scope. Clarify whether they are part of the project and whether the organisation can adapt them later.

A photograph being present on the website does not establish unlimited permission to reuse it in another campaign. Preserve any restrictions alongside the asset record.

5. Instructions for routine tasks

Documentation should explain the tasks your staff actually need to perform. Examples include updating a service description, publishing news, replacing a download and handling an enquiry.

Use the site’s real terminology and roles. A short guide that matches the actual interface can be more useful than a long generic manual.

My NCI and BIUC project pages show different information structures. A school and a specialist business will therefore have different routine publishing tasks. Those public records do not establish the terms of any individual handover agreement.

6. Training and confirmation that staff can use the site

Agree who receives training, which tasks it covers and whether a recording or written guide will be provided. Include the process for requesting help.

Ask a responsible staff member to perform representative tasks using the intended permissions. For example, can they edit approved text, preview it and complete the authorised publication process?

Training is not a substitute for technical maintenance. Staff should know which tasks belong to them and when to contact the provider.

7. Backups and recovery arrangements

Confirm what is backed up, how often, where copies are kept, how long they remain available and who can restore the site. For a conventional website, files and database records may both matter.

Agree a suitable recovery check and document any limits. For an active shop or application system, restoring an older copy can affect newer records, so the recovery process needs more thought than uploading a backup file.

At handover, your organisation should understand how the site is managed, what it depends on and whom to contact when something fails.

8. Evidence that agreed functions were checked

Use an acceptance checklist tied to the scope. Review links, mobile layouts, permitted form tests, downloads, staff access and required integrations. More complex systems need checks appropriate to their workflows.

Record outstanding issues and how they will be resolved. If a function cannot be fully tested until another provider completes a step, state that dependency clearly.

Do not confuse a working visual preview with a verified operational process. A form needs a receipt check, and an account-based system needs appropriate role and access checks.

9. Support, maintenance and future changes

Clarify what the post-launch support period covers and when it ends. Distinguish fixing a fault in agreed work from adding a new feature or producing new content.

Ask how issues are reported, what response arrangements apply and which charges continue. Maintenance, hosting and content production can be separate services.

My website care and technical support addresses ongoing work. New functionality can be assessed under website development or web applications and portals, depending on the requirement.

A practical handover sign-off

  1. Compare delivery against the agreed scope.
  2. Record accounts, owners and renewal responsibilities.
  3. Confirm the agreed code, files, licences and materials.
  4. Review instructions and complete relevant training.
  5. Confirm testing and recovery arrangements.
  6. List unresolved items, owners and agreed next steps.
  7. Record support terms and ongoing charges.

The sign-off should record the actual state of the work. For a larger project, involve the staff responsible for the operational process as well as the person who approved the design.

Frequently asked questions

Should I receive every administrator password?

Access should follow the agreed ownership and management model. Confirm appropriate control and recovery without requiring unnecessary access to a provider’s unrelated systems.

Can I change developer later?

Discuss transfer arrangements before appointment. The process depends on accounts, licences, service terms, code access and documentation.

Is handover the same as ongoing support?

No. Handover records delivery and enables agreed management. Ongoing support is a continuing arrangement with its own scope.

Discuss your project

Tell me about your organisation, the people your website serves and what you want to improve. We can review the requirements and agree the scope, timing and cost.

  1. WhatsApp: Send me a message on WhatsApp.
  2. Contact page: Send your project enquiry.
  3. Email: [email protected].
  4. Phone: +234 703 799 7791.

Based at 15 Ekpenyong Street, Off Barracks Road, Uyo, Akwa Ibom State. Remote working arrangements can be discussed.

Lawson Godwin Hezekiah

About Lawson Godwin Hezekiah

Technology entrepreneur, website developer and founder of Mita School and Techmita. I work with businesses, educational institutions, government organisations and NGOs.

Read my story ↗

Keep exploring

Let us work together

Put the ideas into practice.

If your website or digital strategy needs attention, let us discuss a useful next step.