Before the First Hour: Confirming Purchase Order Cover on UK Client Work

Most delivery problems announce themselves loudly. A missed deadline, an unhappy client, a supplier who has not been paid. The purchase order problem is quieter. Work starts on a telephone call, a member of staff is allocated, costs are incurred, and the order that should have justified all of it arrives three weeks later, or arrives with the wrong value, or does not arrive at all. By then the organisation has already committed itself, and the conversation about payment becomes a negotiation rather than an administrative step.

Controlling this does not require a heavy process. It requires a short check performed consistently before anyone is committed, a clear method for handling the occasions when the check cannot be completed in time, and a record that shows what was agreed and when.

Cover is a control, not a courtesy

A purchase order is often treated as a formality that follows the commercial conversation. In practice it is the point at which the client organisation confirms three things at once: that the work is wanted, that a named person is authorised to request it, and that funds have been identified to pay for it. Without that confirmation, the service provider is carrying the client's internal approval risk on its own balance sheet.

That risk is rarely obvious at the outset. It becomes visible when an invoice is rejected because the order number does not match, when a buyer says the value exceeded their delegated authority, or when the finance team reports that the relevant budget line closed at the end of the previous quarter. Each of these is recoverable, but each costs time, goodwill and, frequently, margin.

A five-point check before mobilisation

The check should be quick enough to complete within a working day and specific enough that two different people would reach the same conclusion. Five points are usually sufficient.

The order number itself. Record it exactly as issued, including any suffix or call-off reference. Framework arrangements and multi-site contracts often produce a parent number with separate call-off numbers beneath it, and invoicing against the wrong level is a common cause of rejection.

The value and its limit. Confirm the total authorised value and whether it is a fixed sum or a ceiling. Where the order is a ceiling, check that the expected hours, days or deliverables sit comfortably beneath it, with a margin for the variations that always appear.

The expiry date. Orders expire. A purchase order raised for a financial year, or for a defined programme, will not necessarily cover work that runs past that boundary. Note the date and diarise a review point well before it arrives.

Scope alignment. Read the description on the order and compare it with what has actually been requested. A one-line description covering "consultancy support" may be too vague to support a specific piece of work, and a mismatch discovered at invoice stage is far more expensive than one resolved at the start.

The authorised requester. Identify the individual who raised the order and confirm that they hold the authority to do so. Where a request has come from a project manager but the order was raised by a procurement function, make sure the two are aware of each other.

Where all five points align, the work can proceed and the details should be recorded. Where any point is unclear, the work waits, and the query is raised in writing.

Where cover usually breaks down

Three patterns account for most difficulties. The first is the phase extension: a project that was ordered in stages, where the next stage begins before the next order is issued because everyone assumes it will follow. The second is the framework call-off, where the parent agreement exists but the specific instruction has not been placed against it. The third is the informal variation, where a client contact asks for additional work in conversation and the request is absorbed into the delivery team's workload without any commercial record.

None of these is dishonest. Each is a small, reasonable-seeming shortcut that transfers risk quietly from the client to the provider.

When the request is genuinely urgent

Some work cannot wait for a purchase order. A system failure, a regulatory deadline, a site that cannot open. A blanket refusal to mobilise is not a practical position, and a team that hides behind process during a genuine incident will lose the client regardless of what the paperwork says.

The answer is a documented exception rather than an informal one. Three elements make the difference.

First, obtain written instruction from the client, even if it is a short email confirming the request, the likely value and the name of the person authorising it. This is not a substitute for an order, but it establishes that the work was requested and by whom.

Second, agree an internal limit on what may be committed before formal cover arrives. A capped mobilisation, sufficient to stabilise the situation but not to deliver the full scope, keeps exposure bounded and gives the client's finance team a realistic window to issue the order.

Third, record the exception and set a review date. Someone senior should be able to see every item of work currently running without a valid order, how long it has been in that state, and what has been committed. Exceptions that are visible get resolved. Exceptions that are not become the norm.

The purchase order log

A single register, maintained by one named person and reviewed weekly, prevents most of the difficulty described above. It does not need to be elaborate. For each live instruction, record the client, the order number, the value and type, the expiry date, the scope summary, the requesting contact, the date work started, and the invoice status.

Two fields do most of the work. The expiry date allows the team to see renewals approaching before they become urgent. The start date without an order field makes exposure visible rather than assumed.

Reviewing the log weekly, alongside the invoicing schedule, closes the loop. Any instruction approaching its value limit, nearing expiry, or still awaiting an order number should be raised with the client contact at that point, not at the point of invoicing. A short written note asking for confirmation is far easier to send in week two than a disputed invoice is to defend in month four.

A discipline, not a blockade

The purpose of the check is not to slow delivery down. It is to ensure that the work the organisation performs is work it will be paid for, on terms both sides understood at the outset. Teams that apply the check consistently tend to find that clients respect it. It signals that the provider manages its commitments carefully, which is generally the quality a client is looking for in the first place.

The first hour of a new instruction is the cheapest moment to ask the question. After that, the answer becomes progressively harder to obtain and considerably more expensive to live without.