Royal Army College

Lesson Overview

Lesson 01 set the tone of LOG 220: procurement is a public trust, and every dollar the Army spends was given for the people of Kaharagia. This lesson takes the first practical step in any purchase, the step that must happen before a single quote is sought or a single dollar is committed. It is the work of deciding what the force actually needs, proving that it is a need and not a want, and then writing that need down clearly enough that a supplier can quote for the right thing and that several quotes can be compared fairly. Procurement done well begins long before the money moves. It begins with definition.

Most procurement that goes wrong does not go wrong at the paying end, where the controls of Lesson 04 catch fraud. It goes wrong at the start, when nobody troubled to define what was needed. A purchase made from a vague want delivers the wrong item, or too much of it, or too little, or something that looked right in the catalogue and turns out useless in the field, and no three-way match can save a purchase that was wrong before it was ordered. This lesson teaches the discipline that prevents that loss: distinguish need from want, write a specification that states what is needed, to what standard, how much, and by when, and pitch the quantity so that the force neither over-buys and wastes nor under-buys and fails to sustain. Defining before buying is unglamorous, and it is where value for money is actually won or lost.

This is the knowledge layer of identifying and specifying a need. The hands-on stores work that surrounds it, signing for what arrives, stocktaking what is already held so you know what you truly lack, and storekeeping what comes in, is practised and signed off in person where supervision allows, because a specification is only as honest as the stocktake that tells you what you already have. By the end you will be able to distinguish a genuine requirement from a want and test which you are facing, write a clear specification stating what is needed, to what standard, how much, and by when, explain why a good specification lets suppliers quote for the right thing and lets quotes be compared fairly, calculate a sensible quantity from holdings and consumption so as to avoid both over-buying and under-buying, and recognise the common traps that turn a specification into a description of one supplier's product rather than the force's real need.

Key Terms

Need (requirement): a genuine, justified gap between what the force has and what a task or standing role demands, which must be filled for the force to do its job. A need can be stated in terms of the function it serves, not the product that fills it.
Want: a preference for a particular item, brand, or upgrade that is not required to meet the task. A want may be reasonable in itself, but it is not a basis for spending public money until it is shown to be a need.
Specification: the written statement of a need that a supplier quotes against. A good specification answers four questions: what is needed, to what standard, how much, and by when.
Functional specification: a specification written in terms of what the item must do or achieve, leaving the supplier free to offer any product that meets it. The preferred form, because it keeps competition open.
Technical specification: a specification written in terms of measurable characteristics, dimensions, capacity, material, performance figures, that the item must meet. Used where the function alone is not precise enough.
Standard: the level of quality, durability, or performance the item must reach to be fit for purpose, stated so it can be checked on delivery and against the law where the law applies.
Fit for purpose: good enough for the job it is bought to do, no less and no more; the test a specification is written to capture.
Over-buying: purchasing more than the need requires, tying up money and storehouse space in stock that may expire, deteriorate, or never be used. A waste of public trust.
Under-buying: purchasing less than the need requires, so the force cannot sustain the task and must buy again, often in a rush and at a worse price. A failure to sustain.
Consumption rate: how fast a commodity is used, from LOG 210, the figure a sensible purchase quantity is calculated from for anything consumed rather than held.
Requisition (demand): the internal request that records and justifies a need before it becomes a purchase, naming what is wanted, why, how much, and by when, and routed for approval.

Why definition comes first

Begin with the reason this lesson sits where it does, second in the course and ahead of sourcing, quotes, ordering, and paying. It is because every later step inherits whatever the first step decided. A supplier sourced in Lesson 03 is sourced to meet a specification; a quote compared in Lesson 03 is compared against a specification; an order placed in Lesson 04 orders what the specification asked for; a goods receipt checks delivery against the order, which came from the specification; and the three-way match that stops fraud matches three documents that all trace back to that first definition of need. If the definition is wrong, every control downstream is working faithfully to deliver the wrong thing. The cleanest payment in the world, perfectly matched and properly authorised, is still a waste of the Principality's money if it pays for an item the force did not need.

