How to run a 90-day renewal review for defensive domains

How does a 90-day defensive renewal review work?

A 90-day defensive-domain review is a planning window for checking expiry, client instructions, ongoing purpose, and renewal cost. It is not a universal legal deadline. Ask the connected registrar for current account data, route unresolved decisions to the responsible person, and verify completed renewals against the resulting expiry dates.

A defensive portfolio can outlive the campaign, launch, or matter that created it. That makes renewal review a records problem as much as a registrar operation. Staff need to know what is approaching expiry and whether the original purpose still applies.

The AIvikings brand/IP page includes account expiry queries and renewals. A 90-day review can use those tools to assemble the facts while leaving client and legal decisions with the appropriate people.

Place this task within the defensive domain administration workflow, from an approved brand decision through client records and renewal responsibility.

Why use a 90-day window?

It gives the team a defined planning horizon for collecting instructions, resolving missing records, and preparing purchases. The number is a workflow choice. It is not a statement that every registry, client agreement, or legal obligation uses the same deadline.

Choose a cadence that fits the portfolio and its actual expiry dates. A review that runs once and is then forgotten does not provide ongoing coverage, regardless of how broad its initial window was.

Make ownership explicit. Someone should know when the next review is due and where exceptions are recorded. An assistant can perform a query when asked, but that does not establish a recurring monitoring or reminder process unless one has actually been configured.

Which holdings should enter the review?

Read the connected account's current domain records and select names whose expiry falls within the defined window. Include missing or unclear dates as exceptions rather than dropping them from the results.

The MCP tools reference describes listing and status operations. Use them to establish the facts available from the account, and inspect individual names when more detail is needed.

Compare the list with the firm's client-domain inventory. A holding may be missing because it was transferred, is held at another registrar, or was never entered into the correct account record. Do not assume that an empty query proves the client has nothing approaching expiry.

Record the observation time. A report used several weeks later should still show when its operational data was collected and which entries need another check.

What decision should be made for each name?

Assign a clear outcome: renew under existing authority, seek instruction, investigate, or record an authorized decision not to renew. These are suggested workflow states, not legal requirements or native registrar fields.

Keep the ongoing purpose visible. A domain may support an active brand, an obsolete product, or a prior defensive strategy. The assistant can group those records, but it should not infer permission to abandon a client holding from a lack of recent website activity.

When instructions are needed, state the question concretely. Include the exact domain, expiry, proposed term, expected cost, and relevant context. A request for a general portfolio opinion can take longer to resolve than a specific renewal decision.

Retain the decision source in the firm's records. This helps another staff member understand why a name was renewed or deliberately excluded without replaying the original conversation.

How should costs be prepared?

Use current renewal information for the selected holdings. The AIvikings prices page distinguishes renewal costs from first registrations and transfers. Treat domain-specific exceptions separately where the ordinary catalog does not establish the applicable price.

Show the currency and additional period. If the original instruction covered a different term or a budget that no longer fits, return the difference for a decision instead of silently changing the operation.

Keep approved spending distinct from account funding. A permitted renewal can still fail if the account cannot pay for it. The process should establish readiness without presenting an available balance as authorization to renew every holding.

For future years, label forecasts as forecasts. Today's renewal price supports the present decision; it does not guarantee what the next review will cost.

How should approved renewals be executed?

Freeze the approved names and terms into an execution list. Avoid a moving instruction such as "renew whichever domains now fall inside the window" when the authorization concerned a previously reviewed set.

Record the starting expiry, issue the authorized operation, and inspect the resulting account record. A submission acknowledgement and a completed extension are different facts.

If the response is uncertain, preserve the request details and investigate before another paid attempt. Do not interpret a timeout as a confirmed failure or remove the row because the assistant continued with other names.

Keep a result for each authorized holding. The final reconciliation should distinguish confirmed renewals, explicit failures, unknown outcomes, and names never attempted.

How do you handle names close to expiry?

Review the actual registrar and extension conditions rather than relying on a generic grace-period assumption. ICANN's expired-registration guidance explains the relevance of renewal and recovery terms for covered domains.

Escalate unresolved instructions or account issues through the firm's existing process. The report should identify the deadline, the missing decision or technical result, and the person responsible for the next step.

Do not invent a universal emergency rule that allows the assistant to spend without authority. Equally, do not leave a known exception buried in a completed batch report. The workflow should make the situation visible to someone who can decide.

What closes the review?

Every reviewed name needs a documented status and next owner. Confirmed renewals should show the resulting expiry and next review date. Deliberate non-renewals should retain the applicable instruction. Unresolved items should remain open.

Reconcile the account data and the firm's record after the batch. The operational expiry may have changed, while the business purpose and review responsibility remain. Preserve both kinds of information.

The completed report should make the next review easier. It should explain the remaining work, not require the next operator to infer it from missing checkmarks.