Lesson Overview
A commander decides what a task should achieve; the Quartermaster NCO works out whether the force can be kept supplied long enough to achieve it, and tells the commander plainly. That is the work of this lesson. When a section or detachment is sent out to do something, to run a water point after a storm, to hold a relief position for a week, to carry blankets and food to a cut-off community, somebody has to answer a hard question before the team leaves: what will this task consume, how much of it, and how does it keep arriving until the job is done? Answering that question is the logistics estimate, and producing a clear, honest answer is one of the most important things a QM NCO ever does. A task that is planned without a sustainment estimate is a task running on hope, and hope runs out at about the same time as the water.
This lesson takes the sustainment estimate you met in LOG 210 and puts it in the QM NCO's hands as a planning tool that produces three things the rest of the force depends on. First, the estimate itself: the commodities, quantities, resupply, and transport a task needs, built up from people, duration, conditions, and activity, with a sensible margin. Second, the service support paragraph of orders, which is how that estimate is written into the orders the team works from, so that everyone knows what they are carrying, what is coming, and when. Third, a resupply schedule the team can rely on, so that resupply arrives before stock runs out and never after. The estimate is the calculation, the orders paragraph is the promise, and the schedule is the proof that the promise can be kept.
This is the knowledge layer. The hands-on stores work behind a plan, signing for the stores a team draws, stocktaking what it has left, storekeeping a forward holding, is practised and signed off in person where supervision allows, because an estimate is only ever as good as the count it is built on. By the end you will be able to build a logistics estimate for a task from people, duration, conditions, and activity, working out the commodities and quantities needed with a margin and applying the consumption-rate method of LOG 210; turn that estimate into the service support paragraph of orders, cross-referenced to PME 210; and produce a resupply schedule the team can rely on, with timings, quantities, and a trigger for when to demand more.
Key Terms
- Logistics estimate (sustainment estimate): the calculation that turns who, how long, in what conditions, and doing what into how much of each commodity is needed, plus a margin, together with how it will be resupplied and moved. It is the QM NCO's central planning product for a task.
- The four inputs: the questions every estimate begins from, people (how many), duration (how long), conditions (hot, cold, wet, cut off), and activity (how hard the work is), because these four together set how fast each commodity will be used.
- Consumption rate: how fast a commodity is used, expressed per person or per item per unit of time, for example litres of water per person per day, or batteries per radio per day; the figure all sustainment planning is built from (LOG 210).
- Commodity: a kind of thing a task uses up, planned and demanded as a group: water, rations, power and batteries, fuel, shelter, medical supplies, and the like.
- Margin (contingency): the planned extra held above the calculated need, to cover under-counting, waste, loss, delay, and the task running longer or harder than expected. A margin is planned, not guessed in a panic later.
- Resupply: the delivery of more of a commodity to keep stock at the planned level, by push (sent forward on a schedule against expected need) or pull (sent in response to a demand from the point of need).
- Resupply schedule: the timetable of what is delivered, in what quantity, by what means, and when, so the team knows resupply is coming and the QM NCO knows when to dispatch it.
- Reorder level (trigger): the stock level at which a fresh demand is raised, set high enough that the new stock arrives before the held stock runs out.
- Service support paragraph: the paragraph of a set of orders (commonly the fourth) that tells the team the logistics plan: what is held, what is carried, what is coming, when, and how, written up from the estimate (PME 210).
- Sustainability statement: the QM NCO's plain advice to the commander on what the task can and cannot be supported to do, and for how long; the honest "we can sustain this for five days, not ten" that shapes what the force attempts.
The QM NCO as planner
The step this lesson asks you to make is from working a plan to making one. A storekeeper executes a sustainment plan: draws the stores, loads them, issues them, demands more. A QM NCO builds the plan the storekeeper executes, and stands beside the commander as the logistics adviser while the task is being shaped, not after it has been decided. This matters because logistics is most useful early. Once a commander has committed to holding a position for ten days, telling them on day six that the water will not stretch is a failure report; telling them in the planning that ten days needs this much water, this many runs, and these vehicles, or else the task must be cut to five days, is advice that shapes a sound plan. The QM NCO's job is to be in the room early, with the numbers, speaking plainly.
Speaking plainly is the heart of it. The QM NCO is not there to say yes to everything, and not there to say no out of caution; they are there to say what is true. The honest sustainability statement, "we can support a section on this task for seven days from what we hold, and to ten days if we can run resupply twice in the week, and beyond that not without a second vehicle", is worth more than any optimism. A commander can plan around a true constraint. A commander cannot plan around a cheerful guess that turns out wrong in the field, where the cost of running out is not embarrassment but a team that cannot do its job and people who do not get helped. The QM NCO who is trusted is the one whose numbers have held before, and numbers hold when they come from a method rather than a feeling. That method is the estimate.
Building the logistics estimate
The estimate is built up, not guessed down. You start from the four inputs, apply a consumption rate to each commodity, multiply out the raw need, add a margin, and arrive at a quantity to hold and a quantity to resupply. Take the inputs in turn.
People. How many are on the task? Count everyone the force must sustain, the team itself and anyone attached, and on a humanitarian task remember that the people served are sustained too, planned separately but from the same arithmetic. The number of people multiplies almost every commodity, so an under-count here under-supplies the whole task. Count carefully and, where the number is uncertain, plan to the higher figure.
Duration. How long is the task, in days? Duration multiplies the daily consumption into the total, and it is the input most often optimistic, because tasks run longer than planned far more often than they finish early. Plan the duration honestly and let the margin and the resupply schedule carry the risk that it runs long.
Conditions. Hot, cold, wet, dusty, cut off? Conditions change consumption rates sharply. People in heat or doing hard physical work drink far more than the resting baseline; cold raises the demand for warmth, calories, and battery drain; wet and rough ground raises wear and the loss of stores; being cut off lengthens the resupply gap the held stock must bridge. The estimate reads the conditions and adjusts the rates accordingly, rather than using a single fair-weather figure.
Activity. What is the team actually doing, and how hard? A team digging, carrying, and working in the heat consumes more water, food, and energy than a team holding a quiet position. Hard activity raises consumption; it also raises wear on equipment and the medical demand. The activity sets which rate, at the heavy or the light end, you apply to each commodity.
With the inputs fixed, work each commodity: need = people x duration x rate, then read across the commodities you planned in LOG 210, water, rations, power and batteries, fuel, shelter, medical, and any task-specific stores. Then add the margin. A margin is not slack for the careless; it is the planned answer to the things you know will happen but cannot price exactly: the count was a little low, some was spilt or spoiled, a run was delayed, the task ran a day long. A common working margin is in the order of ten to twenty-five per cent on the calculated need, set higher when the inputs are uncertain, the conditions hard, or the resupply unreliable, and higher still on a humanitarian task where the number of people is usually under-reported. The margin is decided on the worksheet, in the open, not improvised in the field when the stock is already short.
The output of all this is two numbers per commodity: how much to hold or carry at the start, and how much to resupply, and how often. Those two numbers feed the orders paragraph and the resupply schedule that follow. Below is a worksheet that lays the method out as a QM NCO would fill it.
LOGISTICS (SUSTAINMENT) ESTIMATE WORKSHEET (apply LOG 210)
TASK: ............................ PREPARED BY (QM NCO): ...........
INPUTS
People (to sustain) ....... P = ____ (team + attached + served?)
Duration .................. D = ____ days
Conditions ................ [ ] hot [ ] cold [ ] wet [ ] cut off
Activity .................. [ ] light [ ] moderate [ ] heavy
-> conditions + activity SELECT the rate (light/heavy end)
COMMODITY RATE (per RAW NEED MARGIN TO HOLD /
person/item = P x D x rate (+ %) RESUPPLY
/day)
------------- ------------ -------------- --------- -----------
Water __ L/pers/day ____ L + __ % ____ L
Rations __ /pers/day ____ + __ % ____
Batteries __ /radio/day ____ + __ % ____
Fuel __ /veh/day ____ + __ % ____
Shelter by person/hh ____ + __ % ____
Medical with MED 210 ____ + __ % ____
Task stores ............ ____ + __ % ____
TRANSPORT: total weight/volume to MOVE = ____ means: ..........
loads/runs needed = ____ (does it fit / how many trips?)
SUSTAINABILITY STATEMENT (plain advice to the commander):
"We can sustain this task for ____ days from what we hold, and to
____ days WITH resupply ____ x; beyond that NOT without ........."
From estimate to the orders paragraph
An estimate that stays on the QM NCO's worksheet has helped no one. It becomes useful when it is written into the orders the team works from, so that every member knows what they carry, what is coming, and when. In the standard format taught in PME 210, the logistics plan lives in the service support paragraph, conventionally the fourth main paragraph of orders, after the situation, the mission, and the execution. This is where doctrine and your estimate meet: the estimate gives the content, and PME 210 gives the form.
The service support paragraph answers, for the team, the practical logistics questions. What stores are held and carried, and by whom? What is the resupply plan, what comes forward, when, and by what means? Where are the medical arrangements and the casualty stores? What are the transport and movement details for the task? Where is the QM NCO or the stores point, so that demands have somewhere to go? The discipline is to write it plainly and completely, so that a team in the field can act on it without coming back to ask. A vague service support paragraph, "resupply as required", is not a plan; it is a gap the field will fall into. A good one names quantities, times, and means, because those are what the team needs to trust the supply and what the QM NCO is committing to deliver.
Writing the paragraph also disciplines the estimate, because turning numbers into a promise the team will rely on forces you to check them. If you cannot write a confident resupply line, the estimate behind it is not finished. The paragraph below is an outline a QM NCO can fill from the worksheet; the headings follow the staff-duties form of PME 210, and the content is the estimate made into orders.
SERVICE SUPPORT (paragraph 4 of orders) (form per PME 210;
content per estimate)
4. SERVICE SUPPORT
a. GENERAL
- Task duration planned: ____ days. Sustainment plan summary:
held for ____ days, resupplied ____ x to reach ____ days.
b. SUPPLY (by commodity)
- Water: carry ____ L/person; resupply ____ L on Day __, Day __.
- Rations: carry ____ days; resupply ____ on Day __.
- Batteries/power: carry ____; resupply ____ on Day __.
- Fuel: ____ ; refuel point / plan: ..........
- Medical: team scale carried; replens via ......... (MED 210).
- Task stores: ..........
c. TRANSPORT / MOVEMENT
- Means: ......... Loads/runs: ____ First-on / first-off:
water + medical forward and reachable.
d. MEDICAL
- Casualty stores held: .......... Evacuation plan: ......... (MED 210)
e. STORES POINT / DEMANDS
- QM NCO / stores point located at: ..........
- How to demand: ......... Reorder is triggered at: ____ stock.
RULE: name QUANTITIES, TIMES, and MEANS. "As required" is not a plan.
The resupply schedule the team can rely on
The estimate sets how much, the orders paragraph tells the team, and the resupply schedule makes the supply happen on time. Its whole purpose is captured in one rule from LOG 210: resupply must arrive before stock runs out, never after. A delivery that comes the morning after the water ran dry is not resupply; it is a record of a failure. So the schedule is built backwards from that rule. You take the held stock and the consumption rate, work out the day the held stock would run low, and set the resupply to arrive comfortably before then, leaving a buffer for the run itself to be late.
A reliable schedule has a few plain features. It names the day and the quantity of each delivery, so the team can see supply is coming and the QM NCO can prepare and dispatch it. It uses both push and pull: a scheduled push of the predictable commodities, water and rations going forward on fixed days against the known rate, and pull for the less predictable, the team demanding more of what it is using faster than planned. It carries a reorder trigger, a stock level at which a demand is raised regardless of the schedule, set high enough that the new stock arrives before the held stock is gone. And it has a fallback, a known alternative if the normal run cannot get through, because a humanitarian task is often a task where the roads are exactly what the flood has cut, and a schedule with no fallback is a schedule that fails the first time the weather does. The schedule is the QM NCO's promise made concrete, and it is the thing a team in the field actually trusts: not the estimate they never see, but the water that arrives on the day it was said to.
RESUPPLY SCHEDULE (built BACKWARDS from "before it runs out")
Commodity: WATER Held at start: 1,800 L Use: ~300 L/day (heavy)
-> held stock alone lasts ~6 days; buffer the runs, do not wait for 0.
Day: 1 2 3 4 5 6 7
Held (L): 1800 1500 1200 900* 600 300* -
Push run: +900 +900
(* = run ARRIVES here, on Day 4 and Day 6, BEFORE stock is low)
REORDER TRIGGER: raise a demand whenever held water falls to 600 L,
even off-schedule (pull), so new stock beats empty.
PULL: team demands extra if rate rises (heat, more people than planned).
FALLBACK: if the vehicle run is cut (flooded road), water moves by
......... ; civil-lead stocks at ......... as alternate source.
SAME TABLE per commodity (rations, batteries, fuel, medical).
RULE: every delivery lands BEFORE the line would reach empty.
In Practice: Planning a seven-day water point
A spell of severe weather has fouled the wells in a generic upland district, and the civil authorities ask the Army to run a water point on the high ground for a community for about a week while the wells are made safe. A Quartermaster NCO, a Sergeant, is given the task with a section of eight to run it, and she builds the plan as this lesson teaches rather than loading a vehicle and hoping.
She starts the estimate from the four inputs. People: eight on the team, plus the community served, which the civil lead puts at two hundred but which she plans at two hundred and fifty because relief numbers run high. Duration: seven days planned, so she works the held stock and resupply to reach ten, because tasks run long. Conditions: cool and wet, with one access road that the same weather may cut. Activity: moderate for the team, but the served commodity is water, so she plans it at the full Sphere figure of about fifteen litres per person per day. On the worksheet, water for two hundred and fifty people at fifteen litres comes to about 3,750 litres a day before margin, a real tonnage that at once tells her this is a transport problem as much as a stores one. She adds a generous margin on the served water, a quarter, against the under-count, and a lighter margin on the team's own commodities. She reads across rations, batteries for the radios, fuel for the vehicle, and a medical scale with MED 210, filling each line of the worksheet.
She then writes the service support paragraph for the section's orders in the PME 210 form, so the team knows exactly what it carries and what is coming: the water held at the point and the daily push to top it up, the team's rations and battery plan, the medical stores and the evacuation arrangement, the vehicle and its runs with water forward and reachable, and where she and the stores point sit so demands have somewhere to go. No line says "as required"; every line names a quantity, a day, and a means. Last she builds the resupply schedule backwards from the rule that water must never run dry at a point with a queue in front of it: she sizes the held stock, sets a daily push of water against the consumption rate, fixes a reorder trigger so a demand goes up before the held stock is low, and, because the one road may flood, names a fallback means and the civil lead's stocks as an alternate source. To the commander she gives the plain sustainability statement her worksheet supports: "We can run this point for seven days, and to ten with the daily run holding, but if the road is cut for more than two days we will need the fallback or the task shortens." The task is sound because it was estimated, ordered, and scheduled, and the community has water every day it needs it because a QM NCO planned for the day the road went under, not just the day the sun shone.
Check Your Understanding
- Name the four inputs a logistics estimate begins from, and explain how each one changes the quantity of a commodity the task will need. Why is a planned margin part of the estimate rather than something added later in the field?
- A QM NCO writes a service support paragraph whose resupply line reads only "water resupplied as required." Explain what is wrong with this, and rewrite it as a line a team in the field could actually rely on, naming the things a good resupply instruction must include.
- Explain the rule that resupply must arrive before stock runs out and never after, and describe how a resupply schedule is built backwards from it. What is a reorder trigger, and why is a fallback important on a humanitarian task?
Reflection (write a short paragraph): The QM NCO's most valuable contribution to a task is often the honest sustainability statement, the plain "we can support this for so long and no longer." Write about why it can be harder to say that than to promise more, and what it costs a force when a logistician tells a commander what they want to hear rather than what the numbers show.
Summary
- The QM NCO is the commander's logistics adviser and should be in the planning early, with the numbers, giving a plain sustainability statement of what the task can and cannot be supported to do, and for how long.
- Build the logistics estimate up from the four inputs, people, duration, conditions, and activity, applying a consumption rate to each commodity (need = people x duration x rate), then add a planned margin for under-count, loss, delay, and a task that runs long.
- The margin is decided openly on the worksheet, larger when the inputs are uncertain, the conditions hard, or, on a humanitarian task, the number of people likely under-reported. It is planned, never improvised when stock is already short.
- Turn the estimate into the service support paragraph of orders in the PME 210 staff-duties form: name quantities, times, and means for each commodity, the transport, the medical plan, and where to send demands. "As required" is not a plan.
- Produce a resupply schedule built backwards from the rule that resupply arrives before stock runs out and never after: scheduled push for the predictable commodities, pull for the rest, a reorder trigger set high enough that new stock beats empty, and a fallback for when the normal run cannot get through.
- Cross-references: applies the sustainment estimate and consumption-rate method of LOG 210 (Field Logistics and Sustainment), especially Lessons 01 to 06; writes orders in the form of PME 210 (Basic Staff Duties and Written Orders); builds on LOG 201 stores discipline and the account work of LOG 310 Lessons 01 and 02; ties to MED 210 (Field Health) for medical stores and water, to HCR 220 (Emergency Preparedness) for continuity and fallbacks, and to LDR 420 (ethical leadership) for the honesty of the sustainability statement.
Crown Copyright © 2026 | Published by Authority of H.R.H. The Prince of Kaharagia