Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2565
NATO member and partner nations ratifying and disseminating the AMedP-8.10 leadership guide within their own forces
STANAG 2565 is NATO's agreement by which member nations commit to implement AMedP-8.10 Edition B, a guide giving military leaders practical strategies for psychological support across the deployment cycle.
STANAG 2565 is the NATO Standardization Agreement covering "A psychological guide for leaders across the deployment cycle." It was promulgated 19 March 2026 and supersedes "STANAG 2565, Edition 2, dated 31 October 2019" - the cover notes the document "has been updated from previous edition released in 2019." STANAG 2565 is available free of charge from NATO's Standardization Documents Database, which is also the authoritative record of which nations have ratified it and how they have implemented it.
A STANAG is the agreement by which NATO nations commit to implement a standard, not the technical or subject-matter content itself. STANAG 2565's own text is short and administrative: an aim, an agreement, and the ratification, implementation and review machinery. The guide's actual content sits in a separate publication, AMedP-8.10, Edition B, which the STANAG names as the standard participating nations "agree to implement." Anyone looking for the guide's own guidance needs AMedP-8.10's own text, not this cover agreement.
The stated aim is "to produce a series of guidelines for psychological support in military operations, in the form of a Military Leaders Guide to help standardise practice," grounded in "a common understanding among both leaders and mental health professionals of the importance of psychological readiness and support." The cover names seven areas nations should weigh when disseminating the guide - leaders' role in psychological readiness, what unit members and leaders expect, individual psychological fitness, morale and unit effectiveness, military family readiness, mitigating stress reactions, and working with mental health professionals - without elaborating on any of them here. The guide itself "took a general approach in order to be as relevant to leaders from as many nations as possible," and the cover directs specific questions to "their own mental health professionals in their own nation." That detail, and the guide's substance generally, lives in AMedP-8.10, which has its own record.
STANAG 2565 binds nations, not suppliers. It is effective "upon receipt for use by the participating nations and NATO bodies," and it becomes binding on a given nation through ratification, "as reflected in the NATO Standardization Documents Database (NSDD)." Dissemination is a further step: nations "agree to review the document and consider disseminating the information to their military leaders." Partner nations are only "invited to provide their implementation details through the electronic reporting tool" rather than bound by the agreement. Ratification and implementation details, for both, go through "the electronic reporting tool (e-Reporting)" and are recorded in the NSDD. Nothing in the document sets an obligation reaching a supplier or a company directly.
STANAG 2565 describes no certification scheme and no audit of a supplier, a company or a product. What it describes is nations reporting their ratification and implementation status to NATO: "National responses are recorded in the NATO Standardization Documents Database (NSDD)." The document never uses the word "certified" or "certification." The STANAG itself "is to be reviewed in accordance with AAP-03," with the result "recorded within the NSDD," and it is supervised under NATO's medical standardization structure: COMEDS, MCMedSB, MedStd, MHC and MMH P.
STANAG 2565 covers AMedP-8.10, the Allied Medical Publication that carries the guide's actual content, and the only standard the document names ("OTHER RELATED DOCUMENTS None."). Its review clause references AAP-03: "This STANAG is to be reviewed in accordance with AAP-03."
STANAG 2565 creates no obligation for a supplier or a company: it is the mechanism by which NATO nations commit to disseminate a leadership guide, AMedP-8.10, within their own forces, and doing that runs through national command and mental-health channels, not a contract deliverable.
Where a defence contract brings other STANAGs and Allied Publications into scope alongside this one - quality assurance, technical or engineering documents that a company genuinely has to evidence - ComplyTrain gives that organisation one auditable place to hold the procedures, training records and audit trail those documents require.
ComplyTrain does not write, deliver or evidence the psychological guide itself. That is AMedP-8.10's content, and delivering it to military leaders is a national command and mental-health-professional matter, not a compliance-software task.
Which STANAGs and Allied Publications actually apply to a given contract or programme is set by the contract and the customer's quality clause, not by us. Browse the explorer to see what sits alongside STANAG 2565 and AMedP-8.10, and talk to us about the evidence trail once you know which ones are in your contract.
Tell us how you need to work with STANAG 2565 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.
Only where a nation has ratified it, and it reaches a company only where a contract or tender invokes it or the AMedP-8.10 guide it covers directly. The document itself sets no NATO-wide compliance date - NATO Effective Date is stated as "Not applicable."
STANAG 2565 is the NATO ratification agreement; AMedP-8.10, Edition B is the publication that actually carries the psychological guide for leaders. Ratifying STANAG 2565 is how a nation commits to implement AMedP-8.10.
No. STANAG 2565 describes nations ratifying the agreement and reporting implementation to NATO, recorded in the NATO Standardization Documents Database. It describes no certification or audit scheme for a supplier, a company or a product.
Yes. This edition supersedes "STANAG 2565, Edition 2, dated 31 October 2019," and the cover states the document "has been updated from previous edition released in 2019."
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.