Platform
Modules
By sector
By sector
By standard
Blog
News
Events
ATP-3.4.1.2
Naval and maritime force commanders and staffs planning and conducting multinational humanitarian assistance and disaster relief operations
NATO tactical doctrine for how maritime forces plan and conduct multinational humanitarian assistance and disaster relief operations, at sea and ashore.
ATP-3.4.1.2, Multinational Maritime Support of Humanitarian Operations, is a NATO Allied Tactical Publication (ATP): the technical, working-level doctrine that sits beneath the STANAG covering it, STANAG 1448. It sets out how maritime forces plan and conduct humanitarian assistance and disaster relief (HA/DR) operations, both at sea and once ashore, and it is currently at Edition B, Version 1 (September 2015), which "supersedes ATP-03.4.1.2(A)(1)" and was itself "derived from and replaces EXTAC 1011," drawing further on the UN refugee agency's Handbook for Emergencies and the Oslo and MCDA guidelines on the use of military and civil defence assets in disaster relief.
The document is explicit about who it is for: it "is designed for use by NATO nations when conducting humanitarian assistance/disaster relief (HA/DR) operations in conjunction with other NATO nations, non-NATO nations, or a mixed coalition of nations." In practice that means the naval commander and the maritime force's own staff sections - operations, logistics, legal, medical, engineering, public affairs, civil affairs - who plan and run the mission, plus the advance party and liaison officers drawn from those forces. It does not address a supplier, a manufacturer, or a certifying body, and it creates no obligation for a company directly: like any Allied Tactical Publication, it binds through the STANAG that nations ratify, and this edition carries recorded national reservations from Poland, Romania, Turkey and the United States. A supplier meets it, if at all, only when a tasking order or contract supporting a maritime force's HA/DR mission invokes it.
Two opening chapters set the frame. Chapter 1 defines humanitarian operation and humanitarian assistance in NATO's own terms (from AAP-6) and disaster relief in ATP-3.4.1.2's own terms, names four types of operation that can occur together - security programmes, disaster relief, dislocated-civilian support, and civil support - and requires a commander to distinguish a permissive environment from an uncertain or hostile one before commencing a mission, since the two demand different force postures. Chapter 2 sets out eleven enduring principles for employing forces: objective, unity of effort, perseverance, security, restraint, legitimacy, responsiveness, simplicity, flexibility, economy, and neutrality.
Chapter 3 covers civil involvement: the "response triad" of political, military and humanitarian elements; embassy and country-team roles; the distinct legal character of international organisations, NGOs and PVOs; the UN agencies most often encountered (UNHCR, OCHA, UNICEF); the Red Cross/Red Crescent Movement; and the International Organization for Migration. It describes the Civil-Military Operations Center (CMOC) as the coordination point through which "all NGOs/PVOs/IOs shall realize that their only entry into the system is through the CMOC," and requires SecDef/MOD-level or higher approval before releasing rules of engagement to NGOs, PVOs, IOs or host-nation personnel.
Chapter 4 covers sea-based operations: identifying and surveying vessels carrying migrants, survivors or displaced persons at sea; embarkation planning and marshalling areas; the separate responsibilities of the amphibious task force commander, the landing force commander, and individual ship commanding officers; converting a well deck into billeting; and shipboard security, food service, hygiene, medical care, safety and morale once people are aboard. Weapons are never permitted aboard for embarked recipients - the document is direct on this: "Do not permit weapons to be brought or retained aboard ship."
Chapter 5 covers operations ashore: planning, execution (coordinating dozens of NGOs/PVOs/IOs at once, subdividing the area of operations into humanitarian relief sectors), mission transition and termination, intelligence, communications, public affairs, legal affairs, health service support, engineering, and security. On security specifically, the document treats military force, even for protecting NGOs and PVOs, as a last resort, used "only where a capability gap exists that civilian government agencies and international organizations are not able to fill."
Annex A carries operational and logistic planning: the commander's intent, synchronization and execution matrices, and a set of named logistics-planning equations for food, warehouse space, forklifts, and long- and short-haul trucking and fuel, all keyed to a population estimate expressed in metric tons per 30-day "month of supply." Population estimation itself is a two-step process of data collection and analysis, refined weekly once an operation starts.
Annex B covers liaison officer duties before, during and after a tour, and the CMOC's request-and-completion workflow. Annex C covers legal affairs: the international-law basis for rendering assistance and rescuing persons at sea (citing the 1958 Geneva Convention on the High Seas, the 1982 UN Convention on the Law of the Sea, and the 1974 SOLAS Convention), the definition and handling of temporary refuge, camp regulations and fraternization rules, and the legal aspects of rules of engagement and the use of force - including that riot control agents require approval "at the highest national/coalition levels."
Annex D, the most granular chapter, covers HA/DR camp considerations: shelter and billeting standards (a general-purpose medium tent, sized to the UNHCR figure of 3.5 to 5.5 m² of usable floor space per person, houses 14 to 15 people); camp layout and security, including fencing and lighting deliberately designed to "minimize the 'concentration camp' look and feel"; utilities, sanitation and construction guidance, including a 30-metre firebreak for every 300 metres of built-up area; space requirements for a 10,000-person camp (100 acres in total); equipment lists; camp administration and self-government (tent leader, block leader, camp president); a screening and processing sequence; and camp security, up to a five-level graduated use-of-force scale.
Annex E gives the document's own definitions distinguishing citizens, internally displaced persons, evacuees and refugees, and a four-step recipient-processing sequence: segregation, interviewing, identification, and medical examination. Annex F covers logistics sourcing (contracted, military, or from NGOs/PVOs/IOs and the host nation), the functional elements of combat service support, and dedicated guidance on waste management, a hazardous-material officer, and a five-step risk-assessment process.
Unusually for a NATO tactical publication, this edition carries formal, named reservations against specific paragraphs and tables: the United States disputes treating the UNHCR floor-space figure as an "absolute requirement" across the wider spectrum of humanitarian operations, and Poland and Romania each note that Table D-3's equipment list assumes US-standard items their own armed forces do not use.
There is no certification, accreditation, or third-party audit scheme against ATP-3.4.1.2, and it names no certifying body. Compliance is judged inside a commander's own chain of command, using the publication's wording conventions: "'Shall' indicates the application of a procedure is mandatory," "'Should' indicates the application of a procedure is recommended," and "'May' and 'need not' indicates the application of a procedure is optional." It is also explicit that it "is not a directive" and "does not supersede guidance issued by such commanders or higher authority" - it sits underneath, not in place of, a commander's own orders. The closest thing to an evaluation mechanism is the measures of effectiveness a commander tracks under Annex A, used to judge "the success or failure of an operation" and decide when it is "ready to be transitioned to another organization" - self-assessment, not a third party checking compliance.
ATP-3.4.1.2 defers to NATO's civil-military cooperation policies and doctrine, found in MC 411 and AJP-9, which it says "take precedence" over its own informational chapter on civil involvement, and to its companion volume, ATP-3.4.1.1, for convoy security, area presence, and separation of hostile parties, which it points to repeatedly rather than repeating. It sits beneath AJP-3.4, the wider Non-Article 5 Crisis Response Operations doctrine that HA/DR sits within, and it does not attempt to cover combat operations, maritime interdiction, or non-combatant evacuation operations happening at the same time, pointing readers to national and allied tactical documentation for those instead.
NATO publishes ATP-3.4.1.2 free of charge through the NATO Standardization Document Database. ComplyTrain does not sell it or host a copy; the NSDD listing for ATP-3.4.1.2 is the source. It is covered by STANAG 1448.
ATP-3.4.1.2 is operational doctrine, not a management-system standard: the work it describes - surveying a vessel at sea, converting a well deck into billeting, laying out and running a camp for thousands of people, screening and processing recipients - happens in the day-to-day conduct of the operation itself, not in software. What a force, or a contractor supporting one, needs to evidence is disciplined documentation of that work: the security, fraternization and camp standard operating procedures the document repeatedly calls for; training records for rules-of-engagement, use-of-force, and preventive-medicine training completed before personnel come into contact with recipients; camp inspection and mess-sampling records; and the after-action reports that feed the measures of effectiveness a commander tracks.
ComplyTrain, as a quality management and evidence system, supports exactly that kind of work in general: controlled procedures, training records, internal audits, and corrective-action tracking that a commander, an inspector-general, or a supporting nation can review. It does not survey a vessel, build or run a camp, screen or process HA/DR recipients, or make the legal, medical, or rules-of-engagement decisions the document assigns to specific officers and the chain of command - those calls stay with the naval commander and the specialist staff ATP-3.4.1.2 addresses. If your organisation needs to evidence its part of a maritime HA/DR tasking, talk to us about how the documentation and training side of that fits together, and see the standards explorer for what sits alongside ATP-3.4.1.2.
Tell us how you need to work with ATP-3.4.1.2 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.
ATP-3.4.1.2 binds through STANAG 1448, which NATO nations ratify - ratification and national implementation are separate steps, and a nation's ratification can carry reservations, as this edition's own recorded reservations from Poland, Romania, Turkey and the United States show. Whether it applies to a particular force or contractor depends on the operation order, tasking, or contract that invokes it, not on the document existing.
No. It names no certification body, notified body, or accredited scheme, and describes no mechanism for assessing a company or product against it. It is tactical doctrine a commander plans and executes against, using its own "shall/should/may" wording conventions to judge compliance within their own chain of command.
STANAG 1448 is the agreement by which NATO nations record their commitment to use ATP-3.4.1.2; it is the cover, not the content. ATP-3.4.1.2 is the tactical publication itself, containing the actual doctrine, procedures and planning detail for multinational maritime HA/DR operations.
The document states it "also applies to operations within the framework of a combined joint task force in a multinational force of NATO and non-NATO nations," so a coalition including non-NATO partners is within its scope, alongside NATO forces acting alone.
NATO publishes it free of charge through the NATO Standardization Document Database. ComplyTrain does not sell or host copies of NATO documents.
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.