Know who owns every domain
Record the registrant, registrar, renewal date and responsible client contact. A website launch is not complete if nobody knows who can renew the domain next year.
Document DNS and the service behind it
Keep a simple relationship map between domains, important records and the service they point to. This makes migrations and incident response much faster than reverse-engineering everything under pressure.
Separate client environments
Avoid unnecessary coupling between unrelated client workloads. Separate credentials, hosting accounts or Cloud Servers reduce the impact of mistakes and simplify handover.
Define backup and restore expectations
“We have backups” is incomplete. Record what is backed up, how often, how long it is retained and who knows how to restore it. Test recovery for important projects.
Control administrative access
Use individual accounts where possible, remove access when responsibilities change and avoid storing critical infrastructure credentials in personal notes. Keep the minimum level of privilege required for the work.
Standardise the handover
A client should receive a clear list of domains, DNS ownership, hosting or server resources, application credentials, backup expectations and renewal responsibilities. Standardisation protects both the client and the agency.