A practical reflection for anyone facing exclusion because of a medical condition, disability, health limitation, or access need — and for managers who need to respond differently.

“A right you cannot recognize is difficult to use. A right you cannot name is easy to bypass. And a right you admire but never practice remains politically underdeveloped.”

I wrote those words recently in a reflection on the Charter of Fundamental Rights of the European Union. At the time, they belonged to an argument about civic education: that rights should not remain beautiful abstractions, admired from a distance, quoted on official days, or placed ceremonially inside democratic language while people are left unable to recognise them in the ordinary settings where they are most needed.

Then life offered the kind of example no one wants to receive.

My own case happened inside an EU-funded project. REDefine is a partner organisation in an international consortium coordinated by another organisation in another country. A physical, in-person training was scheduled in Poland. My participation would require travel. For medical reasons, I cannot travel at this moment.

That is the factual background. But it is not the full meaning of the situation.

The important distinction is this: the problem is not that I cannot do the work. I can do the work. I have done core development work for this project, including the development of modules and the technical side of the digital structure. I can still contribute. I can still deliver training input digitally. I can still fulfil my role. The barrier is not competence, commitment, or professional availability. The barrier is physical travel at this moment, for medical reasons.

Treating those two things as the same — inability to travel and inability to work — is precisely how exclusion begins to disguise itself as management.

Discrimination does not always arrive with cruelty on its face. Often, it arrives dressed as logistics, budget realism, risk management, project protection, team efficiency, or even concern. It says: “We understand.” It says: “Health comes first.” It says: “Maybe someone else can do it.” It says: “We are only trying to protect the project.”

That is why rights literacy matters. Not because every difficult situation is automatically unlawful discrimination, and not because rights language should be used carelessly. It matters because many people experience discrimination first as confusion. Something happens, and they feel humiliated, pressured, exposed, reduced, or quietly pushed out. The surrounding language insists that nothing serious happened. It was only a practical solution. It was only a management issue. It was only a budget concern. It was only a suggestion.

The gap between what happened and what it is called is where many forms of exclusion survive.

This article is not only about EU-funded projects. My case happened inside one, and that matters because EU-funded work often carries explicit commitments to inclusion, equality, accessibility, participation, and non-discrimination. But the pattern I am describing is much wider. It can happen in universities, NGOs, public institutions, companies, schools, creative industries, remote teams, grant-funded initiatives, consultancy contracts, and ordinary workplaces.

The setting may change. The mechanism is often the same. A person raises a legitimate health-related barrier, and instead of asking how that person can continue participating, the organisation asks how the work can continue without them.

That is not inclusion.

That is exclusion arriving as project management.

This article is written in two parts. The first is for people who find themselves on the receiving end of discrimination, exclusion, or humiliating “solutions” when they disclose a medical condition, disability, or health-related limitation. The second is for project managers, coordinators, employers, and organisational leaders who need to understand what should happen instead.

It is not legal advice. It is a practical, rights-aware reflection from someone who has now experienced this from the inside — and who has also led more than 40 projects across her career.

Because I know project management is complex. I know budgets are limited. I know deadlines matter. I know international work has rules, risks, partner obligations, and reporting pressures. I know that project management is not performed in ideal conditions.

And still: exclusion is not a management solution.

Part I — When You Are the Person Affected

1. The Medical Limitation That Should Have Been Handled Differently

The first harm was not only the proposed “solution.” It was the setting in which the situation was handled.

A medical limitation affecting travel should be treated as sensitive. It should be discussed privately, respectfully, and with a clear intention to understand what the person can still do, what barrier exists, and what adjustments might allow the work to continue. Instead, this situation was handled publicly, during a digital call with more than ten people from all partner organisations.

