Article-level gap view
Per article, teams see whether an area is ready, still has gaps, or is missing evidence entirely. Open points remain attached to the affected article.
Product module · Audit playbook
Audit playbook for the EU AI Act: turn article-level gaps into concrete actions
SimpleAct does not stop at checklists. The audit playbook shows per AI system and per article what is ready, where gaps remain, which evidence is missing, and who is working on the action with which deadline.
Visible in the product
The audit playbook translates regulatory obligations into concrete work. Governance then takes over evidence, review, and final approvals.
Status per article with ready, gap, or missing
Open points and missing evidence visible directly on the article
Action plan with owner, due date, note, and quick fix
How SimpleAct handles this
The audit playbook makes obligations operationally manageable
Instead of merely flagging regulatory gaps, SimpleAct turns them into concrete work packages. That keeps audit preparation out of scattered spreadsheets and disconnected tickets.
Action plan with accountability
For each gap, teams can maintain owner, owner override, due date, priority, SLA, and note. That turns an abstract obligation into a concrete work item.
Direct handoff into governance
When evidence is missing, the playbook leads directly into evidence work. Governance then handles review, approval state, and hard finalization gates.
Product flow
From article status to a defensible evidence chain
The audit playbook sits between regulatory classification and final approval. It is where teams reduce actual compliance backlog.
01
1. Legal logic and system context provide the basis
Role, deployment context, and obligation profile are already known from legal logic. The audit playbook uses that frame to structure articles and actions.
02
2. Manage actions per article
Teams see open points, missing evidence, suggested owners, and deadlines. Quick fix, reopen, and mark done keep the work moving.
03
3. Close work through evidence and approval
Once the operational task is complete, the focus shifts to evidence and approval. Governance then secures review, evidence quality, and FINAL state.
What teams actually see and control in the audit playbook
The module uses operational terms on purpose because real follow-up work is managed here.
Ready, gap, and missing state per article directly in the overview
Open points with direct relation to missing evidence
Suggested owner and owner override per action
Due date, priority, and SLA for operational steering
Quick fix, reopen, and mark done for work-state control
Direct path to the missing evidence instead of a separate task list
Open-Source Framework
simpleact-ai-governance-playbook
Open-source playbook: article mappings, action templates, and audit items for the EU AI Act – ready to use in SimpleAct.
Frequently asked questions about the audit playbook in SimpleAct
Is the audit playbook just a checklist?
No. Checklist logic is only the entry point. In the product, the focus is on article-level gaps, actions, owners, deadlines, and the direct connection to missing evidence.
Why do quick fix and reopen matter?
Because audit work is rarely linear. Teams need to trigger actions quickly, close them, reopen them, or refine them with more context without leaving the system.
Where does the audit playbook end and governance begin?
The audit playbook manages operational execution. Governance takes over the evidence register, review flow, approver logic, and final approvals.
An audit playbook is only useful if it creates real work
SimpleAct keeps actions, responsibilities, deadlines, and evidence paths in one system. That turns regulatory backlog into an operational flow teams can actually manage.
