Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG 2611
National authorities implementing NATO counter-insurgency doctrine, and defence suppliers whose contract or tender names AJP-3.27
STANAG 2611 is NATO's ratified agreement committing member nations to implement AJP-3.27, the Allied joint doctrine for counter-insurgency; it binds nations rather than suppliers.
STANAG 2611 commits NATO nations to implement AJP-3.27, Edition A, the Allied joint doctrine for counter-insurgency (COIN). The agreement itself runs to five pages and holds no doctrine: it states an aim, names the publication, and sets out how a nation ratifies and implements it. Its aim is given as an interoperability requirement, "To provide NATO/Coalition forces with a common doctrine for the planning and execution of counter-insurgency operations in support of a host nation's government, pursuant to a North Atlantic Council's mandate."
A STANAG is the instrument, not the content. Nations ratify it, implement it through their own doctrine, education and training programmes, and a company encounters it only because a contract or a tender invokes AJP-3.27 or the doctrine it carries. Ratification and implementation are separate, a nation may ratify with reservations, and so the question "is STANAG 2611 mandatory" has a contractual answer and no general one.
The agreement defines its own test: it "will be implemented when AJP-3.27, Edition A, has been included into national doctrine, promulgated nationally, included in national education and training programmes, and used by personnel/within units that would operate in NATO operations or exercises." Doctrine written down, without the training and use limb, does not satisfy it on its own.
Nations report both ratification and implementation through NATO's electronic reporting tool: "Allies and NATO bodies shall provide implementation details through the electronic reporting tool (e-Reporting)." Partner nations are invited to report rather than required to.
Edition 3 was promulgated on 29 April 2022 and supersedes "STANAG 2611, Edition 2, dated 14 July 2016". The change is more than a new date: the document itself notes that the publication it now covers was renumbered, recording that AJP-3.27, Edition A, is a rewrite of the former AJP-3.4.4, restructured and updated. A reader who knows this STANAG as the cover for AJP-3.4.4 should look for AJP-3.27 now.
This one is not read alone. It names STANAG 2490 and AJP-3, the Allied joint doctrine for the conduct of operations, and STANAG 2299 with ATP-3.4.4.1, the counter-insurgency tactics publication, as related documents. Its own review runs under AAP-03.
It describes no certification, no notified body, no government quality assurance and no audit of an organisation. Its only stated check is its own review under AAP-03, recorded in the database, and it sets no NATO effective date, recording "Not applicable".
There is no compliance obligation in STANAG 2611 for a company, so there is nothing here to map onto a platform and we will not invent one. The honest connection is narrower: where a programme expects people to be trained on the doctrine a contract names, what a customer can ask to see is the documented procedure a team works to and the record of who was trained on it.
ComplyTrain holds exactly that: controlled documents, training records against them, and the trail those produce over time. It does not write doctrine, plan operations, or decide what a nation implements.
Which documents a contract actually invokes, and what comes with them, is set by that contract and the customer's quality clause, never by us. The standards explorer shows what sits alongside this agreement, and we are glad to talk through what a specific tender asks for.
Tell us how you need to work with STANAG 2611 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.
No. It binds the nations that ratify it. It reaches a company only when a contract or tender invokes AJP-3.27 or the doctrine it carries.
Only the machinery: the aim, the agreement to implement, the ratification and implementation steps, the review clause. The doctrine is in AJP-3.27.
Because the publication was renumbered. The document records that AJP-3.27 is a rewrite of the former AJP-3.4.4, restructured and updated, and this edition's cover reflects the new number.
When the doctrine has been included into national doctrine, promulgated nationally, written into national education and training programmes, and used by the units that would operate under it.
No. The agreement names no certification, no assessment body and no audit of any organisation.
Edition 3, promulgated 29 April 2022, superseding Edition 2 of 14 July 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.