Start a free trial
Menu

AJP-4.6

AJP-4.6 doctrine for the joint logistic support group

Joint NATO commanders and staffs forming, commanding and coordinating a Joint Logistic Support Group, and the contractors and support elements a JLSG coordinates

NATO's doctrine for how a Joint Logistic Support Group is formed, commanded and coordinated to run logistics for a NATO operation.

Edition
C
Published
2018-12

What it is

AJP-4.6, Allied Joint Doctrine for the Joint Logistic Support Group, is NATO's Allied Joint Publication describing how a Joint Logistic Support Group (JLSG) is formed, commanded and employed. The JLSG itself is "a joint, force generated, deployable logistic capability" that a Joint Task Force commander (COM JTF) can stand up for an operation, and once activated it provides "the tactical-level executive for command and control of COM JTF's assigned forces for the delivery of the joint logistic support network." Edition C, Version 1 was promulgated in December 2018, and it builds on the principles set out in AJP-4, Allied Joint Doctrine for Logistics.

The document names its own audience directly: it "is intended primarily as guidance for joint NATO commanders and staffs," and is "instructive to, and provides a useful framework for, operations conducted by a coalition of NATO members, partners and non-NATO nations," as well as being "a reference for NATO civilian and non-NATO civilian actors." It is not written for a company. Nations adopt the doctrine through NATO's own promulgation process rather than a law or a general contract clause, and the current edition carries a recorded national reservation from the United States on how it reads the LOGCON/TACON command relationship. A company's own connection to AJP-4.6 runs only through a contract to supply logistics, host-nation support or commercial services into an operation a JLSG is coordinating.

Why the JLSG exists and how it is built

The JLSG coordinates a joint force's logistics collaboration "with the exception of medical support" across nations, partners, host nations, logistic lead and role-specialist nations, international and non-governmental organizations, and contractor support, aiming to achieve economies of scale and reduce the overall logistic footprint of an operation. Four operating principles shape it: readiness (held above first-echelon combat troop readiness, to support reception, staging and onward movement), scalability (able to support anything from low- to high-intensity operations), modularity (built from addable or removable functional modules) and a tailored spectrum, from a small coordination cell to a fully augmented headquarters, decided during the operations planning process.

Command, responsibilities and their limits

COM JLSG answers to COM JTF for "the coordination and execution of operational-level logistic support," again excluding medical support, "using assigned national, host nation and/or commercial resources." The doctrine lists the authorities COM JLSG will normally hold, including designing the joint logistic support network (JLSN), coordinating National Support Element (NSE) assets when authorised, and establishing movement and transportation requirements, but it also draws a clear boundary around that authority: "COM JLSG should not be assigned as an area commander," and, separately, "COM JLSG shall not be the joint rear-area security commander." The standard organizational structure the doctrine names is "111+2 NSPA contractors."

The JLSG headquarters is built from named branches, including Plans, Supply and Services, Movement and Transportation, Host-Nation Support, Medical, Military Engineering, Civil-Military Cooperation, Intelligence, and Purchase and Contracts. The Purchase and Contracts (P&C) Branch is where a contractor's relationship with the JLSG sits: its responsibilities are "limited to contracting support" under the theatre head of contract's delegations, other than initial "First Entry" contracting, which the branch handles directly, and it is "augmented by the NSPA who will provide support related to NSPA contracts." The branch coordinates contracting activity with NSEs to avoid competing for resources, deconflicts other NATO, national, international, NGO and private-sector contracting agencies in theatre, establishes unfunded basic ordering agreements for use across NATO forces, and provides liaison "between civilian contractors, customers and financial controllers."

Deployment, sustainment and where contractors sit

