Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2616
Commanders, staff and planners in NATO and partner-nation forces, and the national authorities that ratify and implement the doctrine
STANAG 2616 is the NATO agreement by which member nations ratify and commit to implementing AJP-3.22, the Allied joint doctrine for stability policing.
STANAG 2616 is a NATO Standardization Agreement, not a technical manual in its own right. Its entire operative content is one line: "Participating nations agree to implement" AJP-3.22, Edition A, the Allied joint doctrine for stability policing. The requirements a unit or a supplier actually works to live inside that Allied Publication; the STANAG is the ratified commitment that puts it into force.
The document's own stated purpose is to close a gap in existing Allied doctrine: it says its doctrine "will contribute to fill a void in Allied Joint and Land Doctrine concerning the support and training of indigenous police forces which is not adequately addressed in current Counterinsurgency or Stability Activities doctrine." It also describes itself as the bridge "between the military component of stabilization mission and the follow on International police component," covering the handover from a military stabilization operation to a following international police presence.
Two groups, in the document's own terms. First, the nations that ratify and implement it: the agreement "has been ratified by member nations, as reflected in the NATO Standardization Document Database (NSDD)," is "effective upon receipt and ready to be used by the implementing nations and NATO bodies," and partner nations are separately "invited to adopt" it. Second, the people the doctrine itself is written for: "commanders, staff and planners when designing and conducting crisis response operations and Stabilization & Reconstruction missions," mainly at the strategic and operational level, though the document says it "could also be used as a guide at the tactical level." It also states the doctrine is "equally applicable to operations conducted by a coalition of NATO with partner nations, non-NATO nations, and other organizations."
The STANAG sets an operational test for implementation rather than a paperwork one: it is met when AJP-3.22 "has been included into national doctrine, promulgated nationally, included in training programmes and used within units earmarked for NATO." Nations report their implementation using the form in Annex H to AAP-03(J); partner nations report adoption using the form in Annex G to AAP-03(J). The document names no accredited body, no notified body and no audit against this STANAG; the checking it describes is nations reporting their own position to the NATO Standardization Office, not a third party assessing a supplier or a product.
The STANAG itself is reviewed "at least once every three years," and a nation or NATO body may propose changes "at any time" for the next review cycle, so the edition and the doctrine it points to can move.
STANAG 2616 does not stand alone. Its own list of related documents places AJP-3.22 under the capstone AJP-01 and the conduct-of-operations doctrine in AJP-3 and AJP-3.2, and alongside doctrine on peace support (STANAG 2181, AJP-3.4.1), counterinsurgency (STANAG 2611, AJP-3.4.4), military police (STANAG 2296, AJP-3.2.3.3), tactical stability activities (STANAG 2606), tactical counterinsurgency activities (STANAG 2299), and civil-military cooperation (STANAG 2509, AJP-3.4.9). An organisation reading STANAG 2616 in isolation from that hierarchy will read it thin; the requirements live in the doctrine set it belongs to.
STANAG 2616 is an operational doctrine agreement, not a management-system standard, so there is no certificate to hold and no software feature that maps to it. The work it describes, bringing AJP-3.22 into national doctrine, training units against it and using it in the field, is done by nations and their forces, not by a compliance platform.
Where this kind of document usually meets ComplyTrain is downstream of it: a contract, a training programme or a support role that names STANAG 2616 or AJP-3.22, and needs the paperwork trail behind it held somewhere auditable. That looks like procedures for the specific tasks a role or contract requires, training records showing people were prepared against those procedures, and a record of when the documentation was last checked against the STANAG's own three-year review cycle.
ComplyTrain does not conduct stability policing operations, does not write or substitute for national doctrine, and does not certify or assess anyone against this STANAG. No accreditation or certification scheme for it exists to claim.
Tell us how you need to work with STANAG 2616 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 in the way any STANAG is: it binds the nations that ratify it, and a nation implements it through its own doctrine, training and units. It reaches a supplier or a contractor only when a specific contract, tender or programme names it or the doctrine it covers, not automatically.
STANAG 2616 is the two-page ratified agreement; AJP-3.22 is the Allied joint doctrine for stability policing that the agreement commits nations to implement. The requirements sit in AJP-3.22, not in the STANAG cover.
No. The document names no accreditation body, notified body or audit scheme. Implementation is a national act, reported by nations to the NATO Standardization Office, not a certificate a company or a product can hold.
The document states it is reviewed at least once every three years, with the result recorded in the NATO Standardization Document Database. A nation or NATO body may propose changes at any time for the next review.
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.