Identify what the new administrator needs to manage
A domain can involve several separate accounts. The registrar handles the registration and renewal. A DNS provider hosts the records that direct website and email traffic. Web hosting and email services may have their own controls. Before granting access, list the tasks the incoming administrator will perform and identify which account controls each one. Access to a website dashboard, for example, may not allow someone to renew the domain.
Note which account is responsible for the domain’s nameservers, billing, and recovery settings. If these functions belong to different people or teams, make that division explicit. This prevents a routine DNS request from turning into an urgent search for the one person who can approve it.
Keep ownership separate from day-to-day access
Where a service supports separate user accounts, invite the new administrator using their own account rather than passing along a shared password. Give them the level of access their responsibilities require. Someone who edits DNS records may not need permission to change billing details or transfer the registration. Account roles vary by provider, so review the available permissions instead of assuming similarly named roles work alike.
Confirm who will retain authority over account recovery and major ownership changes. If an outgoing administrator used a personal email address or phone number for recovery, replace it with an appropriate address or method controlled by the continuing owner, following the provider’s process. Avoid sending passwords, backup codes, or other recovery secrets in a handover document.
Prepare a concise handover record
A useful handover record tells the next person where to go and what to check without exposing credentials. Include the registrar and DNS provider names, the domains covered, the people responsible for renewals and billing, and the location of internal documentation. Record any important service dependencies in plain language, such as an email service that relies on records in the domain’s DNS zone.
Explain any unusual arrangements. A domain might use nameservers at a provider other than its registrar, or one team might manage the main website while another manages email. Note upcoming decisions and unresolved issues, but distinguish confirmed facts from assumptions. Store the record where the continuing team can find it and update it when responsibilities change.
Test access before the outgoing administrator leaves
Ask the incoming administrator to sign in with their own account and locate the domain, renewal settings, nameservers, and DNS records. They should be able to identify where a proposed change would be made without actually changing a live record. If access is insufficient, adjust permissions while the outgoing administrator is still available to help.
Check that account notifications reach the right people and that renewal payment arrangements remain valid. For changes to recovery information or security settings, follow the provider’s confirmation steps and verify the result afterward. These checks are easier to complete during a planned overlap than after an account becomes inaccessible.
Close the handover deliberately
Once the new administrator can perform the required tasks, review the outgoing person’s access across the registrar, DNS provider, and any related services. Remove access that is no longer needed, but do not remove the only working administrative account or recovery method. If shared credentials were previously used, replace them through the provider’s normal process and confirm that authorized users can still sign in.
Finish by assigning a named owner for periodic checks of renewals, contact details, and access permissions. The aim is not to make every person an expert in every system. It is to ensure that the team knows who can act, where each task belongs, and how to keep the domain working when responsibilities change again.



