Platform
Modules
By sector
By sector
By standard
Blog
News
Events
MACP-01
Government negotiators and programme officers drafting an MOU or PMOU for a NATO co-operative armaments programme
NATO guidance and a 30-item checklist for negotiating the Memoranda of Understanding that set up a co-operative armaments programme between NATO nations.
MACP-01 (NATO prints it MACP-1), an Allied Acquisition Publication, is guidance and a checklist for the government officials who negotiate a Memorandum of Understanding (MOU) or Programme MOU (PMOU) that sets up a joint armaments programme between NATO nations. It is not addressed to industry. It is addressed to the negotiators: "Memoranda of Understanding (MOUs) are formal written arrangements between governments (or between governments and NATO Agencies) setting forth the conditions under which they intend to co-operate in given areas." Volume I consolidates and supersedes three earlier AACP-1 documents into one publication, and nations record their recommendation to use it through STANREC 4792, a recommendation rather than a ratified commitment. The checklist itself says plainly that its own items "are not mandatory".
That distinction matters because an MOU produced with this guidance is a binding agreement between the signing governments, but MACP-01 imposes nothing on a supplier directly. A supplier only meets what an MOU decided once a Contract implements it: the document notes that its own provisions on disclosure and use of technical information "will in most cases be implemented in Contracts to be let under the MOU". Reading MACP-01 tells you where a defence contract's clauses on intellectual property, quality assurance, security and third-party sales actually come from, not what your own compliance obligations are.
Traditional NATO practice negotiated an MOU phase by phase, which "has often led to time-consuming negotiations when it appeared during the programme that Participants had fundamentally differing assumptions as to how collaboration should have been performed". The Programme MOU concept answers this: it is signed at the earliest suitable opportunity and normally starts with the Feasibility Study phase, covering the programme "at least up to and including the Production phase". A PMOU does not remove the need to negotiate each phase's detail; it only makes renegotiating the basic overall arrangements unnecessary each time.
Section III of MACP-01 lists everything an MOU or PMOU should consider: title page and classification, definitions, introduction, objectives and scope, government organisation, industrial organisation, report requirements, contractual relationship, work-sharing, cost-sharing, financial matters, taxes, contractual arrangements, transfers and exchanges, intellectual property, inspection and quality assurance, standardization/codification/configuration control, management of assets, insurance and indemnification, logistic support, sales and disposals, security and exchange of personnel, release of information and publicity, admission of additional participants, withdrawal and termination, settlement of disputes, amendment, the signature page, and annexes. Guidance and sample legal text follow for 26 of these in turn, and the drafter chooses only what applies to the programme in front of them: negotiators are told the items "are not all necessarily applicable" and can be addressed in a different order than the checklist itself.
A programme can be run through a lead-nation model, an integrated model (an International Programme Office reporting to a Joint Steering Committee), or a fully decentralised model where national structures are left untouched. Contracts can be awarded centrally, by a Contracting Participant acting for everyone or by a NATO Agency, or on a decentralised basis where each Participant contracts for its own work-share. Work is allocated on criteria such as technical merit, cost, and encouragement of multinational industrial collaboration, and a work-share plan is normally approved by the Participants before it is implemented. Cost-sharing can follow equal shares, shares related to industrial benefit or output, or another agreed key.
This is the longest section of the document by a wide margin. It works through ownership of Foreground and Background Information, the rights of use Participants secure for Programme, Defence or Government Purposes, protection of information disclosed in confidence, licensing, and how inventions made under the MOU are handled. Before signing, Participants have to check that "their national disclosure policies and regulations allow disclosure of the [Technical] Information necessary for the execution of the MOU", because the resulting rights and obligations get written straight into the Contracts let under the MOU.
Section 13's sample provisions give two options. Where NATO arrangements apply, Participants implement STANAG 4107 (Mutual Acceptance of Government Quality Assurance) directly, and national quality assurance services follow whichever AQAP that STANAG 4108 assigns to the Contractor's work. Where NATO arrangements do not apply, quality control simply follows the host Participant's own national laws and procedures. MACP-01 does not itself specify which AQAP applies, what a quality manual has to contain, or how audits are scheduled; those decisions sit inside the STANAGs and AQAPs it points to, or inside the Contract the MOU produces. Similarly, the document does not set cost-sharing formulas, security classification levels, or export-licence policy; it only tells negotiators what questions each of those areas needs answered.
Withdrawal provisions are meant to be adapted to each phase of the programme, from Feasibility Study through Design and Development, Production and In-service Support. Disputes are resolved by consultation between the Participants rather than referred to a tribunal or third party, a principle the document repeats from its opening considerations. Public releases of programme information, such as notices of a Contract award, need co-ordinated approval so one Participant's announcement does not embarrass another.
MACP-01 is an operational and process document for government negotiators, not a management-system standard a supplier implements. A supplier does not draft the MOU; its own government does. What reaches a supplier is downstream: once a Contract carries the MOU's provisions on quality assurance, disclosure of technical information, security and third-party sales, those Contract clauses become the actual set of things to evidence.
ComplyTrain is a place to hold that evidence: quality assurance records under whichever AQAP the programme names, controlled handling of Foreground and Background Information disclosures with an audit trail of who saw what, and training records for staff who handle classified programme information. It works the same way it does for any other contractual requirement, documented procedures, controlled documents, and a record an auditing nation can be shown on request.
It does not negotiate the MOU or PMOU, decide work-share or cost-share formulas, or determine which AQAP or security classification a given programme requires. Those decisions belong to the participating governments and the programme's own management structure, not to a vendor. Which requirements apply to your contract is set by the MOU and the Contract that implements it. If you are preparing to bid into a NATO co-operative armaments programme, the standards explorer shows what else sits alongside MACP-01, including STANAG 4107, and our team is glad to talk through how you would evidence the clauses your contract actually contains.
Tell us how you need to work with MACP-01 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.
No. Nations record only a recommendation to use it, through STANREC 4792, rather than a ratified commitment through a STANAG. The document's own checklist says its items "are not mandatory nor, depending on the programme, are they all necessarily applicable", and negotiators are free to adapt or omit sections.
MACP-01 is written for the government officials negotiating an MOU or PMOU between NATO nations, not for suppliers. It reaches a supplier only once a government writes the resulting provisions into a Contract; what applies to a given contract is set by that Contract and the customer's quality clause, not by MACP-01 directly.
An MOU can be negotiated for a single phase of a programme. A PMOU is signed earlier, normally from the Feasibility Study phase, and sets out the principles for the programme's whole life, at least through Production, so that later phases do not each require a fresh negotiation of the basic arrangements.
Not directly. Its sample provisions have Participants implement STANAG 4107 (Mutual Acceptance of Government Quality Assurance) where NATO arrangements apply, with the specific AQAP assigned under STANAG 4108. Where NATO arrangements do not apply, quality control follows the host nation's own laws and procedures instead.
Edition B, Version 1, promulgated in February 2017. It consolidates and supersedes three earlier AACP-1 Part I documents (versions from 1989, 1997 and 1998) into a single publication.
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.
Medical device manufacturers operate under more regulatory pressure than almost any other sector outside pharmaceuticals. The rules govern how you design a device, how you make it, how you track it after it ships, and how you respond when something goes wrong.
Learn how EU dual-use export controls apply to encryption, sensors, and software, how classification works under Annex I, and why sending source code by email can count as an export.
A practical way to turn in-your-head risk management into a register that survives staff turnover and answers the risk questions now showing up in tenders.