AI register: start with a use case, not a software list

Fictional example — AI usage register

You use an AI assistant to prepare an FAQ, a product description or meeting notes. A list of software does not explain how the result is produced and checked. Start with a concrete task.

1. Describe what you want to achieve

“Prepare an answer to a frequently asked question” is more useful than “use AI”. Specify the intended audience and the expected result. A draft for internal review does not follow the same process as published text.

2. Record the permitted inputs

In our fictional example, the FAQ uses information about a product that is already public. Customer contact details and confidential documents are excluded. This entry makes the limits visible; it does not prove that the tool enforces these rules automatically.

3. Assign the human review

Before publication, someone checks the facts, quoted prices and links. Record the role responsible for the review and what they must examine. If nobody is assigned, the register must leave that gap visible.

4. Keep a record of changes

A new tool, source or destination may change the practice. Add a date and a note to the log. Keep successive exports so you can recover the context of a decision.

Test your first record

Review it with someone unfamiliar with the process. Can they understand the task, inputs, owner and planned review? Resolve ambiguities before adding more uses.

The register is an organisational tool. It provides no AI Act classification, legal advice or certification. Sensitive uses require an appropriate review.

View the free example.

Help with using digital files.

Find the guides on the main DocPilotIA website.