What agencies forget in project handover
The files, systems, and control gaps that only become obvious after everyone assumes the project has already been handed over.
Handover problems rarely happen because nobody cares. They happen because everyone assumes the important bits are already covered.
The site is live. The files were shared. The supplier says everything has been sent over. The client thinks the agency has it. The agency assumes the freelancer still controls the remaining loose ends. Nobody is being careless on purpose, but nobody is looking at the whole picture at once.
That is where handover risk lives.
What often gets missed
- The source files exist, but only in the supplier workspace.
- The site is live, but hosting access is still unconfirmed.
- Analytics is “set up”, but nobody knows who actually administers it.
- The copy deck was shared once, but nobody checked it against the live version.
- The domain is fine until the person controlling it disappears.
In practice, agencies rarely get caught out by one dramatic missing item. More often it is a cluster of smaller gaps. That is what makes them expensive: each one seems manageable in isolation, until the project needs to change hands quickly.
The dangerous phrase in handover is we have it. That can mean almost anything. What matters is not just whether something exists, but whether the agency can actually rely on it.
Project record
Client website build
Must resolve
MissingHosting access
No confirmed admin route exists for the live environment.
Control gap
ExternalFigma working file
The agency has exports, but the source of truth still lives in a supplier workspace.
A good handover record should answer five questions:
What resources should exist?
What systems and accounts matter?
Who is expected to provide them?
Who currently controls them?
Has the agency actually verified them?
Pressure test
If the current supplier stepped away tomorrow, could your team still keep the work moving safely?
If the answer is uncertain, the handover is not finished. That is the simplest useful rule.
This is where many teams go wrong: they track delivery, but not custody. They record that something arrived, but not whether the agency can use it, control it, and rely on it later.
For most agency projects, the first things worth checking are not glamorous. They are simply the assets and access routes that would hurt most if they turned out not to be under control.
Worth checking before sign-off
These are usually the first things worth pinning down before a handover gets treated as complete.
Primary source files
Brand asset libraries
Final copy or content documents
CMS or admin access
Hosting or deployment access
Analytics and reporting access
Domain or DNS control
Paid media or third-party platforms that affect delivery
You do not need a giant process document to do this well. You do need a truthful record.
That means being able to distinguish between missing, supplied, externally controlled, and verified.
Missing
Not received at all.
Supplied
Delivered, but not yet checked.
External
Still controlled somewhere outside the agency.
Verified
Checked, usable, and trusted.
Those distinctions are what stop a handover from becoming a false sense of safety.
The best handover process is not the one with the most admin. It is the one that makes unresolved risk visible early enough to do something about it.
A reliable handover is not just everything was sent. It is this: everything important is known, controlled, and usable.
That is the standard worth aiming for.
How Custody helps
Custody helps agencies turn handover into a visible record of what is missing, what is still externally held, and what has actually been verified.