What Role Does AQAP 2110 Play in NATO Procurement
- 1 day ago
- 5 min read
AQAP 2110 is the requirement NATO uses to trust a supplier's quality across design, development, and production. It contains all of ISO 9001:2015 and adds NATO-specific rules on top: configuration management, risk management, product dependability, and the acquiring government's right to inspect you while the contract runs. The current version is Edition D, Version 1, promulgated by the NATO Standardization Office in June 2016 and still in force in 2026.
If you supply a NATO-facing prime, AQAP 2110 is rarely optional. When a contract names it, the requirement binds every process needed to deliver, and it flows down your supply chain to subcontractors and service providers, translation vendors included. With European defense spending rising fast, more suppliers are meeting these requirements for the first time.
What AQAP 2110 requires beyond ISO 9001
Chapter 4 of the standard makes ISO 9001:2015 apply in full. Chapter 5 then adds the NATO-specific requirements a commercial quality system leaves out.
The additions that matter most on a defense contract:
Configuration management under ACMP 2100, with a documented plan so every design change is identified, controlled, and recorded.
Risk management aligned to ISO 31000:2009, starting at contract review and kept current, with the plan available to the government.
Product dependability, covering availability, reliability, maintainability, and safety across the item's service life.
Identification and traceability, mandatory wherever a component failure could cost equipment, performance, or life.
Control of nonconforming product, including a Certificate of Conformity you sign when the product is released.
Every one of these produces documented evidence a government representative can ask to see. That evidence trail is the whole point.
Why there's no AQAP certificate in the ISO sense
Here's what trips up new suppliers. You don't prove AQAP 2110 conformity to a certification body the way you do with ISO 9001. You demonstrate it to the acquiring government through Government Quality Assurance, or GQA.
The standard defines GQA as the process by which national authorities gain confidence that a contract's quality requirements are met. A Government Quality Assurance Representative acts for the acquirer, with the right to enter your facilities, audit your quality system, and reject nonconforming product. STANAG 4107, the agreement recording nations' use of the AQAPs, lets one country's quality authority run GQA on behalf of another, so a German buyer can rely on a French authority's assurance of a French supplier.
You can still hold a third-party certificate that your quality management system meets AQAP 2110, and many suppliers do. We at AD VERBUM are AQAP 2110 certified through Bureau Veritas. The certificate proves our quality system meets the standard. On a specific NATO contract, the acquiring nation still exercises its GQA rights directly.
AQAP 2110 versus 2120, 2210, and 2131
The AQAP 2000 series divides quality requirements by contract scope. Four numbers come up often, and one of them is now history:
AQAP 2110 covers design, development, and production, the full life cycle of a contracted item.
AQAP 2120, the old production-only publication for building to someone else's design, was folded into AQAP 2110 when Edition D superseded it in 2016.
AQAP 2210 doesn't stand alone. It adds software-specific quality requirements on top of AQAP 2110.
AQAP 2131 covers final inspection and test, for contracts whose scope is verifying conformity rather than designing or producing.
For anyone producing NATO documentation, AQAP 2110 is almost always the reference, because design, development, and production are the requirements that flow down the chain.
How AQAP 2110 reaches a translation vendor
AQAP requirements don't stop at the prime. Section 5.4.6.1 of the standard tells the supplier to flow down the applicable requirements, including the relevant AQAPs, to external providers, and to put one line in every purchasing document: that all requirements may be subject to GQA.
A translation vendor handling a technical manual, a bid file submitted under Directive 2009/81/EC, or a maintenance procedure sits inside that chain. Those tenders often surface only in a national language, which is a problem worth solving before the bid is even written. If your prime's contract carries AQAP 2110, the traceability, configuration control, and GQA-access expectations reach your language partner too. An unvetted freelancer or a shared consumer AI tool won't meet them.
That baseline is what we built AD VERBUM's defense workflow around. A translation partner inside a NATO supply chain has to show four things:
Version traceability, so a change to a source file is carried through and recorded downstream, matching the configuration-management discipline AQAP 2110 expects.
A certified translation process, which means ISO 17100 with qualified linguists and an independent revision step, not a single pass.
Information security that keeps controlled technical data inside audited, EU-hosted systems, which is where our ISO 27001 certification applies.
Linguist nationality vetting, because handing controlled technical data to the wrong person can count as technical assistance under EU Dual-Use Regulation 2021/821 Article 2.
We hold AQAP 2110 certification alongside ISO 17100 and ISO 27001, so the quality and security record a government representative might ask for already exists. We set out how we compare against other providers on these exact criteria in our look at the translation companies that qualify for NATO AQAP 2110 work. For a prime writing an AQAP flow-down clause, that's the difference between naming a vendor and inheriting an audit gap.
Our defense translation services
Our translation services for regulated sectors run on ISO 27001 and ISO 42001 certified, EU-hosted infrastructure, with no reliance on public cloud tooling for core processing. Every project runs through our AI+HUMAN hybrid workflow: we ingest client Translation Memories and Term Bases first, our proprietary LLM-based LangOps System generates output constrained by client terminology on client-tuned open-weight models, and our certified subject-matter experts review for technical accuracy and regulatory compliance. Our QA is aligned to ISO 17100 and ISO 18587, with sector-specific requirements such as AQAP 2110 quality assurance and Regulation 2021/821 controlled-data handling applied where relevant. We serve Life Sciences, Legal, Finance, Defense, and Manufacturing clients across 150+ languages with 3,500+ subject-matter linguists. For teams managing audit-sensitive content, contact us to discuss your security and compliance requirements directly.
FAQ
What is AQAP 2110?
AQAP 2110 is NATO's quality assurance requirement for design, development, and production. It contains all of ISO 9001:2015 plus NATO-specific requirements such as configuration management, risk management, and Government Quality Assurance. The current version is Edition D, Version 1, published in June 2016 and recorded in STANAG 4107.
Is AQAP 2110 the same as ISO 9001?
No. AQAP 2110 includes every ISO 9001:2015 requirement and adds configuration management under ACMP 2100, risk management under ISO 31000, product dependability, and government inspection rights. A supplier can hold ISO 9001 without meeting AQAP 2110.
Can you get an AQAP 2110 certificate?
You can hold a third-party certificate that your quality management system meets AQAP 2110, and AD VERBUM holds one through Bureau Veritas. Conformity on a specific NATO contract is still demonstrated to the acquiring government through Government Quality Assurance, not through a certificate alone.
What is the difference between AQAP 2110, 2210, and 2131?
AQAP 2110 covers design, development, and production. AQAP 2210 adds software-specific requirements on top of it, and AQAP 2131 covers final inspection and test. The old production-only AQAP 2120 was folded into AQAP 2110 when Edition D took effect in 2016.
Does AQAP 2110 apply to translation vendors?
Yes, through flow-down. Section 5.4.6.1 requires a supplier to pass applicable AQAP requirements to external providers. A translation vendor producing NATO documentation inherits the same traceability, configuration-control, and GQA-access expectations as the prime.
How does AQAP 2110 relate to controlled defense data?
Technical files shared for translation can be controlled under EU Dual-Use Regulation 2021/821 Article 2 on technical assistance. AQAP 2110 traceability, paired with ISO 27001 security and linguist nationality vetting, gives a defensible posture that a plain non-disclosure agreement cannot.