Skip to content
Skip to content

Practical AI project guide · By Yes AI

How to set up an AI register for your business

Published 5 min read

An AI register is a single list of the AI systems your organisation uses, what each one is for and who is accountable for it. The Australian Government's Guidance for AI Adoption asks organisations using AI to create and maintain one. This guide covers what to include, which fields to start with and how to keep it from going stale.

Quick answer

An AI register is a table or database listing every AI system your organisation uses, including AI features built into software you already pay for. For each entry, record the system and supplier, its purpose, the accountable person, the personal information it uses, any decision it makes or informs, its risk level and oversight, and a review date. Start in a spreadsheet, give one person responsibility for it and update it whenever a tool is added or changed.

Office manager in a Canberra office updating a spreadsheet while a colleague reads from a supplier contract
Supplier contracts and software settings supply most of the facts a register entry needs.

What is an AI register for?

The register records which AI systems the organisation uses, what each one is for and who looks after it. The National AI Centre describes it as a table or database listing each AI system's key characteristics, use cases, accountable people and appropriate governance level. It helps staff check whether a tool is already in use before buying another, gives managers one view of AI across teams and reduces shadow AI by making approved use visible. The Centre is clear that the register is about transparency and documentation and does not replace impact assessments or risk management.

What should go on the register?

Include every AI system, whether you built it, bought it or switched it on inside existing software. The foundations guidance specifically mentions AI embedded in other systems, such as human resources and customer engagement tools. Include approved standalone tools such as chat assistants, recording the approved uses and leaving out individual prompts. Where staff use one tool for purposes with different risks, give each purpose its own entry, because the guidance points out that the same tool can carry different risks depending on how it is used.

  • Tools built in-house or by a contractor.
  • Bought AI products and subscriptions.
  • AI features inside accounting, customer management, HR, helpdesk and document systems.
  • Approved standalone assistants, with each approved use listed.
  • Agents or automations that take actions in other systems.

Which fields should each entry have?

Start with the fields in the table below for every entry, then add detail for higher-risk uses. The implementation guidance lists what a full entry can hold: accountable people, purpose and business goals, capabilities and limitations, origin and updates, technical components, datasets and their provenance, acceptance criteria and test results, impact and risk assessments, the risk treatment plan, audit requirements and review dates. A meeting note-taker rarely needs all of that, but a tool that screens job applicants or approves credit needs most of it.

Who fills it in and who owns it?

Give the register one owner, usually the person accountable for AI governance or someone reporting to them. Each entry then needs its own accountable person: the manager of the process the tool supports, who knows how it is used and can answer for its results. The foundations guidance asks organisations to make a specific person accountable for every AI system as their use matures. IT staff or your managed service provider can supply technical fields such as where data is stored, but they should not be the accountable person for a business process they do not run.

How do you keep the register current?

Registers go stale when updating them depends on someone remembering. Tie updates to events that already happen in the business, as listed below, and put a review date on each entry. The National AI Centre also suggests encouraging staff to check the register before deploying, buying or using any AI system, which works best when the register is easy to find and the approval route is quick. When a tool is switched off, mark the entry retired and keep its history.

  • A request for a new tool, or a new use of an existing tool.
  • A software renewal or new contract, checked for AI features.
  • A vendor release that adds or changes AI features.
  • An incident, complaint or near miss involving an AI output.
  • A change of accountable person when staff move or leave.

How does the register connect to other obligations?

A good register makes several other jobs quicker. From 10 December 2026, organisations covered by the Privacy Act must describe in their privacy policy certain decisions that computer programs make, or substantially and directly inform, using personal information. A register field recording the decision each system makes or informs turns those systems into a filtered list. The same entries support risk screening, supplier reviews at contract renewal and reporting to a board, which can ask how many systems are in use, which are higher risk and which are overdue for review.

Starter fields for an AI register, with hypothetical example entries

FieldWhy it mattersHypothetical entry: meeting note-takerHypothetical entry: applicant screening tool
System and supplierIdentifies the product and who to contactNote-taker built into the video meeting platformScreening module in the recruitment platform
Business useDefines the approved purposeInternal meeting summaries onlyRanks applicants for a shortlist
Accountable personNames who answers for the resultsOperations managerHR manager
Personal information usedFlags privacy obligationsNames and anything said in meetingsCVs and screening answers
Decision made or informedFlags privacy policy wording under APP 1.7NoneWho is shortlisted
Risk level and oversightSets the controlsLow; spot-check summariesHigher; a person reviews every shortlist
Next review dateStops the entry going staleSix months after approvalEach hiring round and at contract renewal

Practical checklist

  • One owner for the register is named, with a backup.
  • Every entry has an accountable person who runs the related process.
  • Built-in AI features in existing software have been checked and recorded.
  • Each entry records the personal information used and any decision it makes or informs.
  • Higher-risk entries link to their risk assessment and test results.
  • Updates are triggered by new tool requests, renewals, vendor releases and incidents.
  • Every entry has a next review date.

Common questions

Do we need special software for the register?

No. The National AI Centre publishes its template as a Word document and an Excel spreadsheet, and a shared spreadsheet with controlled edit access works for many small and medium businesses. Move to a database or governance platform when the number of entries, owners or linked documents makes a spreadsheet hard to keep accurate.

Should free tools be on the register?

Approved free tools should be, with the account type recorded, because the data terms of free and business plans can differ. Unapproved tools found during a discovery exercise belong on the register too, marked with the decision made about them, so the record shows what was found and what happened next.

How detailed should a low-risk entry be?

Detailed enough for someone else to understand what the tool does, who owns it and what data it touches. For a low-risk internal tool, the starter fields are usually sufficient. Save the fuller set from the implementation guidance, such as datasets, test results and audit requirements, for uses that affect customers, staff or money.

Who should be able to see the register?

Staff should be able to see at least the list of approved tools and uses, because the National AI Centre suggests staff check the register before buying or using an AI system. Detailed fields such as risk assessments or contract terms can sit in a restricted version for managers and the board.

Does keeping a register meet the Guidance for AI Adoption?

It covers one getting-started action under one of the six practices, sharing essential information. The other practices ask for an accountable owner, impact assessment, risk screening, testing and human oversight. The register is a useful index for that work, but the National AI Centre says it does not replace impact assessments and risk management.

Sources and further reading

Continue planning

Turn the project decision into an agreed next step

Describe the business process, project stage and decision you need to make. We can discuss scope, evidence and who should own the next step. Keep confidential records, credentials and sensitive commercial details out of this enquiry.