So the discipline of procurement starts before the market is ever approached. The question is not yet who sells this or what does it cost. It is what, exactly, does the force need, and how do I know. Answering that honestly does two things at once. It protects the money, because a need that has been examined and written down is far harder to inflate into a want, a wish, or a favour. And it makes everything that follows possible, because a supplier cannot quote for, and you cannot fairly compare, a need that exists only as a vague feeling that the store is short of something. Definition is the act that turns an itch into a thing that can be bought, measured, and checked.

There is a second reason definition comes first, and it is about honesty. Money is most easily misspent at the point where nobody has written down what it is for. A loose request, get us some more of those, leaves room for the wrong item, the over-large quantity, the supplier who happens to be a friend, and the upgrade nobody needed but somebody fancied. A written need closes that room. It states the requirement plainly enough that an approver can challenge it, an auditor can read it later, and the person buying cannot quietly substitute their own preference for the force's actual need. In a course about spending public money in trust, the written need is the first control, earlier even than the controls of Lesson 04, because it is the one that decides whether the right thing is being bought at all.

Need or want: the test

The first judgement to make about any proposed purchase is whether it is a need or a want, because only a need justifies spending public money, and the two are easy to confuse, especially when the want is reasonable and the person feeling it is sincere. A need is a genuine gap between what the force has and what a task or standing role requires: the section has no working stove and a field exercise next week requires hot food, so a stove is needed. A want is a preference that is not required to meet the task: the section has a working stove but a newer model is lighter and looks better, so a new stove is wanted. The newer stove may be a perfectly sensible thing to own one day, but wanting it is not, by itself, a reason to spend the Principality's money now.

The test that separates them is a short chain of honest questions, asked in order and answered plainly. What task or role does this serve? What does the force already hold that meets it, in full or in part? What is the gap, stated as a function rather than a product? What happens if the gap is not filled? And could the need be met another way, by repair, by reissue from stock, by borrowing, or by doing without? A proposed purchase that survives these questions, that serves a real task, fills a real gap that stock cannot, and would cause a real failure if left unfilled, is a need. One that falls at the first honest question, where the force already holds something that does the job, or nothing would actually fail, is a want, and a want is sent back, not bought. The point of the test is not to refuse everything; it is to make sure that what is bought is bought because the force needs it, and that the reason can be shown.

   NEED OR WANT: THE TEST  (ask in order; answer honestly)

   QUESTION                              NEED if...        WANT if...
   -----------------------------------   --------------    -----------
   1. What task or role does it serve?   names a real      "would be
                                         task / duty       nice to have"
   2. What do we already hold that       nothing, or not   we already
      meets it?                          enough            hold one that
                                                           works
   3. What is the GAP (as a function,    a real shortfall  no real gap;
      not a brand)?                      in capability     it's an
                                                           upgrade/brand
   4. What fails if we DON'T fill it?    a task can't be   nothing fails;
                                         done / sustained  it's nicer
   5. Could we meet it another way?      no: repair /      yes: repair,
      (repair, reissue, borrow, do       reissue / borrow  reissue, or
      without)                           won't do it       do without
                                                           works fine
   -----------------------------------   --------------    -----------
   ALL point to NEED  -> proceed to specify and requisition.
   ANY points to WANT -> send it back. Public money is for needs.

Two cautions keep the test honest. The first is that a want can be dressed as a need by the person who wants it, sincerely, because wanting something makes its absence feel like a gap. The test is written down precisely so the judgement does not rest on how strongly someone feels, but on whether a task fails and whether stock already covers it. The second is the opposite trap: refusing a true need because it looks like an indulgence. A piece of safety kit, a medical consumable, a means of keeping members warm and fed, can read as comfort to someone far from the field, yet fail the task and the duty of care if it is not bought. The test cuts both ways. It asks only whether the force needs the thing to do its job, and it answers that from the task and the stock, not from taste or thrift for its own sake.

