Platform
Modules
By sector
By sector
By standard
Blog
News
Events
STANAG
Defence suppliers whose contract or tender flows down a STANAG requirement.
A STANAG is a NATO Standardization Agreement: the terms under which member nations agree to a common military or technical procedure, or a common piece of equipment. Nations ratify and implement them, and the requirement reaches a supplier through the contract.
STANAG stands for Standardization Agreement. It sets out the processes, procedures, terms and conditions under which NATO member nations agree to a common military or technical procedure, or to common equipment. The point is interoperability: an aircraft, a data link or an imagery feed from one nation has to work with another nation's systems.
A STANAG is agreed between nations, not issued to companies. Each member state ratifies the agreement and then implements it within its own armed forces. What reaches you as a supplier is the implementation: a national requirement written into a contract or a tender.
Every STANAG is maintained under AAP-03, NATO's directive for the production, maintenance and management of its standardization documents. It sets how nations report that they have ratified and implemented an agreement, and when the agreement is next reviewed, which is why every STANAG cover cites it. Because it governs how the agreement is kept rather than what the agreement requires, our pages do not list it among a standard’s references.
STANAGs carry four-digit numbers, allocated in broad blocks by the body responsible for the subject area: 2000 and 2500 for army and joint-service matters, 3000 and 7000 for air, 4000 and 5000 for armaments and for communications and information systems, 6000 for the International Military Staff. The number is an address, not a difficulty rating: a low number is not an easier requirement.
The three covered here are all in the 4000 series, which is where unmanned systems, imagery and armaments interoperability sit.
Not in the way ISO 9001 certification works, and the distinction is worth getting right because the two are often confused. There is no accredited body that audits a company and issues it a STANAG certificate. A STANAG is ratified by nations and implemented nationally, and you meet it because a contract says so.
That said, a particular STANAG can sit underneath a national approval that very much is a certificate. STANAG 4671 is the clearest example: the airworthiness requirements in it are what a military airworthiness authority assesses a type certification case against. So the honest answer is that you are not certified to a STANAG, but you may hold an approval that a STANAG defines the basis for.
The two families are joined at the top. STANAG 4107 is the agreement that records nations' acceptance of mutual government quality assurance and their agreement to use the Allied Quality Assurance Publications, covering AQAP 2000, 2009, 2070, 2105, 2110, 2131, 2210 and 2310 among others. So when a contract cites AQAP 2110, the reason every NATO nation recognises it is a STANAG.
In practice the split is simple. The AQAPs govern how your quality is assured. The technical STANAGs govern what your product must do to work alongside everyone else's.
ComplyTrain is not limited to the standards written up on this site. The product is built around a requirement tree, and a requirement tree can be built for any standard, agreement or contractual specification that has requirements in it. The pages here are the ones we have documented so far, not the boundary of what the system handles.
We add standards on request, and the list grows steadily. If the STANAG or standard your contract cites is not here, tell us which one you need and we will tell you what supporting it in your workspace involves.
Most STANAGs are not published at all. STANAGs you cannot download explains why, how organisations obtain them, and lists every one that is not released or is classified.
A technical STANAG lands on you as a long list of requirements that somebody will later ask you to evidence, one by one. That is the same shape of problem whichever agreement it is:
Because the requirement tree is the product's core rather than a per-standard feature, a standard we have not written a page for is a content job, not an engineering one. Ask, and it can be added.
ComplyTrain holds no NATO qualification and does not need one: it is the system you run your own obligations in and hold the evidence for.
Tell us how you need to work with STANAG 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.
Standardization Agreement. It records the terms under which NATO member nations agree to a common military or technical procedure, or to common equipment, so that one nation's systems work with another's.
Not in the ISO 9001 sense: no accredited body audits a company and issues a STANAG certificate. Nations ratify a STANAG and implement it, and it reaches you as a contractual requirement. A specific STANAG can still underpin a national approval that is a certificate - STANAG 4671 is the basis on which a military airworthiness authority assesses a type certification case.
With four digits, allocated in blocks by subject area: roughly 2000 and 2500 for army and joint service, 3000 and 7000 for air, 4000 and 5000 for armaments and for communications and information systems, and 6000 for the International Military Staff. The number identifies the subject, not the difficulty.
The AQAPs govern how your quality is assured; the technical STANAGs govern what your product must do to interoperate. They are formally linked: STANAG 4107 is the agreement recording nations' acceptance of mutual government quality assurance and their agreement to use the AQAPs.
Yes. The pages on this site are the standards documented so far, not the limit of what the product handles - ComplyTrain is built around a requirement tree, and one can be built for any standard, agreement or contractual specification. We add standards on request. Tell us which one your contract cites and we will explain what supporting it in your workspace involves.
Implementation
A technical agreement is met requirement by requirement, and demonstrated the same way.
The national implementation is what binds you, and it can add to or constrain the agreement. Work from what the contract actually cites.
Every requirement as a tracked item with its criticality, so the set is countable and nothing sits in a paragraph nobody re-reads.
Test records, analyses and declarations belong on the requirement they satisfy, at the time they are made rather than in the week before a review.
The matrix is what an assessor or a prime asks for. Generated from the tree it is always true; maintained by hand it is true on the day it was written.
A standard usually arrives as a contract condition rather than a project anyone planned for, and often at a company with no quality manager. Software is half the answer. Skylen's consultants are the other half, and because they build on ComplyTrain from day one you keep a live system your team owns rather than a binder and a departed consultant.
A clause-by-clause read of where you stand against the standard your contract cites, turned into a prioritised plan you could act on with us or alone.
What an assessment coversOur consultants build the system with your team - procedures, document control, the records you need to keep and the review cadence - and prepare you for the certification audit.
How an engagement worksWe run and maintain the quality system for you, so a small team can reach and hold a standard without hiring a quality manager.
What full-service meansThe primary sources behind this page. Where a standard is quoted here, the publisher's own page is the authority.
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.
A 90-day plan for the smallest defence suppliers: let the tender set your scope, document what you already do, fix the security basics primes check, and keep the system small enough for two people to maintain.
Learn how to qualify, approve and monitor sub-suppliers, flow down requirements through purchase orders, and keep the records an auditor will ask to see under ISO 9001 clause 8.4 and AQAP.
Learn how to run an ISO 9001 Clause 9.3 management review that turns evidence into decisions, with the right inputs, actionable outputs, and a cadence that fits your risks.