What actually happens on August 2, 2026
For many AI teams the deadline feels abstract until they map it onto release work. August 2, 2026 is not only a legal milestone. It is an operating milestone. By then, teams shipping high-risk systems into the European market need a documentation story that can survive internal review, customer diligence, and formal conformity preparation. The teams that move fastest are not the ones that write the best checklist. They are the ones that stop separating documentation from technical evidence.
Does your system likely qualify as high-risk
If your workflow touches recruitment, education, access to finance, healthcare support, or other decisions that materially affect people, you should assume that a high-risk pre-evaluation is worth doing now. Teams often waste time searching for certainty before they start building the package. A better pattern is to run a preliminary pre-evaluation, draft the package structure, and then validate the scope with legal counsel.
What documents teams usually underestimate
The usual gap is not the high-level policy statement. It is the operational section that explains how risk management is tested, how events are logged, how human approval is triggered, and what evidence shows that the system is still within the claimed quality bar. Articles 9, 12, 14, and 15 are where many engineering teams discover that their internal quality process is not yet legible enough for an external reader.
What auditors and reviewers actually look for
Reviewers look for coherence. If the document says humans can intervene, there should be an approval path. If the document says risks are monitored, there should be recurring evidence. If the document says logging exists, there should be traceable records. Technical evidence does not replace legal interpretation, but without it the package feels speculative.
A 12-week execution plan
Weeks 1 to 2: run a pre-evaluation and define the system boundary. Weeks 3 to 4: draft Article 9 and Annex IV structure. Weeks 5 to 8: run the first evidence loop, create recurring test cases, and link the report outputs to documentation sections. Weeks 9 to 10: tighten review, oversight, and monitoring. Weeks 11 to 12: hand the package to legal and compliance for final interpretation and gap review. This sequence is much healthier than trying to build everything in the final month.