Why Adjustments Stall

The agreement means almost nothing

A manager says yes. HR confirms it in an email. The employee feels, briefly, like the system has worked. Then three months pass, and the chair that goes up and down is still not there.

This is not unusual. The gap between a reasonable adjustment being agreed in principle and that adjustment actually arriving is one of the most consistent failures in workplace inclusion — and it is almost never caused by bad faith. It is caused by process architecture that nobody designed with adjustments in mind.

Understanding where requests die is the first step to building something that works.

The handoff problem

Most reasonable adjustment requests begin in HR and end somewhere else: facilities, IT, procurement, a line manager's budget. That transition — the handoff — is where the majority of requests stall.

HR confirms the adjustment is appropriate and lawful. Then the request moves to the person or team who can actually action it, and at that point it enters a completely different system with different priorities, different timescales and, critically, no obligation to treat the adjustment as urgent. A facilities team managing a building programme has no particular reason to reprioritise a desk installation ahead of a scheduled office refurbishment unless someone with authority tells them to.

The structural problem is that HR owns the decision but not the delivery. Facilities owns the delivery but not the decision. Nobody owns both, and nobody is accountable for the gap between them.

Where the approval chain adds delay

Even when both sides are willing, the approval chain itself introduces lag. A height-adjustable desk typically requires a quote, a budget code, sign-off from a line manager, possible sign-off from a department head if it exceeds a delegated spending limit, and a purchase order raised through procurement. In a large organisation, each of those steps can take a week. Together they can take six.

The request rarely fails at any individual step — it just sits in an inbox waiting to become someone's priority. Approval chains work well for planned expenditure. They were not built for time-sensitive individual needs, and they apply the same friction to a £400 keyboard as to a £40,000 building alteration.

Some organisations address this by creating a central access fund — a ringfenced budget that sits outside departmental cost-centres and can be drawn against without a line manager's approval. This removes the most common single point of failure, which is a manager who is sympathetic but reluctant to take the budget hit. The desk that goes up is cheaper than the one that doesn't — but it is never free, and who pays for it shapes whether it happens at all.

The specific moment most requests die

If you had to name one moment, it is this: after HR has confirmed the adjustment and before facilities or IT has received a formal instruction with a completion date attached.

That gap — sometimes a day, sometimes a month — is the space in which the request floats. HR considers it done. Facilities does not yet consider it started. The employee is waiting. Nobody is chasing because nobody has been assigned to chase.

The fix is procedural rather than motivational. Every confirmed adjustment needs a named owner, a target completion date and a check-in mechanism — not a wellbeing conversation, a practical one: has the equipment arrived, has access been changed, does the software work? Organisations that close this gap tend to have done one specific thing: they have made the adjustment tracker a live document rather than a filed email, and they have given someone — usually a named HR business partner or a dedicated access coordinator — the standing to follow up across team boundaries.

What good process looks like

The organisations that get this right share a few structural features. A central budget that can be accessed without departmental approval. A single named owner for each request from agreement through to completion. A standard completion timeframe — thirty working days is a reasonable benchmark for most adjustments — with escalation if it is missed. And a close-out step: someone confirms with the employee that the adjustment has actually resolved the barrier, not just that the equipment has been delivered to a building.

That last step is rarer than it should be. A screen reader installed on the wrong profile, a parking permit issued for the wrong bay, a reworked shift pattern that looks right on paper and fails in practice — these are completions that are not completions. Without a close-out, the adjustment is ticked off and the barrier remains.

The process map, then, runs through agreement, assignment, approval, procurement, installation and confirmation. Most organisations have a version of the first step and a weak version of the rest. The question to ask of any adjustment system is not whether it agrees requests — it is whether it tracks them, owns them and closes them out.