Recommended Free Tools
iTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Short answer: 43 minutes and 12 minutes are not measurements of the same thing. The UK government reported that a Microsoft 365 Copilot pilot across 90 NHS organisations found the tool could save an average of 43 minutes per staff member per day or more. The roughly 12-minute figure is Office Watch’s conversion of a separate four-hours-per-month figure attributed to the underlying evaluation. It is not an independently published NHS daily measurement.
A separate HM Revenue & Customs trial estimated about 60 minutes saved per week from participant self-reports, after an adjustment. That is useful context, but none of these figures proves a universal saving for every Copilot user or establishes that the NHS headline was “really” 12 minutes.
What the NHS actually claimed
The Department of Health and Social Care and NHS England announced the NHS result on 21 October 2025. Their release described a pilot of Microsoft 365 Copilot involving more than 30,000 workers in 90 NHS organisations. It said AI-powered administrative support “could save NHS staff on average 43 minutes per staff member per day or more.” The announcement also described that as equivalent to five weeks of time per person annually.
Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsThose words matter. “Could save” and “on average” describe an estimated potential, not a guarantee that every employee saved 43 minutes every working day. The same release projected that a full rollout could free up to 400,000 staff hours per month and said the NHS estimated potential savings of millions of pounds per month based on 100,000 users. These are government projections, not independently audited realised savings.
#1 Best Overall
Darren Hardman, CEO of Microsoft UK and Ireland, used similarly qualified wording in the announcement: “By reducing admin and giving healthcare workers back a reported 43 minutes every day, Microsoft 365 Copilot can help the NHS redirect hundreds of thousands of hours each month towards patient care and potentially save hundreds of millions of pounds every year.” The word “reported” identifies this as a statement about the reported result, not a new measurement by Microsoft.
The public release does not explain the sample selection, denominator, calculation, survey questions, or whether time was directly observed. Office Watch later reported that a fuller evaluation was referenced in an FOI response, but the underlying report and response are not available in the material reviewed here. That means the press-release number cannot be independently reconstructed from the release alone.
Where the “12 minutes” number comes from
Office Watch reported that the evaluation document associated with the NHS claim contained a four-hours-per-month figure. Dividing four hours (240 minutes) across roughly 20 working days produces about 12 minutes per working day. That arithmetic explains the headline’s “real number,” but it does not turn the monthly figure into a direct daily observation.
Free tools Windows power users keep installed
One-click scans. No signup required.
In other words, 12 minutes is a conversion made by Office Watch, not a daily result stated in the NHS announcement. The two figures may also refer to different populations, tasks, or calculation methods. Treating 43 as a measured daily result and 12 as its corrected daily result would imply a like-for-like comparison that the available evidence does not support.
Office Watch also reported that the document referred to 86 self-selected case studies, while another passage apparently gave a count of 69. It reported a separate 33-minute-per-day figure in the same document as well. Because the primary evaluation was not located, those counts and figures should remain attributed to Office Watch rather than presented as independently verified NHS statistics.
How the figures compare
| Source and date | Participants and design | Reported saving | How to interpret it |
|---|---|---|---|
| DHSC and NHS England, 21 October 2025 | More than 30,000 staff across 90 NHS organisations | 43 minutes per staff member per day or more; up to 400,000 hours per month projected for full rollout | Official potential average and rollout projection; the release does not publish the calculation method |
| Office Watch, 2026 account of the NHS evaluation | 86 self-selected case studies reported, with 69 also appearing elsewhere in the document | Four hours per month converted to approximately 12 minutes per working day; a 33-minute-per-day figure also reported | Secondary reporting and arithmetic conversion, not an independently verified NHS daily measurement |
| HM Revenue & Customs, 9 July 2026 | 3,000 staff randomly allocated licences; 500 additional licences for selected volunteers or earlier-phase volunteers; 1,364 users answered the main survey | Self-reported savings of 2–3% of a working week, about 60 minutes per week for a full-time pattern | HMRC reduced estimates by approximately 20% and calls the result a baseline, not a precise impact measure |
| Government Digital Service, 2 June 2025 | 20,000 government employees in a 2024 experiment; 7,115 survey responses | 26 minutes per day, calculated from the midpoints of respondents’ selected ranges | Self-reported estimate with a 60-minute cap for the highest range, not a time-and-motion measurement |
What HMRC’s trial adds
HMRC’s phase-three evaluation, published on 9 July 2026, provides a clearer description of study design than the NHS press release. The trial ran from September through December 2024. Three thousand staff were randomly allocated licences. Another 500 licences went to selected volunteers or people who had taken part in an earlier phase.
The primary survey received 1,364 responses, representing 45% of those randomly allocated licences. HMRC supplemented the survey with usage monitoring, focus groups involving 35 people, and a task exercise involving 49 people. Participants estimated that Copilot saved 2–3% of their working week, which HMRC expressed as approximately 60 minutes for a full-time working pattern.
HMRC then reduced the estimate by about 20%. The adjustment allowed for licence holders who did not use Copilot and for the possibility that survey respondents were more active users than non-respondents. HMRC describes the resulting number as a baseline estimate rather than a precise impact measure.
This is stronger contextual evidence than a single headline because it states the allocation, response rate, supplementary methods, and adjustment. It still relies primarily on self-reported time savings, however, and it was not an NHS trial. Its 60-minute weekly estimate cannot be used to confirm or refute the NHS’s 43-minute daily figure.
What the Government Digital Service found
The Government Digital Service ran an experiment from 30 September to 31 December 2024 involving 20,000 government employees across participating organisations. It collected adoption and usage data, a user survey, feedback forms, and five focus groups. The survey produced 7,115 responses.
GDS did not ask respondents to provide a single exact number. Instead, people selected a time-saving range. Analysts calculated an average by using each range’s midpoint and assigning 60 minutes to the largest band. That process produced an average self-reported saving of 26 minutes per day.
What’s actually slowing this PC down?
Pick the symptom - the matching free tool is one click away.
Because the result comes from estimated ranges rather than direct observation, it should not be read as 26 minutes recovered on a stopwatch. The report also notes that benefits were harder to realise for nuanced, complex, or data-heavy work, and that security or sensitive-data concerns reduced benefits for a minority of users.
Why the Australian Treasury evaluation is a warning
The Australian Treasury evaluated a 14-week Copilot trial in 2024. Participants volunteered, the study had no robust counterfactual, and the sample may have favoured people who were already interested in generative AI. Only 100 staff had matched pre-trial and post-trial survey data, and the evaluation relied mainly on self-reported information.
The Treasury report does not provide a comparable daily time-saved figure in the passages available here. Its value is methodological: a short trial, volunteer recruitment, limited matched data, and no strong comparison group make it difficult to separate tool effects from enthusiasm, changing habits, or ordinary variation in workload.
How to judge any Copilot productivity number
Before comparing two percentages or minute counts, check the following six dimensions:
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11- Outcome: Is the number self-estimated time saved, an objectively timed task, usage, adoption, satisfaction, or a modelled capacity projection? These are different outcomes.
- Denominator: Does it include every licence holder, only active users, survey respondents, volunteers, or selected success stories? A result from active users will usually differ from one that includes non-users.
- Study design: Random allocation, a control or counterfactual, and matched before-and-after observations increase confidence that the tool caused the change.
- Calculation: Did participants enter exact values or choose ranges? Were range midpoints used? Were non-users included? Is the period daily, weekly, or monthly?
- Task and context: Drafting routine administrative text and summarising meetings may produce different results from clinical reasoning, confidential work, or data-heavy analysis.
- Time and maturity: Trial length, training, product version, and the time people need to build new habits can all change usage and measured benefit.
The NHS announcement leaves several of these questions unanswered. HMRC and GDS document more of their methods, but their estimates remain largely self-reported. That is why the numbers should be treated as context-specific indicators rather than a universal Copilot rate.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What the NHS projection means in practice
The projected 400,000 hours per month is a capacity calculation tied to a full rollout, not a timesheet showing that NHS employees actually banked that many hours. The release also tied potential savings of millions of pounds per month to an assumed 100,000 users. Both figures depend on adoption, the mix of jobs, the tasks people use Copilot for, and whether released time is redirected to patient care or absorbed by other work.
Even the 43-minute wording includes “or more,” which makes it unsuitable as a personal quota. A worker who uses Copilot only for occasional drafting should not expect the same result as someone whose role includes frequent notes, correspondence, meeting summaries, or other administrative tasks. Conversely, a high estimate does not mean every minute becomes available for clinical activity; checking outputs, handling sensitive information, and correcting errors also consume time.
A practical way to measure your own result
Organisations that need a defensible number should measure their own workflow rather than borrow a headline. A simple evaluation can separate genuine time saved from impressions:
- Define the tasks first. Choose a small set of repeatable activities, such as drafting a standard update, producing a meeting summary, or converting notes into a template.
- Record a baseline. For a representative period before deployment, record task duration, rework, and quality checks. Keep the task definitions unchanged.
- Track all assigned users. Include people who do not use the licence, not only enthusiastic adopters. Record usage so non-use is visible rather than silently excluded.
- Measure quality and risk. A shorter first draft is not a saving if reviewers spend longer correcting omissions, factual errors, tone, or data-handling problems.
- Use a comparison where possible. A similar team without Copilot, or a staggered rollout, gives a better counterfactual than a simple before-and-after impression.
- Report the denominator and period. State whether the result is per active user, per licence holder, or per respondent, and whether it is daily, weekly, or monthly.
- Repeat after adoption settles. Early novelty and training effects can inflate or depress results. A second measurement period shows whether the initial estimate persists.
This approach will not produce a universal number either, but it will tell an organisation whether Copilot helps its own roles, under its own security rules and workload patterns.
Bottom line
The NHS’s 43-minute figure is an official reported potential average from a large pilot, not a guarantee or an independently audited daily measurement. The roughly 12-minute figure comes from converting a separately reported four-hours-per-month figure; it is not a direct NHS finding and should not be presented as the definitive correction. HMRC’s approximately 60 minutes per week and GDS’s 26 minutes per day show how different designs and calculations produce different self-reported results. The honest conclusion is that Copilot may return meaningful administrative time, but the size of that benefit depends on who is measured, which tasks are counted, and how the estimate is calculated.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
