Transparency for deployers (instructions for use)
Description
Article 13 — Providers must furnish deployers with instructions for use enabling them to interpret outputs and use the system appropriately.
⚠️ Risk Impact
If deployers misuse the system, the provider remains liable unless the misuse was beyond what reasonably-trained deployers could foresee from the documentation. Vague documentation = retained liability.
🔍 How EchelonGraph Detects This
EchelonGraph's Tier 1 Cloud Scanner automatically checks for this condition across all connected cloud accounts. Violations are flagged as high-severity findings with remediation guidance.
🔧 Remediation
Provide instructions for use per system: intended purpose, performance characteristics, known limitations, human-oversight requirements, accuracy/robustness metrics, recommended monitoring. Translate to languages of all EU markets you serve.
💀 Real-World Attack Scenario
A facial-emotion-recognition vendor sold its product to call centres for 'agent training feedback'. One call centre deployed it for performance evaluation — affecting hiring decisions. The vendor's instructions for use didn't explicitly prohibit performance-evaluation use. When workers' unions raised an enforcement action, the vendor was held liable for the deployer's misuse because the instructions didn't clearly bound the use case.
💰 Cost of Non-Compliance
Article 13 transparency gap: up to €15M / 3% revenue. Provider-vs-deployer liability shift when instructions are vague: typically 70:30 in favour of provider liability (EU AI Office guidance Q2 2026).
📋 Audit Questions
- 1.Show me the instructions for use for your top deployed system.
- 2.Which deployer behaviours are explicitly out-of-scope?
- 3.How are instructions distributed to deployers? In what languages?
- 4.Have any deployer-misuse incidents resulted in instructions updates?
⚡ Common Pitfalls
- ⛔Burying critical limitations in section 7 of a 40-page PDF — deployers never read past page 3
- ⛔Failing to translate instructions — single-language documentation can't bind multi-language deployers
- ⛔Not refreshing instructions as deployment patterns reveal new misuse vectors
📈 Business Value
Clear instructions for use are the strongest provider defence against deployer-misuse liability. Material in commercial contract disputes and reg probes.
⏱️ Effort Estimate
2-3 weeks initial authoring + translation per system
EchelonGraph generates instructions-for-use templates from your Annex IV documentation
🔗 Cross-Framework References
Automate EU AI Act ART13-TRANSPARENCY compliance
EchelonGraph continuously monitors this control across all your cloud accounts.
Start Free →