Article 50 Review
A scoped review of one customer-facing AI system.
A person, not a tool, reviews what your users actually see. You get the relevant Article 50 questions, the evidence behind each observation, and a prioritised list of what to do next.
Starting price
€490
for one system or flow
Subject to scope confirmation. The scope check confirms the system, the flow, the channels and the final price.
What a single system or flow can look like
Illustrative examples- The chat assistant on your help centre, on web and in the mobile app
- A voice agent answering your support line
- An in-product feature that generates images for users
- A newsletter on matters of public interest drafted with AI
What you receive
- 01
Scope and role assumptions
The system, the flow, the markets and whether you act as provider, deployer or both, written down as assumptions to confirm.
- 02
Reviewed user-facing flow
The journey a user takes, step by step, as it was reviewed on the stated dates and channels.
- 03
Evidence notes
What was observed at each step, with references to the screenshots, messages or metadata that support it.
- 04
Relevant Article 50 questions
The transparency questions that apply to this system and role, and the ones considered and set aside, with the reason.
- 05
Prioritised actions
Practical next steps, ordered by priority, each linked to the finding it addresses and a suggested owner.
- 06
Review call
A call to walk through the findings with your team and answer questions about the report.
How the review runs
- Step 1
Scope check
You describe the system and where users encounter it. We confirm the scope, the role assumptions and the price in writing.
- Step 2
Review
We walk the agreed flow as a user would, on the agreed channels, and record evidence at each step.
- Step 3
Report
You receive the findings and evidence report, structured like the sample report.
- Step 4
Review call
We walk through the findings together. Timing for each step is agreed during the scope check.
What we need from you
- Access to the user-facing flow as a user would see it, for example a public URL or a staging environment
- A short description of the system, the vendor or model it relies on, and the markets it serves
- A contact who can answer product questions during the review
We do not need source code, production credentials or personal data. If the flow sits behind a login, we agree a safe way to access it during the scope check. Please do not send credentials through the contact form.
Start with a scope check.
Tell us about the system you want reviewed. We reply with the proposed scope, the role assumptions and the price.