1. Define what is changing
Write down the exact domain, current registrar, receiving registrar, intended registrant, and person who can approve each step. Identify whether the assignment involves a purchase, an account move, a registrar transfer, or a separate DNS change. These actions can have different requirements. Record the agreed completion conditions before the work begins, including which party confirms ownership and which party checks live services.
2. Check eligibility before agreeing a date
For generic top-level domains, check the current registrar transfer process, any transfer lock, and the authorization-code requirements with the registrars involved. Country-code domains can follow different registry rules. Obtain a current answer for the specific name rather than assuming that every extension follows the same process. Keep authorization codes out of ordinary enquiry forms and restrict their sharing to the approved transfer channel.
3. Record the services that depend on the name
Prepare an inventory of the authoritative DNS provider, website hosting, mail provider, subdomains, verification records, redirects, and certificate responsibilities. Save an authorized copy of the current configuration before changing it. A registrar transfer and a nameserver change are different decisions; explicitly record whether DNS is expected to stay in place. Assign someone to investigate any dependency that cannot yet be identified.
4. Coordinate approvals and verification
Keep a short event log: the request submitted, approval received, account receiving the domain, and checks completed. Agree who is watching registrar messages and who can act if an approval is missing. After the move, verify the receiving account, contact and recovery arrangements, renewal settings, and intended nameservers. Check the actual website and email services as part of the agreed scope, rather than relying on a registrar success message alone.
5. Close with an accessible handover
The final record should identify the domain location, account owner, renewal responsibility, DNS provider, work completed, and unresolved items. Store this in the client-approved location with appropriate access. Confirm temporary access arrangements and agree when they should end. A useful handover lets the next authorized administrator understand the setup without searching through personal inboxes.
Illustrative example: an acquired name before launch
A business buys a name but plans to keep its existing hosting for several weeks. The immediate brief can cover ownership and registrar access, while the later launch has a separate DNS and email plan. The handover lists both milestones, the current authoritative nameservers, the owner of each task, and the evidence needed to close each stage. This is an example of a possible scope, not a claimed client result.
A useful starting point
Confirm ownership, renewal responsibility, and service dependencies separately before calling a transfer complete.