Writing the specification: the four questions

Once a need has passed the test, it has to be written down in a form a supplier can quote against, and that written form is the specification. A good specification is not a long document; it is a clear one, and it answers four questions, in order: what is needed, to what standard, how much, and by when. Get those four right and a supplier knows exactly what to offer, you know exactly what to compare quotes against, and the person who receives the goods knows exactly what to check on delivery. Get any of the four wrong or leave it vague, and you have invited the wrong item, the wrong quality, the wrong quantity, or a delivery that arrives too late to be any use.

Take the four in turn. What is needed should be stated as a function wherever it can be, not as a brand or a single product, because a need stated as a function keeps competition open and lets several suppliers offer ways to meet it. A means of boiling water for two hundred people in the field is a function; one named model of urn from one catalogue is a product, and writing the product into the specification quietly closes the competition before it starts. Sometimes the function alone is not precise enough and you must add technical detail, a capacity, a size, a material, a performance figure, and that is proper, but the discipline is to specify what the item must do and only then, where needed, the measurable characteristics it must have to do it. The aim is always the real need, never one supplier's answer to it.

To what standard states the level of quality, durability, or performance the item must reach to be fit for purpose, and it is the question most often skipped, to everyone's cost. A standard is what lets you reject a delivery that technically matches the description but is shoddy, flimsy, out of date, or unsafe. It is stated so it can be checked: a material that withstands field use, a battery that holds a stated capacity, a medical consumable in date by a stated margin, a garment that meets a recognised safety standard where the law or the task requires one. Where a real standard exists, a safety mark, a recognised grade, an expiry rule, name it, because a named standard is one a supplier must meet and a receiver can verify, while good quality on its own means whatever the supplier wishes it to mean. Fit for purpose is the governing idea: the standard is set at what the job genuinely requires, no lower, so the kit does not fail, and no higher, so the force does not pay for a grade it has no use for.

How much is the quantity, and because it is where over-buying and under-buying live, the next section treats it on its own. By when is the date the need must be met, and it matters because a delivery that arrives after the task is no delivery at all, exactly as resupply after the floor was a failed task in LOG 210. The by-when date drives everything that follows: it sets how long there is to seek quotes, how much lead time a supplier needs, and whether a slower, cheaper option is even available or whether the deadline forces a dearer one. State it honestly, with the real date the kit must be in hand and serviceable, not the date someone hopes it might be wanted, and state any milestone within it, a sample to approve, a part-delivery, so the supplier and the approver both see the timeline the purchase actually lives in.

   SPECIFICATION TEMPLATE  (one per need; precede with the need/want test)

   REQUISITION No: ............    DATE RAISED: ............
   RAISED BY: ..................   FOR TASK / ROLE: ............
   NEED / WANT TEST PASSED?  YES (attach answers)   [needs only]

   1. WHAT IS NEEDED  (state as a FUNCTION first; brand-free)
      ...........................................................
      ...........................................................
      Technical detail, only if function alone is not precise:
        capacity ........  size ........  material ........
        performance ......................................

   2. TO WHAT STANDARD  (quality / durability / safety; checkable)
      Named standard / grade / mark: ..........................
      In date by (consumables): ........  Other: ..............
      Reject on delivery if: ..................................

   3. HOW MUCH  (from STOCK + CONSUMPTION, not a round guess)
      Already held (per stocktake) .......
      Required for task / period ........ at rate ........
      = Shortfall to buy ........  + margin ........ = ORDER ........
      Unit of issue: ........   (avoid over-/under-buying)

   4. BY WHEN  (real date kit must be IN HAND and serviceable)
      Needed in hand by: ............
      Milestones (sample / part-delivery): ....................

   ESTIMATED VALUE (USD): $..........   BUDGET LINE: ............
   ----------------------------------------------------------------
   This document is what suppliers QUOTE against and what the
   goods receipt is CHECKED against. Vague here = wrong delivery.

