Svenska Dokumentmallar
AI Act Article 50.2 – machine-readable AI labelling, detection and proof of testing | Word/PDF/Excel
AI Act Article 50.2 – machine-readable AI labelling, detection and proof of testing | Word/PDF/Excel
- File format
- DOCX, PDF, XLSX
- Document language
- Five Swedish working documents and a Swedish user guide; one English User Guide; Excel in Swedish.
- Number of files
- 7
Digital download. No physical product is shipped.
Couldn't load pickup availability
About this template
Does your company develop or provide an AI system that generates synthetic text, images, audio, or video? This Swedish template package helps affected AI providers document machine-readable labelling, actual detectability, technical testing, and release decisions in accordance with Article 50.2 of the EU AI Act. The package contains working documents and registers – it does not install any watermarking, detector, or certified technology.
Purchase overview: 7 independent documents (five Swedish working templates, a Swedish user guide, and a separate English User Guide) as editable Word files and corresponding searchable, printable PDF files; plus a nine-tab Excel workbook in Swedish. A total of 15 customer files in a designated ZIP package for digital download after future activation. The PDF files are not interactively fillable. The main documents are in Swedish; the English guide is an instruction, not a legally translated main template. Swedish usage context and EU law, version 1.0 (2026-11-09).
01. Package contents
7 independent documents: Applicability assessment, technical specification, detection test protocol, non-conformance and corrective action protocol, release and evidence decision, Swedish guide, and English User Guide. All in DOCX and searchable PDF (14 format files). In addition, 1 XLSX with nine tabs. A total of 15 customer files. PDF copies are not additional independent documents.
02. What the files contain
Role and exemption assessment under the AI Act, selection of labelling method and detection tool, actual testing of text/image/audio/video, robustness after file conversion, non-conformance tracking, retesting, release decision, and traceable source references. Excel calculates administrative counts and statuses, but does not automatically assess legal applicability or technical compliance.
Who should choose this package?
Example A: A Swedish software provider builds its own image-generating AI system and needs to show how the output is labelled and how the labelling can actually be detected after export. Example B: A provider of generative text or audio needs to document its role, technical exemptions, test results, and the next release before deployment.
Do not choose this as your only solution if the company only uses an external AI tool as a deployer, if the customer wants to label deepfakes under Article 50.4, or if a full conformity assessment of a high-risk AI system is required. The product's forms do not replace actual implementation, external legal assessment, or a competent authority's decision.
File by file – concrete practical utility
| Document | When it is used | Language | Format |
|---|---|---|---|
| 01 Applicability and provider role | Assess system, actor role, output, exemptions, and transition period | Swedish | DOCX + PDF |
| 02 Technical labelling specification | Document labelling, detector, format, limitations, and owner | Swedish | DOCX + PDF |
| 03 Technical detection test | Testing of original file, export, transcoding, and negative controls | Swedish | DOCX + PDF |
| 04 Non-conformance and correction | Log errors, temporary measure, root cause investigation, and retesting | Swedish | DOCX + PDF |
| 05 Release and evidence handover | Defined internal decision and references to approved test | Swedish | DOCX + PDF |
| 06 Swedish user guide | Steps, legal boundaries, common misunderstandings, and sources | Swedish | DOCX + PDF |
| 07 English User Guide | Instructions for completing the Swedish templates | English | DOCX + PDF |
| 08 Labelling and test register | System, output, labelling, tests, non-conformances, decisions, and evidence | Swedish | XLSX |
The Excel tool – what has been tested?
The workbook has nine tabs: Overview, System and Roles, Output and Scope, Labelling Technology, Detection Tests, Non-conformances, Decisions and Release, Evidence Register, and Read Me. The overview counts registered IDs and explicit statuses. A fictitious test with a technical result of “Failed” and a release status of “For assessment” has been tested and subsequently removed. A passed technical test is not automatically a legal approval. No formula designates a product as AI Act-compliant.
Workflow: from rule assessment to release decision
- Determine who is the provider of the AI system and what types of synthetic output are affected.
- Assess whether Article 50.2 applies, and separately document possible exemptions and transitional rules.
- Describe the actual machine-readable labelling, how it is implemented, and which detector is used.
- Test output in relevant formats and distribution chains. Save the sample files' IDs, results, and limitations.
- Record failed tests, correct them, and perform retesting.
- Decide internally on the exact version, conditions, risks, and archiving. An internal signature is not an authority certification.
Legal and time limits – important differences
Article 50.2: Providers of affected AI systems shall ensure machine-readable labelling and that synthetic content can be detected, with requirements for effective, interoperable, robust, and reliable solutions to the extent technically possible. There are exemptions, including for certain standard editing functions and output that does not substantially alter the input or semantics. If an exemption applies, it must be assessed for each actual system. See AI Act Article 50.2 – EU AI Act Service Desk.
Article 111.4: There is a limited transitional period until 2 December 2026 for affected systems placed on the market before 2 August 2026. It is not a general reprieve for all AI systems. See EU Regulation Article 111.4.
Technical methods: Watermarking, metadata, and cryptographic provenance can be alternative technical methods depending on the type of content; the law does not generally prescribe that a single particular standard must be used. Read the EU Commission guidelines. The EU Code of Practice is voluntary and does not replace the actual legal obligation.
Compare with related documents
The AI Governance Package is a broader foundation for AI governance. Deepfakes and AI influencers under Article 50.4 primarily concerns a different obligation, mainly related to the provider's disclosures. This product focuses specifically on the provider's technical labelling and detectability under Article 50.2.
Frequently Asked Questions
Is Article 50.2 the same as deepfake labelling?
No. Article 50.2 is aimed at the provider's machine-readable labelling and detection. Article 50.4 addresses separate disclosure obligations for certain uses, including deepfakes. An actor may be affected by different obligations depending on its role.
Do we have to use C2PA or watermarking?
Not automatically a particular named method. The actual solution must be assessed against Article 50.2, current guidance, content type, and technical feasibility. The template helps you document choices and tests, but does not provide the technology itself.
Can an ordinary AI user use the template?
Only if the actual need is provider responsibility and technical testing. Companies that only use external tools should first determine their legal role and may need other documents.
What does “Passed” mean in Excel?
A registered technical test or a manual release decision. It does not mean authority-approved, legally approved, or compliance with the law.
Can Excel or PDF create machine-readable marks?
No. Excel is a traceable control register. The PDF documents are searchable working documents; they do not add watermarks or metadata to the customer's own AI output.
Have the documents been reviewed by a lawyer?
No independent external legal review is warranted. AI-assisted source control of the relevant version and functional file tests are documented separately. For complex provider roles or exemptions, an individual assessment is required.
Sources, dates, and transparency
Version 1.0, document date 2026-11-09. AI-assisted source control 2026-11-09 against Regulation (EU) 2024/1689 (consolidated 2026-07-27), especially Articles 50.2, 111.4, and 113, as well as the EU Commission guidelines for Article 50. The product is based on relevant public sources but is not authority-approved, certified, or provided with a guaranteed AI ranking.
