The handover test: can your team run it without us?
A project is not finished when it launches. It is finished when the people who own it can change it without calling anyone.
Plenty of projects launch successfully and then quietly calcify, because every change requires the people who built it. That is not a maintenance plan; it is a dependency.
What a real handover includes
Editable content that a non-developer can genuinely edit
Access to every account, in the client's name, not the supplier's
A written record of the decisions that would otherwise be re-litigated
A path to deploy a change, documented and actually rehearsed
Test it before you need it
Ask someone from the client team to make a small, real change while the original team is still available to watch. Everything that gets stuck is a gap in the handover, discovered at the cheapest possible moment.
Ownership is not a document
A folder of credentials is not ownership if nobody has ever used them. The test is behavioural: has the team done it, unaided, once?
The measure of a good handover is how boring the first month afterwards is.