Received an AI Act request from a regulator, customer, partner, or the EU AI Office? Identify the request type and generate a structured, point-by-point response letter — with your role, system details, documentation, gaps, and next steps — in minutes.
An AI Act compliance request asks an organisation to demonstrate how an AI system complies with Regulation (EU) 2024/1689. A proper response identifies the request, states the organisation's role (provider, deployer, importer, or distributor), identifies the system, answers each question point by point, references the relevant documentation, discloses any gaps with a dated remediation plan, and names a responsible contact. Requests may come from a market surveillance authority, the EU AI Office, a customer running due diligence, or a business partner. The right response type depends on the sender, the topic (high-risk system, GPAI model, Article 50 transparency), the organisation's role, and the deadline.
Received a request and not sure what to send back? Answer five quick questions and we’ll point you to the right response and what it should contain. No sign-up, nothing stored.
Select one option in each of the five questions to see your recommendation.
Match the request you received to the response you should send — and what it should contain.
| Request source | Typical issue | Your likely role | Best response | What to include |
|---|---|---|---|---|
| EU AI Office | GPAI model documentation | GPAI provider | GPAI documentation response | System/model name, model documentation, risk measures, GPAI Code of Practice reference |
| Market surveillance authority | High-risk system inquiry | Provider / deployer | High-risk documentation response | Request reference, technical documentation, risk-management & human-oversight records, timeline |
| Regulator (general) | Compliance / information request | Provider / deployer | Regulator request response | Request reference, role statement, point-by-point answers, enclosures, named contact |
| Customer / procurement | Vendor AI due diligence | Provider / supplier | Due diligence response | Due-diligence answers, documentation summary, compliance status, responsible contact |
| Business partner | Article 50 transparency / labelling | Provider / distributor | Article 50 transparency response | Article 50 disclosure, content-labelling approach, user notice, marking method |
| Any sender (tight deadline) | Not enough time to respond fully | Any obligated party | Extension request letter | Request reference, reason for delay, proposed new date, partial answer, named contact |
General information, not legal advice. Roles and responses depend on your specific situation under Regulation (EU) 2024/1689.
Original AI Act timeline vs the Digital Omnibus proposed timeline. “Proposed” dates are conditional on formal adoption and publication of the Digital Omnibus in the Official Journal.
| Topic | Original date | Digital Omnibus | Status |
|---|---|---|---|
| Prohibited practices (Art. 5) | 2 Feb 2025 | Unchanged | Active |
| AI literacy | 2 Feb 2025 | Unchanged | Active |
| GPAI model obligations | 2 Aug 2025 | Unchanged | Active |
| GPAI enforcement powers | 2 Aug 2026 | Unchanged | Pending |
| Article 50 transparency (most) | 2 Aug 2026 | Unchanged | Pending |
| Article 50(2) provider watermarking | 2 Aug 2026 | 2 Dec 2026 | Proposed |
| Annex III high-risk systems (standalone) | 2 Aug 2026 | 2 Dec 2027 | Proposed |
| Annex I embedded high-risk systems | 2 Aug 2027 | 2 Aug 2028 | Proposed |
Status key: Active = in force now · Pending = applies on the original date, unchanged · Proposed = new date, conditional on the Digital Omnibus being adopted.
General information, not legal advice. The Digital Omnibus was a provisional political agreement at the time of writing and is not yet formally adopted.
A market surveillance authority asks how your system complies. The EU AI Office requests documentation for a general-purpose AI model. A customer's procurement team sends an AI due-diligence questionnaire before they will sign. A business partner asks how you meet the Article 50 transparency rules. Each of these is an AI Act compliance request, and each one needs a clear, documented, formal answer.
The instinct is to fire back a quick email. That is exactly what turns a routine inquiry into an investigation. A reply with no structure, no identification of your role, no documentation, and no remediation plan signals that you are not in control of your obligations — and invites follow-up questions, escalation, or a failed vendor assessment.
The opposite mistake is silence or delay. A request with a deadline that passes unanswered is far worse than a request answered with an honest gap and a remediation timeline. Regulators and customers reward organisations that respond precisely, on time, and on the record.
The hard part is not willingness — it is knowing exactly what kind of response is expected, what it must contain, and how to phrase it so it closes the loop instead of opening new ones.
DocuGov.ai turns an incoming AI Act request into a structured response in two moves. First, the triage tool above classifies your situation — who sent the request, what it concerns, your role, what you need, and how urgent it is — and tells you the response type that fits, from a regulator request response to a GPAI documentation response, an Article 50 transparency response, a customer due-diligence response, an extension request, or a remediation plan.
Then the generator produces a complete, point-by-point letter built on the structure authorities and partners expect: it identifies the request, states your role under the Act, identifies the system, answers each question, references your documentation, is candid about any gaps with a dated remediation plan, and closes with a named contact and a clear next step.
This is not a generic AI Act explainer written for boards and law firms. It is an operational tool for the person who has a request in their inbox and a deadline on the calendar. You stay in control: every draft is yours to review and edit before you send it.
Triage the request — Use the tool above to classify who sent it, what it concerns, your role, and your deadline. You get the recommended response type and a checklist of what it must contain.
Generate the response — Describe the specifics in plain language. We produce a complete, structured response letter citing the relevant AI Act articles, listing your enclosures, and proposing next steps.
Send and keep the record — Download in DOCX or PDF, send it to the authority, customer, or partner, and keep a clean, dated paper trail that shows you responded properly and on time.
Why it fails: An unstructured reply with no role statement and no documentation reads as a lack of control and invites escalation.
✓ Solution: Send a formal, point-by-point response that identifies the request, your role, the system, and your enclosures.
Why it fails: A passed deadline is far more damaging than an honest gap, and can trigger formal proceedings.
✓ Solution: If you cannot answer fully in time, send a documented extension request before the deadline, with a proposed new date.
Why it fails: Regulators and customers respond far better to a documented remediation plan than to silence or denial.
✓ Solution: State what is missing, what you are doing about it, and by when — with milestones and owners.
Why it fails: Obligations follow from whether you are a provider, deployer, importer, or distributor; the wrong role frames the whole answer incorrectly.
✓ Solution: State your role explicitly and answer from that position.
Why it fails: If the system processes personal data, the GDPR applies at the same time and data protection authorities keep jurisdiction.
✓ Solution: Address both regimes where relevant, rather than treating it as an AI Act-only matter.
Answer a few questions and get your professional letter in minutes
Answer a few questions and get your professional letter in minutes
Select the document type that best matches your situation.
Pay per document. No subscriptions. No hidden fees.
Attorney help for routine formal documents
can cost hundreds of dollars. DocuGov.ai helps you create a structured draft in minutes for $9.
$200+
Lawyer
$9
DocuGov
AI Letter
Perfect for straightforward cases
AI + Expert Review
For complex or high-stakes matters
An AI Act compliance request is a formal or semi-formal request asking an organisation to explain how an AI system complies with Regulation (EU) 2024/1689 — usually by identifying the system, the organisation's role, the applicable AI Act category, the relevant documentation, and any remediation steps. It can come from a market surveillance authority, the EU AI Office, a customer or partner, or as part of a complaint.
It should identify the request, state your role under the Act, identify the AI system, answer each question point by point, reference the relevant documentation, explain any gaps with a dated remediation plan, and name a responsible contact with a clear next step.
Typically a national market surveillance authority, the EU AI Office (for general-purpose AI matters), a customer or downstream provider running due diligence, or a business partner verifying contractual AI compliance. An individual affected by a system may also raise a complaint, which is handled differently.
Use the triage tool on this page. Answer five quick questions about who sent the request, what it concerns, your role, what you need, and your deadline, and it will point you to the response type that fits and what it should contain.
Send a documented extension request before the deadline passes. State the request reference, a specific reason for needing more time, the new date you propose, and any partial answer you can give now. A timely, reasoned extension request is far stronger than a missed deadline.
No. This is a practical tool that helps you produce a structured response and understand what it should contain. It is general information, not legal advice. For your specific situation, check the current text of Regulation (EU) 2024/1689 and consult a qualified lawyer.
The dates already in force (prohibited practices, GPAI obligations) are final. Several high-risk obligations may move under the Digital Omnibus on AI — a provisional agreement that, at the time of writing, is not yet formally adopted. See the deadlines tracker on this page for the current original-versus-proposed timeline.
This page is for organisations that received an AI Act compliance request and need to respond. If instead you are an individual affected by an AI decision — a rejected loan or job application, an automated decision, or a deepfake — you are looking for a different tool. See our AI rights letters for affected individuals, including prohibited AI practice complaints and GDPR Article 22 objections.
If an algorithm made a decision about you — credit, hiring, a deepfake — challenge it here.
Learn moreReport a banned practice under Article 5 to your national authority.
Learn moreObject to a solely automated decision and demand human review.
Learn moreThe current timeline, the Digital Omnibus, the penalties, and how to respond.
Learn moreJoin thousands of people who got professional government letters without hiring a lawyer.