Platform
Modules
By sector
By sector
By standard
Blog
News
Events
AJP-4.3
NATO commanders and staffs planning host-nation support, and the sending and host nations named in it
AJP-4.3 is NATO doctrine giving commanders and staffs a common framework to plan, arrange and execute host-nation support, agreed to by nations under STANAG 2234.
AJP-4.3 is NATO's Allied Joint Publication on host-nation support (HNS): the civil and military assistance a host nation gives to NATO or other forces and NATO organizations that are located on, operating on or from, or transiting through its territory. Nations record their agreement to use it in STANAG 2234, and AJP-4.3 builds on the principles set out in AJP-4, Allied Joint Doctrine for Logistics. Its purpose is to give joint NATO commanders and their staffs a common framework for planning, coordinating and executing HNS, and it is written primarily for them; NATO members, partners and non-NATO entities are told the doctrine is also instructive as a reference, which is a weaker status than the guidance NATO commanders and staffs receive. The current edition is Edition A, Version 1, promulgated 27 April 2021, which superseded AJP-4.5, Edition B, Version 1 - HNS doctrine previously sat under a different Allied Joint Publication number.
Sending nations give a point of contact, take part in planning with subject-matter experts, submit a concept of requirements and a signed statement of requirements, and reimburse the host nation for the support they receive. The host nation, "within its means and when possible", responds to the formal HNS request, gives NATO planners early visibility of its capabilities through capability catalogues, facilitates site surveys, and retains control of its own resources unless it explicitly agrees to release that control to the NATO commander. The NATO commander sits across the whole process: negotiating the memorandum of understanding and technical arrangement, coordinating the planning conferences, and deciding what is eligible for NATO common funding.
None of this works without groundwork that AJP-4.3 assumes rather than creates. HNS arrangements have to sit consistently with the NATO or Partnership for Peace status-of-forces agreement, the Paris Protocol, and any further protocols in force, since those instruments give NATO forces and headquarters their legal status in the first place. Where no SOFA exists, a HNS arrangement can carry limited, preliminary provisions on the status of forces instead, but that is a fallback, not the normal route.
HNS planning sits inside the wider operations planning process and produces a defined sequence of documents: a host-nation support request, a memorandum of understanding (MoU), a technical arrangement (TA), a note of accession or statement of intent, final financial arrangements, a joint implementation arrangement (JIA), capability catalogues, a concept of requirements and statements of requirements (SORs).
This is the part worth reading carefully, because the documents do not all carry the same weight. Host-nation support arrangements in general, the MoU included, are "non-binding arrangements that translate treaties and policies into agreed terms, conditions and procedures", and the MoU template itself states plainly that it "does not allocate funding nor represent an obligation on the part of SNs or the NATO commander." What actually commits resources is the final financial arrangement, which AJP-4.3 calls "contractually binding", and the joint implementation arrangement, which the document's own lexicon says is "considered as the only legally binding document" in NATO's HNS planning process (a final, signed statement of requirements can do the same job instead of a JIA). Treating a signed MoU as a guarantee that support is arranged and paid for gets the sequence the wrong way round.
Financial principles run through the whole sequence: reimbursement should be agreed before forces deploy wherever that is possible, a host nation "should not profit from NATO military activities", and custom limits it to claiming "the incremental cost of the service provided", not the full commercial cost. Where support is procured commercially rather than provided directly by the host nation, the MoU template says it is obtained "via a competitive bidding process from the lowest compliant bidder".
Once an activity is under way, HNS is coordinated through a host-nation support joint steering committee, co-chaired by the NATO commander and the host nation, and, where the scale of the activity calls for it, coordination cells working at the tactical level. AJP-4.3 asks for HNS status to be reported through the logistic reporting system, for performance to be tracked against measures of performance and effectiveness, and for lessons to feed the NATO Lessons Learned Portal.
Nations are invited to keep capability catalogues current, refreshed annually, recording geolocations and main supply routes. AJP-4.3 is explicit about their limits: the catalogues are "neither legally binding, nor real time, nor a collection of supplies and services." What a nation can actually deliver is only confirmed through the statement-of-requirements process, not by appearing in a catalogue - a distinction planners relying on catalogue data alone can miss.
Crossing into a host nation's territory still needs a diplomatic clearance and a movement credit, even where a status of forces agreement or transit treaty has already settled the legal status of the force. AJP-4.3 treats HNS planning and movement planning as work that has to be synchronised, not run as separate, sequential steps, because the availability of HNS directly shapes what a movement plan can actually promise.
AJP-4.3 does not set a retention period for HNS records, and it does not describe any certification, accreditation or third-party assessment against itself. Reservations recorded against this edition, by Belgium, France, Croatia and the United States, are a reminder that nations can and do qualify how far they accept even a ratified STANAG's provisions.
AJP-4.3 binds nations, not companies, and nothing here suggests otherwise. Where a company's work actually touches it is narrow: a commercially procured support contract sitting underneath a nation's HNS arrangements, awarded through competitive bidding, or work on a base whose host-nation-support arrangements set what can be accessed, invoiced, or has to be handed back at redeployment. For that kind of work, ComplyTrain gives you a place to hold the procedures a contract like that actually asks for - site-survey records, the delivery and invoicing evidence that supports reimbursement, and the host-nation regulations on health, safety, security, environment and agriculture that a memorandum of understanding says should be supplied in English - version them, and keep the trail a financial reviewer or a customer would ask to see.
ComplyTrain does not negotiate a memorandum of understanding, a technical arrangement, or a statement of requirements, and it does not stand in for the government-to-government legal and diplomatic process AJP-4.3 describes. That happens between nations and NATO commanders, not in software.
Which arrangements and which standards actually apply to a given activity is set by the contract and the customer's quality clause, not by this page. See the standards explorer for what sits alongside AJP-4.3, and talk to us about the evidence trail behind it.
Tell us how you need to work with AJP-4.3 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. AJP-4.3 binds nations, which agree to use it by ratifying STANAG 2234, and a nation can ratify with reservations. A company meets it only indirectly, where a national HNS arrangement or a support contract built on top of one requires something of it.
The memorandum of understanding is the overarching, non-binding agreement that sets out policy and principles for HNS between a host nation and NATO's strategic commands. The technical arrangement amplifies it for a specific military activity, detailing how the host nation will actually provide the support. Neither is the document that creates a binding financial commitment; that role falls to the final financial arrangement or the joint implementation arrangement.
No. AJP-4.3 states that the MoU "does not allocate funding nor represent an obligation on the part of SNs or the NATO commander." The commitment comes later, through a final financial arrangement or a joint implementation arrangement negotiated for the specific activity.
Edition A, Version 1, promulgated 27 April 2021. It superseded AJP-4.5, Edition B, Version 1, which was destroyed under local document-destruction procedure once the new edition took effect.
No such certification exists. AJP-4.3 names no certification body, notified body or accredited scheme; it is planning and coordination doctrine for nations and NATO commanders, not a standard a company is assessed against.
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.