--- title: "The EU AI Act: What it means for your documentation workload" id: "22361" type: "post" slug: "the-eu-ai-act-what-it-means-for-your-documentation-workload" published_at: "2026-06-01T07:12:26+00:00" modified_at: "2026-06-01T07:12:26+00:00" url: "https://www.cherryleaf.com/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload/" markdown_url: "https://www.cherryleaf.com/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload.md" excerpt: "On 2 August 2026, the EU AI Act’s main enforcement phase begins. For organisations developing or deploying AI systems in the European market, documentation is a legal requirement. Here’s what it might mean to your workload. Does it apply to..." taxonomy_category: - "AI" taxonomy_post_tag: - "AI act" - "EU" - "law" - "trends" --- On 2 August 2026, the [EU AI Act’s](https://artificialintelligenceact.eu/) main enforcement phase begins. For organisations developing or deploying AI systems in the European market, documentation is a legal requirement. Here’s what it might mean to your workload. ## Does it apply to you? ### The Act applies to both providers and deployers Providers are organisations that build AI systems and place them on the EU market under their own name. If your organisation makes software with AI features used by European customers, you’re a provider. Deployers are organisations that use AI systems in the course of their work. If you use an AI-powered tool (a recruitment system, a customer service chatbot, a document review tool) in your internal processes, you may be a deployer. Both roles carry documentation obligations. ### A risk-based approach The legislation dictates a sliding scale of obligations depending on the potential risk an AI application poses to human safety and fundamental rights. #### Unacceptable risk (Banned) Systems that threaten human safety or rights are strictly prohibited. #### High risk Systems used in critical infrastructure, healthcare, education, law enforcement, or HR (such as automated CV-scanning) require rigorous risk assessments, high-quality data governance, documentation, and continuous human oversight. #### Limited/Transparency risk AI systems interacting directly with humans (e.g., chatbots) or generating synthetic media (deepfakes) must clearly disclose that the content or interaction is AI-generated. #### Minimal risk The vast majority of AI systems (such as spam filters or AI-enabled video games) fall here and remain largely unregulated, with no mandatory compliance requirements. ### Deadlines The [Digital Omnibus on AI](https://digital-strategy.ec.europa.eu/en/library/digital-omnibus-ai-regulation-proposal) is a European Union legislative package that amends and simplifies the EU AI Act. The Omnibus delays several high-risk compliance timelines to give businesses and developers more time to adapt. Deadlines for stand-alone Annex III systems (such as HR or education AI tools) have been deferred to December 2, 2027, while embedded product software under Annex I moves to August 2, 2028. This documentation must be drawn up before the system is placed on the market or put into service, and kept up to date throughout its lifetime. It must be retained for ten years after the system is placed on the market. ## What documents are required? For high-risk systems, the Act specifies nine categories of technical documentation under Annex IV. As a technical writer, these will look familiar, but the framing is new: - A general description of the system - What it does, its intended purpose, what hardware it runs on, how it interacts with other systems - A detailed account of the development process - Design specifications, data governance, training data origin, labelling procedures, and testing methods - Monitoring, control, and human oversight mechanisms - Who can override the system, and how - Performance metrics and how they were validated - A risk management log, covering known risks, mitigations, and residual risks. - This must be maintained continuously. - A record of changes throughout the system’s lifecycle, including any modifications that may affect compliance - An EU Declaration of Conformity - A aftermarket monitoring plan ## The three most common gaps According to Ferndesk, there are three common areas where documentation teams most often find they’re starting from scratch. ### Data provenance The Act requires detailed documentation of training data origin, selection criteria, labelling procedures, and cleaning methods. ### Living documentation Several sections explicitly require ongoing maintenance. Treating documentation as a one-time deliverable is a compliance risk. A static PDF from six months ago is unlikely to be compliant. ### Evidence, not assertion Regulators look for verifiable information: actual test results that influenced design decisions, genuine risk assessments, real audit logs. Assertions without evidence will not pass conformity assessment. It preserves design decisions that might otherwise exist only in individual team members’ heads, provides a baseline against which to evaluate whether system modifications are substantial enough to require a new conformity assessment, and enables faster root-cause analysis when issues arise in production. ## What this means for technical writers The documentation has to exist. Someone has to write it well. For technical writers who want to make the case for their value in organisations developing AI products, the EU AI Act is a strong argument. ### Share this: - [Share on Facebook (Opens in new window) Facebook](https://www.cherryleaf.com/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload/?share=facebook) - [Share on LinkedIn (Opens in new window) LinkedIn](https://www.cherryleaf.com/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload/?share=linkedin) - [Share on WhatsApp (Opens in new window) WhatsApp](https://www.cherryleaf.com/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload/?share=jetpack-whatsapp) - [Share on Bluesky (Opens in new window) Bluesky](https://www.cherryleaf.com/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload/?share=bluesky) - ### *Related* ### Leave a Reply[Cancel reply](/2026/06/the-eu-ai-act-what-it-means-for-your-documentation-workload/#respond) This site uses Akismet to reduce spam. [Learn how your comment data is processed.](https://akismet.com/privacy/) #### Previous post [Take part in our 2026 survey into the adoption of AI in technical communication](https://www.cherryleaf.com/2026/05/take-part-in-our-2026-survey-into-the-adoption-of-ai-in-technical-communication/) #### Next post [What tools like Claude Code and OpenAI Codex actually mean for L&D teams](https://www.cherryleaf.com/2026/06/what-tools-like-claude-code-and-openai-codex-actually-mean-for-ld-teams/) #### Browse posts by month Browse posts by month Select Month October 2026 (1) September 2026 (12) August 2026 (8) July 2026 (7) June 2026 (14) May 2026 (8) April 2026 (6) March 2026 (14) February 2026 (9) January 2026 (9) December 2025 (7) November 2025 (9) October 2025 (10) September 2025 (7) August 2025 (6) July 2025 (1) June 2025 (3) May 2025 (2) April 2025 (5) March 2025 (3) February 2025 (3) January 2025 (2) November 2024 (8) October 2024 (3) September 2024 (2) August 2024 (3) July 2024 (4) June 2024 (1) May 2024 (2) April 2024 (4) March 2024 (1) February 2024 (2) January 2024 (1) December 2023 (2) November 2023 (9) October 2023 (8) September 2023 (5) August 2023 (3) July 2023 (1) June 2023 (1) May 2023 (2) April 2023 (3) March 2023 (2) January 2023 (2) December 2022 (4) November 2022 (1) October 2022 (1) September 2022 (1) August 2022 (1) July 2022 (1) June 2022 (1) May 2022 (2) April 2022 (1) March 2022 (1) February 2022 (1) January 2022 (2) December 2021 (1) November 2021 (2) October 2021 (1) August 2021 (1) July 2021 (2) June 2021 (3) May 2021 (5) April 2021 (3) March 2021 (3) February 2021 (1) January 2021 (2) December 2020 (4) November 2020 (4) August 2020 (3) February 2020 (3) January 2020 (1) November 2019 (3) October 2019 (1) September 2019 (1) August 2019 (3) July 2019 (2) June 2019 (3) May 2019 (4) April 2019 (1) November 2018 (2) October 2018 (1) July 2018 (2) June 2018 (4) May 2018 (2) April 2018 (3) March 2018 (4) February 2018 (2) January 2018 (3) December 2017 (2) October 2017 (3) September 2017 (1) August 2017 (3) July 2017 (2) June 2017 (7) May 2017 (4) April 2017 (5) March 2017 (1) February 2017 (7) January 2017 (1) December 2016 (3) November 2016 (4) October 2016 (1) September 2016 (5) July 2016 (1) June 2016 (3) May 2016 (1) April 2016 (2) February 2016 (2) January 2016 (5) December 2015 (1) November 2015 (4) October 2015 (2) August 2015 (1) July 2015 (1) June 2015 (2) May 2015 (3) February 2015 (2) January 2015 (6) December 2014 (1) October 2014 (1) September 2014 (4) June 2014 (4) May 2014 (1) April 2014 (2) March 2014 (3) February 2014 (4) January 2014 (4) November 2013 (2) October 2013 (5) September 2013 (3) July 2013 (3) June 2013 (11) May 2013 (4) April 2013 (6) March 2013 (7) February 2013 (4) January 2013 (4) December 2012 (9) November 2012 (23) October 2012 (14) September 2012 (8) August 2012 (4) July 2012 (12) June 2012 (12) May 2012 (10) April 2012 (8) March 2012 (12) February 2012 (3) January 2012 (6) December 2011 (2) October 2011 (3) August 2011 (1) June 2011 (5) May 2011 (2) April 2011 (1) January 2011 (1) December 2010 (1) November 2010 (3) October 2010 (4) September 2010 (8) August 2010 (5) May 2010 (2) April 2010 (3) March 2010 (3) February 2010 (2) January 2010 (3) December 2009 (2) November 2009 (6) September 2009 (1) July 2009 (6) June 2009 (7) April 2009 (8) March 2009 (3) February 2009 (3) January 2009 (3) December 2008 (1) November 2008 (3) October 2008 (3) September 2008 (4) August 2008 (1) July 2008 (3) June 2008 (5) May 2008 (2) April 2008 (2) March 2008 (3) February 2008 (2) January 2008 (1) November 2007 (3) October 2007 (2) September 2007 (1) July 2007 (3) November 2006 (1) October 2006 (2) September 2006 (3) August 2006 (1) April 2006 (1) March 2006 (3) #### Browse posts by category