On November 18 the Government of Canada published the results of its consultation on the federal AI Register. Respondents welcomed public disclosure and described the information they still needed to understand a system in use. For an organisation preparing its own AI inventory, the report offers a practical reading test. Hand one entry to the person responsible for the service and see whether they can explain what happens to a customer's request.
What the consultation examined
The Treasury Board of Canada Secretariat gathered feedback on the initial version of the federal register. Its consultation report records support for publishing an early version and improving it in response to feedback. People generally wanted to keep the fields that were already there. Some described what would make a particular entry easier to read. Others wanted a route from the entry to documents explaining how the system is governed.
The register covers federal systems. In a company buying an inventory, two colleagues might open the same record for quite different reasons. A procurement lead renewing a contract needs to find the product owner. A service manager handling a complaint needs to know how staff used the output on the case in front of them. A single entry can serve both people if its wording is specific enough.
Try the entry on a real kind of request
Imagine a municipal office testing software that suggests a destination for incoming maintenance requests. A resident writes, “The streetlight by the corner is out. Someone could trip on the loose paving stone underneath it.” The office's inventory says the new software improves service delivery. Reading that entry from the counter, you still cannot tell who has the message. It might already be with a road crew. It might be sitting on a clerk's screen waiting for someone to choose a department.
Try this description in the review meeting instead. “The tool suggests a receiving team for a written request. The duty clerk reads the message and can choose a different team before the request is assigned.” A colleague can now tell where human judgement enters the process. Those sentences describe our fictional office. Before putting either in a working register, sit with the duty clerk and watch what appears on their screen.
- Ask the manager for a type of request that regularly lands in the wrong inbox. A single anonymised example will do.
- Give the entry to somebody who missed the project meeting. Note the first thing they need to ask a colleague in order to follow that request.
- Identify the person who can correct the entry if the workflow changes. A link to a supplier's technical manual rarely tells the reader who owns the local process.
- Record the review date and the evidence the reviewer checked. Keep the earlier entry available to the team dealing with older cases.
What to put in a scope of work
Price the collection of evidence separately from formatting the register. In the maintenance example a reviewer might need to sit with a clerk to establish what the software actually does when a request mentions two problems. That observation is a different task from putting an approved description into a searchable table. A quote that includes only the second task leaves the most useful conversation with the buyer.
Ask for one sample entry before commissioning an inventory across several departments. Give it to a colleague who receives public enquiries and ask them to find the owner of a correction. If they can locate the right team but cannot tell whether the tool is still in use, add an operating status and a review date. A reader can then distinguish an active service from a pilot that has ended.
Start with the system that already has an owner
Choose a service whose manager can review the wording and approve a correction. Remolda's AI strategy and governance services cover the planning work around organisational AI use. Send Remolda a governance brief naming the service and the person who needs to read its first entry. Include one question they have had to take back to the project team. An invented maintenance request like the one above gives us enough context to scope that work.