That kind of setting matters. Medical conditions and accessibility limitations are not ordinary logistics. They touch dignity, professional reputation, and a person’s sense of safety inside a team. When a private limitation becomes a public agenda item before a solution has even been explored, the affected person is no longer participating in a professional coordination discussion. The meeting becomes a theatre of accountability in which the person with the limitation is implicitly asked to justify why their body has interrupted the plan.

The normal procedure should have been simple. The coordinator should have spoken privately with me and with REDefine. The coordinator should have asked what work I could still do, what travel limitation existed, what alternatives were possible, and what project rules or funding authority guidance might be relevant. Only after that should the wider partnership have been included, and only in a way that protected dignity and focused on the solution.

That is not what happened.

1.1. The Psychological Setting: A Comrades’ Court, Not a Coordination Meeting

The psychological setting matters. This was not a neutral conversation among equals. It was a digital call with more than ten people from all partner organisations, where two representatives of one organisation — me and my director — were made to respond publicly to a situation that should first have been handled privately. The imbalance was immediate: the whole consortium on one side, the affected partner on the other.

In that setting, the conversation did not feel like coordination. It felt like a kind of Soviet-style comrades’ court: not a space designed to solve a problem, but a ritual designed to assign blame, expose the accused, destabilise them, and make them carry the emotional weight of a collective failure.

I use that comparison deliberately. The point of such a setting is not genuine inquiry. It is public pressure. It turns a complex situation into a moral scene with one visible “problem” at the centre. The person or organisation being questioned is no longer treated as a partner in solving the issue, but as the object through which the group processes its anxiety, frustration, delay, or fear of consequences. That is why the format itself was harmful. Before any solution was properly explored, the meeting had already created a psychological frame: REDefine had to defend itself, and I had to experience my medical limitation as though it were a threat to others.

A professional coordination process should do the opposite. It should reduce panic, protect dignity, clarify facts, and create options. It should separate the person’s medical limitation from wider project delays. It should ask what can still be delivered, what accommodation is possible, what risks are real, and what procedure must be followed. Instead, the public format intensified pressure and humiliation. It transformed a manageable project issue into a spectacle of accountability.

That is not transparency. That is public pressure disguised as coordination.

The need for dignity does not mean that a project, organisation, or workplace must ignore operational realities. Of course the work must continue. Of course timelines matter. Of course budgets matter. A professional process begins with private clarification, then moves toward solution design, and only then communicates what the wider team needs to know. The only thing the group needs is a clear and respectful implementation plan.

When that sequence is reversed, the affected person and/or organisation becomes the site where organisational anxiety is performed. The meeting stops being about solving the problem and becomes about making someone answer for the discomfort their limitation has created. That is precisely why procedure matters. Good procedure is not bureaucracy. In sensitive situations, good procedure is a form of care.

2. When Medical Need Is Turned Into Moral Judgment

The second harm came through the language used in the meeting.

A member of the consortium referred to her own personal loss and said that, despite it, she continued to participate in life. I do not question the reality or pain of anyone’s personal loss. Personal loss can be devastating. People deserve support when they experience grief, trauma, emotional distress, or any destabilising life event. But that comparison had no appropriate place in a professional discussion about my medical inability to travel.

The effect of that comparison was to move the conversation away from accessibility, reasonable accommodation, and project procedure, and toward a moral comparison about endurance. The implication was not subtle: some people suffer and continue; others fail to do so. Some people are strong enough to keep going; others are not. Some people show dedication through hardship; others become inconvenient.

That is not an inclusion framework. That is a moral hierarchy of suffering.

A physical limitation is not a lack of dedication. A medical condition is not a character defect. Needing accommodation is not weakness. When a person’s health-related limitation is publicly compared with someone else’s capacity to “continue,” the conversation becomes humiliating. It turns rights into grit. It turns support into judgment. It turns a concrete physical barrier into a personal test of endurance, resilience, loyalty, or worth.

2.1. Grit Is Not Accommodation