A specification written to these four questions does two jobs at once, and both matter. It lets a supplier quote for the right thing, because it tells them precisely what to offer and to what standard, so their quote is for the force's actual need and not for whatever they guessed it might be. And it lets quotes be compared fairly, because when three suppliers all quote against the same clear specification, the quotes differ on price, on lead time, on the value they offer for the stated need, and not because each understood the request differently. Two quotes for two different understandings of a vague request cannot be compared at all; you would be choosing between answers to different questions. The specification is what makes a fair comparison possible, and a fair comparison, as Lesson 03 will show, is how value for money and honest dealing are actually achieved.

How much: avoiding over-buying and under-buying

The quantity question deserves its own treatment, because it is where good intentions most often turn into wasted or insufficient stock, and because both errors are failures of the same discipline: pitching the quantity from evidence rather than from a feeling. Buy too much and you have over-bought: money and storehouse space are tied up in stock that sits, deteriorates, expires, or is never used, and the over-buy looks harmless because the kit is at least there, which is exactly why it slips past. Buy too little and you have under-bought: the force cannot sustain the task, runs short, and must buy again, usually in a hurry, at a worse price, from whoever can deliver fastest rather than whoever offers best value. Both are losses of public money. Neither is honest stewardship. The quantity has to be right, and right means calculated.

The calculation starts not at the supplier but at the storehouse, with the stocktake of Lesson 01 and LOG 201. You cannot know how much to buy until you know how much you already hold, and the commonest cause of over-buying is buying what you already have because nobody checked the shelf. So the first figure in any quantity is current holdings, taken from the ledger and confirmed by a physical count, because a ledger that has drifted from the shelf will mislead the purchase as surely as it misleads everything else. Against that holding you set the requirement: for a one-off item, how many the task needs; for anything consumed, water, rations, batteries, medical consumables, the requirement comes from the consumption rate of LOG 210, rate times people times days, the same arithmetic that drives the sustainment estimate. The quantity to buy is the requirement minus what is already held, plus a sensible margin for loss, wastage, or a slightly heavier task than planned, and no more. That figure, the shortfall plus a stated margin, is what goes on the specification as how much.

   HOW MUCH TO BUY  (calculate; never round up "to be safe" blindly)

                    [ over-buying ]            [ under-buying ]
   ----------------------------------------------------------------
   symptom     too much stock: money &      too little: force runs
               space tied up; expires,      short, can't sustain,
               deteriorates, never used     re-buys in a rush dear
   looks like  "harmless, it's at least     "thrifty, we saved a
               there"                       few dollars"
   real cost   wasted public money, dead    failed task + worse
               storehouse space, write-off  price on the rush re-buy
   ----------------------------------------------------------------

   THE CALCULATION  (lands between the two):

     REQUIREMENT   (one-off: task qty;  consumable: rate x people x days)
   - ALREADY HELD  (LEDGER confirmed by a physical STOCKTAKE)
   = SHORTFALL
   + MARGIN        (stated reserve for loss / wastage / heavier task)
   = QUANTITY TO BUY        rounded to the supplier's UNIT OF ISSUE

   Example (USD), field water treatment tablets, 3-day relief task:
     Requirement   208 people x 3 days x 4 tablets/person/day = 2,496
     Already held         (stocktake)                       =   400
     Shortfall                                              = 2,096
     + margin (~1 day, ~830)                                =   830
     = to buy                                               = 2,926
     round to unit of issue (packs of 100)                 = 3,000
     est. value at $0.04/tablet ............................ $120.00

Two practical habits keep the quantity honest. The first is the unit of issue: suppliers sell in packs, boxes, drums, or cases, and the calculated figure must be rounded sensibly to how the item is actually sold, but rounded with eyes open, so that rounding three thousand and twenty up to three thousand one hundred is a small, noticed margin and not an accidental doubling because someone bought ten boxes when two would do. The second is to resist the false economy of the bulk discount that the force does not need. A lower unit price on a quantity beyond the requirement is not a saving; it is over-buying with a discount attached, and if the surplus expires on the shelf the force has paid more in total for stock it threw away than it would have paid for the right amount at the higher unit price. Value for money, as Lesson 01 insisted and Lesson 03 will develop, is value against the need, and a discount on stock beyond the need is no value at all. The quantity that is right is the one the calculation gives: enough to sustain, not so much as to waste, landed in the narrow band between under-buying and over-buying that honest definition is meant to find.

