Before the Weekend: A Midweek Pause for Project Approvals

Friday afternoon has a particular energy in UK project offices. The inbox is thinning, the site team is packing up, and someone forwards a purchase order with the line: 'Can you approve this before you go?' It feels like progress. It is often the opposite.

A sign-off that lands at 4:45pm on a Friday has almost no room for a second look. If the cost code is wrong, the supplier is on different payment terms, or the delivery date clashes with a shutdown, nobody finds out until Monday. By then the supplier may have booked the slot, the invoice may be in the queue, and the person who could have answered the question is on annual leave.

That is the case for a midweek pause: a simple cut-off for non-urgent approvals, purchase orders and supplier commitments, placed somewhere around Wednesday afternoon. Not a bureaucratic gate. A breathing space.

The Friday illusion

Late-week approvals look efficient because they clear the list. But they often transfer risk to the weekend, when nobody is checking. A project lead signs off a variation on Friday morning, the supplier confirms it by lunchtime, and the site team discovers on Monday that the access date was never agreed. The paperwork said yes. The practicalities said wait.

The cost is rarely dramatic. It is a few hours of rework, a supplier chasing payment, a delivery that has to be rebooked. But those small costs stack up, and they tend to land on the same people who are already busy.

A midweek pause does not stop decisions. It moves the cut-off to a point where a mistake can still be caught by someone with the right information.

What the pause actually covers

The rule should be narrow. It is not about every email or every question. It applies to commitments that are hard to unwind: purchase orders above an agreed threshold, new supplier setups, contract variations, invoice approvals that release money, and any delivery date that affects the site programme.

Low-value, repeat items can carry on as normal. The point is to protect the decisions that would be awkward to reverse, not to create a queue for its own sake.

A short sign-off routine

A Wednesday checkpoint works best when it is short and specific. Book fifteen minutes, open the approval list, and run three checks.

• The project lead checks scope and timing. Does this match the plan, the site sequence and the client's expectations?
• Commercial or finance checks value and paperwork. Is the budget code right, are the payment terms agreed, and does it need a purchase order?
• The delivery or site lead checks practicality. Can we receive it, store it or install it when the supplier says we can?

If all three are clear, approve it the same day. If one is missing, park it until Monday and say why. That is the whole routine. No form, no committee, no extra meeting.

A shared note with three columns — item, checker, status — is usually enough. The value is not the document. The value is that someone specific has looked at the detail before the week ends.

What waits until Monday

Not everything needs to wait. Urgent safety issues, site stoppages and contractual notice deadlines should still move. But most other things can sit for two days without harm.

Price comparisons that are still being gathered, supplier questionnaires, contract reviews without a hard deadline, and approvals where the requester is still collecting information can all wait. Monday morning is a perfectly good time to look at them with fresh eyes.

The test is simple: if nothing bad happens because this waits until Monday, it waits.

Friday exceptions without the faff

A rule that cannot bend will break. Genuine Friday exceptions exist: a safety concern, a supplier about to lose a slot that affects the programme, or a notice that must be served by a contractual date.

Keep the exception process deliberately light. One nominated approver can say yes. The requester writes a two-line note in the project log: what was approved, and why it could not wait. On Monday, the team reviews it for ten minutes. No blame, no lengthy post-mortem.

That is enough to keep the rule credible without turning it into a bureaucratic exercise.

Why this is not bureaucracy

A midweek pause is a habit, not a policy manual. It gives the week a shape: early week for decisions, midweek for checks, Thursday and Friday for finishing and planning. It also protects the weekend, which is when most people need to switch off properly.

Project teams in the UK are already dealing with enough process. This one earns its place because it prevents the Monday morning scramble that nobody enjoys.

A one-month test

If you want to try it, pick one project and run the pause for four weeks. Note how many errors were caught on Wednesday, how many Friday approvals were genuinely urgent, and how many people complained. Adjust the threshold and the cut-off time to suit the team.

The aim is not to make Friday quiet. It is to make Monday less expensive.