This is one of the most dangerous things that happens when discrimination is disguised as management. The actual issue — what barrier exists, and what reasonable adjustment could allow the person to continue — gets replaced by a different, more punitive question: why can’t you manage like others do?

But human beings do not have identical bodies, identical health conditions, identical histories, identical support systems, identical risks, or identical recovery timelines. All of us are entitled to support when we need it: medical, emotional, institutional, and procedural. If someone needs more emotional support or a longer leave because of grief, there are procedures for that. If someone cannot travel because of a medical condition, there are procedures for that too. These situations should not be placed in competition with each other.

The question should never be: who is stronger?

The question should be: what barrier exists, what support is needed, and what reasonable solution protects both the person and the work?

3. The False Inclusion of “Hire Someone Else”

Then came the proposed “inclusivity” option: hire other people.

On paper, that may sound flexible. In reality, especially in a low-funding project or small organisation, “hire other people” does not magically create new money, new capacity, or new continuity. It usually moves scarce resources away from the person who has been doing the work. It transforms a medical limitation into a professional penalty. In practical terms, it may mean: lose your role, lose your income, lose your authorship, lose your place in the work you have already built.

This is why the distinction between accommodation and replacement matters so much.

3.1. Inability to Travel Is Not Inability to Work

The problem was never that I could not do the work. The problem was that I could not travel. Those are not the same thing.

I had done core development work for the project. I had worked on modules. I had contributed to the technical side of the digital structure. I could still provide the training input digitally. The essential professional capacity remained. What was temporarily impossible was physical displacement to Poland at that moment.

This distinction is crucial for anyone facing a health-related barrier. Inability to attend in person is not necessarily inability to contribute. Inability to travel is not necessarily inability to train. Inability to work under one format does not mean inability to work under all formats. When an organisation treats one access barrier as total professional incapacity, it is often not evaluating the person fairly. It is using the default format as a gatekeeping mechanism.

3.2. Accommodation Is Not Replacement

Accommodation asks: what conditions would allow this person to continue participating?

Replacement asks: who can do this instead?

Those are not the same question.

A replacement may sometimes be necessary in professional life. People leave jobs. Contracts end. A person may become fully unavailable. A project may need to adapt. But replacement should not be presented as the default “inclusive” response when the person can still perform the essential work through adjusted conditions. If the person has done the core work, remains able to do the core work, and only cannot meet one physical condition — such as travel — then replacing that person is not accommodation. It is displacement.

This is where exclusion often becomes elegant. It stops sounding like exclusion and starts sounding like efficiency. It says: “Let us be practical.” It says: “The programme allows it.” It says: “You can contract someone else.” But a technical possibility is not the same thing as a fair, feasible, or rights-respecting solution.

3.3. Why Replacement Can Mean Loss of Work

In this case, the financial reality matters. This is a low-funding project: five entities sharing a total budget of approximately €250,000 over two years. REDefine’s budget is around €45,000 for the whole project period, and that includes all categories of expense, not only staff costs. The real staff-cost capacity is below €30,000 for two years. A senior expert with the skills required for this kind of work costs far more than that. So the idea that REDefine could simply hire equivalent expertise mid-project was detached from the financial reality of the project.

There is also a labour and operational reality. Portugal’s labour context does not make it simple or desirable to treat core staff as disposable gig-style units. Replacing people is not automatic. It can involve legal, financial, continuity, ethical, and organisational consequences. Even where external contracting is technically possible, it does not solve the knowledge-continuity problem. You cannot simply plant a new person in the middle of a project and expect them to perform as though they had developed the work from the beginning.

But the deepest issue is moral. If a person has done the work, continues to be able to do the work, and only cannot travel physically for medical reasons, replacing that person is not an inclusive solution. It is the opposite. It punishes the person for being ill. It removes the person precisely at the moment when accommodation should be considered.

4. When Organisational Size Becomes a Weapon

