In September 2026 Omni Calculator published a survey of 705 employed US adults who use AI for writing, and one line in it is worth reading twice: 54% of managers and 48% of executives run 70% or more of what they write past an AI before they send it, against 30% of experienced individual contributors. The people with the most authority to press send are the ones least willing to do it alone.
I build AI systems and trained as an executive coach, so I read that number twice: once as an engineer who knows what a model does with a pasted draft, once as a coach who knows what a habit of asking permission does to judgment. The question here is not whether AI makes your emails better. Often it does, a little. It is what happens to your judgment when the AI decides an email is ready, and how to keep the useful part of the check without handing over that decision.
What the 2026 numbers actually say
The Omni report calls AI's new role a gatekeeper, and its numbers support the word. 77% of respondents have delayed sending something specifically so an AI could review it first, and 74% have held back a message they already considered finished. 73% say AI feedback has directly changed whether or how they sent something, and 15% sent a message specifically because the AI said it was good to go: without the green light, it would not have gone out. The most telling pair of figures is this one: 77% say they check for grammar and clarity, yet 79% have changed a piece of writing based on AI feedback even when they already believed the original was fine. That is a confidence check, not a spell-checker.
The authors call the next finding the managerial paradox: managers and executives are roughly twice as likely as entry-level staff (13%) to send a document specifically because AI confirmed it was ready. 32% of all respondents feel less confident in their own writing since they started using AI, against 23% who feel more confident. Omni sorts respondents into 74% "Pragmatic Safeguard" (they trust their writing but check routinely), 10% "Fully Independent" and 16% "Reassurance-Driven"; executives land in that last group at 21%, the same rate as entry-level staff.
The limits matter. This is a self-reported online survey of US adults run through Prolific by a calculator company, not a peer-reviewed study, and it measures behaviour and feelings, not whether the checked emails were actually better. Read it as a description of a habit that has quietly become normal, not as proof of harm.
The other side of the send button
The same company ran a second survey in June 2026 that answers the question managers rarely ask: what does the recipient notice? Of 913 US employees who report to a manager, 50% say their manager has used AI to answer a question or make a decision they should have handled themselves. 68% say AI-generated messages from a manager feel less personal, and 42% say a manager who relies on AI seems less competent. When workers can spot it, the most common giveaway, cited by 45%, is a message that does not sound like the manager.
Put the two surveys side by side and the cost becomes visible. The pass that makes an email more polished is the same pass that pulls it away from the way you actually talk, and your team knows how you talk. That objection applies to voice-matching inbox tools too, covered in should you let AI reply to your email in your voice, and it applies just as much to the lighter "just check this" pass. If you are choosing an AI email client for triage rather than for judgment, the Superhuman vs Shortwave vs Fyxer comparison is the better starting point.
Why the check changes you, not just the email
The engineering side
When you paste a draft and ask "is this good?" or "can you improve this?", you have asked a system tuned to be helpful to find something to help with. A model asked to improve text will almost always produce an improvement, because a reply of "no changes needed" reads as unhelpful. That is the 79% figure from the machine's side: each accepted edit is a small vote that your first version was not good enough. I wrote about the wider version of this problem, agreeable models telling you what you want to hear, in how to get AI to challenge your decisions.
The research side
The best evidence on the judgment mechanism is still the 2025 Microsoft Research and Carnegie Mellon study presented at CHI 2025. Its authors surveyed 319 knowledge workers about 936 real tasks and found that higher confidence in generative AI was associated with less critical thinking, while higher self-confidence was associated with more. Set that next to Omni's finding that a third of AI writers now feel less confident in their own writing, and you have a plausible loop: the check lowers self-confidence, lower self-confidence predicts less critical thinking, and less critical thinking makes the next check feel more necessary. Both studies are correlational, so that loop is a hypothesis, not a finding. More on that in when to trust an AI's confident answer and why we trust confident speakers.
The cleanest causal evidence comes from a randomized experiment. Zara Contractor and German Reyes at Middlebury College had 211 undergraduates study an unfamiliar topic and write an essay with or without AI, then complete unaided tests and essays immediately and about a week later; the paper was first posted on arXiv on July 9, 2026 and revised on October 4. AI access raised test scores and a smaller gain persisted a week later. But the gains held for students who used AI as a tutor, to explain concepts ("augmentation"), and faded for students who had AI write for them ("automation"): the automation users' essay advantage was absent from their unaided essays a week later. These were students, not executives, so the transfer is an inference, but the split is the useful part: working with the model left something behind in the person; having it do the work did not. I looked at the learning side of this in do AI tutors actually work.
The coaching side
Sir John Whitmore's Coaching for Performance rests on two ideas that map directly onto the send button: awareness, seeing clearly what is actually happening, and responsibility, genuinely owning the choice to act. His argument against telling people what to do is that it creates dependence and suppresses self-belief, while a good question builds both awareness and ownership. A rewrite is telling. A verdict of "this is ready to send" is telling. A question such as "how will she read this sentence?" is coaching. That gives a simple design rule for any pre-send check: it should raise your awareness of how the message will land, and it should leave responsibility for sending with you.
The four pre-send modes
"Check this" hides four different requests, and they do very different things to the author.
| Mode | What you ask | What it does to your judgment | Use it for |
|---|---|---|---|
| 1. Proofread | "Fix spelling and grammar only. Change nothing else." | Close to neutral. Mechanical errors are not where your judgment lives. | Long or external documents where a typo costs credibility. |
| 2. Flag | "Where could this be misread? Ask, don't rewrite." | Augmentation: you stay the author and the judge, and you practise reading your own writing as the recipient will. | High-stakes messages to people who know your voice: direct reports, a cofounder, investors. |
| 3. Rewrite | "Make this better." | Automation: the email improves, your skill does not, and the text drifts toward the "doesn't sound like you" giveaway. | Formats you genuinely do not know, or a language that is not your first, and always with a reread in your own voice. |
| 4. Approve | "Is this ready to send?" | Hands over the decision itself. This is Omni's 15%: messages that went out because the model said so. | Not as a habit. If you need a verdict, the message probably needs a person, a phone call or a night's sleep. |
The modes are ordered by how much of the decision leaves your hands. The practical move: drop modes 3 and 4 as defaults and make mode 2 the standard check for anything that matters.
The flag-don't-rewrite check, run once
Here is the mode 2 prompt, run once. The email is an example written for the test and "Marta" is invented: a founder writing to the head of customer success about missed Q4 renewals, where tone does most of the damage.
Tested October 6, 2026. I had my research agent run this exact prompt against Claude Opus 5.5 (default settings, one run, no earlier conversation). The prompt:
I have already written the email below and decided it is ready to send. Do not rewrite it. Do not suggest alternative wording or produce a new version.
Your job is narrower: name at most three places where the recipient could misread me, or where sending it as written could cost me something. Phrase each one as a question I have to answer myself, and quote the exact words it refers to. Then say in one line whether any of the three is a reason not to send. If nothing is material, reply only "Send it." and stop. Do not compliment the draft.
Context: I am the founder of a 12-person software company. The recipient, Marta, leads our customer success team and reports to me.
---
Subject: Q4 renewalsHi Marta,
Thanks for the renewals update yesterday. I know the team has had a lot on its plate.
I went through the numbers again last night. We're at 71% on Q4 renewals against the 85% we […]
The start of what came back, unedited:
1. **"I'm not sure the current approach is working, and I think we need to look at things differently going forward."** Is this a concern about tactics or about Marta's leadership? From a founder to a direct report, it can read as a performance warning. Are you comfortable if she reads it that way?
2. **"Can you put together a plan by Friday? Happy to discuss whenever."** Is the plan meant to rescue the two unsigned enterprise accounts this quarter, or to change the approach "going forward"? If she guesses wrong, does "discuss whenever" leave her building the wrong thing alone until Friday?
3. **"I went through the numbers again last night."** Coming right after her update, could "again" suggest you didn't trust her numbers or are checking her work? Is that something you want to signal?
None is a reason not to send, as long as you're fine with whichever reading of #1 she takes.
One run is one run: the same prompt gives a different answer next time, and a different model answers differently.
What it did well: it obeyed the brief. It did not rewrite a word, it quoted the exact phrases, and it phrased every point as a question the sender has to answer. The first flag is the one that matters: "I'm not sure the current approach is working" from a founder to a direct report can read as a performance warning, and the email never says whether that is intended. The third flag caught something easy to miss on a quick read: "again", one small word, suggests the founder was checking Marta's numbers rather than reading them. The second found a real tension between a Friday deadline and "happy to discuss whenever".
What it did badly: the verdict line hedges. "None is a reason not to send, as long as you're fine with whichever reading of #1 she takes" hands the decision back, which is what I asked for, but it is also the kind of soft permission a reassurance-seeking reader would take as a green light. It used all three slots, and from a single run I cannot tell whether three is a cap it treats as a quota; And it stopped one step short of its own first flag: a message that can read as a performance warning may belong in a fifteen-minute call, not an email. The model reviewed the words; choosing the channel stayed with the human.
A pre-send routine that keeps the decision yours
Decide it is ready before the AI sees it
The prompt opens with "I have already decided it is ready to send" on purpose: the AI reviews a decision you made instead of making it. If you cannot honestly write that sentence, the draft is not ready.
Answer the flags in your own words
The value is in the minute you spend answering "tactics or her leadership?" yourself. Pasting the flags back for the model to fix turns mode 2 into mode 3.
Keep an unchecked lane
Omni found that 52% of respondents check even a Slack message to a colleague. Pick one class of message, internal chat or routine replies, and send it without any AI pass at all. It keeps the muscle working and your team hearing your actual voice. The broader version of this discipline is in how to use AI every day without becoming dependent on it.
Test yourself without it now and then
Gartner predicts, as reported by HCAMag in September 2026, that through 2026 the erosion of critical-thinking skills from generative AI use will push 50% of global organizations to require "AI-free" skills assessments. You do not need to wait for one. Once a week, write and send one consequential message unassisted. If that feels harder than a year ago, see keeping critical thinking sharp in the age of AI.
Where this advice breaks
The evidence for this exact behaviour is thin: the Omni data is self-reported, the CHI study is correlational, and the only randomized evidence comes from undergraduates, not managers. No study I could find tests whether pre-send AI checks make leaders' messages land better or worse. Omni's largest group, the 74% who trust their writing and check anyway, suggests the habit usually coexists with judgment rather than replacing it. If you write in a second language, a rewrite pass may be the right default. For anything with legal exposure, the second opinion should be a person. For the interpersonal cases that are harder than an email, such as a conflict with your boss or cofounder, see what the research says about taking ChatGPT's advice in a conflict.
What I am confident about is the distinction underneath it. An AI that asks you "how will she read this?" leaves you a slightly better writer and a fully responsible sender. An AI that tells you "this is ready" leaves you with a better email and a little less trust in yourself. The second habit is already normal among people who run teams. It does not have to be yours.
Sources
Omni Calculator — Are We Losing Our Judgment? 76% of Workers Get AI's Approval Before Emailing Their Boss (2026 Survey), September 2026: 705 US adults who use AI for writing; 77% delayed sending for AI review; 73% say AI changed whether or how they sent; 15% sent because AI said it was ready; 79% changed writing they already thought was fine; 54% of managers and 48% of executives check 70%+ of their writing; 32% less confident vs 23% more; 74% / 10% / 16% groupings; Slack message to a colleague 52%
Omni Calculator — Survey: Half of Workers Have Caught Their Bosses Using AI (2026), July 2026: 913 US employees surveyed June 8-15, 2026; 50% say a manager used AI for something they should have handled; 68% less personal; 42% less competent; 45% "doesn't sound like the manager"
Microsoft Research — The Impact of Generative AI on Critical Thinking (Lee et al., CHI 2025): 319 knowledge workers, 936 examples; confidence in GenAI linked to less critical thinking, self-confidence to more
Contractor and Reyes — Experimental Evidence on the Learning Impact of Generative AI (arXiv 2607.08849, v1 July 9, 2026, v2 October 4, 2026): randomized experiment with 211 Middlebury undergraduates; gains persist for augmentation users, fade for automation users
HCAMag — Is AI making your managers stupid?: Gartner prediction that 50% of global organizations will require "AI-free" skills assessments
Sir John Whitmore, Coaching for Performance (5th edition, 2017): awareness and responsibility; telling creates dependence
