Charles Schultz, a quality assurance specialist at Defense Contract Management Agency Great Lakes in Illinois, whose check prevented non-conforming hinge pins reaching Tinker Air Force Base. DCMA is the organisation named in AQAP-4107-SRD.1 as the United States Department of Defense Central Control Point for incoming requests. U.S. Department of Defense photo by Cheryl Jamieson, Defense Contract Management Agency (public domain, via DVIDS). Illustrative: appearance does not imply endorsement.

Eight Nations Changed Their GQA Contact Details in One Version, and a Misrouted Request Does Not Bounce

AQAP-4107-SRD.1 Edition A Version 12, promulgated on 16 April 2026, updated the government quality assurance contact details of eight NATO nations: Belgium, Canada, Croatia, the Czech Republic, Hungary, Latvia, Türkiye and the United States. It is the routing table on which the whole mutual GQA mechanism depends, and only one of those eight changes touched an email address.

Technical Summary

The NATO Standardization Agreement (STANAG) 4107 Edition 14, promulgated on 4 June 2025 under the Conference of National Armaments Directors (CNAD) Life Cycle Management Group (AC/327) Working Group 2 on Quality, superseded Edition 13 of 7 November 2023. It binds participating nations to nine Allied Quality Assurance Publications (AQAP): AQAP-2000 Edition D, AQAP-2070 Edition C, AQAP-2105 Edition C, AQAP-2110 Edition D, AQAP-2131 Edition C, AQAP-2190 Edition A, AQAP-2210 Edition B, AQAP-2310 Edition B and AQAP-4107 Edition B. Among the things implementation requires of a nation, the agreement lists one that sounds administrative and is not: “appoint a GQA focal point”.

AQAP-4107 Edition B Version 1, promulgated the same day, sets out what that focal point is for. A request for Government Quality Assurance (GQA) passes from the appropriate National Authority in the acquiring country, termed the delegator, to the appropriate National Authority in the supplying country, termed the delegatee. Paragraph 2.2.b states that requests shall be forwarded to the delegatee, “a list of which is contained in the Standard Related Document (SRD.1) to this AQAP-4107”. That single clause is what makes SRD.1 operative rather than informative. It is not background reading attached to the agreement. It is the address to which every cross-border Request for Government Quality Assurance (RGQA) is sent.

AQAP-4107-SRD.1 Edition A Version 12 was promulgated on 16 April 2026 and supersedes Version 11. Its Letter of Promulgation itemises the changes by nation, reproduced in the table below. Table 1 of the document lists 31 of NATO’s 32 members, Iceland being absent, and three of those entries carry no contact data at all: Albania and North Macedonia are recorded as “Ratification - No response” and Montenegro as “Future Implementation”. Twenty-eight allies are therefore routable through the table as it currently stands. A second table carries partner nation contacts, with an explicit caveat that their presence “shall not be interpreted as authority for mutual GQA involving partner nations”.

Seven of the eight Version 12 changes were to organisation names, postal addresses, telephone numbers and a withdrawn fax line. Only the United States changed an email address. The other seven are the class of change that produces no delivery failure notice at the sender. ISC assessment, from AQAP-4107-SRD.1 Edition A Version 12, 16 April 2026

Analysis of Effects

Set the revision rate of the contact table against the revision rate of the requirements it serves. AQAP-2110, the contractual workhorse of the suite, has stood at Edition D Version 1 since 24 June 2016 and remains in force unamended, a span of nine years and ten months to the date of Version 12. The sibling standards related document, AQAP-4107-SRD.2 AQAP Selection Guidance, has stood at Edition A Version 1 since 8 November 2018, seven years and five months. The parent agreement moved once in that window, from Edition 13 in November 2023 to Edition 14 in June 2025. Against those, SRD.1 has reached its twelfth version, and commercial standards catalogues record Version 9 as a 2023 issue, placing at least three revisions in roughly three years. Promulgation dates for Versions 1 to 11 were not established for this article, so the cadence is characterised rather than measured. The direction of the comparison is not in doubt: the address book turns over several times faster than anything it points at.

That is by design, and the design is defensible. Earlier practice kept the routing list inside the agreement, and the migration away from it is documented rather than inferred. AQAP-2070 Edition B Version 3 instructed the delegator to transmit the RGQA “to the appropriate National Authorities or focal points (reference STANAG 4107 Annex A)”. The current AQAP-2070 Edition C Version 1, promulgated on 4 June 2025 alongside the parent agreement, carries the same sentence at section 8.5 with the pointer changed: transmission is now “to the appropriate National Authorities or focal points (reference AQAP-4107-SRD.1)”. Lifting the list out of a ratified STANAG annex and into a separately numbered standards related document means a nation can correct its own address without triggering a ratification round across the alliance. The cost of the efficiency is that the routing data now moves on a cycle wholly disconnected from the documents a procurement office actually keeps on file. A quality manager who downloaded the AQAP suite when AQAP-2110 Edition D was issued would still hold the current contractual requirement today. The contact list saved in the same folder would be eleven versions behind.

The dependency is not confined to the narrative text. The RGQA form at Annex B of AQAP-2070 Edition C Version 1 addresses itself out of the table directly. Its recipient field reads: “To: Delegatee: (Appropriate National Authority or Focal Point Listed in AQAP-4107-SRD.1)”. Whoever fills in that box is copying an address from a standards related document into the instrument that carries the request, which is as close to a hard dependency as a paper process gets.