The conversation became even more painful when the same consortium member framed the issue through the language of “small organisations like you.” That phrase may sound minor to someone who says it casually, but in a partner meeting it is not neutral. It attaches value to size. It implies that smaller organisations are somehow less capable, less professional, less serious, or in need of correction by larger or more established entities.

REDefine is not a university. Our institutional dimension is different. But we have a defined operational role in the consortium. We have delivered core work. We are responsible for the digital backbone of the project. We should not be spoken to as if our size reduces our legitimacy.

4.1. Partnership Does Not Mean Hierarchy by Size

In a consortium, partnership does not mean hierarchy by size. Smaller organisations are not less legitimate partners. They are partners with different structures, budgets, legal realities, and operational constraints.

This pattern is not limited to EU projects. Small NGOs are talked down to by universities. Freelancers are treated as disposable by institutions. Small businesses are lectured by larger contractors. Employees in less powerful roles are told what is “realistic” by people who do not understand their workload, contract, budget, national law, or personal circumstances.

That kind of condescension does not merely wound pride. It changes the power dynamic of the room. It suggests that the organisation receiving the advice is not only facing a practical problem, but also failing some imagined standard of professional maturity. It turns a legitimate boundary — we cannot simply replace a person who can still do the work — into evidence of poor management.

4.2. External Partners Should Not Prescribe Internal HR Decisions

Another organisation is not entitled to publicly instruct a partner in another country on how to manage staffing, employment arrangements, or internal HR decisions. It is legitimate to discuss project deliverables, risks, timelines, and possible implementation options. It is not legitimate to casually tell another organisation to “hire other people” as if national labour law, organisational budget, internal structure, and continuity of expertise did not exist.

The claim that someone supports other small organisations elsewhere does not solve this. We do not know in what context that support happens, under which national legislation, with what budgets, what employment structures, what project types, or what contractual arrangements. Experience in one context cannot be used as a universal management rule for another.

Project management requires context-awareness, not generic advice presented as superiority.

5. When Accommodation Becomes a Threat of Replacement

The situation was further escalated by the suggestion that, to protect the other partners, they might look for other organisations to support them.

At that point, the conversation had moved from “you personally can be replaced” to “your whole organisation can be replaced.” That is not a small escalation. A medical limitation had become a basis for questioning not only my role, but REDefine’s place in the project. The implication was devastating: because one person had a medical limitation preventing physical travel, the entire organisation could be treated as a risk to be removed.

5.1. A Medical Limitation Is Not a Breach of Partnership

A medical limitation is not a breach of partnership. Not being able to travel at a given moment does not mean that a person or organisation is unable or unwilling to fulfil their responsibilities. If the work can still be done, if the contribution can still be delivered, and if reasonable alternatives exist, then the managerial task is to explore those alternatives — not to escalate immediately toward replacement.

Partner replacement is not an inclusion measure. “Protecting the consortium” cannot become a polite formula for isolating and removing the partner who needs accommodation.

5.2. Risk Management Should Never Become a Public Threat

Replacing a partner in an international project is a serious governance matter. It should require formal assessment, documentation, review of the contract or grant agreement, communication with the relevant authority where applicable, and evidence that the organisation is unable or unwilling to fulfil its obligations. It should not be raised casually in a public meeting because one person cannot physically travel for medical reasons.

6. When Project Delays Are Dumped on the Person Who Needs Accommodation

There was another layer beneath all of this. The project had already experienced long delays before my health condition became an issue. For a long period, very little moved. Deliverables were delayed. The content REDefine needed in order to complete the digital development was only received from partner organisations in February this year. Our digital structure had been ready for a year before that. Ironically, this is the only project deliverable that was produced on time.

Yet in the public meeting, pressure was placed on us to say what percentage of the platform was ready, with the implication that if it was not ready, the project might fail, and that my inability to be physically present at the training was somehow part of that risk.

6.1. The End of the Chain Cannot Be Blamed for the Beginning

