Skip to content
Interface language: English
Audit / Signal

How to prepare materials for an AI audit and start with facts

Agree the audit question and prepare a source index, access arrangements and evidence matched to the review.

Article language: English

An illustration of a gold-coloured lantern lighting stone steps and cracks in a wall.
In this article

An AI audit does not require bringing the whole company drive and hoping the important files step forward on their own. Agree the scope, prepare an evidence index and identify people who can explain it. Select contracts, use cases, access information and data-flow descriptions according to the audit question. This exposes gaps earlier and helps limit sharing to what is actually needed.

A licence-renewal review needs a different set from a data-flow review or an assessment of agents. Their common core is tools, contracts, uses, responsibility and information sources. The structure below helps prepare input for an agreed task without pretending it is already a diagnosis.

What should be agreed before collecting files?

Write the question the review should answer. Identify the team, processes and period. Agree who receives the report and who approves access to materials. If the scope covers only one part of the company, do not automatically collect data from every other part.

Agree required information categories and how to show them with the provider. Some facts can be confirmed in an admin panel during a shared session. Others need an export or document copy. For each category, know what conclusion examining it should make possible.

Appoint one person to coordinate questions. They need not know every answer, but should be able to find the owner of a contract, tool or process and bring discrepancies to resolution.

How do you prepare a materials index?

Create a register with document name, owner, date, location and access level. Add a “what it should demonstrate” field and availability status. A file list then becomes a source map rather than another unexplained folder.

For contracts, retain information about amendments and validity periods. For exports, record extraction date, scope and column definitions. For instructions, distinguish the approved version from a draft. An undated document or one without an owner may still be useful, but that uncertainty should be recorded.

If material is missing, mark the gap and the person responsible for clarification. Do not fill the register with an assumption. Discovering that the company has no confirmed contract version can itself be an important preparation result.

What should you gather about tools and licences?

Prepare a list of products, plans, organisation accounts, administrators and resellers. Add purchased and assigned access counts, renewal dates and the source of each price. The AI tool inventory (in Polish) gives a more detailed structure.

Obtain administrative reports using the appropriate role and a justified data scope. Microsoft describes Copilot reporting options and access requirements. Keep the report name, period and export date with the file so that the numbers can later be interpreted correctly.

Mark individually paid tools, extensions and trial accounts used for work separately. Central purchasing lists may omit them. When uncertain, return to the tasks performed by the team rather than relying only on brand names.

What should you gather about uses and data?

Select several representative processes. For each, record the task, input material, output and person checking it. Note whether the tool receives a file manually or reads it through an integration. This description helps select further evidence.

At this stage, data categories and approved examples are enough. Agree separately how any real materials will be shared. If a trial is needed, prepare test material that retains the task's characteristics. The guide to preparing an AI data-flow register (in Polish) shows how to map successive storage locations. For a larger set of examples, check consistency of relationships and events in synthetic data (in Polish), so convenient test data still represents the task being assessed.

Include current usage instructions, the procedure for approving a new tool and the way errors are reported. Record which rules are used in practice and which are only planned. An assessment needs both pieces of information in separate fields.

How do you transfer materials and retain access control?

Agree the workspace, roles and access duration. Record who may download copies, to whom questions may be passed and where results will be kept. Confidentiality terms should match the materials before they enter the review.

Do not put passwords or access keys in the document index. If an account is needed, assign an appropriate role in the service. Access to the report itself may be narrower than access to all source data. At the end of the stage, check which permissions are still needed.

Aeneia conceptual photography

What if versions conflict?

Keep both versions and describe the difference. For two licence lists, check dates, organisation scope and export sources. For a contract and a renewal offer, record which describes current terms and which is only a proposal. Do not merge them into one table without explanation. If the package includes model instructions, separately organise versions and owners of the prompt library, so it is clear which instruction actually governed the run under review. For preparation, see the guide to organising prompt-library versions and owners (in Polish).

Assign a question and owner to each discrepancy. The reviewer should know whether sources permit a decision or confirmation is needed from the company or provider. This record lets part of the work begin despite gaps, with their effect on the result stated honestly.

How do you prepare one complete evidence package?

