EUDR Process Architecture | 2026 Edition (Editable Word Doc)
89 Page Microsoft Word Architecture | Version 1.1 | Updated September 2026
Build a connected EUDR operating model that shows how your capabilities fit together, how evidence moves between them, and where ownership, controls and handoffs sit across the end-to-end process.
Where a classification framework identifies what capabilities are required, the Process Architecture shows how they fit together operationally: the end-to-end value stream, the resources each stage needs, the authoritative records that support the process, the activities within each domain, the interfaces between them and the ownership boundaries that hold the model together. When EUDR is run as a collection of separate procedures, ownership, handoffs and information dependencies become hard to see. The Architecture makes those relationships explicit, turning a set of activities into one coherent operating model.
Within the Atoxor operating model, the Process Architecture sits above the free Process Classification Framework and Capability Maturity Assessment, and beneath the SOP System, Process Navigator and EUDR Automate.
What it gives you
Connected operating model: twelve EUDR capability domains working as one system rather than as separate functional procedures.
End-to-end value stream: the case mapped through four operating stages, Scope to Route, Evidence to Assurance, Declare to Release and Monitor to Improve, with enabling capabilities running across the flow.
Twelve capability domains: Due Diligence, Commodity-Specific Requirements, Supply Chain Mapping and Traceability, Geographic Information Management, Legal Compliance Documentation, Verification Systems, Declaration Management, Environmental Impact Monitoring, Crisis Management, Continuous Improvement, Information System Management and Stakeholder Engagement, each decomposed against a consistent structure of operating question, stage role, people, process, data, systems, interface out and operating profile.
Four resource dimensions: every domain examined against People, Process, Data and Systems, showing what each stage needs to operate.
Authoritative record model: thirteen authoritative objects with their owning domains, systems of record and controlled lifecycles, the Due Diligence Case, Commodity Route and Requirement Set, Supply Chain Map and Traceability Record, Geolocation Release Pack, Legality Evidence Set, Verification Outcome, Due Diligence Statement, Reference, Identifier and Coverage Register, Monitoring Record, Issue and Resolution Record, Improvement Action Record, Controlled Record Set and Engagement Record.
Activity-level decomposition: 416 activities across all twelve domains, each presented as a single SIPOC row showing supplier, input reference, input description, process step, output reference, output description and customer. The activity population reconciles exactly to the twelve v1.4 SOPs, domain by domain.
Interface and handoff map at two levels: a readable object-handoff view showing what crosses each boundary, its cardinality, the control point and evidence requirement, and how ownership is maintained as the case moves between domains; and an authoritative register of 125 activity-level interfaces, IF-0001 to IF-0125, each carrying a persistent identifier so an exact producer-output to consumer-input boundary can be resolved. Handoffs are carried through controlled artefacts such as handover checklists and intake-completeness checks, while the SOP System remains the source of record for those artefacts.
Controlled definitions: 29 DEF references to the free PCF v1.1 Definitions Register, cited by identifier, so the architecture and the public classification layer use the same controlled concepts without duplicating definitional authority.
Methodology and Referencing Convention: the reader key explaining the metamodel, the identifier classes, the traceability chain from capability to activity to interface to record, and the boundary between the free and proprietary layers.
Defined ownership: the domain that produces an artefact stays accountable for its integrity even after another domain begins to use it.
100% editable Word format: adapt the structure, terminology, systems, roles and interfaces to your organisation while retaining the underlying architecture.
What is new in Version 1.1
Version 1.1 is a minor release. It adds an activity-level operating layer beneath the retained Version 1.0 object and domain skeleton, without changing the underlying process model. Organisations already working from Version 1.0 will find the same value stream, the same twelve domains and the same thirteen authoritative objects, with substantially more structure beneath them.
Added in this release: full activity-level SIPOC decomposition (416 activities, previously none), the activity-level interface register (125 interfaces, previously object-level handoffs only), controlled-definition bindings to PCF v1.1 (29 references, previously none), and the Methodology and Referencing Convention.
Version 1.1 was independently reviewed against source. The activity population reconciles to the SOPs at 416 of 416, interface endpoints contain no orphans and all definition references resolve to PCF v1.1.
2026 Edition
Version 1.1 was prepared and regulatory-source reviewed in September 2026, reflecting Regulation (EU) 2023/1115 as amended by Regulation (EU) 2025/2650 and the Commission material identified in its Regulatory Currency section. An external EUR-Lex current-law check was completed on 5 September 2026, and no post-baseline change requiring controlled amendment was identified.
Specifications
Format: Microsoft Word (.docx) | Delivery: instant download | Version: v1.1 | Pages: 89 | Editable: yes | Language: UK English
Licence and important note
The Architecture is proprietary and is licensed rather than sold. The purchasing organisation may use and adapt it internally across its own operations and documentation. Redistribution, resale, sublicensing or provision to third-party organisations is not permitted unless separately agreed with Atoxor Ltd.
This document is provided for operating-model and process-design purposes. It does not constitute legal advice, and using it does not by itself demonstrate or assure conformity with Regulation (EU) 2023/1115, as amended, or any other legal or regulatory requirement.
Organisations remain responsible for their own legal obligations and for obtaining appropriate professional advice.
The EUDR and its associated Commission measures continue to develop, so confirm the current regulatory position for your circumstances before relying on any part of the Architecture.