Manager rewrites your email in front of the team: 3 replies

Only 41% of dyslexic adults in Scotland get reasonable adjustments at work (Dyslexia Scotland and the University of Glasgow, October 2024). Of those, only 25% call the adjustments very or extremely helpful. Here is the moment behind those numbers. Your manager puts your email on the screen and rewrites it while the team watches.

Why a live rewrite hurts more than a red pen

A rewrite on a shared screen is an edit with an audience. The text gets fixed, and everyone also watches you get corrected. At director level, your team reads that moment as a signal about where you stand.

You can miss slips in your own text even after checking it carefully. So the rewrite may land on a real typo. It may also land on a sentence that was fine and just not how your manager would say it.

Work out which one it was before you reply. A fix to the content deserves thanks and a quick yes. A fix to typos or style is where the three replies below help.

A check before you press send is your first line of defense. The email tone checker reads your draft for tone and clarity. Fewer emails then reach the screen.

So what for you: decide fast whether the edit is about content or typos, because each needs a different reply.

Reply 1: keep the pen in your hands

Aim to stay calm and take the edit back. You do not need to explain anything on the spot. Pick the line that fits.

If the edit is about content, say this: "Good change. Send me the tracked version and I'll accept it after the meeting." You agree with the substance. You keep control of the document, and the team sees a leader taking feedback.

If the edit is about typos, say this: "Thanks. Send me the list and I'll fix them today." Then fix them with text-to-speech reading the email back to you. Hearing a sentence can show you what your eyes skipped.

Both lines are short on purpose. A long defense draws attention to the moment. A short reply ends it.

So what for you: have both lines ready before your next meeting, and use the one that fits.

Reply 2: move edits out of the room

The next day, ask your manager for a small change in how edits arrive. This is a process request. It does not need a diagnosis attached.

"When you want changes to my writing, could you send tracked changes instead of editing live in meetings? I'll turn them round the same day. It helps me check the whole document at once."

A reasonable manager has little reason to refuse. You get the edits in writing, in your own time, with a read-aloud tool to hand. The meeting stays about the decision.

If your manager agrees, note the date. That small record matters later if the habit returns.

So what for you: ask for tracked changes within a day, while the meeting is fresh and the request sounds routine.

Reply 3: put the adjustment in writing (UK)

If the live rewrites keep happening, move from a request to an adjustment. In the UK, Acas says employers "must make reasonable adjustments by law" (Acas, checked October 2026). That duty comes from the Equality Act 2010.

It applies when your employer knows you are disabled, or should know. Acas gives examples that fit. One is "providing emails and documents in an accessible format". Another is adapted equipment, such as "computer software".

Acas also points to Access to Work for funding. That scheme does not replace your employer's duty.

Your email to your manager or HR should name the task, the effect and the fix. For example: "Live review of my writing makes errors hard to catch, because of my dyslexia. Please send tracked changes and give me 24 hours to reply. I'd also like read-aloud software."

The reasonable adjustments builder turns your difficulties into a draft email like this one. If you are unsure about naming dyslexia at your level, read the disclosure decision guide.

US readers can start with the Job Accommodation Network (askjan.org), which offers guidance on accommodation requests.

So what for you: if a second live rewrite happens, send the written request that week.

Close the loop with the team

After a public edit, the team remembers the ending more than the middle. Send the corrected version to the same group within the hour, with one line: "Final version attached, with thanks for the edits."

That line shows you took the feedback and closed the task fast. It also puts the last word on the record in your own writing. Few people remember the rewrite once the clean file arrives.

If someone on the team commented in the room, a short private word helps. "Thanks for the support" works. Do not apologize for your writing, and do not explain it unless you have chosen to.

So what for you: send the clean version fast, because the file people keep carries your name.

Build a check that runs before anyone else sees it

The best fix is a draft that reaches the screen clean. For important documents, build a short routine and use it every time.

• Let the draft sit for ten minutes, so you read it fresh.
• Play it back with text-to-speech and fix whatever sounds wrong.
• Send high-stakes documents to one trusted colleague first.

A routine beats willpower. If your employer or Access to Work pays for read-aloud software, set it up once and make it the default.

So what for you: pick one step and add it to your next board paper.

When it keeps happening, keep a record

One awkward meeting probably is not a legal problem. A pattern might be. A tribunal case reported in May 2026 shows how this can go. A London Underground train driver was awarded £3,924 (Law360 UK, 7 May 2026). The tribunal found an HR manager did not factor in his dyslexia when remarking that he had overlooked an email footer.

That is one case with a small award, and it is not a rule. The finding turned on whether the manager accounted for his dyslexia. Your notes are what turn a feeling into evidence.

After each incident, write down the date, who was present and what was said. Add what you asked for and how your manager replied. Email the note to yourself the same day so it carries a timestamp.

If the pattern continues after your written request, call the Acas helpline or speak to an employment solicitor. This is information, not legal advice. Whether an incident breaks the law depends on the facts.

So what for you: keep a dated note after every incident, because a same-day record beats a memory.

What this means for you

If it happened once, use Reply 1 in the room and Reply 2 the next day. That is a fair first step. If it happens again, send the written request in Reply 3 and keep your notes.

You do not owe the team an explanation in the moment. You do owe yourself a process that checks your writing in a way that works. Senior roles bring more written output, so settle this while the stakes are small.

So what for you: start with a short reply, then build the paper trail.