A workplace adjustment remains open until there is a usable answer

## Follow the request through the organisation

Our programme began with eighteen employee requests for changes to workplace access or working arrangements. It crossed properties we owned and estates we managed for other owners. The first summary made the work look substantially complete because consultations had taken place. Employees had been heard, managers had attended and proposed responses had been recorded. Those were necessary steps. They were not the same as an implemented arrangement that a colleague could use when arriving for work the next day.

The difference is easy to lose when a programme moves through several functions. HR can complete a conversation, property colleagues can complete an assessment and an operating manager can submit a proposal. Each team may accurately report its activity as finished while the request itself remains unanswered. The employee experiences the whole sequence, including the gaps between functions. I wanted one account that followed the request rather than several accounts that each ended at the boundary of a department's task.

That did not mean giving HR authority it did not possess. A physical adaptation required qualified examination, relevant permissions and proper acceptance. A working arrangement needed to fit the actual work and be discussed with the person concerned. Health information, where genuinely needed, required appropriate handling and professional involvement. The people function could coordinate responsibility and support a decision. It could not turn a well-intentioned proposal into a technical certificate or decide privately that an arrangement must be suitable because it had been funded.

Managers asked for a common completion date. They needed to plan resources and wanted the programme to have a definite end. I understood that request. An open-ended initiative can become a way of avoiding difficult decisions. But a deadline should identify when a responsible person will decide or explain the next step, not create a reason to relabel an unresolved request as complete. We needed a timetable that strengthened accountability without asking the report to describe something the workplace had not yet delivered.

The employee's role also needed care. Consultation should give the person a voice in what would be useful, without making them responsible for negotiating every internal boundary. A colleague should not have to discover which property owner controls a change or repeatedly explain private circumstances because one function has handed the file to another. We established a continuing responsible contact for each request and limited the management account to information needed to understand progress and decisions. The programme was about access to work, not public disclosure of personal histories.

## Distinguish progress from an implemented arrangement

The approved programme total was ₹84 lakh. Seven requests reached implemented physical adaptations, and six reached agreed working arrangements. Five remained unresolved at the review date. These categories accounted for all eighteen requests. They did not establish that one form of response was inherently better than another. A working arrangement could be the appropriate answer to a person's circumstances and the work's requirements. A physical change could be valuable while still requiring follow-up about its practical use. The report needed precision without turning its categories into a hierarchy of inclusion.

The five unresolved requests remained visible to the executive team. Some depended on further assessment or decisions involving another owner. We did not interpret the property boundary as a completed refusal or assume that a colleague should simply accept the delay. The employer still needed to examine available options and its actual obligations with the relevant advisers. The account could explain why a particular step was pending without treating the explanation as the end of responsibility. A reason for delay and a satisfactory response are different things.

I also separated approval of expenditure from evidence of completion. The ₹84 lakh programme figure described the authorised resource; it was not a claim that every item had been spent or that all requests were resolved. Finance retained the proper expenditure account, while property and operating owners retained their acceptance responsibilities. This prevented a familiar reporting shortcut in which a funded initiative becomes a completed outcome simply because the budget has reached a senior approval meeting. The colleague needs the arrangement, not merely the authority to spend on one.

The revised account was less convenient for an announcement. Thirteen implemented or agreed arrangements sat beside five open requests and continuing work. I considered that a stronger description of management's responsibility. It allowed directors to ask what decision remained, who could make it and what alternatives were being considered. It also prevented the people team from seeking credit for the most visible completed work while leaving the harder cases outside the main account. A programme should not define success by excluding the people for whom implementation is most complicated.

We made no claim about improved health, productivity or universal satisfaction from those immediate outcomes. An appropriate arrangement can matter greatly without supporting a broad causal statement in a leadership biography. The next question was whether it remained useful in practice and what needed to change if the work or circumstances changed. That follow-up belonged in a proportionate individual process. It did not require collecting every personal detail or turning employees into proof points for a public corporate narrative.

## Keep responsibility where authority is divided

Managed properties make the division of authority visible, but similar divisions exist inside a single company. One executive may control the employment offer, another the building budget and another the operating method. If each waits for the others to provide a complete answer, the person affected can remain in the middle indefinitely. The leadership task is to make the decision path workable while respecting the authority needed at each stage. Coordination is not the same as taking over somebody else's professional judgement.

Meera Velqomi helped distinguish requests that could proceed through our own estate arrangements from those needing a separate owner's decision. That distinction was useful because it identified real dependencies. It would have become harmful if we had used it to divide employees into those whose access mattered to us and those whose requests belonged entirely elsewhere. The employment relationship remained ours. We needed to consider the available response in the actual circumstances, including qualified advice about obligations, without pretending to control property that another party owned.

For a board, the relevant oversight question is how management follows a material employee request across those boundaries. Directors do not need to choose an adaptation or assess a person's health. They can ask whether responsibility remains clear, whether the reported stage is accurate and whether the unresolved cases receive the attention and resources needed for a decision. They should also expect management to protect private information. A useful board account can show the nature of a dependency without exposing the individual behind it unnecessarily.

My own improvement would be to define the outcome categories before the programme begins. We initially allowed completed conversations to carry too much weight because they were easy to count. A more careful design would have made consultation, assessment, approval and implementation visible from the start, with the employee's practical question running through them. That would not remove every delay. It would make a delay harder to hide inside a reassuring summary and easier to bring to the person who could help resolve it.

The lesson I carry is that access work should end with a usable answer, not merely with the last meeting scheduled by one department. Some answers require further work, and some proposed routes may prove unsuitable after proper assessment. Those realities deserve an honest account. The company can remain responsible for a request without claiming control over every condition. What it cannot do credibly is announce that the process is complete while the colleague is still trying to discover how the workplace will actually become accessible to them.