There is a matching asymmetry in formal standing. SRD.2 states its own position at Chapter 1 without hedging: “This publication is not a contractual document; therefore, its content has no legal or contractual status, nor does it supersede, add to or cancel any of the AQAP requirements.” SRD.1 carries no equivalent declaration only because it carries almost no prose at all, being a table and a covering letter, but it belongs to the same class of publication. The document that determines whether a request for government quality assurance physically reaches the right desk therefore has the weakest formal status in the stack and the highest revision rate in it.

What turns a stale entry from untidy into consequential is the way the failure presents itself. AQAP-2070 Edition C Version 1, at section 9.1, provides that “The focal point shall acknowledge receipt of the RGQA. The acknowledgement should be sent as soon as possible, but not later than 5 working days. The acknowledgement signifies that the RGQA has been received.” Read the modal verbs carefully. The obligation to acknowledge is mandatory. The five working day figure is a recommendation, not a limit, and the standard sets out no point at which a missing acknowledgement becomes a defect. A delegator whose request went to a superseded address therefore sees precisely what a delegator whose request reached a busy delegatee sees, which is nothing yet. The wording is unchanged from the previous edition, so this is settled practice rather than a drafting oversight in a new text.

The mechanism built to surface this class of problem is routed through the same table. AQAP-2070 Edition C Version 1 at section 4.4 encourages the delegatee to give feedback to “the delegating nation’s GQA focal point on the quality of the RGQA and RIAC” and the delegator to give feedback to “the delegatee nation’s GQA focal point on the quality of services provided”, and it lists “timely RGQA acknowledgment” among the recommended minimum performance indicators for the process as a whole. Where an entry has gone stale, the instrument for reporting the problem is addressed using the entry that caused it.

The table holds a second trap that has nothing to do with staleness. Seven entries carry a distinct “Forward Requests for GQA to” address in addition to the National Quality Assurance Authority: Belgium, Canada, France, Italy, Türkiye, the United Kingdom and the United States. The United States entry runs to three stages, naming the National Quality Assurance Authority in the Office of the Under Secretary of Defense for Acquisition and Sustainment, then the Department of Defense Central Control Point at the Defense Contract Management Agency at Fort Lee, then a separate DCMA International Focal Point for the response. The United Kingdom entry gives a quality and configuration management policy helpline first and a Quality Assurance Field Force RGQA receipt point second. Italy removes the ambiguity by stating in the table itself that “All incoming RGQAs have to be sent to” one specific mailbox. A request addressed to the first line of one of those entries lands on a policy function rather than a receipt point, where it depends on a person to forward it rather than on a process to acknowledge it.

Two Table 1 entries name a specific officer rather than a post. Belgium names a quality assurance representative adjunct and Luxembourg a branch head, each with a functional mailbox listed alongside as a copy address. Belgium’s named contact is one of the three fields Version 12 changed. In Table 2, which covers partner nations and confers no mutual GQA authority, Austria’s entry consists of two named officials and their individual mailboxes with no functional alternative at all. Personal mailboxes follow postings. Functional mailboxes follow roles, and roles outlast the people filling them.

Personnel and Process Considerations

For quality assurance and procurement staff the practical actions are narrow and cheap. Check the version rather than trusting the file: the Letter of Promulgation on the front of every SRD.1 issue names both the version in hand and the version it supersedes, so a local copy can be checked against the current one in a single step, and NATO publishes the document at no charge through the NATO Standardization Document Database, stating in the promulgation letter that its standardization documents are not intended to be sold. Address the receipt point rather than the authority wherever an entry distinguishes the two. Prefer the functional mailbox to the named individual where both are given. Treat silence at five working days as a routing hypothesis before treating it as a capacity one, and re-check the entry before chasing the delegatee. Do not depend on fax: Latvia’s sole Version 12 change was to remove its fax number, and a transmission to a withdrawn line does not reliably produce a failure indication at the sender.

One documentary detail is worth recording for anyone version-checking a local copy. The Letter of Promulgation for Version 12 names “Edition A, Version 11” in its first paragraph, then Version 12 in its second and third. The document header, the running footer on every page and the file designator all read Version 12, so the version in hand is not in question. The discrepancy is confined to one line of the covering letter, and it is itself a modest artefact of a document that is revised often and quickly.

Data Gaps

Promulgation dates for Versions 1 through 11 were not established. Only Version 9, recorded as a 2023 issue by commercial standards catalogues, and Version 12, taken from the primary document, are dated here, so the revision cadence is characterised rather than measured. SRD.1 records what changed in the current version but not when each unchanged entry was last revised, so the age of any individual national entry cannot be read from the document. No incident data is published on misrouted requests: the failure mode set out here is structural and inferred from the documents, and whether it has occurred, or at what rate, is not established in open source. Whether Albania, Montenegro and North Macedonia have appointed focal points that are simply unpublished, as distinct from not appointed, is not stated.

Corrections & updates welcome. If you hold open-source data that refines or corrects any parameter in this article, please contact [email protected] citing the specific claim and your source. Verified corrections will be incorporated and credited in the revision history. AI-assisted technical assessment based on open-source material. Not a formal intelligence product.