This is one of the clearest signs of blame transfer. A health-related travel limitation becomes the place where every unresolved project delay is dumped. The person who needs accommodation becomes the symbol of project risk. The partner at the end of the production chain becomes responsible for delays created at the beginning or middle of the chain.

But you cannot deliver the digital platform before you receive the content that belongs inside it.

In every project, there are chain-dependent tasks. If Partner A must produce content before Partner B can upload, structure, test, translate, digitise, or integrate it, then Partner B’s timeline cannot be judged without looking at when Partner A delivered. When delayed content arrives late and the technical partner is then expected to produce results “for yesterday,” that is not project management. It is blame transfer.

6.2. Delayed Content Cannot Become an Emergency Accusation

A project manager must understand dependencies. If content is delivered late, the timeline must be revised realistically. If deliverables arrive behind schedule, the chain of responsibility must be mapped honestly. If a partner at the end of the chain is expected to compress one year of work into less than two months because upstream deliverables were delayed, this cannot be treated as that partner’s failure without looking at the full sequence.

Delayed content cannot become an emergency accusation against the partner expected to digitise, structure, or deliver it. “We sent you the content late, but why is the platform not ready?” is not project management. It is pressure without accountability.

6.3. A Medical Limitation Should Not Become the Container for Project Failure

This matters because the discussion of my medical limitation did not happen in a clean, solution-oriented context. It happened inside a wider atmosphere of delay, pressure, and fear of project failure. Instead of separating the issues — the project timeline, late delivery of content, training arrangements, platform readiness, and my medical inability to travel — the meeting collapsed them into one public accusation field. The result was that my health-related limitation became entangled with the consortium’s anxiety about its own delays.

A medical limitation should never become the emotional shortcut through which a group avoids looking at its own management failures.

7. The Care Contradiction: When a Care Project Fails to Practice Care

Perhaps the most painful contradiction is that this happened inside a project aiming to improve care.

The project speaks about the need to improve access to psychosocial support services, help people cope with trauma, emotional distress and mental health issues, and train the community to recognise and respond to mental health needs. It describes deliverables intended to support mental health,emotional well-being, and effective support for vulnerable groups.

That makes the contradiction sharper.

A project about care should know how to practice care. A project about trauma-informed support should not govern itself through public humiliation. A project about vulnerable people should not make people more vulnerable inside its own meetings. A project about emotional well-being should not moralise illness as weakness. A project about inclusion should not respond to a health-related travel limitation by suggesting replacement.

7.1. Care Cannot Be Only a Deliverable

Care cannot be only a project output. It has to be a project method.

A project about care cannot treat care as something exported outward while being absent inward. If a project teaches people to recognise and respond to trauma, distress, vulnerability, and mental health needs, its own coordination practices should reflect dignity, , proportionality, and psychological safety. Otherwise, care becomes a topic, a toolkit, a training module, a dissemination message, but not a culture.

7.2. If Care Disappears When It Becomes Inconvenient, It Was Only Written

Many organisations know how to write care. They know how to put it in proposals. They know how to describe vulnerable groups, psychosocial support, resilience, inclusion, accessibility, participation, and wellbeing. But care is not proven by vocabulary. It is proven by conduct.

The real test comes when care is inconvenient. When someone cannot travel. When someone needs adaptation. When a timeline breaks. When a small partner needs to be respected. When a person inside the team becomes vulnerable, not only the target group outside the project.

If care disappears when it becomes inconvenient, then it was never embedded. It was only written.

Part II — When You Are the Manager, Coordinator, Employer, or Project Lead

1. A Manager’s First Duty Is Not Panic, But Procedure

Now let us look at the same situation from the other side.

I am not the lead of this project. But I have led more than forty projects in my career. I know that project management involves pressure. I know timelines slip, budgets tighten, partners delay, deliverables depend on each other, staff become unavailable, and managers often have to solve problems quickly. I know that in funded projects, a late deliverable can create stress. I know that in small organisations, every person matters. I know that international partnerships are difficult. I know that project management is not performed in ideal conditions.

