Quality improvement training ROI: how to quantify the savings from administrative improvement projects

No items found.
Blog thumbnail image

A hospital team redesigns its claims workflow. It trains the administrative staff on the new process, and six months later the cost per claim is lower. The finance office is pleased and asks for a number: how much did the training save?

The honest answer is harder than the question. In the same six months, staffing changed, claim volumes moved and a payer altered its rules. Some of the saving came from the redesign, some from the training and some from none of the above. Quality improvement training ROI is the work of separating those pieces and reporting what remains with a stated level of confidence.

This is an illustrative scenario, not a documented case. This guide is for hospital L&D directors and the informatics or compliance leads who work with them. It covers how to define the comparison, measure the actual task, connect that evidence to operational data, rule out other explanations and report results without overclaiming.

What is quality improvement training ROI?

Quality improvement training ROI compares the benefits of a training-linked improvement project with its costs. It asks what the organisation gained that it would not have gained without the training, and whether that gain was worth what the training and the project cost. The most common form is simple: net benefits (benefits minus costs) divided by costs, shown as a percentage.

The arithmetic is the easy part. The hard part is deciding which benefits belong to the training. The ROI Institute, which promotes a five-level evaluation framework, lists "isolate project effects" as its own step when analysing the data (ROI Institute). Its five levels are reaction, learning, application, impact and ROI. Satisfaction and completion sit at the first level. They are useful delivery indicators, but they are not evidence of savings.

Quick facts

QuestionShort answer
What is the task?Measure the cost and benefits of a training-linked improvement project.
What do you score?Net cost estimates and the confidence in attribution.
Is a satisfaction survey enough?No. It shows how the course was received, not what it saved.
Who validates the method?A finance partner and an informatics or compliance lead.
What can training not fix?Staffing changes, volume swings and payer rules happening at the same time.
How do you know it worked?A comparison of baseline and follow-up tasks plus operational data, with other causes checked.

1. Define the outcome and the comparison

Before collecting any data, write down three things: the intervention, the roles affected and the decision the analysis must support. "Did the training save money?" is too vague. "Should we extend the claims-workflow programme to the second site?" is a decision, and it tells you what evidence would be enough.

Then separate two kinds of cost. Delivery costs cover design time, facilitator or coach time, learner hours, materials and any software. Operational costs cover the changes to the process itself: new tools, revised procedures, temporary double-running while staff learn the new method. Training ROI that counts only delivery costs flatters the programme. ROI that counts everything may be the right measure for the improvement project but unfair to the training. Decide which question you are answering and say so in the report.

Staff time deserves care. Hours spent in training are a real cost even when nobody sends an invoice, so record them using a rate your finance partner agrees.

2. Measure the actual task

The task here is not "attend the programme". It is something the learner does at work, such as correcting claims against the new checklist, coding denials by cause or recording an exception. Measure that, using observable evidence.

  1. Set a baseline before training: a sample of real or realistic tasks scored against agreed criteria.
  2. Run a comparable assessment after training, using new tasks of similar difficulty rather than the ones learners practised on.
  3. Keep completion and satisfaction as delivery indicators, reported separately.

This is where task evidence earns its place. If staff can now do the task more accurately on unseen cases, the link between training and any operational change becomes plausible. If they cannot, a saving is unlikely to be the training's doing. For more on writing practice and feedback that link to a task, see our guide to designing interactive practice with useful feedback.

3. Connect task evidence with operational data

Now put the task evidence next to the operational data. For each measure, record four things: the population (who is included), the denominator (per claim, per staff member or per month), the period and the source.

Common measures in administrative improvement projects include rework rate, the share of claims denied for avoidable reasons, time to complete a task and the cost per transaction. Convert each change to money only with a unit cost your finance partner has approved. Then produce the figure that matters:

  • Estimated benefit: the change in the measure multiplied by the agreed unit cost.
  • Share attributed to training: a justified percentage, not a guess, with the reasoning written down.
  • Net estimate: attributed benefit minus the training and project costs you decided to include.

Treat a plausible link as a plausible link. A fall in rework after training is consistent with the training working. It does not prove it did.

4. Account for alternative explanations

Work through what else changed during the comparison period. A short checklist helps:

  1. Workload. Did volumes rise or fall? A quieter quarter often means fewer errors.
  2. Staffing. Did experienced people leave, or new ones join who were never trained?
  3. Customer or payer mix. Did the types of claim change?
  4. Process or system changes. Did anything else about the workflow change at the same time?

Where you can, use a comparison. A matched comparison looks at a similar team that did not yet have the training. A phased rollout gives you that comparison almost for free: the teams trained later act as a control for the teams trained first. Neither is always possible in a hospital, where every team may need the change at once, and in that case you report a lower confidence level honestly.

A 2022 review in BMC Health Services Research of the return on large-scale healthcare quality improvement is useful here. Its authors define return broadly, as any monetary or non-monetary value derived from quality improvement, and point out that outcomes are interlinked and hard to observe. They suggest assessing contribution to outcomes rather than claiming direct attribution, and call traditional ROI "a distal and an incomplete marker of QI value" (Thusini et al., BMC Health Services Research, 2022). That fits administrative projects too. Report the evidence of contribution and the confidence you have in it, not a single figure with false precision.