Common traps in specifying

A few traps recur often enough to be worth naming, because each turns a sound specification into a quiet failure of definition, and each can be avoided once it is seen. The first and most damaging is writing the supplier's product into the specification: copying a brand, a model number, or a catalogue description into the what is needed line so that, knowingly or not, the specification can be met by only one supplier's item. This destroys the fair comparison before it begins, because no competing supplier can quote against a specification that names a rival's product, and it is one of the ways favouritism creeps into honest-seeming paperwork. The guard against it is the functional specification: state what the item must do, add technical detail only where the function genuinely needs it, and where a particular standard or interface really is required, state the standard, not the brand that happens to meet it.

The second trap is over-specifying, demanding a grade, a feature, or a tolerance the task does not need, which narrows the field, raises the price, and pays public money for performance the force will never use. A garment specified to a standard far beyond field use, a battery to a capacity no device will draw, a tolerance finer than the job requires, each is a small over-buy built into the specification itself. Its mirror is under-specifying, leaving the standard vague so that the cheapest, flimsiest answer technically qualifies and a delivery of unfit kit cannot be rejected because the specification never said it had to be any good. Between them sits fit for purpose: specify the standard the task genuinely requires, stated so it can be checked, and no more. The third trap is the rushed by-when, a deadline set too tight because the need was spotted late, which forces a dearer or sole-source purchase and removes the time to seek and compare quotes; it is usually a symptom of poor planning upstream, and its cure is to identify needs early, from the consumption and the task calendar, so that definition has time to do its work before the deadline closes the options.

In Practice: Specifying Blankets for a Cold-Weather Relief Task

A storekeeper, a Sergeant holding the Quartermaster and Logistics speciality, is told the Army may be asked to help shelter displaced nationals in a spell of cold weather, and that the section commander wants blankets bought. It would be easy to ring round for a price on blankets and place an order that afternoon. The Sergeant does not, because LOG 220 has taught her that the order placed that afternoon is the order that arrives wrong. She starts where the course says to start, with the need and the specification, and only then with the market.

First, need or want. The task is real, sheltering people in the cold, and the duty of care is plain, so this is not a comfort upgrade. But she runs the test honestly all the same. What do we already hold? She does not trust her memory; she takes a stocktake of the blanket stock and finds sixty serviceable blankets already on the shelf, a figure nobody had remembered, which immediately changes the quantity she will buy and would have been an over-buy of sixty if she had ordered blind. What fails if we don't fill the gap? People go cold, which is a real failure, so the remaining shortfall is a genuine need. The test passes for the gap, not for the whole notional order, and the difference is sixty blankets of public money.

Then the specification, to the four questions. What is needed: she writes it as a function, a blanket that keeps an adult warm in cold but not freezing field conditions, washable and reusable, and resists the urge to copy the brand name from the catalogue she happens to have open, because naming it would shut out every other supplier and turn her own fair comparison into a formality. To what standard: warm enough for the conditions, durable enough to be washed and reused across a task, and, because these go to members of the public including children, she names a recognised flammability standard so a delivery of cheap, unsafe blankets can be refused on the spot. How much: the task is planned for up to two hundred and forty people; she already holds sixty serviceable; the shortfall is one hundred and eighty; she adds a margin of twenty against loss and a heavier turnout, giving two hundred, and rounds to the supplier's unit of issue of bales of twenty-five, landing at two hundred even, with an estimated value she records in USD against the budget line. By when: the cold spell is forecast within two weeks, so she sets the in-hand-and-serviceable date with a few days' margin and notes it as the figure she is least sure of, because if the weather moves earlier the whole timeline tightens and may force a dearer fast supplier.

