AI Act readiness for an OEM audit
Unclear.Documented.
the answer to “who is the provider?”
- Client
- Industry
- Industry
- Region
- Germany
- Moves
- Comply
- Kick-off to hand-over
- 4 weeks
- Year
- 2025
01The void
An OEM customer asked for AI documentation on three product components. Nobody knew who the provider was, which risk class applied, or where the evidence lived.
02Results
Sample figures. Replace with the numbers the client signed off.
03How we worked
- 01 · 1 dayFind the void
Management briefing: provider or deployer, and why it matters.
- 02 · 1 weeksScope & evals
Inventory of 14 AI systems; three of them inside products.
- 03 · —Build
No build: documentation, not code.
- 04 · 2.5 weeksSecure & comply
Risk classification, technical documentation, ISO 42001 as a layer on ISO 9001.
- 05 · half a weekHand over
Roles assigned; templates live in their QMS now.
04What we built
- 01Inventory14 systems
- 02Classificationrisk class
- 03Roleprovider or deployer
- 04Technical fileper component
- 05QMSISO 42001 layer
- 06Auditevidence pack
05Guardrails
- Classification reviewed by client counsel
- Evidence mapped to existing ISO 9001 processes
- An owner for every AI system
06Stack
07In their words
A quote from the process owner goes here, once they have approved it. No invented testimonials.
More cases like this
of files still need a human. The rest clear themselves.
Finance · Germany · 20259 weeks
KYC review agent
Every file. → Exceptions.what reviewers see
people trained, role by role
Finance · Austria · 20266.5 weeks
AI literacy programme
Slides. → Practice.how Article 4 gets done
of inbound claims, handled end to end
Insurance · Germany · 20257 weeks
Claims triage agent
6 days → 4 hourstime to first decision
Case #10
Your void could be
the next one.
A first call about your void. No deck. If it isn’t a fit, you’ll hear that too.
Find our void