Vendor operations

A domain renewal register that outlives the web developer

A register for domain names, registrar logins, renewal dates, and DNS dependencies that keeps the company in control when the original developer leaves.

Short answer

Start with repeatable IT work that has a clear owner, clear access limits, and a review cadence. Keep risky technical decisions with the manager or provider who owns the system.

Delegation playbook

Best fitRepeatable IT admin
OwnerManager or IT lead
Risk ruleEscalate technical judgment
PilotTwo-week sample workflow
On this pageJump to section

A domain can outlive the developer who registered it, the agency that designed the site, and the manager who approved the invoice. When the renewal notice goes to an old mailbox, the company discovers the problem only after the website stops resolving. A renewal register names the owner, the registrar, the payment route, and the dependencies for each domain. The register is a small document that protects a public asset.

List every domain and its registrar

Start with the public website and the email domain, then add campaign domains, redirects, and old brand names. Check the website source, the invoice history, and the mail records for names that are still in use. Search the registrar accounts the company can access and export the domain list. A domain that nobody remembers is still a domain that can expire.

For each name, record the registrar, the account email, and the renewal date. Note whether the domain is registered directly or through an agency or reseller. Add the nameservers and the hosting provider. This list becomes the spine of the register and the first thing to check in an outage. Add the date the record was last checked and the person who confirmed it.

Separate ownership from login access

The company should own the domain even when an agency manages it. Confirm that the registrant organisation is the business and that the admin contact reaches a company mailbox. Record who can log in to the registrar and what second factor protects the account. Ownership that exists only in a contract is not ownership you can use at midnight. A written transfer is stronger than a promise made during a sales call.

Move agency-held logins to a company-controlled account where the contract allows it. If the agency must retain access, give it a named user rather than the shared master login. Record the transfer date and the person who approved it. The goal is a clear chain from the business to the registrar account. Keep the old access disabled after the transfer and record who approved the change.

Record renewal dates and payment method

Store the expiry date, the auto-renew setting, and the card or invoice route for each domain. Note the renewal period and whether the registrar charges in advance. Record the finance contact who can approve a payment. A domain that relies on a deleted card will fail at the worst moment. A domain that renews on a personal card creates a dependency on that person's credit.

Add a second payment route for the domains that carry mail or revenue. Keep the billing contact in the register rather than in one person's inbox. Check that renewal notices reach a monitored mailbox. The register should answer who pays and how without asking around. Finance should be able to see the renewal in the same calendar as other vendor bills.

Set reminder points that leave time

Create reminders at ninety, thirty, and seven days before expiry. Send them to the domain owner and the person who can pay. Include the registrar, the domain name, and the action required. A reminder that arrives on the expiry day is only a notification of a problem. Name a deputy who can act when the owner is on leave, and record that person in the register.

Check the registrar's grace period and recovery process before relying on it. Record the fee and the steps for a late renewal. Test the reminder path with one domain each quarter. The reminders should reach a person who acts, not a shared inbox nobody reads. A grace period can close without warning if the registrar changes its terms or the registrar is acquired.

Document DNS and mail dependencies

Record which services depend on each domain, including the website, mail, sign-in, and customer portals. Note the nameservers and the provider that hosts them. Add the certificate and redirect rules that would break if the domain changed. A renewal is simple until it takes mail and single sign-on with it. The dependency list should name the person who can test each service after a change.

Keep a copy of the current DNS records outside the registrar account. Note the change process and the approver for each record type. Record the vendor contacts for mail and hosting. When a domain moves, the dependency list tells you what to test. Store an export with the register so a lost account does not lose the zone, and keep it with the renewal dates.

Test recovery before a crisis

Confirm that the company can regain control of a domain if the current manager is unavailable. Check the registrar recovery process, the account recovery email, and the identity documents required. Walk through the steps with a test domain or a read-only review. A plan that has never been read is not a recovery plan. Include the registrar support route and the account recovery mailbox in the test.

Record the results and the time each step took. Fix any contact detail that points to a person who has left. Store the recovery notes with the register and limit access to the people who need them. The test should produce a dated record, not a conversation. Keep the test record short and dated so the next owner can repeat the steps.

Review the register every quarter

Review the domain list, the registrar access, and the renewal dates each quarter. Remove names that are no longer used and confirm that redirects still serve a purpose. Check that every domain has a named owner and a working payment route. The review should take less than an hour. Invite finance and the website owner to the review so the register stays current.

Compare the register with the invoices and the public records. Add any domain that appears in either source. Send the updated register to finance and the website owner. A register that is reviewed on a schedule survives the next staff change. A domain that cannot be matched to an invoice deserves a direct question to the registrar before the next renewal cycle.

Sources and next step

Use the CISA Cross-Sector Cybersecurity Performance Goals and the NIST Cybersecurity Framework 2.0 as primary references for the printer, domain, support rota, licence, and desk move practices discussed in these guides. The NIST SP 800-53 Rev. 5 supports the access and asset records, and the SBA cybersecurity guidance frames the vendor and account ownership checks. Apply your own policies, contracts, and system documentation to the workflow.

Compare this guide with the domain renewal register and the licence true-up worksheet before changing a live process. If the coordination is recurring and your technical owner can define the boundaries, review the IT virtual assistant service areas and contact ITVirtualAssistant to discuss a limited pilot.

Operating brief

What this guide should help you decide

Delegate

Routine intake, status updates, records, screenshots, and documentation upkeep.

Keep ownership

Approvals, risky system changes, security decisions, and final technical judgment.

How to use this guide

Use this page to decide what an IT virtual assistant should handle first. If the task is recurring, documented, and easy to review, it is usually a better first delegation candidate than work that requires live technical judgment.

Treat the article as an operating brief, not just a topic overview. The goal is to turn loose IT work into a named workflow with inputs, outputs, permissions, review cadence, and a handoff rule that protects the business while reducing manager load.

Workflow

Recommended operating workflow

1

Define the request

Write what a domain renewal register that outlives the web developer means in your company, where requests enter, and what finished work looks like.

2

Limit the access

Give the assistant only the tool permissions needed for intake, records, status updates, or documentation.

3

Run a pilot

Use a two-week sample period so the manager can review accuracy before expanding the workflow.

4

Review patterns

Summarize repeat issues, blocked requests, and escalation volume so the technical owner can improve the process.

Decision rules

QuestionVA fit signalEscalate when
Is the work repeatable?The same request appears weekly and can be described in steps.The request changes business policy or system design.
Can quality be reviewed?The manager can inspect the output without redoing the work.Only a senior technical person can judge correctness.
Is access contained?The assistant can work with read-only or role-limited access.Admin rights, customer data, or security settings are involved.

Delegation checklist

  • Write the intake source, expected output, and manager review cadence.
  • Confirm the assistant has only the permissions needed for the workflow.
  • List the events that require escalation before work continues.
  • Track examples for two weeks before changing the workflow.
  • Save examples of good and bad outputs so the assistant has concrete references.
  • Review the workflow monthly and remove permissions that are no longer needed.

Example first-week agenda

Day one should cover the workflow owner, tools, allowed actions, forbidden actions, and escalation language. By the end of week one, the assistant should have produced a small sample of completed work, a list of unclear requests, and a manager-reviewed improvement note.

What to review before delegating

Confirm the owner, access level, review cadence, and escalation path before assigning any recurring IT workflow to a remote assistant.

What should an IT virtual assistant handle first?

Start with repeatable, reviewable work such as ticket summaries, account records, documentation updates, and checklist follow up.

Get free IT support review