watts.it.com // daily AI micro-learning
Tools & connectors model-updatescopilotreliability 2026·07·22 · 4 min · dated

The Silent Engine Swap: What to Do When Your AI Tool Changes Underneath You

// listen · 2 ai hosts · audio edition

AI-generated audio discussion of this module — same content, spoken.

Overview

On 24 July 2026, something changes inside Microsoft 365 Copilot for eligible commercial tenants: OpenAI-operated models switch from off to on for all users, unless an administrator has actively selected “No users” in the admin centre. Separately, OpenAI’s own announcement in early July says GPT-5.6 “will become the new preferred model” across Word, Excel, PowerPoint, Chat and Cowork — and says nothing about telling the person typing. The notice lives in admin documentation and the Message Center; the end user just notices, or doesn’t, that the answers feel different. This module is about the habit that turns “feels different” into something you can actually check: a small set of gold prompts you re-run when the engine under your tool changes. By the end you’ll have the set, and you’ll know the two minutes it takes to use it.

The content

The obvious assumption is that a model change inside your workplace AI is like any other software update — announced, tested, and roughly an upgrade. The reality is narrower: it’s announced to your admin. Microsoft’s own documentation for the July change is written for administrators, the control sits in the admin centre, and nothing in either vendor’s public material describes an in-product notice for the person actually using Word. You are the last to know about a change to the tool you use most.

Would you even notice? The research says you should. When Stanford and Berkeley researchers compared the “same” GPT-4 service three months apart in 2023, accuracy on one task (identifying prime numbers) fell from 84% to 51%; their conclusion was that “the behavior of the ‘same’ LLM service can change substantially in a relatively short amount of time”. A follow-up study of prompt performance across OpenAI API updates found 58.8% of prompt-model combinations lost accuracy after an update — and, more usefully for us: even when an update improved overall accuracy, 87.9% of the time at least one previously correct answer broke. Read that again. An upgrade, on average, still breaks something you relied on.

It isn’t only accuracy. Anthropic analysed 309,815 real conversations across three of its models and found they differ measurably in working style — one model leans towards warmth and affirming your ideas, another towards caution and “candid critiques of the user’s work”. Same product name, different colleague. If you use AI to pressure-test your documents, the strictness of your reviewer can change in an engine swap. And the failure mode is real: a research team reported in June 2026 that a silent GPT-4o update flipped their study’s own conclusion between two runs — they only caught it because they re-ran the measurement.

That re-run is the whole lesson, and it needs a name: gold prompts. Three real tasks from your own work, each with a saved output you’ve checked and trust. They are your baseline. When output starts feeling different — or you hear an engine changed — you re-run the three, compare against the saved versions, and you know in minutes whether it’s you or the tool. No dashboard required, no permission needed, works in any chat tool your organisation gives you. And one sentence worth knowing for context: your admins do get notified of these changes and do hold an opt-out lever — the July change even carries compliance differences (the OpenAI-operated path currently lacks FedRAMP High authorisation and PCI, HITRUST and SOC 1 Type 2 attestations, per Microsoft’s documentation) — so “which model serves our Copilot, and when did it last change?” is a fair question with a real answer, not a mystery.

Two honest limits. First, drift is not decay: in the Stanford-Berkeley study, GPT-3.5 improved on the same maths task while GPT-4 declined. Updates change behaviour; they don’t reliably degrade it — the point of a baseline is knowing, not fearing. Second, those regression figures come from 2023 studies of OpenAI’s API; the exact magnitudes will vary by tool and year. What doesn’t vary is the structure: hosted models change under their product names, and the person typing is told last.

Try it

Build your gold set today — fifteen minutes, in whichever AI tool your workplace gives you (Copilot, Gemini, an internal wrapper, ChatGPT or Claude):

  1. Pick three recurring, real tasks — say, summarising the kind of document you handle weekly; one analysis or calculation with a checkable answer; one draft in your required format.
  2. Run each once. Check the outputs properly — these become your baselines only if you’ve verified them.
  3. Save all three prompt-and-output pairs wherever you keep working notes, dated. If your tool shows which model is active, note that too.

Then the habit: next time an answer feels off — or you hear the engine changed — re-run the three and compare. Different tone of critique, broken formatting, a wrong calculation: now it’s evidence, not a vibe.

Additional reading

Editor’s note

Some people, with some tools, have the motivation to, and privilege of, selecting the model before each task. A handful might test a new model before committing it to a historically repeated task on real work. That handful have the ability to recognise output differences before those differences end up triggering confusion and grief. It’s unlikely that a new generation of an existing model will be “worse”, but sometimes “different” is enough to be a problem. Recognising change is the way to overcome it.

signed-off-by: Luke Topfer <editor> · 2026·07·22
06 Self-check

// three assertions against what you just read · results stay in this browser

assert 1/3

What is the core purpose of keeping a set of 'gold prompts'?

assert 2/3

A colleague says their Copilot drafts suddenly read differently, and they assume the update must have made everything worse. Based on the module, what's the fairer read?

assert 3/3

The module notes that even updates that improved overall accuracy still broke something 87.9% of the time. What practical lesson does it draw from this?