5. Report results and choose the next action

A report that a finance committee can act on fits on one page. This sample layout leaves the result fields empty on purpose. Fill them with your own data, never with borrowed effect sizes.

FieldWhat to recordResult
Intervention and rolesProgramme, project and who took part
Population and periodWho is included, from when to when
Baseline and follow-up task scoresSame criteria, different cases
Operational measure and denominatorFor example rework rate per 100 claims
Estimated benefitChange multiplied by approved unit cost
Share attributed to training and whyReasoning, comparison used
Delivery and operational costsListed separately
Net estimate and confidenceHigh, medium or low, with the reason
Other changes in the periodWorkload, staffing, mix, process
Recommended actionScale, revise or stop

Decide in advance what would justify each action. You might scale the programme when task scores improved on unseen cases, operational measures moved in the expected direction, other explanations were checked and the net estimate stays positive on cautious assumptions. You might revise it when task scores improved but operational measures did not, which suggests constraints outside training. You might stop it when neither moved. Agree these rules with your sponsor before you see the numbers, so the result does not decide the criteria.

Work through a realistic example

Illustrative. A finance partner and an informatics or compliance lead should validate the case and the answer criteria before use.

The case. A team redesigns a claims workflow while staffing and volumes also change. Rework fell in the six months after training. Two experienced coders left in the same period, and volume dropped slightly in the second quarter.

The task. The learner estimates the savings the training can reasonably claim, explains the decision, cites the evidence and names the information still missing.

A first attempt. "Rework fell, so the training saved the whole difference. I multiplied the drop by our cost per rework and reported that as the ROI." This credits the training with everything and ignores the other changes.

Feedback and retry. The coach asks what else changed, whether the trained and untrained staff differ and where the unit cost came from. The learner is asked to split the benefit.

A stronger attempt. "Rework fell, but two experienced coders left and volume dropped, so I cannot attribute all of it to training. Task scores on unseen cases rose, which supports a training contribution. I would report the observed saving, a reduced share I can justify, and a low-to-medium confidence rating. To raise confidence I need rework by trained and untrained staff, and the unit cost from finance." This separates observed savings from caused savings and says what evidence is missing.

Assess capability with a simple rubric

Score each criterion from 0 to 2:

CriterionObservable evidence
Task executionMeasures the cost and benefits of a training-linked project and records the evidence supporting each figure.
ReasoningExplains constraints, alternatives and uncertainty, and checks net cost estimates and confidence in attribution.
BoundariesUses approved procedures and seeks help when information or authority is insufficient.

Anchors: 0 is absent or unsupported, 1 is partial with relevant omissions, and 2 is complete and justified against the agreed criteria. Define critical errors separately, such as attributing the full change to training with no check for other causes, so an overall score cannot hide one. This rubric is a proposal, not a validated readiness standard: adapt it with the practitioner and pilot it. To match each activity to the thinking it demands, see our guide to matching learning activities to Bloom's Taxonomy.

Where interactive delivery helps

Interactive formats help where people should commit before they hear the answer. In a live session, a facilitator can show the claims case, ask each person to type the share of the saving they would attribute to training, and then show the spread before discussing why estimates differ. The same case can run self-paced for preparation. AhaSlides supports interactive learning and moving between live and self-paced delivery. Check any specific authoring, feedback or reporting function you plan to rely on against your own workflow, and treat AI, simulators and system integrations as external or unconfirmed until you have seen them work. For guidance on choosing formats, see our article on when to use adaptive, interactive and live learning.

Constraints that may remain

  • Attribution. Without a comparison group, you can estimate a contribution, not prove a cause.
  • Time lag. Some savings take quarters to appear, and a short window can miss them.
  • Data quality. Operational data may be incomplete, or its definitions may change mid-period.
  • Other changes. Staffing, volume and payer rules can swamp a small training effect.
  • Transfer. Performance on a training case is not the same as performance under daily pressure.

Name these to sponsors early. Training improves what people can do. It does not change the conditions around the work.

Frequently asked questions

What is quality improvement training ROI?

It compares the benefits of a training-linked improvement project with its costs, usually as net benefits divided by costs. The key step is isolating how much of the benefit the training can fairly claim.

Can you prove training caused the savings?

Rarely. A matched comparison or a phased rollout gives stronger evidence, but in most hospital settings you report a justified contribution and a confidence level rather than proof.

Should delivery costs and operational costs be counted together?

Report them separately. Delivery costs describe the training itself. Operational costs describe the wider improvement project. Say which total your ROI uses.

Is a satisfaction survey evidence of savings?

No. Satisfaction and completion are delivery indicators. Savings need task evidence and operational data.

Where to start

Pick one improvement project that already has a baseline. Write the decision the analysis must support, list the costs you will include, choose one operational measure with its denominator and have a finance partner approve the unit cost. Draft the one-page report with the result fields empty, and agree the scale, revise or stop rules before the data arrives.

To see how a case like this could run live with your own team, and be reused self-paced afterwards, explore AhaSlides.

Subscribe for tips, insights and strategies to boost audience engagement.
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Check out other posts

AhaSlides is used by Forbes America's top 500 companies. Experience the power of engagement today.

Get started free
© 2026 AhaSlides Pte Ltd