Disclosure means telling someone something about you that they couldn’t have known otherwise. For some of you it’s a diagnosis. For others it’s anxiety, a chronic illness, caring for someone at home, a learning disability, or being the first in your family at university. This week draws on research about several concealable identities, alongside studies of autistic disclosure.
What the evidence says, and why it disagrees#
Chaudoir and Fisher built a general model of disclosure for any identity a person can keep hidden. Disclosure can help, and when it does, it works through three routes: relief from keeping something concealed, social support, and changes in what other people know. Whether it helps depends partly on the discloser’s goal, whether they’re moving towards something or trying to avoid something (Chaudoir & Fisher, 2010).
On autism specifically, the research splits along a line worth understanding.
In a rating study, observers formed first impressions of autistic adults. Those impressions were more positive when the diagnosis was accurately given than when it was withheld, and raters who knew more about autism rated the autistic adults more favourably (Sasson & Morrison, 2019).
A scoping review of 37 studies found a disconnect. Studies of other people’s perceptions, mostly using written vignettes, found disclosure helped social acceptance. Studies of autistic adolescents and adults found reluctance to disclose, expecting stigma. The reviewers also noted that the research field tends to assume disclosure should happen (Thompson-Hodgetts et al., 2020).
And when 238 autistic adults described disclosing at work, most had disclosed selectively, and just over a third rated the impact of telling supervisors and coworkers positively (Romualdez et al., 2021).
A favourable first impression does not settle whether disclosure will help someone at work. These studies ask different people, in different settings, about different consequences.
Anticipated stigma and the decision#
Before deciding, consider both telling and keeping something private. The following study concerns distress among people with concealable identities; it does not price those two options against each other.
Quinn and Chaudoir asked 300 people holding thirteen different concealable identities what their lives were like, then repeated it with 235 more. Four things predicted psychological distress: how much stigma a person anticipated, how central the identity was to their sense of themselves, how salient it was day to day, and how strongly the thing is culturally devalued. In the second study, anticipated stigma and cultural stigma were related directly to self-reported health (Quinn & Chaudoir, 2009).
The predictor anticipated stigma is what you expect would happen if people knew. It is not the effort of concealing, or whether you have told anyone.
This suggests a question for a department: could making adjustments routine lower anticipated stigma, including for students who never disclose? That is a proposal to test; these studies did not test a department’s adjustment policy.
Levels, not a switch#
Corrigan and Matthews approach disclosing a psychiatric diagnosis by asking what the gay and lesbian community had already worked out about coming out. They weigh social avoidance and disapproval against improved psychological well-being and interpersonal relations, and the paper ends with a review of levels of disclosure for people who opt to come out (Corrigan & Matthews, 2003).
We read the abstract, not the paper, so we will not reproduce their levels. The five audiences and partial-disclosure scripts below are the course’s own. The paper gives us the idea of levels rather than an on switch; its population is people with psychiatric diagnoses, not autistic students.
A fictional case: Rae asks for writing#
Rae wants written instructions at work. The case separates three entries:
| Entry | Where it belongs | Status in this fictional case |
|---|---|---|
| “My supervisor may think I cannot do the job.” | Possible consequence of telling. | Prediction, not an observed response. |
| “I spend twenty minutes reconstructing spoken instructions after each shift.” | A current cost while the need stays private. | Stated experience in the case. |
| “Written instructions would remove that work.” | Possible benefit of asking. | Prediction to check, not a promised outcome. |
In the room — price both columns (8 min)#
Nothing personal gets said aloud, and the page stays yours. Use your own situation or Rae’s fictional case above.
Four minutes, alone. Left: what telling one person might buy or cost. Right: what keeping it private currently buys or costs. Mark each entry as an observation, a prediction, or unknown. Expected rejection if they knew belongs with the possible consequences of telling; worry about that possibility can also be a current cost, if that is what you experience. They are different entries, not two names for the same event.
Two minutes. Circle a condition in either column that the institution could change without requiring more personal information.
Two minutes. Write one proposed change and what you would check to learn whether it helped. Volunteers may share the proposal, not their private case. An empty column or an unknown cost is an answer; do not invent an entry.
What it does to your past#
Here is the part nobody warns you about.
After you tell someone, they go back through everything. The tutorial where you didn’t laugh. The email that was too short. The party you left at nine. They re-read all of it, and they decide what it meant, and they do not tell you they are doing it.
Sometimes this is a relief. A person who thought you were cold for three years understands, and something between you gets easier, and you wonder why you waited.
Sometimes you lose something. There was a version of you in their head — competent, or funny, or just unremarkable — and it is replaced by a version with an explanation attached. You do not get to choose which one they keep. You do not get to take it back.
That risk is real and this course is not going to talk you out of it. It is going to make sure you knew it was there.
Right. Mechanics.
The five audiences#
Telling someone is a transaction, and it is easy to treat five different transactions as one decision. The entries below are the course’s; the workplace row draws on Romualdez et al.
| Audience | What telling can buy | What it can cost | A partial option |
|---|---|---|---|
| Disability services | formal adjustments: exam arrangements, extensions on a plan | a record, and they may ask for documentation (that’s their process, not this course’s) | ask what they can do before deciding what to share |
| A tutor | flexibility in labs, fewer surprises on both sides | the tutor re-reads your participation | the need only |
| A group partner | working arrangements that fit | it can travel beyond the group | the need, framed as working style |
| A friend | understanding, and less masking around them | the re-reading above | whatever pace week 9’s rate limit allows |
| An employer | adjustments; for some, relief from concealing | in one UK survey, just over a third rated telling colleagues and supervisors positively | the need, at a time you choose |
In the room — one audience, one sentence (7 min)#
Four minutes, alone. Pick one audience for your own situation or fictional Rae, who needs written instructions from a supervisor. Write the actual sentence, keeping any personal version private.
Two minutes. Now write what you would say if that sentence went badly. One line. This is week 5’s repair, at a higher stake.
One minute. Put your hand up if the second line was harder to write than the first.
Nobody reads either sentence out. We collect only the show of hands.
Partial disclosure#
You can disclose a need without the label.
“I process written instructions much better than verbal ones. Could you send the task in the chat as well?”
That sentence asks for an adjustment without naming a diagnosis. It uses Chaudoir and Fisher’s third route: changing what the other person knows. You choose whether to share the rest. Partial disclosure is the course’s synthesis, not a tested intervention.
- On the envelope
- “I process written instructions much better than verbal ones.”
- Noted on it
- the need, and what would help
- Payload inside
- send the task in the chat as well
- Kept back, never sent
- the diagnosis, the history, the reason
More needs, no labels:
- “I think better if I can look away while I talk. It’s not that I’m not listening.”
- “Loud rooms cost me a lot. Can we meet somewhere quieter?”
- “I’ll answer better by email than on the spot. Can I get back to you tomorrow?”
- “I have a health thing that means some weeks are worse than others. I’ll tell you early when one’s coming.”
Each one names a need and what would help. None of them explains why.
The timing trap#
In the workplace survey, many people disclosed on an application or after starting a job, and rarely at interview. Many disclosed only after problems had already arisen (Romualdez et al., 2021).
The trap is what happens next, and this part is the course’s own observation. A disclosure that arrives after a problem can be heard as an explanation of the problem, and an explanation can be mistaken for an excuse.
One option is early disclosure of needs: at the first group meeting or in the first week of a job. “Before we start: I work best with things in writing.” You can make it part of the working arrangements before a problem needs explaining.
Receiving a disclosure#
If someone discloses to you:
- Thank them. “Thanks for telling me.”
- Ask about the need, not the label. “Is there anything you’d like me to do differently?”
- Don’t re-read out loud. Whatever you now understand about the tutorial last month, keep it to yourself. Saying “oh, that explains the thing at the party” is exactly the re-reading they were afraid of, happening in front of them.
And one line to leave out entirely, however kindly meant: “you don’t seem like you have that”. It treats the disclosure as a claim you’re assessing.
When it goes badly#
Here are three ways a disclosure can be received badly, with an answer you can try:
| What happens | What you can say |
|---|---|
| They minimise it. “Everyone’s a bit like that.” | “Maybe. The thing I’m asking for is still the written instructions.” |
| They overshoot, and start handling you carefully. | “I’d rather nothing changed except the one thing I asked for.” |
| They tell someone else. | “I’d like to choose who knows. Can we agree it stops here?” |
All three answers do the same thing: return to the need, which is the part you can negotiate, and out of the label, which is the part you can’t.
These sentences cannot undo what happened. They give you something to say without having to compose it on the spot.
In the room — what does the finding allow? (10 min)#
Two minutes, in pairs. Read three proposed conclusions:
- “You should tell your employer, because a diagnosis improved observers’ first impressions.”
- “Quinn and Chaudoir measured how much distress would disappear if someone stopped concealing.”
- “A needs-only sentence guarantees the adjustment without the risks.”
Three minutes. For each, name the source or course model it is borrowing from, the outcome actually studied, and the extra claim it adds. The checked findings are in the opening section of this page.
Three minutes. Rewrite each conclusion so it stays within that evidence. Keep a useful question or option; merely appending “more research needed” will not remove an unsupported promise.
Two minutes. Compare with another pair. Check that your revisions preserve the difference between a first-impression rating, a reported workplace experience, a predictor of distress, and an untested script.
In the room — receiving (6 min)#
One minute. Read the two fictional lines and the checklist: thank, ask about the need, do not re-read the person out loud.
- Rae: “I follow written instructions more easily. Could you put the task in the chat as well?”
- Dev: “Loud rooms cost me a lot. Can we meet somewhere quieter?”
Two minutes. A reads Rae’s line; B answers in two sentences. A checks the three steps and B retries if needed.
Two minutes. Swap roles and use Dev’s line. Both people practise receiving.
One minute. Each privately notes a step to remember. These are character lines, not an invitation to disclose something about yourself.
What this week added to the vocabulary#
Partial disclosure — the need without the label. The five audiences — five transactions, not one decision. The timing trap — the same sentence read as configuration before the problem and as an excuse after it. And anticipated stigma — what you expect would happen if people knew.
Next week: interoperation, not conversion, and the last of the three partnership lab sessions.
If time remains#
What could an institution change so that getting a usable adjustment requires less personal disclosure?
Optional discussion. Finish by 15:55.