Summary
Three things decide a rollout and none of them is the product. Training that teaches the one habit that matters, which is speaking the findings you want recorded. A monitoring framework you actually run, which NHS England requires and which means auditing documentation and reviewing incidents on a schedule. And a plan for the drop-off, because usage in the published studies is wildly uneven and the clinicians who quietly stop are the ones the pilot did not reach.
A pilot is run by people who volunteered, watched closely, for a few weeks. A rollout is run by everyone, watched by nobody, forever. Almost every disappointing deployment in this category is a successful pilot that was scaled without changing anything about how it was supported.
The published evidence is blunt about it. In the Cleveland Clinic evaluation the median participant ran 61 encounters across four weeks with a range from 1 to 181, which means some participants barely used the thing while the average looked healthy. A study across five academic centres was reported under the heading of modest time savings and inconsistent use.
Uneven use is the normal outcome rather than the exception, so the rollout plan has to be built around it instead of hoping it away.
See it in your clinicWe would rather your rollout worked than your contract renewed. Ask us how we support the second month.
Request a demo| What | Why it matters | Who owns it |
|---|---|---|
| The spoken-findings habit, taught | Unspoken examination is where error concentrates | Clinical lead |
| Monitoring framework, running | Required, and the thing that catches drift | Clinical Safety Officer |
| Incident route people will use | An unreported error teaches nobody | Clinical Safety Officer |
| Weekly usage per clinician | The collapse is silent otherwise | Whoever owns the rollout |
| A named person to ask | Adoption dies on small friction | Practice or service manager |
| A stop rule | Deciding it is not working is a legitimate outcome | The board or partners |
Training is one habit, not a module
Most vendor training is a tour of the interface, which nobody remembers and which was never the problem. The thing that changes output quality more than any product difference is whether the clinician speaks the findings they want recorded.
Research puts scribe error highest on the physical examination, which is precisely the part most clinicians perform in silence. A clinician who narrates the examination gets a better note from every product on the market, and one who does not will blame the software for a gap they created.
So teach that, then teach reading the draft before signing, then stop. Two habits, taught in ten minutes, repeated. Everything else can be learned from the interface. Our review of where the errors concentrate is the evidence to show people who think it is a formality.
The monitoring framework, which is not optional
NHS England's ambient scribing guidance asks deploying organisations to implement a monitoring framework, and describes it as ongoing audits of clinical documentation, reviews of incident reports and reviews of system performance. That framework is part of your DCB0160, and a DCB0160 with a monitoring section that was never run is a document rather than a control.
Make it small enough to actually happen. Ten notes a month, read by someone other than the author, against the same criteria the pilot used. The point is not the sample size, it is that somebody is still looking in month seven.
Watch for drift specifically. Products in this category ship model changes frequently, and a note quality that was acceptable in March is not guaranteed in September. That is also why the supplier's clinical safety case report should be updated for every material release, covered in the clinical safety standards.
An incident route people will actually use
A clinician who catches an invented finding at half past six and corrects it has done the right clinical thing and taught the organisation nothing, because nobody else will ever know it happened. The reporting route has to cost less than the correction did or it will not be used.
One line, one place, no form. What the draft said, what was true, which consultation. Read weekly, and separate the harmless from anything touching medication, dose, allergy or a result value.
If the product is a medical device, a serious incident is reportable to the MHRA through the Yellow Card scheme and the manufacturer has its own legal duty to report. Most transcription and summarisation products are not devices after the MHRA guidance of 29 July 2026, which changes the reporting route and not the value of keeping the log.
Plan for the people who quietly stop
Track usage per clinician weekly and treat a collapse as a finding rather than a data problem. The published evidence is full of wide ranges that average into a comfortable number, and a product some people have abandoned looks identical in a monthly report to one everybody uses moderately.
When someone stops, ask once and take the answer seriously. The reasons are usually mundane. It is slow to start, it gets the examination wrong, it does not fit a particular clinic type, the login times out, the headset is in a drawer. Most are fixable and none get fixed if nobody asks.
Some specialties genuinely fit this technology worse than others, and a clinician who tried properly and stopped is evidence rather than resistance. Let them stop, and note why.
Write down what would make you stop
Agree the stop rule before the rollout, for the same reason you agree acceptance criteria before a pilot. It is much harder to decide something is not working once a contract is signed and a rollout has a champion.
Reasonable stop rules look like this. The audit finds errors reaching the record that the clinician did not catch. Usage falls below a threshold across a cohort after the learning curve should have finished. The supplier ships a change that materially alters output without notice.
Stopping is not failure, and the option to stop is worth negotiating into the contract while walking away is still cheap. Ask about exit terms and the price in year two before you sign, which is covered in what to ask a scribe vendor.
Where wai sits
We would rather a rollout worked than a contract renewed, which sounds like a slogan and is mostly a statement about where the difficulty is. The second month is harder than the first and gets less attention from every vendor in this market, including us when we are not careful.
wai shows its working, so a reviewing clinician checks reasoning rather than trusting output, and every patient-affecting action waits for approval. That is what makes the monitoring above possible rather than theatrical.
Ask us what happens in month seven, not month one. Clinicians still decide what enters the record.
Bring the clinician who did not want it. Fifteen minutes, on the part that usually goes wrong.
Request a demoFrequently asked questions
What usually goes wrong when an AI scribe is rolled out?
Uneven use that averages into a comfortable number. In the Cleveland Clinic evaluation the median participant ran 61 encounters across four weeks with a range from 1 to 181, and a five-centre study was reported under the heading of modest time savings and inconsistent use. Some clinicians quietly stop and the monthly report looks fine.
What training actually matters?
One habit. Speak the findings you want recorded, especially during the examination, because research puts scribe error highest there and it is the part most clinicians perform in silence. Then read the draft before signing. Two habits taught in ten minutes and repeated beat any interface tour.
What is a monitoring framework and do we have to have one?
NHS England's guidance asks deploying organisations to implement one, described as ongoing audits of clinical documentation, reviews of incident reports and reviews of system performance. It forms part of your DCB0160. Make it small enough to survive, such as ten notes a month read by someone other than the author.
How should errors be reported internally?
In a route that costs less than the correction did, or it will not be used. One line, one place, no form. What the draft said, what was true, which consultation. Read weekly, and separate the harmless from anything touching medication, dose, allergy or a result value.
Do we report AI scribe errors to the MHRA?
Only if the product is a medical device, in which case a serious incident goes through the Yellow Card scheme and the manufacturer has its own legal duty to report. Most transcription and summarisation products stopped being devices after the MHRA guidance of 29 July 2026, which changes the route rather than the value of keeping the log.
What should we do when a clinician stops using it?
Ask once and take the answer seriously. The reasons are usually mundane and fixable, such as a slow start, a poor examination section, a login that times out or a headset in a drawer. Some specialties genuinely fit this worse, and a clinician who tried properly and stopped is evidence rather than resistance.
Should we agree a stop rule?
Yes, and before the rollout, for the same reason acceptance criteria are agreed before a pilot. It is much harder to decide something is not working once a contract is signed and the rollout has a champion. Negotiate exit terms while walking away is still cheap.
Sources
Ask about month seven
Fifteen minutes on your workflows. If it is a fit we reply within 24 hours.
Partner with us
See it on your own patients, then build it with us
Thirty minutes on your own patients, doctors and rules, in your market. We reply within one working day, and the clinics that partner with us early shape what we build next.
See what wai does between the visits
