Stop Waiting for a Diagnosis: Build a Baseline Support Menu at Work

Diagnosis isn’t a gate to dignity. In UK workplaces, many people who would benefit from support won’t have a formal label any time soon. Waiting for paperwork creates avoidable friction: delayed productivity, preventable stress, and unnecessary attrition. A better approach is to make small, lawful, needs-led adjustments available to everyone—immediately. I call this a baseline support menu.

The problem with “diagnosis-first”

When support hinges on a clinical label, three things happen. First, people who are masking—often to meet unspoken norms—keep struggling out of sight. Second, managers defer simple fixes (“let’s wait for Occupational Health”), even when the solution is obvious. Third, teams lose momentum while decisions sit in limbo. None of this is required by law, nor is it good management.

What the law actually expects (UK)

Under the Equality Act 2010, employers must make reasonable adjustments to remove or reduce substantial disadvantage. Guidance from ACAS reinforces a simple principle: constructive conversations plus proportionate adjustments. In practice, that means you can—indeed should—act on need rather than waiting for proof of identity. A baseline menu operationalises that principle: it creates clarity, consistency and speed, while preserving a path to bespoke support when needed.

What a baseline support menu is

Think of it as seatbelts for cognition: a published, opt-in list of day-to-day supports anyone can use without disclosure. It’s short, plain-English, and embedded in everyday workflow. Typical items include quiet-work options, clearer information formats, predictable deadlines, short recovery buffers around meetings, and access to common tools (for example, text-to-speech, dictation, or screen-reader-friendly documents). Nothing exotic—just thoughtful defaults that reduce cognitive load for everyone.

How to implement without drama

Start with a one-page draft. Name the intent (“support based on need”), list each support with a single sentence on how to use it, and name an owner (IT, Facilities, People Team). Meet once with those owners to confirm what can be “instant yes” and what needs a lightweight request. Publish the page on your intranet and announce it at an all-hands. Then walk managers through a short script: “You don’t need a diagnosis to use our support menu. Pick what helps; if you need something extra, we’ll sort it together.”

Crucially, treat this as a pilot, not a policy tablet of stone. Invite feedback, track uptake, and adjust quarterly. The iteration loop is where most of the value hides.

Will people abuse it?

In my experience, no. When expectations are clear and the menu is modest, usage patterns stabilise quickly. The teams that gain the most are those with complex workflows and heavy meeting loads—where clarity and recovery time translate directly into better output.

How to measure impact (without boiling the ocean)

Pick a small set of indicators you already collect: task throughput, error rates, decision clarity after meetings, and short pulse scores on cognitive load. Look for trend shifts after launch, not perfect attribution. If you can, add stay-interview prompts about “work friction” to capture qualitative change.

Where bespoke adjustments still fit

A baseline menu doesn’t replace individual adjustments; it reduces the number of people who need to climb that hill. When someone needs something outside the menu—specialist software, equipment, or a change to role expectations—route that through your established HR/Occupational Health process. The win is that everyday supports no longer clog that pipeline.

The leadership signal that matters

Publishing a baseline menu tells your people: we design for reality, not for labels. It normalises help-seeking, reduces reliance on heroic masking, and gives managers a practical way to act on inclusion between formal initiatives. That is how cultures shift: not with grand statements, but with small, reliable promises that make work feel doable on a Tuesday afternoon.