Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2182
National authorities and NATO commands implementing AJP-4, and defence suppliers working to a contract or task order that invokes it
STANAG 2182 is NATO's agreement committing member nations to implement AJP-4, the Allied joint doctrine for sustainment of operations; it binds nations, not suppliers, directly.
STANAG 2182 is a NATO Standardization Agreement, currently Edition 4, dated 22 August 2025. It is not a technical specification. It is the agreement by which NATO nations commit to ratify and implement AJP-4, Edition C, the Allied Joint Publication that sets out the strategic concept, underlying philosophy and fundamentals for the sustainment of Allied joint operations. The sustainment doctrine itself, the detail a reader usually wants, lives inside AJP-4, not inside this four-page cover. Read on its own, STANAG 2182 requires almost nothing of a supplier directly. Its obligations run to nations, and it reaches a contractor only indirectly, once a nation has implemented it and a contract or task order names AJP-4's sustainment requirements.
STANAG 2182 is explicit that it binds nations rather than organisations. It "is effective upon receipt for use by the participating nations and NATO bodies." Its letter of promulgation describes the enclosed agreement as one "which has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD), is promulgated herewith." Ratification and implementation are separate steps: nations that have not already done so are invited to "advise the NSO of their intention regarding its ratification and implementation." So "is STANAG 2182 mandatory" has no single answer. It depends on whether a given nation has ratified and implemented it, and, for a supplier, on whether a specific contract invokes AJP-4 as a result.
The stated aim is to respond to a single interoperability requirement: "to provide guidance and direction on the strategic concept, underlying philosophy and fundamentals for the sustainment of Allied joint operations." Under "Agreement," participating nations agree to implement AJP-4, Edition C. None of this is written as a duty on a supplier; it is a duty on the nation, and on the forces and commands that plan and conduct sustainment.
A reader who only has STANAG 2182 in hand does not yet have the sustainment doctrine itself. AJP-4 holds the strategic concept, philosophy and fundamentals this STANAG points at. This document names three sibling doctrine publications for context - AJP-01 (via STANAG 2437), AJP-3 on conducting operations (via STANAG 2490), and AJP-5 on planning operations (via STANAG 2526) - alongside two non-standard references, MC 0586 on the military instrument of power and the NATO Strategic Concept, PO(2022)0200. None of these are prerequisites in a supplier's own sense; they show where AJP-4 sits among NATO's other joint doctrine.
STANAG 2182 "is implemented when the necessary orders/instructions have been issued directing the forces concerned to put the content of the covered standard into effect; and to include it into national education, training and exercises programs." The document states that proper implementation "will provide interoperability during NATO operations." The current edition supersedes STANAG 2182, Edition 3, dated 20 December 2018. The STANAG "is to be reviewed in accordance with AAP-03." The result is recorded in the NSDD, and the agreement is supervised under NATO's logistics standardization committee chain.
STANAG 2182 names no supplier obligation directly: every duty in the text runs to "nations," "NATO bodies" or "forces concerned," never to a contractor or manufacturer. It also names no assessment or certification scheme of any kind. The only stated check is that the agreement itself is reviewed periodically against AAP-03, not that an organisation, a unit or a sustainment activity is certified.
STANAG 2182 itself gives a supplier nothing to implement in software: it is an agreement between nations, and the sustainment doctrine sits in AJP-4. Where ComplyTrain fits is the paperwork trail behind whichever sustainment tasks a contract actually assigns: documented procedures for the work involved, training records showing the people responsible understand them, and a clear corrective-action trail an auditor or customer quality representative can follow when sustainment performance is questioned. That work is done in the day-to-day handling of sustainment activities, not in software, and ComplyTrain's role is to hold the evidence that it happened.
ComplyTrain does not plan or conduct sustainment operations, decide what a specific mission or contract requires of a unit, or substitute for AJP-4's own doctrine - that is work carried out by the nations and NATO commands implementing it. The applicable tier and which sustainment requirements a supplier actually faces are set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 2182 - if you are weighing up what a tender actually requires, we're glad to talk it through.
Tell us how you need to work with STANAG 2182 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.
Not on its own. A STANAG binds a nation once that nation has ratified and implemented it, and it reaches a supplier only when a contract or task order names AJP-4. Whether it applies to a given programme is a question for the contract, not for this page.
STANAG 2182 is the cover agreement: it commits nations to implement AJP-4 but contains no sustainment doctrine itself. AJP-4 is the Allied Joint Publication that actually sets out the strategic concept, philosophy and fundamentals for sustaining Allied joint operations.
No. STANAG 2182 describes no certification or accreditation scheme. Its only stated check is a periodic review of the agreement's own currency, carried out in accordance with AAP-03. NATO does not certify organisations or components against a STANAG.
Edition 4, dated 22 August 2025, which supersedes Edition 3, dated 20 December 2018.
STANAG 2182 names them as related documents: AJP-01 (NATO's capstone Allied joint doctrine, via STANAG 2437), AJP-3 on conducting operations (via STANAG 2490), and AJP-5 on planning operations (via STANAG 2526). They inform AJP-4's sustainment doctrine rather than being required by it.
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.