Start a free trial
Menu

AJP-4.4

AJP-4.4 Allied joint doctrine for movement

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.

Edition
C
Published
2022-09

What it is

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.

Who NATO addresses it to

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.

How it binds: a STANAG, not a contract

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 movement system: levels, nodes and roles

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.

Five modes of transport, and the planning trade-offs

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, control and the information systems behind it

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.

What this edition changed, and what it deliberately excludes

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.

Related NATO doctrine

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.

How we help

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.

Standards it references

Questions

Is AJP-4.4 mandatory?

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.

What is the difference between AJP-4 and AJP-4.4?

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.

What is STANAG 2506?

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.

What is the difference between strategic, operational and tactical movement?

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.

Does AJP-4.4 set requirements for commercial transport companies?

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.