Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-4
NATO commanders and staffs planning and conducting an Alliance operation, not a commercial supplier directly
AJP-4 is NATO's keystone doctrine for sustaining Allied operations - personnel, logistics, medical support, military engineering, finance and contract support - directed at commanders and staffs, not suppliers directly.
AJP-4 is NATO's keystone Allied Joint Publication on sustainment: the doctrine that tells a commander and staff how to plan, coordinate and run the personnel, logistics, medical support, military engineering support, finance and contract support behind an Alliance operation. Edition C, Version 1, promulgated in August 2025, is the first edition to carry that scope. It replaces AJP-4(B), which covered logistics alone, and its own Summary of Changes calls it "the first Allied Joint Doctrine for Sustainment of Operations" - a genuine widening, not a renumbering. Nations agree to use it through STANAG 2182, and the doctrine itself states its purpose: it "provides guidance to commanders and staffs on the planning, execution, coordination and synchronization of the sustainment of Alliance operations and missions." That sentence matters more than it looks: this is guidance for the people running an operation, not a requirement written for a company.
AJP-4 never names a supplier, a manufacturer or an acquirer as its audience. It is addressed to commanders and their staff branches, and, at the strategic level, to the troop-contributing nations that generate and sustain forces. A commercial party appears only from the commander's side of the relationship: as a contractor whose personnel and ownership get vetted before award, as a party in a "commercial agreement, which is legally binding subject to terms and conditions," or as a risk to be managed (the document has a specific term, "contractor fratricide," for what happens when competing buyers bid up the same scarce local goods and services). None of that makes AJP-4 a requirement a company implements. What it reaches is a nation, through STANAG 2182 and that nation's own command structure; whatever a supplier is actually asked to do comes from a specific contract or task order, not from this doctrine directly.
The doctrine defines sustainment as "the provision of personnel, logistics, medical support, military engineering support, finance and contractor support necessary for Alliance operations and missions," and treats each as a distinct function with its own chapter: personnel, logistics, medical support, military engineering support, finance, and contract support. Five principles run across all of them: responsiveness to requirements, reliability, a collective approach, unity of effort, and integrity and ethics. NATO also names eight ways sustainment gets delivered in practice: collectively, jointly, multinationally, through government departments, NATO agencies, contracted support, host-nation support, or civil-military cooperation. Underpinning all of it is the Reinforcement and Sustainment Network, a peacetime-prepared network spanning the whole of Supreme Allied Commander Europe's area of responsibility and managed by the Joint Support and Enabling Command.
Chapter 2 sets the planning pattern every functional chapter then repeats. Planners weigh self-sustainment against reliance on external, often civilian, sources of support, and are pointed at a specific list of contested-environment risks: an adversary attacking sustainment forces directly, disabling infrastructure, capturing stockpiles, or exploiting supply chains through sanctions and economic pressure. An operation itself moves through preparation (developing the operation plan, force generation, pre-execution activities, deployment), sustaining fighting power, transition, and termination and post-termination activities, where redeployment breaks into four defined stages: disengagement, rearward movement, staging and dispatch, and strategic redeployment. Assessment runs continuously throughout, at every echelon, feeding the commander's own decisions rather than producing a certificate anyone holds.
A host nation's assistance is governed by six principles: responsibility, provision, authority, economy, visibility and reimbursement, all aimed at making sure support is coordinated rather than competed for. The chapter also names the vulnerabilities sustainment planning has to account for: credible sustainment (troops need confidence the system will support them), the Reinforcement and Sustainment Network itself being a target, munitions and explosives risk (assessed under Allied logistic publication ALP-16), mass casualty events, large-scale patient flow, protecting commercial information from suppliers who have not been properly vetted, and contractor fratricide.
Chapter 8 is the one place in the document where a company's role is described directly, because contracting is itself one of the six sustainment functions. It sets out three layers: contract support integration (planning and synchronising contracted support), contract support itself (the contracting authority that legally binds a contractor), and contract management, which includes "the oversight and integration of contractors (personnel and equipment) into the operational theatre." It requires segregation of duties between whoever holds the requirement, whoever runs the procurement, and whoever controls the funding, and it directs that vendors be vetted, in part to confirm they are not providing material support to an enemy. Even here, though, nothing is certified: what governs a contractor is the contract itself, and this doctrine only explains the shape that contract is likely to take.
AJP-4 builds on AJP-01, Allied Joint Doctrine, and sits alongside AJP-3 (Conduct of Operations) and AJP-5 (Planning of Operations) as adjacent, closely related doctrine. Beneath it are the more detailed, level-3 publications that actually carry the technical detail for a single function: AJP-4.2 for medical support, AJP-4.3 for host-nation support, AJP-4.4 for movement, and AJP-4.6 for the joint logistic support group, alongside AJP-3.12 for military engineering. If a specific requirement in a tender or contract traces back to NATO sustainment doctrine, it is more likely to cite one of those than AJP-4 itself. The standards explorer lists the rest of what sits alongside this document.
AJP-4 is published by the NATO Standardization Office and, like every NATO standardization document, carries no charge. The NSDD listing for AJP-4 is the authoritative source, and national standardization authorities can also supply a copy. We credit NATO for the catalogue and neither sell nor host a copy ourselves.
AJP-4 is doctrine, not a requirement set, so there is nothing here for a company to implement directly. Its value to a reader is context: understanding why a NATO or national contract touching logistics, medical, engineering or other sustainment-related work is shaped the way it is, and which of the more specific publications beneath AJP-4 (host-nation support, medical support, movement, the joint logistic support group) a particular requirement is actually drawn from.
Where a company does have a role, as a contracted supplier of sustainment-related services, what it can reasonably be asked to evidence is its own internal process: the procedures it follows, the training records for its people, and the documentation a contracting officer or customer audit expects to see. ComplyTrain is a quality and compliance platform for exactly that kind of internal record-keeping: controlled procedures, training records, corrective actions and the document trail that work generates, kept current and ready to produce.
What we do not do: we do not perform sustainment work itself. The personnel administration, the physical movement of materiel, the delivery of medical care, the construction military engineering carries out, and the day-to-day conduct of a contract in theatre all happen in the handling of the operation, not in software, and AJP-4 places none of that on a supplier directly in any case. What applies to a specific contract, and which document actually binds a given supplier, is set by that contract and the customer's quality clause, never by us. The standards explorer shows what else sits in the catalogue alongside AJP-4, and we are glad to talk through what your contract actually requires.
Tell us how you need to work with AJP-4 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 directly. AJP-4 is guidance for NATO commanders and staffs on planning and running sustainment; it never names a supplier, manufacturer or acquirer as its audience. A company's obligations come from the specific contract or task order a customer writes, which may draw on this doctrine's assumptions, not from AJP-4 itself.
No. AJP-4 is the Allied Joint Publication, the technical doctrine itself. STANAG 2182 is the Standardization Agreement by which NATO nations record their agreement to use it. The STANAG is the cover; AJP-4 is what it covers.
AJP-4 is the overarching, keystone doctrine covering all six sustainment functions at the operational level. AJP-4.2, AJP-4.3 and AJP-4.4 are more detailed, level-3 publications beneath it, covering medical support, host-nation support and movement respectively in far more depth. A specific contract requirement is more likely to trace to one of those than to AJP-4 directly.
No. AJP-4 has no certification, audit or accreditation scheme for a company to map a product against, and ComplyTrain makes no claim to implement or align with it. Where ComplyTrain helps is with the internal procedures, training records and audit trail a defence contract's own quality clause requires, whatever standard that clause names.
This page describes Edition C, Version 1, promulgated in August 2025, which is effective on receipt and supersedes Edition B, Version 1. It is a structural rewrite: personnel, medical support, military engineering, finance and contracting are now treated as sustainment functions in their own right, alongside logistics, rather than logistics being the whole subject.
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.