STANAG 2532 and Allied joint doctrine for deployment and redeployment

What it is

An agreement, not the doctrine itself

STANAG 2532 is five pages of agreement, not a technical specification. The doctrine it exists for is AJP-3.13, Edition A, Allied joint doctrine for the deployment and redeployment of forces, and this document's own aim is narrow: to respond to an interoperability requirement, stated as "to provide joint commanders and staffs with a common framework to command, coordinate and synchronize Alliance deployment and redeployment operations". Everything substantive about how forces are actually deployed and redeployed sits in that publication, not in this agreement.

That distinction is the thing readers most often have wrong about a STANAG. It is the instrument by which NATO nations commit to implement a standard. A nation ratifies it, implements it domestically, and a company meets it only because a contract or a tender says so. Ratification and implementation are separate steps, a nation can ratify with reservations, and so "is STANAG 2532 mandatory" has no general answer, only a contractual one.

How a nation implements it

The agreement is "effective upon receipt for use by the participating nations and NATO bodies," and nations are invited to examine their ratification and tell the NATO Standardization Office what they intend. Responses are recorded in NATO's Standardization Document Database.

Implementation is defined, and the definition has two limbs. It is met "when the necessary orders/instructions have been issued directing the forces concerned to put the content of the covered standard into effect," and the agreement adds that preparatory and planning activities are also to be taken into consideration in accordance with the standard. Issuing the order alone is not, on the document's own terms, the whole of implementation. Allies and NATO bodies must then report their implementation details through the electronic reporting tool; partner nations are invited to do the same rather than required to.

What changed in this edition

This is Edition 2, promulgated 17 May 2021, superseding "STANAG 2532, Edition 1, dated 6 June 2008." The letter of promulgation describes the revision as restructuring the doctrine, reducing redundancy and improving continuity with NATO's capstone and keystone doctrine, updating fundamentals, principles, roles and responsibilities, and introducing new sections on redeployment, training, and operational and capability requirements. A reader who last worked from the 2008 edition is working from a materially different document.

What it does not do

It describes no certification, no notified body, no government quality assurance and no audit of any organisation. The only check it names is of itself: a review in accordance with AAP-03, recorded in the database. And it places no obligation on a supplier: nothing in the text addresses a manufacturer, a contractor or a product directly.

Related documents named in the cover

STANAG 2532 covers only AJP-3.13, Edition A - that is the sole standard nations agree to implement here. The cover also lists related reading that informs rather than binds: STANAG 2437 and the AJP-01 doctrine it covers, STANAG 2182 and the AJP-4 logistics doctrine it covers, and STANAG 2506 and the AJP-4.4 movement and transportation doctrine it covers. Four NATO Military Committee policy documents are named alongside these and sit outside our catalogue: MC 0055 (NATO logistic readiness and sustainability policy), MC 0133 (NATO's operations planning), MC 0319 (NATO principles and policies for logistics) and MC 0336 (NATO principles and policies for movement and transportation).

Standards it references

• STANAG 2437Background
• AJP-01Background
• STANAG 2182Background
• AJP-4Background
• STANAG 2506Background
• AJP-4.4Background