Start a free trial
Menu

AAP-32

AAP-32 formatting NATO standardization documents

NATO custodians, writing teams, tasking authorities and working groups who draft and maintain NATO standardization documents, not suppliers or contractors

AAP-32 is NATO's own formatting and drafting handbook for NATO standardization documents; it is a house style NATO's document custodians follow, not a requirement any supplier implements.

Edition
C
Published
2025-07

What it is

AAP-32 is NATO's own formatting and drafting handbook. It sets "the minimum requirements for content, structure, format and layout of NATO standardization documents" - the two families that cover everything in this catalogue: covering documents (STANAGs and STANRECs) and Allied Publications (NATO standards and standards-related documents, SRDs). It is easy to mistake for a technical requirement because it sits in the same publication series as documents that are, but it is something different: a house style for how NATO's own documents get built, not a requirement a supplier's quality system holds evidence against.

Who it actually directs

The Preface is explicit about its own readership: AAP-32 is "primarily intended as a guide for custodians and writing team members who are drafting NATO standardization documents, but is also to be used as a reference for tasking authorities (TAs) and delegated tasking authorities (DTAs), as well as working groups (WGs)". That is NATO's own standardization machinery, not a supplier, manufacturer or national regulatory authority - the word "supplier" never appears in the document, and no contract mechanism is defined anywhere in it. AAP-32 itself carries no covering STANAG and went through no national ratification; it was approved directly by the Allies in the Committee for Standardization and endorsed by every existing tasking authority and delegated tasking authority before promulgation. One qualification is worth carrying forward: on endorsement, NATO's Military Committee Joint Standardization Board noted that AAP-32 "generally governs the development of NATO standardization documents" but that AAP-47 remains "the primary guidance and authority for the formatting of Allied Joint Publications."

What Edition C changes

Edition C, Version 1, promulgated 31 July 2025, restructures the whole publication into a hyperlinked handbook meant to be read alongside NATO's own templates. It requires custodians to draft using the current templates from the NSO website, adds a new mandatory Preface covering scope, purpose, application and linkages, and moves the "Summary of Changes" out of the letter of promulgation into its own stand-alone front-matter section. It also introduces a new requirement for custodians to supply an abstract and keywords as searchable metadata in the NATO Standardization Documents Database - purely for document management and search, since "these requirements do not impact the content of the document" - and it strips out several elements the previous edition carried: national letters of promulgation, records of reservations and the list of effective pages no longer appear in Allied Publications. Requirements take effect immediately for documents still in development, though drafts already with a tasking authority for ratification or promulgation are not reissued.

The elements of a document

The bulk of AAP-32 works through each element of a NATO standardization document in turn - classification, short and long title, edition and version numbering, promulgation date, tasking authority, references, conventions and more - marking in a table which ones are mandatory, conditional or optional for a STANAG, a STANREC and an Allied Publication respectively. A few things stand out. Documents carry the lowest classification level that protects the information, and no marking at all where possible, to allow the widest distribution; a covering document and the Allied Publication it covers may carry different classifications. "Shall", "should" and "may" are fixed conventions meaning mandatory, recommended and optional respectively, and measurements are given in SI units, with imperial shown in parentheses only if useful. "Interoperability Requirements" is a STANAG-only element explaining why the agreement exists; "Standardization Requirements" is its STANREC equivalent and explicitly carries no mandatory content. "Implementation of the Agreement" gives Allies and NATO bodies a detailed list of actions needed to put a covered standard into effect - national doctrine changes, procurement programmes, training, exercises, facilities - illustrated in the text with worked materiel and operational examples.

How a document is laid out

Annex A sets out three pagination schemes - traditional (numbered straight through, reissued in full on amendment), chapter (numbered by chapter and annex, suited to page-by-page replacement) and electronic (continuous from the table of contents) - plus named paragraph and heading styles for both covering documents and Allied Publications. Four fully worked layout templates follow in the appendices, one each for a STANAG, a STANREC, a NATO standard and a standards-related document, printed bilingually in English and French as NATO's own templates are.

