Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-3
NATO commanders and staffs planning and conducting joint operations
AJP-3 is NATO's keystone doctrine for how commanders and staffs plan, conduct and assess joint operations; nations record their agreement to use it through STANAG 2490.
AJP-3, Allied Joint Doctrine for the Conduct of Operations, is NATO's keystone doctrine for how commanders and their staffs prepare, conduct and assess joint military operations. The Preface is direct about who it is for: "AJP-3 is written for NATO commanders and their staffs engaged in joint operations." It is described as "the foundational doctrine for the AJP-3 series", the wider family of more detailed publications on individual topics such as sustainment, targeting or force protection. This edition, Edition D Version 1 of August 2025, superseded Edition C Version 1 and rearranged the doctrine into three chapters and four annexes.
The document does not address suppliers, manufacturers or any commercial role. Beyond NATO commanders and staffs, it offers itself more loosely elsewhere: "The doctrine provides a useful framework for operations conducted by a coalition of partners and non-NATO nations", and "AJP-3 also provides a reference for NATO civilian and non-NATO civilian actors." A framework and a reference are not obligations, so nothing here reads a requirement onto a partner, a non-NATO nation, or a civilian actor.
AJP-3 is doctrine, not a contract or a regulation, and it does not bind a company directly. NATO nations ratify a separate covering document, STANAG 2490: "The agreement of nations to use this publication is recorded in STANAG 2490." This edition "is effective upon receipt and supersedes AJP-3, Edition C, Version 1, which shall be destroyed in accordance with the local procedures for the destruction of documents." Coalition partners and non-NATO nations have not ratified that STANAG, which is why the text offers them a framework and a reference rather than an obligation. Where a company meets this world of doctrine in practice, it is normally through a level-2 or level-3 publication that a contract or tender actually names, not through AJP-3 itself.
The three chapters work through the doctrine in order. Chapter 1, Fundamentals, sets out the "four key tenets of doctrine" (the behaviour-centric approach, the comprehensive approach, the manoeuvrist approach, and mission command), the continuum of competition and its four campaign themes, the twelve principles of joint and multinational operations, the legal context an operation is conducted within (the law of armed conflict, international human rights law, national laws, status of forces agreements, rules of engagement, self-defence and national caveats), the military contribution to human security built around six cross-cutting topics, and command and control fundamentals, including the distinction between operational command (OPCOM) and operational control (OPCON).
Chapter 2, Preparation, sustaining, transition and termination, covers forming the joint task force, including NATO's force generation and activation procedure and the "force certification procedures" that check a contributing nation's forces - particularly a non-NATO contributing nation's forces - before a mission. It goes on to establishing the joint task force headquarters, training, pre-execution activities such as lines of communication and host-nation support, sustaining fighting power, transition and its risks, and termination and redeployment, run in four stages: "disengagement, rearward movement, staging and dispatch within the JOA, and strategic redeployment from the JOA to the national location".
Chapter 3, Execution, covers operational art and its three elements (commander's vision and skills, operations design, operations management); mission command, described as "NATO's philosophy for the command of military operations"; the eight joint functions (command and control, intelligence, manoeuvre, fires, information, civil-military cooperation, sustainment, and force protection); operations management, including decision-making, engagement space management, information management and risk management; operations assessment; and the operations process itself: "plan, prepare, execute, and assess."
Four annexes go into more depth than the chapters allow. Annex A describes the operating environment: four natural environments, eight specific environments (from littoral to riverine), the five operational domains, and the engagement space, which this edition treats as a synonym for "battlespace" - the "Summary of changes" records that it "Changed the term 'battlespace management' in 'engagement space management'", so a reader who knows the previous edition's terminology needs that mapping. Annex B sets out how a joint headquarters is staffed, from the commander's principal and functional advisors through the J1 to J10 staff directorates to the boards and working groups that run its battle rhythm. Annex C covers engagement space management in detail: coordination, combat identification, the four levels of operational area, and spectrum management. Annex D adapts risk management for a military headquarters, and says plainly where the model comes from: it is "inspired from civilian international risk standards as given in ISO 31000:2018(E)."
AJP-3 does not put a company, or a nation, through certification against it. The nearest process it describes is "force certification": "A NATO command or TCN undertakes force certification procedures" to check a contributing nation's forces before a mission - looking at caveats, organisation, training, equipment, interoperability and effectiveness against the operation plan. That checks whether a nation's forces are fit for a specific mission, not whether an organisation complies with a standard, and NATO awards no certification of that kind to a company. Separately, operations assessment reviews an operation itself: its purpose is "to inform the commander if the operation is being executed as planned and if the operation is achieving the desired results" - an internal review of a NATO operation, not an audit of a supplier or contractor.
AJP-3 sets out doctrine, not testable technical requirements: it tells a commander and staff how to think about and organise an operation, not what a supplier must deliver. It names contractors and commercial support only where operations rely on them - for example commercially contracted logistics during redeployment, and host-nation support arrangements that may draw on local commercial contracts
the detailed requirements of sustainment, targeting, force protection or any other specific discipline; for those it points to the level-2 and level-3 AJPs below it.
AJP-3 "builds on the principles described by AJP-01, Allied Joint Doctrine" and is "especially related to AJP-5, Allied Joint Doctrine for the Planning of Operations." It also draws on AJP-2 for intelligence, AJP-4 for sustainment, AJP-6 for communication and information systems, and AJP-10 for strategic communications, and it names ISO 31000 as the model for its own risk management annex. Below AJP-3 sit the level-2 and level-3 publications the text cites for detail on specific disciplines, among them AJP-3.9 on joint targeting, AJP-3.13 on deployment and redeployment, AJP-3.14 on force protection, AJP-3.16 on security force assistance, AJP-3.19 on civil-military cooperation, and AJP-4.3 on host-nation support.
AJP-3 is doctrine for NATO commanders and staffs, not a set of requirements addressed to a supplier, so there is no mapping between this document and a ComplyTrain feature to describe honestly. Where a defence contractor actually meets this world of doctrine in practice, it is usually through the level-2 or level-3 publications AJP-3 points to, because a contract or a tender names one of those, or through the operational support arrangements a customer force runs under this doctrine, such as host-nation support agreements and commercially contracted logistics. For that kind of contracted defence work, ComplyTrain gives an organisation a place to hold the documented procedures, training records and audit trail an assessor would ask for, and to keep them current as a contract's requirements change. It does not plan or conduct a military operation, staff a joint headquarters, or substitute for the judgement AJP-3 places with a commander and their staff - that work happens in a headquarters and in the field, not in software. Which standards and tiers actually apply to a given contract is set by that contract and the customer's quality clause. The standards explorer shows what sits alongside AJP-3 in the catalogue, including the AJPs referenced above; talk to us about how your documentation and evidence trail hold up against what a contract in this space is likely to ask for.
Tell us how you need to work with AJP-3 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.
AJP-3 itself is doctrine, not a rule. NATO nations ratify their agreement to use it through STANAG 2490, so it binds a nation through that ratification, not through AJP-3 existing. It does not describe any mechanism by which a company is required to meet it; a company only meets NATO doctrine where a contract or tender cites a specific requirement from a subordinate publication.
STANAG 2490 is the agreement NATO nations ratify to use AJP-3; AJP-3 is the doctrinal content itself. The promulgation letter states it plainly: "The agreement of nations to use this publication is recorded in STANAG 2490."
No. AJP-3 describes no certification scheme for organisations. The closest process it names, "force certification procedures", checks whether a contributing nation's forces are fit for a specific mission - it is a NATO military process, not a compliance certification a company can hold.
Edition D, Version 1, published in August 2025, superseded Edition C, Version 1, which the promulgation letter says "shall be destroyed in accordance with the local procedures for the destruction of documents." This edition also renamed "battlespace management" to "engagement space management", so material referring to the older term describes the same activity.
AJP-3 names contractors only in passing, where operations rely on commercial support: commercially contracted logistics during redeployment, and commercial contracts as part of host-nation support. It does not set out requirements addressed to a contractor; those, where they exist, sit in the level-2 or level-3 publications a specific contract cites.
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.