But project management is not panic. It is not public blame. It is not moral comparison. It is not threatening replacement because someone has a medical limitation.

A competent manager does not turn vulnerability into blame. They turn it into a risk-management question, an accommodation question, and a governance question.

2. Handle Health-Related Limitations Privately First

The first obligation is to handle medical limitations privately. A medical limitation affecting travel, presence, schedule, workload, or format should not be debated in front of the whole team. The correct sequence is to speak privately with the affected person and, where relevant, their organisation or representative; clarify what the limitation is; ask what work the person can still perform; identify possible accommodations; review the contractual, budgetary, legal, and operational implications; consult HR, occupational health, the funder, the project authority, or legal support if needed; and only then inform the wider team or partnership with a neutral and solution-focused message.

The group meeting should not be the first place where such a situation is processed. That is poor management and poor care.

3. Stop Moral Comparisons Immediately

The second obligation is to stop moral comparisons immediately. If someone begins comparing their personal hardship to the affected person’s medical limitation, the manager or coordinator must intervene. Leadership requires saying, calmly and clearly, that the meeting will not compare suffering, dedication, grief, illness, or resilience. The issue before the group is not who has endured more. The issue is what barrier exists, what responsibility the organisation has, and what reasonable solution can protect both the person and the work.

This matters because once a meeting becomes a comparison of suffering, the inclusion process has already been contaminated. Personal grief, trauma, illness, disability, and hardship should never be used as evidence of who is more committed. In rights-aware management, the question is not “Why can’t you push through?” The question is “What conditions would allow you to participate without harm?”

4. Do Not Treat Technical Permission as Real Feasibility

The third obligation is to understand that technical possibility is not real feasibility. The argument “you can hire someone else” is not enough. A contract, programme, or budget line may technically allow staff changes, subcontracting, or substitution. That does not mean every organisation has the money, timing, labour-law flexibility, or operational capacity to make replacement a fair or realistic solution.

This is especially true in small organisations, NGOs, low-funding projects, and specialised work. A large university may have a pool of staff, departments, administrative layers, and contracted experts. A small NGO may not. A company in one country may have one labour regime; an organisation in another country may have a very different one. A suggestion that sounds simple in one context may be impossible, damaging, or legally complex in another.

Managers must understand context before prescribing solutions. External partners may discuss deliverables. They should not publicly prescribe another organisation’s staffing decisions as if national labour law, budget structure, internal responsibilities, and knowledge continuity did not exist.

5. Do Not Prescribe Another Organisation’s HR Decisions

One organisation is not entitled to publicly instruct another partner, contractor, or collaborating body on how to manage staffing, employment arrangements, internal budgets, or human-resources decisions. This is especially true in international work, where partners operate under different legal, cultural, social, financial, and administrative systems.

It is possible to ask whether a deliverable can still be completed. It is possible to ask what alternatives exist. It is possible to ask whether the organisation has another representative who can attend physically. But it is not appropriate to move from those questions into casual instructions about hiring, replacing, dismissing, subcontracting, or restructuring another organisation’s team.

That is not collaboration. It is overreach.

6. Never Treat Replacement as the Default Accommodation

The fourth obligation is to avoid treating replacement as the default accommodation. Replacement may sometimes be necessary, but it should not be the first response to a medical limitation when the person can still perform the essential work through adjusted conditions. The first question should be: can this person still do the work with reasonable adjustments? Not: who can do it instead?

That distinction is everything.

A manager who moves too quickly to replacement may think they are solving the project problem. But they may be creating a rights problem, a dignity problem, a labour problem, a trust problem, and a reputational problem. They may also be damaging the quality of the work, because replacement disrupts knowledge continuity. People are not interchangeable project parts. Expertise is not merely a name on a budget line. Work carries memory, authorship, tacit knowledge, and context.

