The price of a gift

There is a photograph taken in a great many countries. A minister, an ambassador, a line of new vehicles or vessels or scanners, and a ribbon. It is a good day, and the gratitude is genuine. The capability is real and it would not otherwise have been affordable.

The difficulty arrives about eighteen months later, and it is rarely traced back to the ceremony.

What the gift actually transfers

A donated capability transfers the capital cost to the donor and leaves every other cost with the recipient. Maintenance, spares, consumables, fuel, insurance, the training pipeline that keeps operators current, the technicians who service it, and eventually replacement. Those costs are real, they are recurrent, and they usually arrive in a budget that was never adjusted to receive them.

This is not a criticism of donors. It is arithmetic. A donor budget is structured to buy things; a recipient budget has to run them. The two are rarely reconciled at the point of handover because at that moment nobody in the room is incentivised to raise it.

The capital cost is announced. The through-life cost is inherited, and it is inherited by an organisation that was not consulted about the specification.

The caveats that travel with it

Most gifts arrive with conditions. They are usually reasonable, and they are usually not read closely by anyone who will later have to operate within them.

• End-use conditions. Restrictions on where the equipment may be deployed, against whom, and alongside whom. These can rule out precisely the task you had in mind.
• Operator restrictions. Requirements about who may use it, what vetting they must hold, and sometimes the presence of donor personnel. That is a constraint on your own establishment.
• Reporting and monitoring. Obligations to account for use, sometimes indefinitely, sometimes to a body that will also be assessing you for the next tranche.
• Spares and vendor lock. Proprietary parts from a single supplier in the donor country, occasionally requiring an export licence for each order. A vessel awaiting a licensed part is not a vessel.
• Data. Modern sensors, radios and management systems generate data and often move it. Establish before acceptance where it is hosted, who has access, and whether your patrol pattern is visible to anyone other than you.
• Withdrawal. Support is a function of a relationship. Relationships change, and when they do you are left owning an asset you cannot sustain and cannot easily dispose of.

The deeper problem is whose requirement it answers

All of the above is manageable. The harder issue is that a donated capability tends to answer the donor’s problem rather than the recipient’s.

Donor priorities are legitimate but they are theirs. Counter-narcotics, irregular migration, counter-terrorism and maritime interdiction attract funding because they matter to the donor’s own public. If the recipient’s actual first-order problem is domestic violence, vehicle crime, evidence handling or a court backlog, no amount of donated maritime radar addresses it, and the effort spent absorbing that radar is effort not spent on the real thing.

Worse, capability shapes doctrine. An organisation given a tool will find a use for it, write procedures around it, allocate people to it and eventually describe it as core. Ten years later the shape of the institution reflects a sequence of other people’s priorities, and nobody decided that.

What buying actually buys

The argument for purchase is not that it is cheaper, because it is not. It is that you keep the decisions.

• You write the requirement, against your own assessed gap, in your own order of priority.
• You compete the supply, which disciplines both price and specification.
• You negotiate spares, training and support as part of the same deal rather than discovering them later.
• You set the data terms, including where it is held and who may see it.
• You specify interoperability with what you already own, rather than accumulating three radio systems from three donors that cannot speak to each other.
• You know the whole-life cost before you commit, and can decline if you cannot carry it.
• It remains yours when the political weather changes.

None of that is free, and for many institutions purchase is simply not available at the scale required. That is a real constraint and this piece does not pretend otherwise.

The rule that actually helps

The useful distinction is not gift against purchase. It is whether the requirement was written by the organisation that has to live with the result.

A gift accepted against your own written, prioritised requirement is a good outcome and you should take it. A purchase made against a vendor’s brochure is a bad outcome and you have paid for the privilege. The failure mode is identical in both cases: somebody else decided what you needed, and the only difference is who sent the invoice.

Which means the discipline that matters is upstream of both. Know the gap, in your own order, with the consequence of each stated. Then a donor conversation becomes a negotiation rather than an acceptance, because you can say what you would like instead, and you can say it with a document behind you.

Eight questions before accepting

None require special expertise. They require somebody to ask them before the ceremony rather than after.

• Which line of our own gap register does this answer, and where did it rank?
• What is the annual cost of running it, and whose budget line carries that from year one?
• What is the spares route, how long is it, and does any part of it require a licence?
• Who may operate it, who must vet them, and can we sustain that pipeline ourselves?
• What conditions attach to its use, and do any of them rule out the task we wanted it for?
• What data does it generate, where does that data go, and who else can see it?
• Does it interoperate with what we already have, or does it become a fourth island?
• If support stopped tomorrow, how long would it remain serviceable?

If the answers are good, accept it and be glad. If several are unknown, the gift is a liability with a delay on it, and the right response is not refusal but a conversation with the donor about a different gift.

Our interest in this argument

We advise on writing requirements, and we can source equipment. An article arguing that institutions should specify and buy rather than accept is an article arguing for work we do. Read it accordingly, and discount it where you think it deserves discounting.

We would add only this. The recommendation we make most often in this area is not to buy anything. It is to write down the gap and its order of priority, which costs nothing, and which turns out to be the thing that makes both a purchase and a gift work.

Read next · Assessment method

Borrowed capability

Why the hardest question in a security review is the one about what happens after the help leaves.