The joint logistic support network (JLSN) is "a system of interconnecting logistic nodes, activities, organizations and sites, and their multimodal links" within the joint operations area, built from points of debarkation and embarkation, lines of communication, logistic bases, principally the Theatre Logistic Base (TLB), convoy support centres and staging areas. COM JLSG's own mission focuses on the "sustain" activity of NATO's operations framework: deployment (reception, staging and onward movement), sustainment (replenishment, host-nation support, operating bases), and redeployment (rearward movement, staging and dispatch). At the TLB, the JLSG's main hub, the doctrine is explicit that "contractors and the NSEs will most likely be collocated" there "but not under the command of COM JLSG." A JLSG's own units and resources, in turn, "could be provided by contractors, other government departments and, in exceptional circumstances, non-governmental organizations (NGO) and international organizations (IO)."

Command relationships and logistic control

COM JLSG's command and control rests on operational control of specifically assigned forces, tactical control of transiting units at JLSG nodes, movements control exercised jointly with battlespace owners, and a supporting/supported relationship in which COM JTF names COM JLSG the supported commander specifically during reception, staging, onward movement and redeployment when those are the main effort. Logistic control (LOGCON), the authority troop-contributing nations are asked to prioritise granting, gives visibility over logistic requirements, but the doctrine is precise about its limit: "there is no inherent authority to direct national elements, although nations may choose to grant this authority," and the Lexicon adds that LOGCON "does not confer authority over nationally-owned resources held by a national support element, except as agreed in the transfer of authority."

What it does not cover

AJP-4.6 excludes medical support from COM JLSG's own coordination responsibility throughout, even though the Lexicon's own definition of "logistics" includes "medical and health service support." Medical support is instead coordinated at JTF level, through AJP-4.10. The doctrine also sets no certification, accreditation or audit scheme of its own: it is a command framework, and the nearest thing to an assessment it describes is the internal "assessment" of a deployed JLSG's mission progress against its own operations plan, not a conformance check against the document.

How we help

AJP-4.6 is operational, organisational doctrine describing NATO's own command structure. The work it describes, forming a JLSG, commanding it, coordinating a joint logistic support network, happens in a deployed headquarters and in theatre, not in software, and this page will not pretend otherwise.

A company's real point of contact with AJP-4.6 is as a contracted logistics, host-nation-support or commercial-services provider whose activity a JLSG coordinates, principally through its Purchase and Contracts Branch and its liaison arrangements. What helps there is a documented procedure for how liaison and contract staff engage with a JLSG, training records showing deployed personnel understand the reporting and coordination lines the doctrine describes, and a controlled record of how that activity is reported back to the customer. ComplyTrain holds that procedure, that training record and that evidence trail in an auditable form.

What ComplyTrain does not do: it does not form, command or operate a JLSG, negotiate a logistics contract, or decide what tier of support an operation requires. The command structure that applies and the standards that come with it are set by the operation and the customer's own contract and quality clauses. Explore the related standards to see what sits alongside AJP-4.6, including AJP-4 and the component logistic doctrines it names, or talk to us about the evidence trail your own contracted logistics support needs to hold.

Standards it references

Questions

Is AJP-4.6 mandatory?

Not on its own, and not for a company. It is NATO doctrine, covered by STANAG 2230, and nations adopt it through NATO's own promulgation process, with the option to record reservations, as the United States has for the LOGCON/TACON relationship. A company only meets it where a contract to supply logistics or commercial support into a NATO-led operation brings that activity inside a JLSG's coordination.

Does AJP-4.6 apply to contractors directly?

The doctrine mentions contractors and commercial support repeatedly, as a resource COM JLSG coordinates, a presence collocated at the Theatre Logistic Base, and a counterparty for the Purchase and Contracts Branch, but it addresses NATO commanders and staffs, not contractors themselves. A contractor's obligations come from its own contract, not from this doctrine directly.

What is the difference between AJP-4 and AJP-4.6?

AJP-4 is Allied Joint Doctrine for Logistics, the senior doctrine that sets NATO's general logistics principles. AJP-4.6 builds on it specifically for the Joint Logistic Support Group, the deployable headquarters that executes operational-level logistics for a given operation.

Does the JLSG handle medical logistics?

No. AJP-4.6 is explicit that COM JLSG's coordination and execution responsibilities exclude medical support throughout, even though the document's own definition of "logistics" includes medical and health service support. Medical support is coordinated separately at Joint Task Force level.