When a person has developed the modules, built the structure, held the continuity of the work, and remains able to contribute through a different format, the responsible managerial question is not how quickly that person can be removed. The responsible question is how the conditions can be adjusted so that their contribution remains possible. If the only barrier is travel, then the first solutions to examine should be travel-related or format-related: remote delivery, hybrid participation, pre-recorded input, live digital facilitation, adjusted scheduling, shared facilitation, or another reasonable arrangement that preserves both the work and the person’s role in it.

Replacement should be a last resort, not the first reflex. It may become necessary if the person truly cannot perform the essential tasks, if no reasonable adjustment is possible, or if the work would otherwise be genuinely impossible to deliver. But when the person can still do the work, replacement becomes something else. It becomes a way of making the person disappear so the system does not have to adapt. That is where a management decision can become exclusionary, even when it is described as practical.

The language matters here. Saying “we can replace you” is not the same as saying “let us explore how you can continue.” Saying “hire someone else” is not the same as asking “what support would allow you to fulfil your role?” One preserves participation. The other removes the person from the centre of their own work. One begins with accommodation. The other begins with disappearance.

A rights-aware manager must understand this difference. Accommodation is not charity. It is not a favour granted when convenient. It is part of how organisations make participation possible when standard conditions exclude someone. If the standard condition is physical travel, and the person cannot travel for medical reasons but can still provide the content, expertise, and delivery digitally, then the accommodation conversation should begin there. It should not begin with replacement.

7. Never Use Organisational Replacement as a Casual Threat

The fifth obligation is to avoid casual threats of organisational replacement, contract termination, or role removal. Replacing a partner in an international project, removing a contractor, excluding a staff member, or threatening an organisation’s role is a serious governance matter. It should require formal assessment, documentation, review of the contract or grant agreement, communication with the relevant authority where applicable, and evidence that the person or organisation is unable or unwilling to fulfil their obligations. It should not be raised casually in a public meeting because one person cannot physically travel for medical reasons.

A threat of replacement changes the psychological and professional atmosphere immediately. It moves the conversation from solution-seeking to coercion. It tells the person or organisation that they are no longer being treated as a partner in resolving the problem, but as a risk to be removed if they do not comply with the preferred version of reality. In that moment, the issue is no longer only practical. It becomes about power.

This is especially damaging when the organisation being threatened is a smaller partner, a contractor, a freelancer, or a less institutionally powerful actor. Large organisations often underestimate the force of such statements. To them, replacement may sound like an administrative option. To the smaller organisation, it can sound like existential pressure: the loss of income, reputation, future opportunities, and professional standing. That asymmetry matters.

Risk management should never become a public threat. A coordinator or manager who turns a medical limitation into a replacement discussion is not reducing risk. They may be creating new risks: legal risk, reputational risk, trust risk, quality risk, and human harm. If a person or organisation remains able to deliver the work through reasonable alternatives, then replacement is not a proportionate first response. It is an escalation.

The correct managerial question is: what is the real risk, and what is the least harmful, most proportionate way to manage it? If the answer is remote delivery, adjusted format, revised timeline, or formal clarification with the funder, then those options should be explored before anyone speaks about removal. A serious governance measure should never be used as a pressure tactic.

8. Manage Timelines; Do Not Publicly Bargain Them

The sixth obligation is to manage timelines properly. A coordinator or manager cannot allow an organisation at the end of a production chain to be blamed for delays that began earlier in the chain. If one partner or staff member is responsible for digitalisation, integration, training delivery, design, publication, or technical structuring, their timeline depends on receiving the necessary content, materials, decisions, validations, and approvals from others. A platform cannot be completed in substance before the content that must populate it has been delivered. A training cannot be finalised before the curriculum has been approved. A report cannot be published before contributors submit their sections.

