Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-4.4
NATO commanders and staff at strategic and operational level headquarters, not suppliers or contractors
AJP-4.4 is NATO's Edition C doctrine for planning and coordinating the movement of personnel and materiel in joint operations; it binds nations through STANAG 2506, not companies directly.
AJP-4.4 is NATO's Allied Joint Doctrine for Movement, Edition C, Version 1, promulgated in September 2022. It is level 2 NATO doctrine: the shared framework strategic and operational headquarters use to plan and control the physical movement of personnel and materiel in support of joint operations. It builds on the broader principles in AJP-4, Allied Joint Doctrine for Logistics, and on NATO's policy for movement and transportation, MC 0336/2. The agreement of NATO nations to use it is recorded in STANAG 2506, and this edition supersedes the previous Edition B.
The doctrine says plainly who it is for: it "is intended primarily for strategic and operational level headquarters involved in operations", though it is also "instructive" for a coalition of NATO members, partners and non-NATO nations, and provides a reference for civilian actors working alongside them. It names the roles in detail: troop-contributing nations, which keep national responsibility for their own forces' movement; host nations, which hold "the ultimate authority to approve, coordinate and control all movement" on their own territory; and, on NATO's side, Allied Command Transformation, Allied Command Operations and SHAPE, the joint force commands, the Standing Joint Logistic Support Group and its Allied Movement Coordination Centre, and the NATO Support and Procurement Agency, which provides the contracting tools nations and NATO commands actually use to buy transportation and terminal services. A commercial carrier or logistics contractor is never this document's own reader. Where the text mentions contractors, it is describing NATO commanders coordinating with them, not setting requirements for them directly.
Like every Allied Publication, AJP-4.4 has no force on its own. It acquires force through the STANAG that covers it: "the agreement of nations to use this publication is recorded in STANAG 2506." A nation ratifies the STANAG, and the doctrine then applies inside NATO's own command structure whenever a joint or coalition operation is planned or run. That is a different mechanism from a regulation that binds by date and territory, or a management-system standard a company chooses to implement. There is no tender clause that invokes "AJP-4.4" the way one invokes an AQAP; a company meets this doctrine's world only where a specific movement, transport or terminal contract, led by a nation, a NATO command or NSPA, requires it.
The doctrine defines movement as "the set of activities involved in the physical transfer of personnel and/or materiel as part of a military operation", broken into four levels: national movement (a national location to a port of embarkation or debarkation), strategic movement (between those ports), operational movement (from a port of debarkation to the assigned area of operations, or back), and tactical movement (within that area). It describes a movement support network built from named nodes - the forward mounting base, ports of embarkation and debarkation, the theatre reception centre, marshalling areas, holding areas, staging areas, convoy support centres, assembly areas and border crossing points - each with its own defined function. Chapter 2 sets out who owns which piece of this: national roles for troop-contributing and host nations, and NATO roles running from doctrine development at Allied Command Transformation through strategic coordination at the SJLSG/AMCC to tactical execution by component commanders and the joint logistic support group.
Chapter 3 works through sea, air, road, rail and inland waterway transport, and the trade-offs a planner has to weigh for each: sea movement carries the most and costs the least per tonne but is slow and depends on suitable ports; air movement is fast and reaches places other modes cannot, but is expensive and limited in capacity; road movement is the usual choice inside a joint operations area but rarely used over long strategic distances; rail moves heavy, bulky loads efficiently but only where the infrastructure and rolling stock exist and is vulnerable to disruption; inland waterway is cheap and reliable but inflexible about its routes. Supporting functions - military engineering, force protection, medical support - are "key to enable and sustain the movement of personnel and materiel", and named movement authorities for air, port, rail and road each carry specific control responsibilities.
Command and control for movement runs at three levels: strategic, coordinated by the SJLSG/AMCC; operational, led by the commander joint task force while the host nation keeps ultimate authority over its own territory; and tactical, run by component commanders and the joint logistic support group. NATO "is mandated to use" its own logistic information management system - the LOGFAS suite, including ADAMS for deployment planning, EVE for execution visibility, and CORSOM for reception, staging and onward movement - and nations using a different system "must ensure that data is provided in a compatible format." Reporting has to be "timely, accurate and in the agreed format", and secured whenever classified information moves through it.
This edition dropped "transportation" from its own title, because transportation is only one enabling capability alongside mobility, infrastructure and movement control, not the whole subject. It also removed detailed deployment and redeployment planning, pointing instead to AJP-3.13, and dropped training content to avoid duplicating lower-level documents. The doctrine says so of itself: "it does not contain detailed procedures, which should be covered in lower level documents." A reader looking for step-by-step movement control instructions, rather than the framework those instructions sit inside, will not find them on this page or in the source document.
AJP-4.4 sits inside a wider family. It is covered by STANAG 2506, builds on AJP-4 (Allied Joint Doctrine for Logistics) and is mutually supportive with AJP-4.6 (Joint Logistic Support Group). It works alongside AJP-3 (Conduct of Operations), AJP-3.13 (Deployment and Redeployment of Forces), AJP-3.19 (Civil-Military Cooperation) and AJP-5 (Planning of Operations), and it defers to ALP-16 for explosives safety and munitions risk management requirements it invokes but does not itself set out. Correct citation of its own terminology is governed by AAP-47 (Allied Joint Doctrine Development) and by AAP-77, the NATO Terminology Manual. None of these are requirements a supplier meets on their own account; they are the doctrine chain a NATO commander reads alongside AJP-4.4.
The work AJP-4.4 describes - planning a movement architecture, coordinating with a host nation, running command and control, submitting a deployment plan through LOGFAS-ADAMS - happens inside NATO's own command structure, and that work is not something software does. Where a company holds a contract to provide transportation, terminal or logistics services in support of a NATO-led or coalition operation, what a customer or a nation's authority is likely to ask for looks like the evidence trail for any operational standard: written procedures for how consignments are handled at the movement nodes the doctrine defines, records that explosives safety requirements were addressed before munitions moved, training records showing staff understand the reporting formats a NATO information system demands, and a corrective-action trail when a movement report flags a delay.
ComplyTrain gives that kind of work a place to live - controlled procedures, training records tied to the people who need them, and an audit trail that a movement plan's paperwork was actually followed - generally, not mapped to AJP-4.4 itself, because no such mapping exists.
What ComplyTrain does not do: plan, authorize or execute a movement, or stand in for the command relationships the doctrine describes. The applicable tier of NATO documentation on a given contract is set by that contract and the customer's quality clause, not by this page. The standards explorer shows what else sits alongside AJP-4.4, and we are glad to talk through what a specific contract requires.
Tell us how you need to work with AJP-4.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, and not for a company. AJP-4.4 binds through STANAG 2506, which NATO nations ratify; a nation's forces and headquarters then work to the doctrine when planning and running an operation. A company meets it only where a specific contract, led by a nation, a NATO command or NSPA, requires movement or transport work to follow it.
AJP-4 is the capstone Allied Joint Doctrine for Logistics, covering the whole logistics function. AJP-4.4 is subordinate to it and focused specifically on movement: the planning, roles and enabling capabilities needed to physically move personnel and materiel through a joint operations area.
STANAG 2506 is the NATO Standardization Agreement recording nations' agreement to use AJP-4.4. The doctrine itself is not a technical specification with independent force; it acquires its force through this agreement, the way most Allied Publications do.
Strategic movement runs between an assigned port of embarkation and a port of debarkation. Operational movement connects a port of debarkation to the assigned area of operations, or back. Tactical movement is everything that happens within that area, between its own nodes.
No. It describes NATO commanders and nations using and coordinating with commercial transport, for example through NSPA's contracting tools or civil resources identified during planning. Any requirement on a specific carrier or contractor comes from the contract that engages them, not from this doctrine directly.
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.