Guide
How long does AI compliance take? Realistic timeline
A data protection and AI compliance project isn't a weekend job, but it's not a six-month project either. What happens in which order, where things typically get stuck, and how to shorten the timeline.
In practice, data protection and AI compliance takes 3 to 5 weeks. The biggest time factor is almost never the implementation itself, but how quickly content, access, and decisions come from your side.
01 — Timeframe
How long it takes
- Typical duration
- 3 to 5 weeks
- Price
- Individual based on effort
The timeline starts after approval of the quote. Lead time for initial meeting and quote: typically one to two weeks. We provide a fixed price after this initial meeting.
02 — Process
The steps in detail
Taking stock
What is being used, by whom, with what data. Usually more than management is aware of.
Classification
Risk class per application, and the specific obligations that follow.
Writing the rules
A policy that's short enough to actually be read.
Implementing and documenting
Build in labeling, document training, file the records.
03 — Bottlenecks
What typically causes delays
- Content and deliveries. By far the most common cause of delay. Text, images, price lists, access credentials — what's missing blocks progress.
- Decisions. When it's unclear who approves, the project waits. A named contact person with decision-making authority noticeably shortens the timeline.
- Access to third-party systems. Getting access to inventory management, phone systems, or CRM regularly takes longer than the integration itself.
- Endless review rounds. Two correction rounds are normal, five are a sign that the goal wasn't clear at the start.
04 — Scope
What's included
- Inventory: which AI tools are actually being used in the business
- Classification under the EU AI Act — risk class and resulting obligations
- Review of the data protection situation for each tool, including data processing agreements
- Usage policy that's practical in everyday work rather than just formally correct
- Implement labeling requirements for chatbots and AI-generated content
- Proof of AI competence through documented training
05 — Questions
Frequently asked questions
Does this also apply to sole proprietorships?
Yes. The AI Act doesn't distinguish by company size, but by purpose and risk. Anyone with a chatbot on their website is affected — regardless of whether one or a hundred people work in the business.
Do AI-generated texts need to be labeled?
For content that is published and synthetically generated or substantially modified, yes. Purely internal use — research, drafts, summaries — typically does not trigger this obligation.
How often does the inventory need to be updated?
Whenever a new tool is introduced or the purpose of an existing one changes. An annual review as a minimum interval makes sense, even without a specific trigger.
Do we need a data protection impact assessment?
Not generally. It becomes necessary when the processing is likely to pose a high risk to data subjects — such as extensive profiling. For an FAQ chatbot on a website, it's usually not required. We review this case by case and document the result in writing.
What if we use multiple AI tools from different providers?
Each tool is assessed individually — provider, data processing, and risk class differ. The usage policy summarizes the results so no one has to look up each tool separately.
May we enter customer data into ChatGPT?
In the free version without contractual safeguards: no. With a business account, data processing agreement, and training excluded, it may be permissible — depending on what data is involved. Precisely this distinction belongs in the usage policy, because it's constantly relevant in daily operations.
Is a verbal agreement within the team sufficient instead of a written policy?
No, in case of dispute or audit, only what is documented counts. A brief written policy also protects new team members who never heard the verbal agreement.
06 — Next
Related pages
- Data protection and AI compliance — Overview
- Data protection and AI compliance — Process
- Data protection and AI compliance — team and acceptance
- Data protection and AI compliance — where to start
- Data protection and AI compliance — AI labeling
- Data protection and AI compliance — How it works
- Data Protection and AI Compliance — Risks
- Data protection and AI compliance — requirements
- AI Consulting
- AI training
- AI chatbot
- All guides
Data protection and AI compliance by region
Next step
Initial assessment, no obligation.
Briefly describe what you need. You'll get an honest answer about what's realistic and what it will roughly cost.