Prove it
Status report for your AI governance
What applies, from when and what is missing, in a document that can circulate within the organisation.
What it is for
The “Status report” brings together on one page the recorded state of your AI governance, as a map of obligations: what applies under the classification of your systems, from when, and what is pending recording or review.
No percentages or overall scores: it reflects the recorded state, not a rating. It is not an external audit: it reflects what is recorded in Alethexis as at the date shown.
It carries no names of people, no record of who decided what, and not even the names of your risks, so that it can circulate. The only personal data item is the email address of the person who generates it.
How it works
Obligations with their date
Each obligation appears with its date of application — “In force since…” or “Applicable from…”, with the days remaining — derived from the recorded classification of each system.
Detail of each system
Level, route, effective role and date of application of each system; with High-Risk Ready, also the DPIA screening and the FRIA; with Agentic, the “Agentic” column. Levels P0–P6 are Alethexis's internal taxonomy, not the AI Act's terminology.
What is pending, linked to where it is resolved
Systems with no current classification or no determined role, missing DPIA screenings, classifications and sections flagged for review, open high risks with no mitigation plan, and controls with no owner or with an overdue review. On screen, each line takes you to the screen where it is resolved; if nothing is pending, it says so.
Recorded AI literacy measures
With Visibility, the report includes the current AI use policy, its acknowledgements among the people with access to the account, and the training evidence recorded.
Period and change over time
You choose 30, 90 or 365 days for the activity in the period: decisions recorded by type, evidence and AI use requests. From the second PDF downloaded onwards, the report compares its figures with those of the previous one.
What you get
PDF with integrity hash
The same content as the screen, with an annex holding the full inventory of systems and the audit log integrity. It is produced in the account's legal language. Its SHA-256 hash is recorded in Alethexis: the hash shows that the document has not changed, but it does not identify who issued it.
FAQ
- Who can generate it?
- The Owner, AI Officer, DPO and Auditor open the report and download the PDF. The Contributor does not see it: the link does not appear in their menu.
- Do I need a specific module?
- It does not depend on a specific module. With Visibility alone the report is shorter: the blocks for modules you do not have active are left out.
- Are versions of the report kept?
- The report is not versioned: each PDF is a snapshot of the moment it is generated. Each download is recorded in the audit log as “Document downloaded”.
- How do I check that a PDF has not been altered?
- Compute the SHA-256 of the downloaded file and compare it with the hash recorded in Alethexis.