What it is
A handover of credentials form records exactly what a developer, agency or IT supplier hands to its client at the end of a project or contract: domain names, hosting, administrator accounts, third-party services, source code and documents. Passwords are never written on the form; it records how they were sent securely, and when the supplier's own access will be removed.
How it works
You fill in each domain, account and service handed over, how the passwords and keys were sent, and the date your own access will be removed. The client checks each item works, notes anything missing, ticks to confirm and signs. Then your company signs. Both keep the sealed copy.
What you fill in
- Client
- Project
- Parent agreement number
- Domain names
- Hosting and DNS accounts
- Website, system and administrator accounts
- Third-party services
- Source code and documents
- How passwords and keys were sent
- Our access removed by
Sending it with Sign2Approve
In Documents, it comes with who signs, in what order, and what each person fills in already set. The order is a suggestion: change it before you send. Anyone can decline with a reason; you correct a copy and send that as the next version, and the declined one is kept. Once everyone has signed, the document is sealed with a completion certificate, and everyone gets a copy.