Choose the question and gather only materials needed to resolve it. A renewal review might include the contract, next-period offer, assignment export and description of use. Link each file to the same order and period. The provider can then check dependencies without guessing which attachments belong to the same case.

Working example: a spreadsheet shows a different access count from the invoice. Add the dates of both sources, the organisation-account scope and information about assignment changes. The question is what explains the difference. Do not assume immediately that the provider billed incorrectly or the team has excess licences. First check whether the period and definitions of the counts match.

For this kind of case, use the questions before Copilot renewal (in Polish). If the review concerns task quality, include AI pilot criteria (in Polish), material approved for the trial and a way to accept the result. Activity reports alone cannot replace these elements.

How do you describe material with limited availability?

In the index record what the document confirms, who holds it and the agreed method of inspection. That could be a shared session, selected export scope or prepared copy. If some information is hidden, describe the limitation's effect on the analysis. A missing column can prevent a specific conclusion even when the file opens correctly.

Label a prepared copy as review material and retain its connection to the source version. Do not overwrite the original. Before transfer, check sheets, comments, attachments and other places that may contain additional information. The scope of that check should match the file type and the data owner's agreement.

If the team cannot establish the version in force, start with organising the company knowledge base (in Polish). The auditor should receive notice of the conflict and the person responsible for resolving it. Hiding the discrepancy in a “final” export can make the finding harder to reconstruct later.

How do you test the handover before analysis starts?

Choose several representative index entries. Ask an authorised recipient to open the material, read its date and identify the question it concerns. Check source links and agreed download access. Record incorrect permissions, unavailable attachments and unclear names as specific tasks to fix.

Microsoft's Copilot reporting documentation distinguishes several reporting locations and required roles. We checked the cited official material on 27 October 2026. Enter the exact report and the account that produced the export in the index. Match administrative access to the task without sharing the password of the person who works there daily.

Also agree how questions are raised. One list with a material identifier, question, owner and deadline reduces the risk that an answer remains only in a private message. When a question affects scope or the result date, the coordinator should see that dependency.

What should be retained after preparation and review?

Close the index in a version corresponding to the agreed stage. Record what was supplied, what was not obtained and which limitations remain. Then review access to folders, test accounts and working copies. Restrict or end permissions no longer needed, within the agreed scope.

The company should receive a clear set of findings and a way to maintain them. Accepting documentation, code and access after agent work (in Polish) shows a similar problem in a technical project. For an audit, also retain the list of open questions so the next person knows which facts were confirmed and which still need evidence.

If the scope includes live workflows, gather their run history, errors and examples of manual work after automation. An audit of business-process automation (in Polish) helps describe triggers, exceptions and responsibility for recovery. Input materials then show everyday operation, not only the design the flow was intended to follow.

If materials include scans, first check OCR text-recognition quality (in Polish). A number or heading may be read incorrectly before the model analyses it. Keep the ability to compare a representative passage with the original.

How do you check readiness to start work?

Walk through the index with the review coordinator. Open a few sample materials using the agreed permissions. Check that gaps have owners and that people know how to ask questions. Determine which gaps affect timing or the possible scope of the result.

  • The question and review boundaries are recorded.
  • Materials have owners, dates and source descriptions.
  • Exports include scope and definitions.
  • Transfer and access termination have been agreed.
  • Gaps have a deadline for clarification.

If the review concerns a law firm, add a Shadow AI map. Determine the preparation scope using the Aeneia Audit offer. For preparation, see the guide to mapping Shadow AI in a law firm (in Polish).

Aeneia / Aeneia editorial

Editorial article. Source links are included in the text.

About Aeneia

Brands we have worked with

  • L’Oréal
  • Garnier
  • Netflix
  • Carrefour
  • Warner Bros. Discovery
  • Biedronka
  • HBO Max
  • Wolt
  • Żabka
  • COSRX
  • Embassy of China in Poland
  • Mixa
Aeneia / Initium

From knowledge to a decision

Tell us what you want to put in order. We will agree on where to start.

Contact Aeneia

We partner with and use solutions from:

  • Google
  • OpenAI
  • Microsoft
  • Stripe
  • Anthropic
  • Linear