When delays occur, the manager’s job is not to create a public bargaining session. The manager’s job is to map the delay, identify where the bottleneck occurred, consult the responsible people, establish a realistic revised timeline, assess feasibility, and, where necessary, communicate with the funder or relevant authority. Public blame does not repair a timeline. It only damages trust.

A timeline is not a weapon. It is a management tool. If it has become unrealistic, the answer is not to pressure the partner at the end of the chain into impossible delivery. The answer is to revise the timeline honestly, document the reasons, and communicate the adjustment through the proper channels. This is not weakness. It is responsible coordination.

The worst version of project management is the one that ignores delays for months and then suddenly manufactures urgency at the point where the consequences become visible. In that scenario, the person or organisation holding the final stage of delivery becomes the symbolic problem, even if they were waiting for inputs from others. That is not accountability. It is displacement.

Good project management requires chain literacy. A coordinator must understand who depends on whom, which tasks can run in parallel, which tasks require prior inputs, and what happens when one part of the chain is late. Without that understanding, projects become emotionally chaotic. Instead of solving the actual bottleneck, the group looks for someone to blame.

9. Make Values Operational, Not Decorative

The seventh obligation is to make values operational. Many organisations know how to write inclusion. They know how to mention accessibility, diversity, wellbeing, resilience, vulnerability, participation, or care in proposals, websites, policies, work packages, and reports. But the real test comes when those values become inconvenient. When someone cannot travel. When someone needs adaptation. When a timeline breaks. When a small partner needs to be respected. When protecting the work requires more than protecting the schedule.

That is where values become visible.

In the case of this project, the contradiction is especially painful because the project is explicitly about mental, psychological and emotional health, trauma, vulnerability, and resilience.

A project about care cannot treat care as something exported outward while being absent inward. If a project teaches people to recognise and respond to trauma, distress, vulnerability, and mental health needs, its own coordination practices should reflect dignity, privacy, proportionality, and psychological safety.

This principle extends far beyond one project. Any organisation that publicly claims inclusion, wellbeing, equality, mental health, accessibility, or care must be prepared to practise those values when they create inconvenience.

If care disappears at the moment it requires adjustment, then care was never embedded. It was only branding.

Closing — The Difference Between Care as Language and Care as Practice

Many organisations know how to write inclusion. They know how to place it in proposals. They know how to put it in HR policies. They know how to mention vulnerable groups, accessibility, resilience, participation, wellbeing, reasonable support, emotional safety, and care. They know how to write “diversity” on a website and “inclusion” in a funding application.

But the real test comes when inclusion becomes inconvenient.

When someone cannot travel. When someone needs adaptation. When a timeline breaks. When a small partner needs to be respected. When a medical condition interrupts the plan. When protecting the work requires more than protecting the schedule. When the person who needs support is not an abstract target group, but someone inside the room.

That is where values become visible.

Rights literacy matters because it helps us recognise the moment when care turns into control, when support becomes substitution, when project management becomes public pressure, and when inclusion becomes a word used to remove the person who needs it most.

A right you cannot recognize is difficult to use.

A right you cannot name is easy to bypass.

And a right you admire but never practice remains politically underdeveloped.

Rights are not powerful because they are written beautifully. They become powerful when people know enough, trust enough, and care enough to use them. And sometimes, using them begins with one sentence:

This is not inclusion.

This is exclusion.

And I can name it.

Download the companion practical guides

This article is a reflection, but recognition also needs tools. If you are facing exclusion because of a medical condition, disability, health limitation, or access need — or if you manage a team, organisation, project, or partnership where this situation arises — I have prepared two practical guides to help you move from confusion to clarity.

The first guide is for people affected by discrimination or exclusion. It helps you document what happened, separate the issues, name the accommodation question, distinguish support from replacement, and identify possible routes for help.

Download

The second guide is for managers, coordinators, employers, and organisations. It explains how to handle health-related limitations without creating public humiliation, blame-shifting, or exclusion, and how to protect both the person and the work.