Blog

Who Owns the Website Files? A Better Supplier Handover

A website handover should leave the business with a clear record of access, files, licences and responsibility, not only a working homepage.

By Middle East Icons · · 2 min read

Original editorial diagram: Access, Rights, Recovery. A conceptual framework, not measured data.

Look beyond the launch screen

A website can look finished while the business lacks a clear record of its source files, licensed assets or maintenance responsibilities. The UAE Government intellectual-property overview includes software, databases, photographs and drawings among copyright categories. These can all appear in a website project, which makes the handover more than a visual approval.

This checklist is a proposed supplier-management method, not a determination of who owns a particular site. Resolve ownership and usage rights in the relevant agreement. The practical aim is to make the final delivery understandable to someone who did not participate in the build.

Separate access from ownership

List the domain account, hosting account, content system, analytics and any external services used by the site. Record who is responsible for each and how authorised staff recover access. Access details should be handled securely, not collected in an ordinary shared document containing passwords.

An administrator login does not by itself explain the rights to a font, photograph or software component. Maintain a separate asset list showing the source, licence, renewal responsibility and any usage limits. Ask the supplier to identify dependencies that would stop working if their own subscription or account ended.

Ask for a reproducible handover

Agree what files, exports, backups and documentation are included. Have the receiving team follow the written instructions for a simple task such as changing a page image or recovering a previous version in a test environment. A handover is stronger when another person can use it without an improvised call to the developer.

Clarify what a backup contains and what it omits. A content export is not automatically a copy of the entire site, its media, configuration and external services. State what was tested and leave any untested recovery step visible rather than describing it as complete.

Name the post-launch owner

Assign responsibility for updates, renewal reminders, content review and incident escalation. Record the support period and what work falls outside it. These are proposed operational controls; the actual service obligations belong in the contract.

Finish with a signed-off inventory and a small list of open items. The best handover is not the largest folder. It is the one that tells the business what it received, what it can use, how it is maintained and what still depends on someone else.

Sources and scope

This is an editorial working method, not legal or tax advice. The UAE sources below supply the public-policy context; the suggested checklists are our analysis. Confirm current obligations for the specific entity and activity with the relevant authority or a qualified adviser.