Skip to content

Audit Phase ​

Audit is where you validate the current state and package it for internal readiness review. The goal is a confirmable snapshot, backed by Evidence and the audit trail.

Audit is the last of the lifecycle phases:

Outcome ​

You leave this phase with:

  • a validated readiness snapshot (Requirements, Controls, Evidence)
  • exports that represent the current state
  • an audit trail that supports internal assurance review

Time to first value: 30–60 minutes
Prerequisites: governance work is underway and Evidence is attached to priority Controls

Internal audit focus

This phase focuses on internal readiness and internal audit review. It is about traceability, Evidence quality, and defensible status snapshots.

Path at a glance ​

  1. Freeze scope Confirm frameworks, versions, and AI System context.
  2. Validate statuses Make sure that the Fulfilled and Executed statuses agree with the Evidence.
  3. Export the AI System Generate the AI System PDF and gather Evidence downloads.
  4. Review the trail Validate decisions and status changes.

Step 1: Freeze scope for the review window ​

Goal: ensure you’re reviewing the right version of the truth.

Where in Modulos

  • AI System → Dashboard for the frameworks, the description, and the current AI Lifecycle Stage
  • AI System → Settings → Frameworks for the version of each framework, if you can open Settings (AI System Owners and the organization roles with full access to AI Systems)

Do this

  • Confirm frameworks and versions are correct for the review window. If you cannot open Settings, ask an AI System Owner to confirm the versions.
  • Confirm the AI system description and lifecycle stage match what is being reviewed.

You’re done when

  • the scope is stable enough for internal review and sign-off

Step 2: Validate statuses against Evidence ​

Goal: ensure statuses match reality.

Where in Modulos

  • AI System → Requirements
  • AI System → Controls
  • AI System → Evidence

Do this

  • For fulfilled Requirements, spot-check mapped Controls and their Evidence.
  • For executed Controls, verify Evidence demonstrates execution and is not stale or irrelevant.

You’re done when

  • readiness claims are defensible from Evidence and mappings

Step 3: Export the AI System for internal review ​

Goal: produce a record that can be reviewed without live navigation.

Where in Modulos

  • AI System → Dashboard → More actions → Export
  • per-file Evidence download from each Control's Control tab

Do this

  • Make the AI System PDF with Export in the More actions menu of the Dashboard.
  • Download the underlying Evidence files an auditor needs to see directly, rather than relying on the PDF summary alone.

You’re done when

  • you can hand off the AI System PDF and the Evidence files that support it

Step 4: Review the audit trail for key decisions ​

Goal: make decisions and status changes traceable.

Where in Modulos

  • AI System → Controls → select a Control → Comments and Logs for the log of each Control
  • AI System → Requirements for each Requirement's review state and its own Comments and Logs

Do this

  • Review the key events in the Comments and Logs of each Control: Owner changes, status changes, and the Evidence that users attach or remove. The status changes of a Requirement, including Fulfilled, are in the Comments and Logs of that Requirement.
  • Confirm that the Comments and Logs of each Control record its status changes. When an Executed Control went back to Not Executed while a mapped Requirement was ready for review, read the reason in its comment.
  • Confirm that each in-scope Requirement was reviewed and marked Fulfilled by its Requirement Owner.
  • Resolve any inconsistencies before final sign-off.

You’re done when

  • the Controls' Comments and Logs and the Requirements' review states support the story your status snapshot is telling

Next ​