Data Nexus

Access and continuity

The point at which a vendor's work becomes the company's property — defined by what is transferred, not by the project being finished.

01/What it means

A complete handover is a short list and every item is checkable: accounts and administrative rights transferred to company-owned identities; the source code in a repository the company controls; the domain and DNS in the company's registrar account; documentation sufficient for a competent third party to continue; the credentials in the company's password manager; and a named contact for the period after.

Written into the engagement at the start, it costs nothing. Requested at the end it becomes a negotiation, and requested after a disagreement it becomes leverage.

02/What people get wrong

A launched site is not a handover. If the repository, the domain and the analytics remain under the vendor's account, the company has bought the use of an asset rather than the asset — and will pay again for the next change, or pay a great deal more to rebuild.

Next

The definitions are the easy part. Whether the figure on your dashboard was computed this way is a different question, and usually the more expensive one.