Your Enterprise Procurement Team Just Asked for Your AI Onboarding Tool's Technical File: Answering the Article 11 and Annex IV Documentation Questions
A procurement manager at a Fortune 500 company just emailed asking for your AI employee onboarding tool's "technical file" — specifically referencing Article 11 and Annex IV of the EU AI Act. Your product uses AI to personalize onboarding paths, predict time-to-productivity, and flag at-risk new hires who may churn early. Now you have 10 business days to respond to 14 sub-questions about documentation you may never have assembled in one place before.
This post breaks down exactly what Article 11 requires, what goes into an Annex IV technical file for an HR AI tool, and how to answer each questionnaire line without a compliance team on staff.
Why Article 11 Matters for HR AI Tools
Article 11 of the EU AI Act applies to providers of high-risk AI systems. An AI tool that evaluates employees or candidates — including onboarding tools that predict fit or flag churn risk — falls under Annex III category 4 (employment, workers management, access to self-employment). That means your system is presumed high-risk and must have a technical file before it's placed on the market in the EU.
The technical file is not a compliance checkbox. It's the document a notified body, market surveillance authority, or enterprise procurement team will ask to review. If you can't produce it, the deal stalls.
What Annex IV Says You Need
The Annex IV technical file for a high-risk AI system includes:
- A general description of the system — what it does, the intended purpose, the version, and the deployer context
- The design and development process — how the model was built, what frameworks were used, what decisions were made during development
- The training, validation, and testing data — where the data came from, how it was processed, how bias was evaluated
- Information on oversight and human intervention — how deployers (your HR customers) are supposed to use the tool and what human steps are required
- Post-market performance tracking plan — how you track performance after deployment
- Declaration of conformity — a signed statement that the system meets EU AI Act requirements
When a procurement questionnaire asks "Do you have a technical file per Article 11 and Annex IV?" — they want to know whether documents (1) through (6) exist and whether you can share them under NDA.
Answering the Questionnaire Line by Line
"Do you maintain an up-to-date technical file per Annex IV?"
Yes. We maintain a technical file for each version of our AI system per Annex IV. The file includes a general system description, development methodology, data governance documentation, and version history. A redacted version is available under NDA upon request.
"Can you describe the intended purpose of the system as specified in your technical file?"
The system is intended to personalize onboarding journeys for new employees by predicting time-to-productivity and identifying early signals of disengagement. It is designed to support, not replace, HR team decisions — a human manager reviews all outputs before any action is taken.
"Does your technical file document the training and validation data used?"
Yes. Our technical file includes a data card covering data sources, preprocessing steps, known limitations, demographic representation analysis, and the results of bias evaluation across protected characteristic proxies. Details are available under NDA.
"What version control process governs changes to the system documented in the technical file?"
Each model version receives a new technical file entry. Material changes — including changes to training data, architecture, or intended use — trigger a conformity assessment review before the updated version is deployed to EU customers.
"Is your post-market performance tracking plan documented in the technical file?"
Yes. Our post-market plan specifies the performance metrics tracked, the thresholds that trigger review, and the escalation path if performance degrades. Deployers (your HR team) receive release notes whenever a model update occurs.
What If You Don't Have a Technical File Yet?
If you're reading this because a customer just asked and you don't have Annex IV documentation, you have two options. First, you can tell the customer you're in the process of completing your technical file (true only if you have actually started). Second, you can accelerate the documentation process — Annex IV is structured, not open-ended, and a technical file can often be assembled from existing internal documentation in four to eight weeks.
Complizo helps you generate the prose for each Annex IV section from your existing product documentation and questionnaire responses. You paste in what you know; we output the structured answer in the format procurement teams expect.
The Procurement Moment This Post Is For
You got an email that included:
"Please provide your Article 11 technical file or confirm that one exists. We require Annex IV documentation as a condition of procurement for all high-risk AI systems deployed in EU member states."
The right response is structured, specific, and version-stamped. It references the actual Annex IV sections, not general claims about your QA process. And it ends with an offer to provide the full file under NDA rather than a vague "we take AI seriously."
Try Complizo free at complizo.com