Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-3.18
NATO joint commanders and staff responsible for planning, conducting and monitoring explosive ordnance disposal support to operations
AJP-3.18 is NATO's Allied joint doctrine for explosive ordnance disposal support to operations, setting out the principles commanders and staff use to plan and coordinate EOD support in joint operations.
AJP-3.18, Allied Joint Doctrine for Explosive Ordnance Disposal Support to Operations, is NATO's overarching doctrine for how explosive ordnance disposal (EOD) is planned, conducted and commanded within joint operations. Nations record their agreement to use it in STANAG 2628. The document is intended primarily as guidance for joint NATO commanders and staff, not for industry: it does not create a requirement for a supplier or a manufacturer, and it is not a document a defence contract cites the way it might cite a quality-assurance publication. Edition B, Version 1 (September 2023) is effective on receipt and supersedes Edition A, Version 1.
The doctrine positions EOD as one area of expertise within the military engineering (MILENG) function, alongside engineering, environmental protection, military search and infrastructure management, all of which exist to shape the physical operating environment. It builds on AJP-3, Allied Joint Doctrine for the Conduct of Operations, and AJP-5, Allied Joint Doctrine for the Planning of Operations, and sits under AJP-01, the NATO capstone publication for all Allied joint publications.
The document works through the range of explosive ordnance (EO) a joint force may encounter: explosives, munitions, improvised explosive devices (IEDs) and "Other explosive items," any of which may carry a chemical, biological, radiological or nuclear (CBRN) payload. EO can be abandoned or unexploded ordnance left over from an earlier conflict, and its threat level depends on factors such as accessibility, condition, and the presence of hazardous agents. The joint EOD capability subsets it identifies are explosive ordnance reconnaissance, explosive ordnance clearance, conventional munition disposal, improvised explosive device disposal, and CBRN explosive ordnance disposal, applied differently across services and nations depending on their equipment and procedures.
EOD's main activities, as the doctrine sets them out, are processing EO incidents, giving EOD advice to commanders, EO recovery on fixed installations, mine countermeasures, and exploiting EO incidents for intelligence value. "Other activities" include humanitarian mine action, which the document notes is "usually not their responsibility" for EOD force elements and is prohibited for armed forces in some nations - it is mostly carried out by international organisations, non-governmental organisations or commercial organisations under United Nations or national mine-action-authority lead - and logistic disposal, the removal of EO from stockpiles. These capabilities apply across the land, maritime, air and cyberspace domains, each with its own operating considerations that the document describes at a doctrinal rather than a procedural level.
EOD contributes to four key joint functions: intelligence, force protection, manoeuvre, and command and control. The doctrine sets out how EOD's work connects to other communities: force protection, where EOD assesses and disposes of threats to vital points and high-value assets; countering improvised explosive devices, where EOD supports the "Defeat the Device" pillar (see AJP-3.15); civil-military cooperation, assisting civilian authorities with EO in conflict or post-conflict areas (see AJP-3.19); CBRN defence (see AJP-3.8); special operations; electromagnetic warfare (see AJP-3.6); intelligence (see AJP-2); battlefield evidence; and technical exploitation (see AIntP-10). A lessons-learned section directs relevant observations into the NATO Lessons Learned Portal.
The doctrine's largest structural contribution is its three-level command and control (C2) architecture. At the strategic level, EOD staff sit within the Infrastructure and Engineering Division at Supreme Headquarters Allied Powers Europe. At the operational level, Chief Military Engineering and a Combined Joint Explosive Ordnance Disposal Cell (CJEODC) coordinate national EOD force elements at NATO Joint Force Commands, with dedicated arrangements for maritime and air components. At the tactical level, an EOD coordination cell sits at brigade, division or component headquarters, an EOD Cell at regiment or battalion level, and each nation appoints a National Point of Contact EOD to coordinate its own force elements. The doctrine requires that "Each EOD tasking authority should be clearly defined in national transfer of authority (TOA) letters, operational orders and within national and international directives," keeping the authority that tasks EOD force elements separate from the level that executes the tasking. Planning runs at both strategic level, generating forces against theatre EOD requirements, and operational level, feeding the physical operating environment and coordinating with AJP-5's planning process, with CBRN incidents calling for a specially designated response capability. Tasking and reporting requirements are built into NATO standards for EOD orders and reports, in line with AEODP-06, feeding threat assessment, the countering-IED effort and technical exploitation.
AJP-3.18 is written for NATO commanders and staff, and the doctrine itself says it is "instructive and provides a useful framework" for coalition operations involving NATO partners as well as members. It binds through STANAG 2628: a nation ratifies the STANAG, sometimes with recorded reservations, not a company. Several nations have done exactly that on this edition, with reservations touching CBRN and underwater EOD, national implementation of related search doctrine, and how battlefield-evidence contributions are handled under national jurisdiction. The document sets out no certification, accreditation or audit scheme, and nothing in it describes a body assessing an organisation's compliance: this is doctrine that shapes how NATO plans and commands EOD support, not a standard held up to a checklist.
AJP-3.18 is deliberately a doctrine document, not a technical or procedural one. It does not specify EOD procedures, safety distances, or render-safe methods; those live in subordinate and related publications, including AEODP-10, EOD Principles and Minimum Standards of Proficiency, and Allied Tactical Publication ATP-3.18.1, which the document names as directly subordinate to it. It also does not address the disposal of nuclear weapons.
AJP-3.18 is doctrine for NATO commanders and staff, not a management-system standard, and there is no product mapping to claim here. The work it describes, planning and conducting EOD support, coordinating force elements, running command and control structures, tasking and reporting, happens inside NATO and national military organisations, not in a compliance platform. Nothing in the document creates an obligation on a company, and applicability runs through a nation's ratification of STANAG 2628, not through anything a supplier signs up to directly.
Where a defence-sector organisation does have to evidence its own procedures, training records and audit trail for EOD-adjacent work set by a contract or a customer's quality clause, that is the kind of documentation and training-record work ComplyTrain supports in general: controlled documents, training records, internal audits and corrective-action tracking that a customer can review. ComplyTrain does not plan or conduct EOD operations, does not decide command and control structures, and makes no EOD technical or operational decision: that stays with NATO commands and the qualified EOD personnel this doctrine describes. The applicable tier for any EOD-related work, and the standards that come with it, are set by the contract and the customer's quality clause. See the standards explorer for what sits alongside AJP-3.18, or talk to us about the documentation side of a defence contract.
Tell us how you need to work with AJP-3.18 and what you need from it. We will come back to you about what ComplyTrain can do.
Thank you. Your list is on its way to your inbox, and we will come back to you on what working with these standards in ComplyTrain involves, usually within one business day.
No. AJP-3.18 is guidance for NATO commanders and staff, and it binds nations through STANAG 2628, not companies through a contract. A supplier only meets requirements that trace to this doctrine where a specific contract or tender says so, and even then the technical detail usually sits in a subordinate publication rather than in AJP-3.18 itself.
AJP-3.18 is the joint doctrine, written for commanders and staff planning and conducting operations. ATP-3.18.1, Allied Tactical Publication for Explosive Ordnance Disposal, is named in AJP-3.18 as directly subordinate to it and carries the tactical-level detail.
The document is addressed to NATO commanders and staff. The one place it mentions a non-military role is humanitarian mine action, which it notes is "mostly undertaken by international organizations, non-governmental organizations or commercial organizations" under United Nations or national lead, a separate activity from the EOD support to operations that this doctrine governs.
Edition B introduces the military engineering (MILENG) function and positions EOD as an area of expertise within it, updates the description of the explosive ordnance threat, adds the cyberspace domain, updates EOD force element and staff structures and command and control, and adds a section on lessons learned. It supersedes Edition A, Version 1.
NATO publishes it free of charge through the NATO Standardization Document Database. ComplyTrain does not sell or host copies of NATO documents.
One system for the whole compliance programme. Start with the module you need most.
Collect information the same way every time, and decide in advance what happens next.
Know whether your controls are operating, not just whether a policy says they exist.
Turn the compliance work you already know about into a plan with owners, dependencies and dates.
Know what you can offer, and hold the evidence behind every configuration you offer it in.
Eight built-in reports across every module, scheduled, delivered, and filed where the evidence lives.
The sector news that matters to your organisation - read and rated by AI, and delivered as a scheduled digest in your own language.
AI reads the tender pack and pulls out the requirements, deadlines and rules - then helps you draft the response from your own approved content, with you reviewing every step.
One current register of the suppliers and partners you depend on - each risk-assessed, re-assessing itself on schedule, and wired straight into your risk register.
See every requirement you face - across every standard, plus your own contracts and policies - traced to the documents, evidence and processes that satisfy it.
Identify, score, treat and review your risks in one place - with AI to help anyone run a proper assessment, and a defensible trail behind every decision.
Assign training, prove it was understood, and hold the competence records an auditor asks for.
Draft compliance documents with AI, keep every version under control, and export them beautifully branded - all in one place.
Audits, corrective actions, processes and approvals in one quality system, organised around ISO 9001.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.