Skip to content

Evidence ​

Evidence is the proof layer of Modulos. An Evidence item can be a policy document, a screenshot, an export, a log sample, a contract, or a test output that shows that a Control is done.

What this is ​

Evidence changes "we did it" into "we can show it".

In Modulos, Evidence has two properties:

  • one location for each file: an Evidence item is in the Evidence Library of the AI System, and you attach it to the Controls that it applies to
  • use in more than one Control: you can attach one Evidence item to many Controls

For the full flow, see Governance Operating Model.

Where in Modulos ​

  • AI System → Evidence has the tab Evidence Library. It lists the Evidence of the AI System with the columns Name, Type, Size, Control(s), Uploaded at, and Uploaded by. New uploads go to the tab Evidence Creation first, which shows only while it holds uploads. The files that you accept from a Scout proposal also go to this tab (Propose Evidence). The Evidence Agent suggests the Controls for each upload. To add the uploads to the library, select them and select Create n Evidence. Modulos then permanently deletes the uploads that you did not select. New Evidence starts an upload, or opens Evidence Creation while it holds uploads.
  • AI System → Controls → open a Control → Control tab → Evidence to attach Evidence to that Control

Who can do what ​

Permissions

  • All members of an AI System can see and download its Evidence.
  • AI System Owners and Editors can upload, edit, attach, and delete Evidence.
  • Evidence is an audit item. Modulos locks it while a Control that uses it is Executed.
Evidence Library of an AI System with the Search field, the Filter button, Advanced Search, the New Evidence button, and a table with the Controls of each Evidence item.

The Evidence Library holds the proof of an AI System and shows the Controls that each item is attached to.

  1. Advanced Search Find Evidence by its Controls and by its upload date before you upload a file again.
  2. New Evidence Upload files. They go to Evidence Creation before they go into the Evidence Library.
  3. Control(s) Shows the Controls that each Evidence item is attached to.
  4. Actions Copy a link to, preview, download, or delete an Evidence item from its menu.

How it works ​

Evidence is a file-like object with metadata ​

An Evidence item is a file with metadata: a code, a name, a description, the file name and type, a URI, and an optional checksum. Evidence items are in the Evidence Library of the AI System. So you can attach one item to more than one Control.

After an upload, Modulos processes the file so that the AI agents can read it. Processing uses the AI quota of the organization. Until the processing is done, the item shows one of these badges:

  • Processing document…: Modulos waits to process the file, or processes it. The tooltip shows the stage, for example Extracting text or Indexing. After a temporary failure, Modulos tries again automatically, and the badge stays.
  • Waiting for AI quota: the AI quota of the organization is used up. Modulos processes the file automatically when the quota has space again, for example in the next month. See AI usage.
  • Processing failed: Modulos cannot read the file, for example because the file is damaged, encrypted, or empty. The tooltip tells the cause. On the Evidence Creation tab, the cause shows below the badge. Upload a copy of the file that Modulos can read.

When the processing is done, the badge goes away. You can create and attach Evidence while Modulos processes it. The Evidence Agent and the Control Assessment Agent read only processed files. When no AI agent is available in your organization, Modulos does not process uploads and shows no badge.

Upload files ​

New Evidence opens the Add New Evidence dialog. Drop the files there, or click to browse:

  • Supported formats: .jpg, .jpeg, .png, .gif, .bmp, .webp, .pdf, .txt, .md, .csv, .docx, .xlsx, and .pptx.
  • Limits: 100 files in one upload, and 50 MB for each file.
  • Modulos uploads each file when you add it. Abort Upload stops the upload, and Retry Upload sends the failed files again. Add File(s) is available when all uploads are complete.

On the Evidence Creation tab, a file that is already in the Evidence Library shows Duplicate of with the code of that Evidence item. A file that you uploaded two times shows Duplicated. Modulos does not select duplicates for Create n Evidence, but you can select them.

The preview of an Evidence item shows PDF files and images. For other file types, it shows No preview available and Download. In the Evidence Library, the menu of each row has Copy Link, Preview, Download, and Delete. Copy Link copies a link that opens the preview of the item.

Evidence attaches to Controls ​

Each Control has one Evidence section on its Control tab. You attach Evidence there, or you link Evidence to Controls when you complete an upload on the Evidence Creation tab. This lets auditors see which Evidence belongs to which Control.

For example, in an AI System with the EU AI Act and ISO/IEC 42001, one Evidence file is attached to two Controls and gives proof for three Requirements:

Evidence Controls Requirements

  • data_pipeline_logs.pdf Uploaded one time
    • MCF-184 Logging Capability
      • EU AI Act Art. 12 — Record-keeping
      • ISO/IEC 42001 AI system life cycle
    • MCF-223 Data provenance
      • ISO/IEC 42001 Data for AI systems

Attach the file to each Control that it proves. The Control must be Not Executed and in the same AI System. You do not upload the file again.

Locking preserves audit integrity ​

An auditor examines an Executed Control. Thus its Evidence must stay as the auditor saw it. An Evidence item can be used by more than one Control, and it locks while one or more of them are Executed:

  • Editable You can edit and delete the Evidence item
  • a Control that uses it becomes Executed
  • no Control that uses it is Executed
  • Locked You cannot edit or delete the Evidence item

An Out of Scope or Archived Control does not lock Evidence. In the Evidence Library, you cannot edit or delete a locked item. But you can attach it to a different Not Executed Control in the Evidence section of that Control, and remove it there.

The status of a Control decides what you can do with Evidence on that Control:

Control statusAttach EvidenceThe Evidence Agent suggests the ControlRemove Evidence from the Control
Not ExecutedYesYesYes
ExecutedNoNoNo
Out of ScopeNoNoYes
ArchivedNoNoYes

The Evidence section of a Control shows Upload New Evidence and Select Evidence only while the Control is Not Executed.

A Control can go back to Not Executed, and Modulos logs the change. You cannot change the status of a Control that is mapped to a Fulfilled Requirement. A failed test, a Metric Test error, or an archived Policy can also set it back to Not Executed. When no Executed Control uses an Evidence item, you can edit and delete it again.

How to use it ​

  1. Start from a Control Find the Not Executed Control that needs proof.
  2. Upload the file In its Evidence section, select Upload New Evidence. Add one file and select Add File(s).
  3. Name and attach the item Type the Evidence Name and the Evidence Description. In Associate to Control(s), add the other Not Executed Controls that the file proves. Select Add Evidence.
  4. Attach it to more Controls After that, to attach the item to a different Control, select it in Select Evidence on that Control.

Keep to these rules:

  • Use it again only when correct: attach it to a different Control only when it shows the same thing.
  • Attach first: attach all the Evidence before you set the Control to Executed. After that, you cannot attach or remove Evidence on the Control, and its Evidence is locked.

Important considerations ​

  • Give each Evidence item a clear name. "Policy.pdf" does not help. "Access control policy v3.2 (approved 2026-01-15)" does.
  • When possible, upload the primary item (a log, a configuration, a contract, a test output) and not a screenshot of it.
  • If you use screenshots, add notes to them and give the date.