How it is checked

Nobody is assessed against AAP-32 itself. The nearest thing to a check it names is a custodian exporting their own portfolio's metadata from the NSDD "to ensure accuracy of these metadata and to report any inconsistencies to the NSO", and a custodian validating their own references are still current before a final draft goes forward. Neither is a certification, an audit or a supplier-facing scheme - both are a custodian checking their own paperwork.

Standards it points to

AAP-32 sits under AAP-03, which governs the wider standardization process AAP-32's formatting rules serve. Custodians check terminology against AAP-77 and military symbols against APP-06. A machine-readable submission carries the metadata set defined in STANAG 5636 / ADatP-5636 and is packaged using conventions referenced through STANAG 4778 / ADatP-4778, while STANAG 4774 / ADatP-4774 covers confidentiality metadata labelling. More specialised formatting guidance for particular document types sits elsewhere - Allied Joint Publications, for instance, look to AAP-47 first.

How we help

AAP-32 is not something ComplyTrain, or a customer, implements. It is NATO's own house style for the documents its standardization process produces, one level removed from anything that reaches a supplier directly. Its value to a reader is interpretive: understanding why a STANAG, STANREC or Allied Publication a contract actually cites is titled, classified, dated and structured the way it is, and why an "Implementation of the Agreement" paragraph reads like an instruction to nations rather than to a company. ComplyTrain keeps AAP-32 in the standards library for exactly that reason, as a cross-reference for teams reading NATO documents correctly, not as a control anyone holds evidence against.

What ComplyTrain does not do: it does not draft, format or promulgate NATO standardization documents, it does not check a supplier's own documents against AAP-32's layout or style rules, and it makes no claim that an organisation is, or could be, assessed against AAP-32, because the handbook describes no such assessment for anyone to pass. The tier of NATO documentation that actually reaches a contract, and the specific Allied Publications that come with it, are set by the contract and the customer's quality clause, not by this page. The standards explorer shows what else sits alongside AAP-32 in the catalogue, and we are glad to talk through what a specific contract requires.

Standards it references

Questions

Is AAP-32 mandatory for a supplier?

No. AAP-32 governs how NATO itself formats and drafts its own standardization documents; in its own words it is "a guide for custodians and writing team members who are drafting NATO standardization documents", not a requirement addressed to a supplier or contractor. A supplier's obligations come from the specific STANAG, AQAP or Allied Publication a contract invokes, not from this handbook.

What changed in AAP-32 Edition C?

Edition C, promulgated 31 July 2025, restructured the whole publication as a hyperlinked handbook, added a mandatory Preface and a stand-alone Summary of Changes section, introduced a new requirement for custodians to supply an abstract and keywords as searchable metadata, and removed national letters of promulgation, records of reservations and the list of effective pages from Allied Publications.

Is AAP-32 the same thing as AAP-47?

No. AAP-32 sets the general formatting rules for all NATO standardization documents. NATO's own Military Committee Joint Standardization Board has noted that AAP-47 remains the primary authority specifically for formatting Allied Joint Publications (AJPs), so that particular document family looks to AAP-47 first.

What is the difference between AAP-32 and AAP-03?

AAP-03 is the directive for how NATO standardization documents get proposed, developed, ratified and reviewed - the process. AAP-32 is the formatting handbook for what those documents look like once written - the layout, structure and style. AAP-32 names AAP-03 as its principal enabling document and is used during the drafting stage of AAP-03's wider process.

Does AAP-32 cover STANAGs and STANRECs as well as Allied Publications?

Yes. AAP-32 sets requirements for covering documents (STANAGs and STANRECs) and for Allied Publications (NATO standards and standards-related documents) alike, with a table marking which elements are mandatory, conditional or optional for each document type.