14% of staff reported an AI error and were told to stay quiet. Keep the record anyway

IT Brief reported on 1 October that GoTo, working with Workplace Intelligence, surveyed 1,250 full-time knowledge workers and 1,250 IT decision-makers across the US, Canada, the UK, Ireland, Germany, Austria, Switzerland, India, Mexico and Brazil. The headline figure is that 83% of employees fear they could be blamed or fired over an AI-driven mistake. The more useful figure sits further down. 14% of employees said they had reported an AI error to a manager or leader and were told to stay quiet about it. Meanwhile the national data still shows no break for the group most often named as exposed: an NBER working paper by Robert Fairlie and Jane Wu, issued in September, found that unemployment among recent US college graduates did not spike in summer 2026 compared with previous summers. The payroll numbers have not moved. The workflow has, and the accountability inside it is going missing.

The errors are already reaching customers

GoTo's IT leaders are past the hypothetical stage. A quarter said AI had already made mistakes that hurt customers or clients. 23% said it had caused financial harm to their company. 91% said they were concerned AI would make a mistake that affects their organisation.

The employee side explains how those mistakes get out of the building. 55% said they do not always review or double-check AI outputs, even for high-stakes tasks. 43% said they had used AI outputs they believed were low quality or suspected contained errors or fabricated information.

The reason is pressure, and the survey measures it. 60% of employees feel pressure to use AI to increase productivity. 47% say AI use is considered in their performance reviews. 42% would rather risk making errors with AI than look "slow" or "replaceable". That is a workforce being graded on speed of adoption and on nothing that measures what ships.

The consensus reading is that this is a policy gap the employer will close. The figures say do not wait for it. Only 24% of small businesses and 36% of midsize companies have an AI policy. Even among enterprises the figure is only 53%. Everywhere else, nobody has written down what gets checked or who answers for it. 84% of workers said their employer could do more to encourage responsible AI use.

Silence is the actual failure mode

Fear of blame reads like an anxiety problem. It is better read as a price signal. The survey shows accountability being offloaded in three directions at once. 26% of employees said using AI lets them avoid personal accountability at work. 25% said it feels safer to blame AI than to admit an error, and 17% said they had already blamed AI for a mistake of their own. And 31% believe there is unspoken pressure at work to trust AI and stay quiet about its mistakes.

Put those together and the picture is an organisation running AI where nobody owns the output. The tool gets blamed, the report gets buried, and the next error ships the same way.

That gap is where the value now sits. A system can draft the contract clause, the forecast or the customer reply. It cannot sign for it. The person who will say "I checked this, here is what was wrong, here is what I changed" is doing the part of the job that cannot be delegated to the tool. AI does the routine work. You do the thinking, and owning the result is part of the thinking.

The time to do it exists. Employees who use AI told GoTo they save an average of 2.3 hours a day. Spend part of that on the check and the record, and you hold the layer your organisation has not yet staffed.

Your Next Move

1. Start an AI error log this week. One line per incident: date, tool, task, what was wrong, how you caught it, what it would have cost if it had shipped. Five minutes an entry. Within a month you have evidence instead of an impression, and evidence is what changes a manager's mind.

2. Write your own review line before your employer writes one. List the outputs you always check in full: anything going to a customer, anything carrying a figure, anything with a legal or financial consequence. List the ones a spot-check covers. Send it to your manager as your working standard. In a firm without a policy, the first written standard tends to become the standard.

3. Raise errors as fixes, with the record attached. Bring the log entry and the check that would have caught the problem. If you are told to stay quiet, keep the dated entry anyway. If AI use counts in your review, a log of catches is the proof of judgement that a usage count never shows.