Managing Reasonable Adjustments

Managing reasonable adjustments means having a clear process for receiving a request, understanding the barrier, deciding what is reasonable, assigning ownership, implementing the adjustment and reviewing whether it works.

It is the difference between a supportive conversation and a reliable system.

A form is not a process. A record is not implementation. A policy is not proof that support is working.

Reasonable adjustment practice is becoming more urgent. On 21 May 2026, the Work and Pensions Committee called for a two-week legal deadline for employers to respond to disabled workers' reasonable adjustment requests and for refusals to be explained in writing.

That recommendation is not current law. It is still significant because it shows the direction of travel: faster responses, clearer records and more accountability.

For Calling All Minds, this reinforces the central point. Organisations do not only need awareness of reasonable adjustments. They need infrastructure that helps them respond.

These are not minor admin issues. They shape whether reasonable adjustments actually happen.

Repeated disclosure happens when a neurodivergent or disabled person has to explain their condition, barriers or support needs again and again.

It often happens at transition points: recruitment, onboarding, new manager, occupational health referral, performance review, internal move, return from absence or workplace change.

The problem is not that people ask questions. The problem is that the organisation has no trusted way to hold relevant context, share it appropriately and update it when needed.

That turns disclosure into a burden on the employee rather than a managed organisational process.

The purpose of maturity is not bureaucracy. The purpose is reliability.

A strong workflow protects everyone. The employee is not left chasing. The manager is not left guessing. HR is not left piecing together fragments later.

The record should be proportionate. It should not collect unnecessary personal detail. It should make support easier to deliver.

An employee has an occupational health report recommending changes to workload planning, meeting frequency and communication. The manager reads it, HR stores it, and the employee assumes something will happen.

Weeks pass. No one has translated the recommendations into actions. No owner has been named. No review date has been set. The report exists, but nothing has changed.

This is a common failure. It is not a lack of information. It is a lack of workflow.

The missing step is operational: who will do what, by when, and how will the employee know it has happened?

An adjustment passport can reduce repeated disclosure by recording a person's needs, barriers and agreed adjustments. It can help preserve context when the person changes manager, team or role.

But an adjustment passport is strongest when it sits inside a process.

A static document may say what someone needs. A managed workflow helps ensure the request is reviewed, actioned, tracked and updated.

This is the distinction that matters: the passport holds the context, but the process delivers the support.

AXS Passport is designed to help organisations manage adjustment requests more clearly and consistently.

It supports the move from scattered conversations to a structured adjustment workflow. That means capturing the barrier, recording what has been requested, documenting what has been agreed, assigning ownership, tracking progress and reviewing support over time.

For employees, this can reduce repeated disclosure and uncertainty.

For managers, it creates a clearer route from concern to action.

For HR and inclusion teams, it gives better visibility of where adjustment processes are working and where they are breaking down.

For organisations, it turns reasonable adjustments from isolated events into part of a wider inclusion infrastructure.

Good implementation is often calm. It removes uncertainty and makes support feel ordinary rather than exceptional.

Last checked: May 2026