Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2524
National authorities implementing NATO joint targeting doctrine, and defence suppliers whose contract or tender names AJP-3.9
STANAG 2524 is NATO's agreement committing member nations to implement AJP-3.9, the Allied joint doctrine for joint targeting; it binds nations rather than suppliers.
STANAG 2524 commits NATO nations to implement AJP-3.9, Edition B, the Allied joint doctrine for joint targeting. The agreement itself is short and holds no doctrine: it states an aim, names the publication, and sets out how a nation ratifies, implements and reports against it. Its own stated purpose is "to provide effective planning and execution of national and NATO targeting activities" and to give commanders and staff "the necessary understanding of NATO joint targeting terms, processes and common framework."
A STANAG is the instrument, not the content. Nations ratify it, implement it through their own doctrine and training changes, and a company encounters it only because a contract or a tender invokes the doctrine. Ratification and implementation are separate steps, a nation may ratify with reservations, and so the question "is STANAG 2524 mandatory" has a contractual answer and no general one.
The document says the doctrine "is intended primarily for strategic and operational level headquarters involved in operations." It also calls itself "instructive" for a wider group: a coalition of NATO members, partners and non-NATO nations, and it "provides a reference for NATO civilian and non-NATO civilian actors." None of that reaches a commercial supplier directly; it describes who inside and alongside NATO uses the doctrine once implemented.
The agreement "shall be considered implemented when nations have made changes to" national doctrine concerning joint targeting and national training plans and standards regarding joint targeting. Beyond that, a nation must "plan and execute national training exercises/events using national doctrine and this publication" and "report any relevant observations through the NATO Lessons Learned Portal." Reporting continues afterwards: "Allies and NATO bodies shall provide implementation details through the electronic reporting tool."
Unusually for a STANAG cover, this one sets a firm NATO effective date rather than recording "not applicable": the agreement "is effective upon receipt for use by the participating nations and NATO bodies." Nations record their ratification response in the NATO Standardization Document Database (NSDD), and are invited, where they have not already done so, to "advise the NSO of their intention regarding its ratification and implementation."
This STANAG is not read alone. It names three other Allied joint doctrine agreements as related reading: STANAG 2437, which covers AJP-01; STANAG 2490, which covers AJP-03, the doctrine for the conduct of operations; and STANAG 2526, which covers AJP-05, the doctrine for the planning of operations. None of the three is a stated prerequisite; they simply sit alongside it in the same family of joint doctrine.
It describes no certification, no notified body, no government quality assurance and no audit of any organisation. Its only stated check is a review of the agreement itself "in accordance with AAP-03," with the result "recorded within the NSDD." This is Edition 3 (AJP-3.9 Edition B), promulgated 9 November 2021. It supersedes "STANAG 2524, Edition 2, dated 8 April 2016."
STANAG 2524 and the doctrine it covers describe national military doctrine, training and reporting requirements, not a management system: the actual work, developing national doctrine and training headquarters staff against it, sits in a nation's own military establishment, not in software. What that leaves to evidence is the paperwork around it: procedures that correctly reference AJP-3.9 and this STANAG, training records showing staff have been trained against the doctrine's terms and common framework, and the trail of observations and implementation details a nation reports onward.
ComplyTrain holds that kind of evidence as a modern, auditable system: version-controlled procedures, training records tied to named individuals and dates, and corrective actions when a gap turns up, all searchable when a higher headquarters or a customer's quality clause asks for it. It does not write doctrine, does not conduct joint targeting activities, and does not decide how a nation implements the agreement or make its ratification and reporting decisions for it.
The applicable tier here, and whatever else it comes with, is set by the contract and the customer's quality clause. If you are working out what sits alongside STANAG 2524, the standards explorer covers the related NATO doctrine, and we are glad to talk through what that means in practice.
Tell us how you need to work with STANAG 2524 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 by itself. It binds the nations that ratify it. A company encounters it only when a contract or a tender invokes AJP-3.9 or the doctrine it carries.
STANAG 2524 is the agreement: the letter of promulgation, the ratification record, and the reporting and review machinery. AJP-3.9 is the doctrine itself, the Allied joint publication for joint targeting that the STANAG gives force to.
When it has changed its national doctrine and national training plans and standards for joint targeting, run national training exercises against them, and reported observations through the NATO Lessons Learned Portal.
No. The agreement names no certification, no assessment body and no audit of any organisation. Its only stated check is a periodic review of the agreement itself under AAP-03.
Edition 3 (AJP-3.9 Edition B), promulgated 9 November 2021, superseding Edition 2 of 8 April 2016.
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.