You didn’t roll out Microsoft Copilot so your team could second-guess it. The whole pitch is speed: draft the email, summarize the meeting, answer the client in less time than it takes to write the first line yourself.
That’s exactly what worries Gartner.
Copilot’s output always looks finished
At Gartner’s Security & Risk Management Summit in Sydney in March 2026, analyst Dennis Xu half-joked that businesses should ban Copilot on Friday afternoons. His reasoning wasn’t about the tool. It was about the person using it. By the end of the week, most people are tired, and tired people stop double-checking things that look done.
Xu’s talk covered five security risks tied to Microsoft 365 Copilot. The one that led to the Friday joke was about tone, not accuracy. Copilot can produce a response that’s factually correct and still comes across as blunt or offensive, the kind of thing that’s fine in a quick message to a coworker and a real problem in an email to a client. His actual recommendation wasn’t “ban Fridays.” It was to review Copilot’s output before it goes anywhere external, and make that review a habit instead of an afterthought.
That distinction matters more than the joke does.
Here’s the part that should worry a business owner
An employee misjudging tone in a rushed email is an old risk. People have always sent messages they later regretted. What changes with Copilot is volume and speed. One employee can generate ten client-facing drafts in the time it used to take to write one, and every one of them can go out the door with nobody but the AI having “written” it.
Now put that on a Friday afternoon, when that same employee is least likely to slow down and read it twice.
This isn’t a productivity problem. It’s a reputation problem. A poorly worded email from a stressed employee is unfortunate. A poorly worded email that went out because nobody had a rule requiring a second look at AI-generated content is a process failure, and it’s the kind of thing a five-minute policy conversation prevents.
What to do about it
Banning Copilot on Fridays isn’t the answer, and Gartner wasn’t seriously proposing it. The answer is a review habit that applies every day, not just the day everyone’s running on fumes.
Set a simple rule: anything Copilot drafts that goes to a client, a vendor, or anyone outside the company gets read by a person before it’s sent. Not skimmed, read. That’s not a knock on the tool. It’s the same standard you’d hold a new hire to before they’re trusted to send email on your company’s behalf unsupervised.
Microsoft builds content filters into Copilot that catch some of this before it reaches an inbox. Turning those on is worth doing, but a filter only catches what it’s tuned to catch. It won’t replace a person deciding whether a message actually sounds like your business.
If you’re rolling Copilot out across your team, put the guideline in writing: what needs a human review before it goes out, and who owns that review. Without it, you’re relying on everyone individually deciding to slow down on a Friday afternoon. History says that doesn’t hold up.
Gartner’s joke landed because there’s a kernel of truth in it. Tired people trust polished output more than they should. But the fix isn’t picking a day to distrust Copilot. It’s building the habit of checking anything that leaves your business under your name, on a Tuesday morning as much as a Friday afternoon.
If you want help setting up simple guardrails around how your team uses Copilot, our managed IT services can put something in place that doesn’t rely on everyone remembering to be careful at 4:30 on a Friday.