Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2288
National authorities implementing NATO land operations doctrine, and organisations supporting a land operation under a specific tasking or contract
STANAG 2288 is NATO's agreement committing member nations to implement AJP-3.2, the allied joint doctrine for land operations; it binds nations, not suppliers, directly.
STANAG 2288 is a NATO Standardization Agreement, currently Edition 3, dated 3 February 2022. It is not a technical specification. It is the agreement by which NATO nations commit to ratify and implement AJP-3.2, Edition B, the Allied Joint Doctrine for Land Operations. The doctrine itself, not this cover, is where the substance lives: the interoperability requirement stated in the STANAG is "to provide guidance and direction for integrating land operations into the planning, conduct and assessment of Alliance operations." Read on its own, STANAG 2288 requires almost nothing of a supplier directly. Its obligations run to nations, and it reaches an organisation supporting a land operation only once a nation has implemented it and a specific tasking or contract invokes the doctrine.
STANAG 2288 is explicit that it binds nations rather than organisations. 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 kept as separate steps, and the document defines implementation precisely: this STANAG "is implemented when the necessary orders/instructions have been issued directing the forces concerned to put the content of the covered standard into effect." Nations that have not yet reported their position are invited to "advise the NSO of their intention regarding its ratification and implementation." So "is STANAG 2288 mandatory" has no single answer: it depends on whether a given nation has ratified and implemented it, and, for an organisation supporting a land operation, on whether a specific tasking or contract then invokes the doctrine that implementation puts in place.
The stated aim is to respond to an interoperability requirement: "to provide guidance and direction for integrating land operations into the planning, conduct and assessment of Alliance operations." The STANAG states it "is effective upon receipt for use by the participating nations and NATO bodies" - a NATO-wide mechanism, not a national or civil one. Its National Effective Date is stated as "once ratified." None of this is written as a duty on a supplier; it is a duty on the nation, and on the NATO and national bodies that direct forces to put the covered doctrine into effect.
A reader who only has STANAG 2288 in hand does not yet have the doctrine it points to. The actual doctrinal content - how land operations are planned, conducted and assessed - sits in AJP-3.2, Edition B. Other related documents named alongside it are STANAG 2490, which covers AJP-3, the allied joint doctrine for the conduct of operations; STANAG 2605, which covers allied land tactics (ATP-32); and STANAG 2199, which covers command and control of allied land forces.
National ratification responses are recorded in the NSDD, and Allies "shall provide ratification details through the electronic reporting tool (e-Reporting)." Once implemented, Allies and NATO bodies "shall provide implementation details through the electronic reporting tool (e-Reporting)," and partner nations "are invited to provide their implementation details" the same way. The STANAG itself "is to be reviewed in accordance with AAP-03," with the result "recorded within the NSDD" - a check on whether the agreement is still current, not an audit of any organisation. It is supervised under the authority of MC, MCLSB, LO, SLDP.
STANAG 2288 names no land-operations procedure, staffing table or equipment requirement of its own - that detail sits entirely in AJP-3.2. It also names no assessment or certification scheme: the only stated check is that the STANAG itself is reviewed periodically, not that an organisation or a force is certified.
STANAG 2288 itself gives an organisation nothing to implement in software: it is an agreement between nations, and the doctrinal content sits in AJP-3.2. Where ComplyTrain fits is the paperwork trail behind whatever role a specific tasking or contract actually assigns in support of a land operation: documented procedures for that role, training records showing the people carrying it out know the doctrine and their part in it, and the audit trail an assessor or a customer's quality representative would ask for when a land-operations commitment is questioned.
ComplyTrain does not plan or conduct a land operation, decide how a force or headquarters should be structured, or determine which doctrine applies to a specific tasking - that is set by the contract and the customer's quality clause, not by this page. Our standards explorer shows what else sits alongside STANAG 2288 - if you are weighing up what a tasking or tender actually requires, we're glad to talk it through.
Tell us how you need to work with STANAG 2288 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 an organisation supporting a land operation only when a specific tasking or contract invokes the doctrine that implementation puts in place. Whether it applies to a given programme is a question for the contract, not for this page.
STANAG 2288 is the cover agreement: it commits nations to implement AJP-3.2 but contains no doctrinal content itself. AJP-3.2, Edition B is the Allied Joint Publication that actually sets out the doctrine for land operations.
No. STANAG 2288 describes no certification or accreditation scheme. Its only stated check is a periodic review of the agreement itself, carried out in accordance with AAP-03. NATO does not certify organisations against a STANAG.
Edition 3, dated 3 February 2022, which supersedes STANAG 2288, Edition 2, dated 15 March 2016.
The STANAG itself answers this precisely: it "is implemented when the necessary orders/instructions have been issued directing the forces concerned to put the content of the covered standard into effect." That is a national act, recorded through NATO's electronic reporting tool, not a step an external organisation takes.
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.