For employers › Confidentiality at work
HR / PEOPLE LEAD · RESPONSIBILITIES
Someone has told you they're neurodivergent. Who can you tell?
Draft article for team review. Sources and legal wording need approval before publication.
IN SHORT
Not automatically anyone. A disclosure hands you information about someone’s health, which sits in a protected category of personal data, and it may at the same time trigger duties you now owe them. Those two things pull in opposite directions. In most cases you may share with people who need to act, for a reason you can state, and the scope is something to agree with the person before you tell anybody. [1]
The honest answer is that it depends, and the conditions matter more than the answer does. This page sets out what you are now holding, who you can usually share it with, and what to settle in the first conversation so the question does not arise in a hurry later.
Two duties switch on at the same moment
The moment someone tells you, two things become true, and they pull against each other. You are now holding information about an identified person’s health, and your ability to pass that on is restricted. [2] At the same time, you may now have knowledge that triggers duties you owe them, most obviously around adjustments, and discharging those duties often requires telling somebody else something. [1]
Most disclosures that go wrong go wrong in the gap between those two. Not through malice. Through somebody passing it on in order to be helpful.
What kind of information you are now holding
Information about a person’s health is treated as a protected category of personal data, which means the ordinary rules about handling staff information are not enough on their own. You need a specific reason to process it, and “it would be useful” is not one. [4] Three practical consequences follow, and they are the ones most often missed.
- A verbal disclosure counts. Nobody has to write it down or use a formal word for the obligations to apply.
- Where you record it matters. A diagnosis noted in a general performance file is handled differently from one held in a restricted record with defined access. [3]
- The word “disclosure” is doing a lot of work. Someone saying “I have ADHD” and someone saying “I’m finding open-plan really hard and I think it’s an ADHD thing” have given you different amounts of information, and you should be careful not to treat the second as though it were the first.
Who you can usually tell, and on what basis
The workable test is not who would find it interesting or who would be sympathetic. It is who needs to act, and what they need to know in order to act.
A line manager can usually be told where they are the person who has to put something in place, and they should generally be told the adjustment rather than the diagnosis. A manager needs to know that meetings are confirmed in writing. They rarely need to know why. [5]
Occupational health sits differently, because you are asking a professional for an opinion and they need the clinical picture to give one. This is normally a referral the person is told about in advance, not one they discover afterwards. [3]
Colleagues are almost never in the “needs to act” category. Where a team genuinely has to change how it works, the change can be described without attaching it to a person.
Payroll, finance or an external funder may need to be involved where an adjustment carries a cost or is funded through a scheme, and the scope of what they see should be limited to what the process requires. [4]
Consent is not the clean answer it looks like
The instinct is to ask the person to agree, treat the agreement as settling it, and move on. It is a reasonable instinct and it is not quite enough on its own. The difficulty is the imbalance built into the employment relationship. Agreement given by somebody whose employer is asking, who may not feel able to say no, does not carry the weight it would between equals, and relying on it as your only basis is a weaker position than it feels like at the time. [3]
That is not an argument against asking. Asking is right, and doing it well is most of good practice here. It is an argument against treating the answer as the end of the matter, and against the version of asking that is really telling: “I’ll just let the team know, is that alright?”
The conversation that prevents most of this
Almost everything above is easier if the scope is agreed at the start rather than reconstructed under pressure. In the first conversation, or shortly after it while it is still open, settle four things: who already knows, who you are proposing to tell and why, what those people will be told, and how the person wants to be told before anything changes. Write down what you agreed and send it to them.
That last step does more work than it looks like. It converts a conversation somebody may remember differently into a shared record, which protects them and protects you, and it makes the boundary specific rather than a general assurance of confidentiality that nobody can later hold you to.
When the two duties genuinely collide
Sometimes they do, and the honest position is that the collision is real rather than a failure of process. Somebody discloses, asks that nobody else be told, and also needs something that cannot be put in place without somebody else knowing. You cannot fully deliver both.
What you can do is name the trade-off rather than resolve it silently. Explain what the adjustment would require, who would need to know what in order to make it work, and let them decide with that in front of them. People frequently choose differently once they can see the actual scope rather than imagining the worst version of it. What you should not do is quietly widen the circle because the adjustment seemed more important, or quietly drop the adjustment because the confidentiality seemed more important. Both are decisions taken on somebody’s behalf that they could have taken themselves.
If it goes wrong
Where information travels further than it should have, there are two distinct routes, and they are often confused. One concerns the handling of the information itself. The other concerns how the person was treated as a result, which is a different question with different tests and different consequences. [6]
The practical point for you is that these are separate. Fixing the first, with a corrected record, a restricted file, an apology, does not dispose of the second. A situation can be handled properly in data terms and still have gone badly wrong for the person.
What to do next
- Write down what was actually said, in their words rather than your interpretation, and note the date. Keep it out of the general performance file.
- Ask who already knows. You may be the third person told, or the first.
- Separate the diagnosis from the need. Work out what has to change. That, not the label, is what most people need to hear.
- Agree the circle before you widen it. Name the people, say what each will be told and why, and get their view.
- Put the agreement in writing to them, briefly, the same week.
- Check where it is recorded, and whether the access to that record matches what you just agreed.
- Diarise a review. Circumstances change, and an agreement made once is not a decision made forever.
Before you tell anyone else
- I can state the reason this person needs to know, in one sentence
- What they will be told is the adjustment, not the diagnosis, unless there is a specific reason otherwise
- The person who disclosed knows this is happening, before it happens
- I have not included anyone because they would be sympathetic or interested
- I have not relied on agreement I did not really give them room to refuse
Recording it
- It is held somewhere with defined access, not in a general file
- I know who can see that record
- What is recorded is what they said, not what I inferred
- There is a date on it
If an adjustment needs wider knowledge
- I have described the trade-off to them rather than deciding it for them
- I have not quietly widened the circle, or quietly dropped the adjustment
- There is a review date
Practical support for an employee
At Reinforce Potential, we provide support workers and assistants who help employees plan, organise and work through their day. An employee doesn’t need a diagnosis to enquire about our support; they may already know they’re neurodivergent or be exploring that possibility. To discuss practical help, read about our employer support service. Agree with the employee what information is needed before you get in touch. This is practical workplace support; the draft article is not an offer of legal advice.
Ask about a support worker
Make an employer enquiry about the tasks an employee wants help with and how support could be arranged. This Local form uses invented test details only and sends no email.
Sources
References below are a draft checking list. The article’s numbered references are not yet verified citations, and the legal wording needs review before publication.
- Equality Act 2010, reasonable adjustments provisions · UK legislation · Statute
- Statutory code of practice on employment · EHRC · Statutory code
- Guidance on handling workers’ health information · ICO · Regulator guidance
- UK GDPR, special category data provisions · UK legislation · Statute
- Guidance on disability and disclosure at work · Acas · Advisory guidance
- Appeal decision on knowledge and adjustments · Tribunal / appeal · Case law
Draft general information, pending legal and source review. Seek advice on your own circumstances before acting on a workplace disclosure.
Review status: publication not approved. Article wording and references need checking before live use.