Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-3.27
NATO commanders and staff planning and conducting counter-insurgency operations
NATO's Allied Joint Publication on counter-insurgency doctrine, addressed to commanders and staff and given effect between nations through STANAG 2611.
AJP-3.27 is NATO's Allied Joint Publication on counter-insurgency (COIN), Edition A, Version 2, promulgated in April 2023. Its own scope statement describes it as covering "the NATO doctrine for the planning, preparation, execution and assessment of counter-insurgency (COIN) operations in the context of Allied operations." Counter-insurgency itself carries a NATO Agreed definition: "a comprehensive civilian and military effort to isolate and defeat an insurgency, create a safe and secure environment, address core grievances, and to enable the promotion of legitimate governance and rule of law." The document runs to four chapters covering the operating environment, the insurgency and the counter-insurgency response, plus three annexes on COIN paradoxes, a learn-and-adapt model, and insurgencies sponsored by major powers in an era of strategic competition.
This is not a document written for a company. NATO says so directly: "AJP-3.27 COIN is primarily intended as a guidance for NATO commanders and staff," adding that it "may also be instructive when conducting COIN operations in the framework of a coalition of NATO Allies and/or non-NATO partners and nations." It is also offered as a reference to NATO education and training bodies, NATO Centres of Excellence, and the international, governmental and non-governmental organisations working alongside a COIN operation. There is no supplier, manufacturer or acquirer named anywhere in the text.
NATO nations record their agreement to use this publication through STANAG 2611: "The agreement of nations to use this publication is recorded in STANAG 2611." That ratification and implementation by a nation, not the document itself, is what obliges that nation's forces to follow it. Even then, an actual COIN operation proceeds only under firm political control: "NATO COIN operations always require North Atlantic Council approval and can originate from a request of a NATO member state under Article 5 of the Washington Treaty, a UN Security Council Resolution and/or at the request of the HN." This is Edition A, Version 2, which supersedes Edition A, Version 1 and realigns the document with NATO's current capstone doctrine, AJP-01.
Chapter 2 sets out how a joint force commander builds a comprehensive picture of the operating environment, principally through the joint intelligence preparation of the operating environment (JIPOE) process feeding a wider comprehensive preparation of the operating environment. The document works through eight variables in turn - political, military, economic, social, information, infrastructure, physical and time (PMESII-PT) - each with the specific questions a staff needs to answer: who holds power and how it is shared, which armed actors operate in the area, how the local economy sustains or undermines an insurgency, what drives social and gender dynamics, how information and propaganda move, which infrastructure is a target or a lifeline, how geography and climate shape operations, and how time itself tends to favour the insurgent.
Chapter 3 describes the adversary the doctrine assumes. It distinguishes root causes - identity, corruption, repression, foreign exploitation or occupation, and a shortfall in essential services - from shorter-term proximate causes that catalyse them into action. It sets out five types of insurgent objective (reform, revolution, secession, nullification and resistance), a membership taxonomy of leaders, cadre, armed elements, auxiliaries, underground and supporting population, and the recurring theme that the population itself is the contested centre of gravity, made up of active supporters, passive supporters or sympathizers, and the uncommitted. It closes with the insurgency's own vulnerabilities: the tension between secrecy and popular support, dependence on a secure operating base, reliance on external funding and supply, and susceptibility to internal division.
Chapter 4 is the doctrine's operational core. It sets out ten COIN principles - among them political primacy, developing host nation (HN) legitimacy, handing responsibility to local forces as soon as practicable, securing the population, and operating within international and domestic law - and three generic approaches to a campaign (indirect, balanced and direct), distinguished by the proportion of military effort against developmental and diplomatic effort. It introduces the shape-secure-develop (SSD) operations framework and its tactical counterpart, clear-hold-build (CHB), the joint functions a commander integrates (manoeuvre, fires, command and control, intelligence, information, sustainment, force protection and civil-military cooperation), host nation security force capacity building through security force assistance and stability policing, and a phased model - tactical, operational and strategic over-watch - for handing security responsibility back to the host nation.
A theme runs through the whole publication that a reader coming from a purely military background may not expect: military action on its own does not win a counter-insurgency. The document is explicit: "Military tactical success often guarantees nothing." It adds that "The more force is used, the less effective it may be," and that "Doing nothing may be the best reaction" where the insurgent's aim is to provoke an overreaction. Force protection is treated as a cost, not a free good: overly imposing measures, in the document's own words, "tend to isolate and, over time, alienate, the security force from the local population." The document's own emphasis sits on legitimacy, the population and restraint, not on a checklist of kinetic tasks.
AJP-3.27 does not stand alone. It sits under NATO's capstone doctrine, AJP-01, and the operational-level doctrine for joint operations, AJP-3, and it uses the general planning process set out in AJP-5. It is the doctrinal basis for the tactical-level publication ATP-3.4.4.1, Counter-Insurgency Tactics, and it is closely linked to AJP-3.16 (Security Force Assistance), AJP-3.19 (Civil-Military Cooperation), AJP-3.21 (Military Police) and AJP-3.22 (Stability Policing), among a wider set of Allied and Allied Tactical publications on intelligence, force protection and strategic communications that the document cites throughout.
AJP-3.27 is doctrine for NATO commanders and staff, not a specification a company implements or is certified against. There is no requirements clause here, no evidence list, and no scheme anyone can be assessed under, so the honest position is that this document itself gives a compliance platform nothing to map to.
Where a company does have a role is one step removed from the doctrine itself. A contractor delivering training, logistics, sustainment or advisory support in a security-force-assistance context still has to hold the documented procedures, training records, vetting evidence and audit trail its own contract demands - the document itself notes that "Some sustainment activities can be outsourced to civilian contractors-national or international-in which accountability and effectiveness of the contractor requires proper vetting and continuous evaluation." That is ordinary compliance work, of the kind ComplyTrain supports generally: version-controlled procedures, training records tied to individuals, and an audit trail showing what was done and by whom. It is not a mapping to AJP-3.27 itself, because AJP-3.27 carries no certification scheme or evidence list of its own for a supplier to meet.
What applies to a given contract, and which standards accompany it, is set by the mandate and the customer's own quality clause, not by this page. The standards explorer shows what sits alongside AJP-3.27 in NATO's counter-insurgency and stabilization doctrine, including the security force assistance, civil-military cooperation and stability policing publications it works alongside. If your contract references this family of doctrine and you need the paperwork behind it under control, talk to us.
Tell us how you need to work with AJP-3.27 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.
AJP-3.27 is doctrine, not a legal instrument. It takes effect for a NATO nation's forces once that nation has ratified STANAG 2611, the agreement recording that nations will use the publication. Even then, whether it binds a particular contractor or unit depends on the mandate, the mission and the chain of command, not on the document by itself.
AJP-3.27 did. Its Edition A, Version 1 "was a product of the full revision of AJP-3.4.4," and the current Edition A, Version 2, dated April 2023, in turn supersedes that Version 1.
No. The document describes no certification, audit or inspection scheme, and NATO neither operates nor recognises one for compliance with this doctrine. The closest thing it discusses is a commander's own assessment of a campaign's effectiveness against its objectives, which is an operational judgement, not a compliance audit.
AJP-3.27 sets the operational-level principles for counter-insurgency. The tactical detail sits in a separate publication: "AJP-3.27 establishes principles for COIN tactical doctrine in NATO, which is currently covered in Allied Tactical Publication (ATP)-3.4.4.1 Counter-insurgency (COIN) Tactics."
Beyond NATO commanders and staff, the document names NATO Education and Training Facilities, NATO Centres of Excellence, and NATO and non-NATO civilian actors - international, governmental and non-governmental organisations - as also drawing on it, and says it "may also be instructive" for coalitions that include non-NATO partners. It separately notes that non-military organisations will find it "a useful source of information about the full range of military capabilities that NATO may contribute" to a COIN response.
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.