Practical guide

Agency domain offboarding guide

A structured agency domain offboarding guide for access location, registrant authority, DNS dependencies, open renewals, and client acknowledgement.

By OpsBlip editorial team · Reviewed July 15, 2026 · Every 90 days or when transfer policy changes review

The outcome

Offboarding is complete only when responsibility, dependencies, and unresolved work are visible to the next accountable party. Access transfer and a change of registrant are different events and must not be merged in a checklist.

Workflow

1.Agree a scope date and list domains, related services, account boundaries, and work that remains outside the engagement.
2.Confirm the client’s authorized contact and record whether registrant, registrar access, billing, and DNS control have been verified.
3.Document the operational dependencies and safe transition sequence; do not place passwords, API tokens, or private keys in the handoff.
4.Issue a versioned record, collect acknowledgement or correction, and revoke only the agency access that the client confirms is no longer required.

Offboarding record

Adapt this to the client’s actual authority and records; do not put passwords, tokens, recovery codes, or private keys in it.

Effective date: YYYY-MM-DD
Domains in scope: [list]
Control status: registrant | registrar | DNS | billing | hosting
Dependencies: mail | redirects | certificates | verification
Open decisions and deadlines: [list]
Agency access to remove after acknowledgement: [list]
Client reviewer outcome: acknowledged | correction requested

Product CTA

OpsBlip’s current build is designed around accountable domain records, renewal decisions, client approvals, and handoff packs. Public production availability is not verified.

See the planned workflow

Sources and limits

External facts on this page are limited to the sources below. Product-specific details not stated by a source are marked unknown and should be confirmed with the provider.

ICANN Transfer Policy