The Fifty-Pound Leak: A Light-Touch Check for Project Budgets

Most project budgets do not fail in one loud moment. They leak. A box of fixings here, a taxi to a site meeting there, an urgent run to the builder’s merchant because the right size was not on the van. None of these feels like a budget decision at the time. That is exactly the problem.

By the time the costs appear in the monthly report, the job has moved on. The receipt is in someone’s coat pocket, the card statement has a name nobody recognises, and the project lead is left trying to remember why four separate trips were needed in the same week. The amounts are small enough to ignore individually and large enough to matter in total.

The £50 rule is a small response to that. It is not a procurement policy, and it is not designed to stop anyone buying what the job needs. It is a way of keeping the small stuff visible without turning every purchase into a form-filling exercise.

The leak is rarely dramatic

On a typical UK project, the quiet spends tend to look like this: consumables, parking, taxi fares, extra materials, a replacement tool, printer toner, safety gloves, a last-minute courier. They are the purchases that keep the job moving. They are also the ones most likely to bypass formal approval because stopping to raise a purchase order would take longer than the purchase itself.

That is a sensible instinct. The trouble starts when the same instinct applies every day for six weeks. A £12 item is not a problem. Forty £12 items with no record is a different conversation.

The usual response is to tighten approval. That rarely works well on a live project. People either wait, which slows the job, or they buy first and explain later, which is where the visibility problem began. A better answer is a low-friction record that sits alongside the work rather than in front of it.

The rule in one paragraph

Any project spend under £50 that is not already covered by a purchase order gets one line in a shared small-spend log, and one named person approves it. The purchase can still happen quickly. The log is not there to punish anyone. It is there so the project lead can see the pattern before month-end.

£50 is not a magic number. It is simply low enough to catch the regular items and high enough to avoid a form for every pack of pens. If your project has different economics, adjust the threshold. Keep it low, keep it simple and write it down so everyone applies the same rule.

Keep the log boring

A small-spend log should not become a mini accounting system. Six columns are enough: date, person, what it was, which phase or job it belongs to, amount, and whether a receipt is held. A shared spreadsheet is fine. A note on the project drive is fine. A pinned message in the project channel is not fine, because it will scroll away.

The test is whether someone can scan it in under a minute and see where the money is going. If the log needs training, it is too complicated. If it needs a separate meeting, it is too heavy. The point is a quick, honest record, not a second set of books.

It also helps to separate “one-off” from “repeat”. A single £18 tube of sealant is not interesting. The same £18 item appearing every few days is a signal that the job needs a proper order, not a series of small buys. The log makes that pattern obvious without anyone having to conduct an investigation.

Name one person

A log with no owner becomes a museum. Someone has to be responsible for glancing at it, asking the obvious question and closing the loop. On a small project, that is usually the project lead or the office manager. On a larger job, it might be a site supervisor with a weekly handover to the project lead.

The approver does not need to approve every item in advance. For routine, low-value purchases, a quick “yes, put it through” is enough. The important part is that the name is known. When a spend appears in the log with no approver, it is easy to spot and easy to correct. When nobody owns the log, the opposite is true.

Ten minutes on a Friday

A weekly review is the whole engine of the £50 rule. Put ten minutes in the diary at the end of the week, before people disappear into the weekend. Open the log, scan the amounts, check the receipts are attached and look for repeats.

Three questions are enough. Are there any entries with no approver? Is anything repeating often enough to become a proper order? Is the total for the week roughly what you would have expected? If the answer to all three is yes, close the file and get on with the job.

If the answer is no, you have found the problem while it is still small. That is the entire benefit. A £400 surprise at month-end is harder to unpick than a £40 entry that looks odd on a Friday afternoon.

When speed matters more

Some purchases cannot wait for a weekly review. An emergency callout, a part that stops a team working, a taxi to a client meeting that cannot be moved. The rule should allow those purchases to happen and be logged afterwards. The log is not a permission gate for genuine urgency. It is a memory aid for everything else.

The distinction to watch is between real urgency and poor planning. If the same “emergency” appears every week, it is probably not an emergency. It is a process gap wearing a high-vis jacket. The log will show that fairly quickly.

What good looks like after a month

After four or five weeks, the small-spend log should tell a simple story. You should be able to see which parts of the project generate the most incidental cost, which suppliers are being used for tiny purchases, and whether the total is drifting. You may also find that some of the spending is unnecessary, not because anyone was careless, but because nobody could see the whole picture.

That is the case for the £50 rule. Not control for its own sake, and not a bureaucratic layer on top of a busy job. Just a lightweight habit that keeps the small spends visible while the work keeps moving. On a UK project in 2026, where margins are tight and good people are busy, that is usually worth ten minutes a week.