Domain renewal approval workflow

The outcome

A renewal reminder is useful, but it is not a decision record. The workflow below makes the requested choice, the authorized client approver, and the deadline explicit.

Workflow

1. 1.Open a decision early enough to resolve unknown ownership or budget questions before the registrar’s critical dates.
2. 2.Attach the domain, proposed action, cost context, due date, and any technical or business consequence of delay.
3. 3.Send the request only to an authorized client approver; record a decision, rejection, or requested correction—not an assumed approval.
4. 4.Record the completed action and preserve the reason and evidence with the decision for future handoff.

Renewal approval request

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

Decision: Renew example.com for [term]
Client approver: [name / role]
Decision due: YYYY-MM-DD
Cost context: [amount / currency / source]
If delayed: [specific consequence]
Evidence reviewed: [registrar / contract / client instruction]
Response: approve | decline | request changes
Agency follow-up owner: [person]

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