What goes forward is not a phone call for a price on some blankets. It is a written specification, function-first and brand-free, with a checkable safety standard, a quantity calculated from a real stocktake and a real headcount rather than guessed, and an honest by-when date. Any of three suppliers can now quote against it; the quotes will be comparable because they answer the same clear question; the goods receiver will know exactly what to check and what to reject; and sixty blankets the force already owned were not bought twice. For this Army, that specification is the difference between people kept warm with money spent well and a hasty order that lands late, unsafe, or doubled.

Check Your Understanding

Distinguish a need from a want and set out the chain of questions that tests which you are facing. Then explain why a want can be sincerely mistaken for a need, and how the written test guards against that without refusing a genuine need that happens to look like a comfort.
State the four questions a good specification answers, and explain for each why getting it wrong leads to a wrong delivery. Then explain how a clear specification both lets suppliers quote for the right thing and lets several quotes be compared fairly, and why two quotes raised against a vague request cannot be compared at all.
Explain over-buying and under-buying, the real cost of each, and why both are failures of the same discipline. Then set out how a sensible quantity is calculated, starting from a stocktake of current holdings and a consumption rate, and explain why a bulk discount on stock beyond the need is not a saving.

Reflection (write a short paragraph): This lesson argues that most procurement that goes wrong was already wrong before any money moved, because nobody troubled to define the need, distinguish it from a want, and write it down clearly. Think of a time you, or an organisation you know, bought the wrong thing, too much, too little, the wrong quality, or something that arrived too late to be useful. Working backwards, which of the four questions, what, to what standard, how much, by when, was left unanswered, and would the need-or-want test have caught the purchase before it was made? How does seeing that failure as a failure of definition rather than of buying change the way you regard the quiet, unglamorous work of specifying before spending?

Summary

Procurement that goes wrong usually goes wrong at the start, when nobody defined the need, not at the paying end where the controls catch fraud. Definition comes first because every later step, sourcing, quoting, ordering, receiving, paying, inherits whatever the first step decided. A perfectly clean payment for the wrong item is still wasted public money.
A need is a justified gap between what the force holds and what a task or role requires; a want is a preference not required to meet the task. Only a need justifies spending public money, and the two are separated by an honest chain of questions, what task it serves, what is already held, the gap as a function, what fails if it is not filled, and whether it could be met another way, answered from the task and the stock, not from feeling.
A specification answers four questions: what is needed (as a function first, brand-free), to what standard (checkable, named where a standard exists, fit for purpose), how much, and by when (the real date the kit must be in hand and serviceable). A clear specification lets suppliers quote for the right thing and lets quotes be compared fairly; a vague one invites the wrong item, quality, quantity, or timing.
The quantity is calculated, not guessed: requirement (a task figure, or consumption rate times people times days for anything consumed) minus what is already held by stocktake, plus a stated margin, rounded to the unit of issue. Over-buying wastes money and space in stock that expires; under-buying fails the task and forces a costly rush re-buy. A bulk discount on stock beyond the need is over-buying, not value.
Common traps to avoid: writing one supplier's product into the specification (which kills fair comparison), over-specifying a grade the task does not need (which raises price for unused performance), under-specifying the standard (which lets unfit kit qualify), and a rushed by-when that removes the time to seek and compare quotes. The cure for all four is functional, fit-for-purpose specification done early.
This lesson builds on Lesson 01 (Procurement as a Public Trust) and feeds Lesson 03 (Sourcing, Quotes, and Fair Selection), where the specification is what quotes are compared against, and Lesson 04 (Ordering, Receiving, and Paying), where the goods receipt is checked against the order that came from it. It draws on LOG 201 (the stocktake and ledger that tell you what you already hold), LOG 210 (consumption rates for quantity), and connects to PME 210 (records and written demands) and LDR 420 (the stewardship that defining before spending serves).

Identifying and Specifying a Need