How to Use Spreadsheets to Track Domain Assets

Using spreadsheets to track domain assets turns a scattered collection of domain names, websites, redirects and email services into a manageable register. A domain asset is anything your organisation controls or depends on: a root domain, a campaign subdomain, a forwarding address, hosting, certificates or a preserved page of published material. Tracking each item in one place makes ownership, renewal dates and future work visible.

The aim is not to build a complicated database. A simple sheet in Excel, Google Sheets or LibreOffice Calc is enough for most small organisations, including teams maintaining historical websites. One row per asset, consistent labels and a few calculated columns provide a dependable reference without slowing down day-to-day work.

That reference becomes especially useful when the domain portfolio has several layers. A main site may include a members area, a media archive, old campaign domains and redirects from addresses printed in earlier publications. Recording these connections helps prevent duplicate purchases and shows which pieces still support the resource hub.

A useful register also needs clear rules for access, backups and review dates. Australian business realities shape some of those rules, particularly domain eligibility, privacy obligations and time zones. The spreadsheet should remain an index to records and archived material, not a substitute for backups, contracts or registrar accounts. It becomes a portable handover document that can survive staff changes, service migrations and years of online publishing.

Build a workable asset register

Start by defining what belongs in the register. A root domain and each subdomain can occupy separate rows, especially when they have different owners, costs or retirement plans. Shared services such as hosting and DNS accounts also need entries, with a parent identifier linking them to the relevant domain. Give every row a stable identifier, such as DOM-001 and SUB-001, rather than relying on visual indentation or naming conventions alone.

Keep the headings consistent across the sheet. Useful fields include asset ID, domain or address, asset type, owner, business unit, registrar, creation date, renewal date, cost, status and last review date. Restrict the Status column to a small set of values such as Active, Dormant, Retiring and Retired. Consistent categories make filtering and reporting possible; free-text notes belong in a separate Notes field.

Turn repeated choices into dropdown lists and use conditional formatting to highlight exceptions. Choose one date format—day/month/year works well in Australia—and apply it everywhere. In Excel, a table formula such as =IF([@[Renewal date]]="","",[@[Renewal date]]-TODAY()) can calculate days to renewal. Put validation lists on a separate reference sheet so the main register remains easy to sort and filter.

Capture ownership, cost and renewal details

Register the person or business entity that owns the asset, the internal team responsible for decisions and a named backup contact. A registrar account is not the same as ownership: resellers and hosting providers may hold the login while your organisation owns the name. Record these roles separately so a staff departure or vendor change does not leave the asset orphaned.

Add the registrar, reseller, account reference, renewal date, paid-until date and recurring cost. Store amounts in Australian dollars and note whether GST is included. Auto-renew settings, multi-year terms and credit-card expiry belong in the record, but passwords and full payment details do not. A secure password manager and a calendar reminder can hold those sensitive items.

Create a renewal workflow as well as a renewal date. Begin internal checks 90 days ahead, then confirm pricing, ownership details and the auto-renew preference before the registrar deadline. Give the owner a decision field, such as Renew, Transfer or Retire, so the register records intent rather than merely showing that a payment happened. Empty fields should mean not recorded, while an explicit Not applicable avoids unnecessary reminders.

Map content, archives and preservation

Content is an asset too, particularly for a site that keeps background information, archived news and community-focused articles. Give each publication a row with its title, current address, permanent address, publication date, editor, rights status and archive location. For a resource hub, an archived news page and a background note may need separate records if they have distinct owners, addresses or retention dates.

The site’s permanent URL policy gives you a clear model for naming and preserving each article’s address, while the spreadsheet shows which pages still have a working replacement. Keep this policy reference alongside the relevant asset IDs rather than mixing it into operational fields that require regular sorting.

For stored files, add the format, size, checksum and storage location. A checksum helps confirm that a PDF or image has not changed since capture, while a second location guards against losing an entire folder. Schedule a restore test: open one archived article and one image from the preservation copy and record the result. If the spreadsheet is the only copy, it is an index without the underlying evidence.

Monitor redirects and link health

Redirects protect old links and preserve pathways through the site, so treat them as assets rather than invisible plumbing. Record the source path, destination, redirect type, owner and date of the last check. A spreadsheet can also reveal chains, loops and redirects pointing to retired material. Keep temporary redirects marked for review because campaigns and maintenance pages often outlive their purpose.

Third-party references need their own sheet or clearly labelled section, with the citing page, destination, purpose, owner and last-checked date. Even a directory listing benefits from this treatment: the address alone says little about who controls it or whether it remains relevant. Record the link because it exists, not because an external page is endorsed.

Review external destinations on a schedule and record Working, Redirected, Blocked or Needs review. A spreadsheet does not crawl the web by itself, so the status must be refreshed by a person or connected to a suitable checking tool. When a link fails, decide whether to repair it, replace it with an archived source or remove it. Keep the old destination and the decision together so the next review does not repeat the investigation.

Add Australian market and compliance context

Australian domain choices affect how the register is organised. Record the suffix and its category, such as .com.au, .org.au or .au, then confirm eligibility with the registrar rather than relying on assumptions about Australian presence. Different evidence of Australian presence or organisational qualification may be required, so keep supporting notes and renewal contacts beside the asset record.

Where the Privacy Act and Australian Privacy Principles apply, a domain connected to customer records, mailing lists or online forms needs an identified controller, a lawful handling process and an access-review date. The Australian Spam Act also matters for commercial email, including consent and unsubscribe details. Store process ownership and evidence locations in the sheet, not people’s personal information; limit access and separate confidential data into an appropriately secured system.

Daylight saving adds another practical wrinkle for teams coordinating Sydney, Melbourne, Adelaide, Brisbane and Perth. Store timestamps in UTC, add the relevant local time zone and avoid relying on a colleague’s clock. For finance reconciliation, keep amounts in Australian dollars, show GST treatment separately and note the invoice date alongside the payment date. These conventions prevent a paid renewal from appearing overdue during a month-end check.

Create a review rhythm

Set review frequencies that match the risk. Review renewals monthly, test important links quarterly, and inspect the archive and backup process at least yearly. Each row needs a Last reviewed value, a Next review date and a Reviewer field. A formula can flag records whose next-review date has passed, which is often more revealing than a list of assets that have never been touched.

Reconcile the register against registrar exports, hosting invoices and finance records every quarter. Look for names nobody recognises, duplicate assets, unexpected price changes and records without an accountable owner. Keep a change log with the date, editor and reason for each amendment. Version history in Google Sheets or Excel can support that trail, but it does not replace a scheduled copy of the file or a proper backup.

Use a small dashboard to count assets by status, renewal exposure and review age. Track renewals missed, stale pages, broken destinations and records missing an owner rather than trying to measure everything. These measures keep attention on the assets that need action and make the register useful to someone joining the team who has never seen the previous spreadsheet.

Turn the register into a shared working document today: create the sheet, import the existing domain list, and assign an owner and review date to every row. Keep credentials and personal data out of the file; its purpose is to track assets, direct people to secure records and expose work that is due.

Use the resource hub to browse preserved background material, follow archived articles and enquire about stewardship of the domain. Start with one important page or domain, record its stable address and responsible contact, publish that first entry and schedule the next review before closing the spreadsheet.