01
Scope and requirements
Systems, legal entities, applicability, and owners are pinned before assessment.
END-TO-END AUDIT · EVIDENCE TO REPORT
Audit 2.0
An audit where every conclusion can be verified
Audit 2.0 brings scope, requirements, evidence, requests, findings, and documents into one secure process. Automation handles routine work while the auditor retains authority.
A2 / REPEATABLE AUDIT CYCLEFrom an AI-assisted plan to verified compliance
The completed cycle is ready to run again
END-TO-END PROCESS
The entire audit in one reviewable chain
Scope, methodology versions, and evidence versions are pinned. The server allows each transition only after authoritative readiness conditions pass.
02
Material collection
Files, websites, conversations, and connected sources enter quarantine.
03
Evidence review
The auditor accepts, rejects, or requests changes with a complete decision history.
04
Coverage and gaps
Coverage is calculated separately from quality, freshness, and AI confidence.
05
Findings and review
Every material conclusion links to a requirement, evidence, actor, and version.
06
Report and approval
Markdown, DOCX, and PDF are built from one canonical version and independently reviewed.
HUMAN DECISION GATES
RESULT
Result: a continuous provenance chain from the audit scope to the approved report package.
MATERIAL LIFECYCLE
Evidence does not become trusted by itself
Every material version passes explicit states and a human accepts its relationship to a requirement.
Quarantine
A file or message is isolated and checked before use.
Extraction
A safe copy, extracted text, and provenance metadata are created.
Normalization
The item is classified, normalized, and assigned a sensitivity level.
Link proposal
A precise source location is proposed for a specific requirement.
Human review
The auditor decides and records quality, freshness, and conflicts.
History
Version, decision, actor, time, and content hash remain immutable.
IN-PROCESS ASSISTANTS
Automation suggests the next step without making the decision
Three assistants join sequentially and route the auditor to an existing authoritative workspace.
Scope readiness navigator
Finds missing applicability decisions, systems without owners, and incomplete scope.
Evidence curator
Surfaces human review queues, unprocessed items, and requirements without evidence.
Gap analyst
Connects coverage, open gaps, and data requests to preserve the next grounded action.
What an assistant cannot do
- Accept evidence
- Decide applicability
- Close a gap
- Confirm a finding
- Approve a report
- Sign a document
VERSION · INTEGRITY · APPROVAL
One conclusion, three delivery formats, and a verifiable history
The canonical result is immutable. Documents are built deterministically and verified before download.
Markdown
Canonical structured result for history and repeatable rendering.
Document
Editable version for review in an established business process.
Final copy
Handoff view with integrity and completeness checks.
EXTERNAL READY
- 01
Complete output set
✓ - 02
Integrity verification
✓ - 03
Independent AITALON approval
✓ - 04
External delivery permission
✓
The same capabilities in four delivery models
AITALON cloud
Fast start with organization isolation and managed updates.
Dedicated environment
A separate environment for one company or holding.
Customer-hosted
Data and processing stay in the organization infrastructure.
Hybrid
Cloud control plane with sensitive processing at the customer.
ANSWERS WITHOUT SMALL PRINT
Audit 2.0 FAQ
What is Audit 2.0 and what problem does it solve?+
Audit 2.0 is a platform for preparing and repeatedly running audits. It links the plan, requirements, evidence versions, findings, and ready documents in one reviewable chain that can be restarted for the next assessment.
Who is Audit 2.0 for and when is it needed?+
The platform is for auditors, compliance and information security teams, and process owners who need to repeat assessments, retain evidence, and update the document package efficiently.
How does Audit 2.0 work?+
An AI assistant helps create a plan from the selected template and requirements. The team then runs a repeatable audit, collects and reviews evidence, receives ready documents for verification, and confirms compliance; the saved cycle can be restarted at any time.
What does an Audit 2.0 customer receive and how can the result be verified?+
The customer receives a pinned audit result and a document package generated from one data version. Findings trace back to the requirement and exact evidence version, while decision history, approvals, and file integrity support independent verification.
How do we start an Audit 2.0 pilot and where is the data hosted?+
The pilot starts with one repeatable audit type, a pinned scope and requirements, and a ready-made or custom template. The platform can run in the cloud, a dedicated or closed environment, or a hybrid setup; the selected deployment model is fixed before evidence is uploaded.
Does Audit 2.0 replace the auditor?+
No. The platform automates collection, completeness checks, coverage calculation, and document preparation. Applicability, evidence acceptance, findings, and approval remain under human control.
How is the coverage percentage justified?+
Every percentage drills down to scope, requirement, state, and exact evidence versions. Quality, freshness, and AI confidence remain separate.
Can evidence from a previous audit be reused?+
Yes, after scope, requirement version, and freshness checks. Previous acceptance is never inherited automatically.
Can the platform run in a closed environment?+
Yes. Customer-hosted, dedicated, and hybrid options are supported. Original evidence and personal data are not sent to a cloud model.