The Rounds Journal · Healthcare finance

How to evaluate a healthcare cost-saving proposal

Check whether a proposed saving can be realised and what it might shift elsewhere.

Written byThe Rounds editorial team
Published
Reading time5 min read

Check whether a proposed saving can be realised and what it might shift elsewhere.

Identify what would actually change

Write down which expense could fall, who controls it and when the reduction could happen. In an illustrative scheduling change, staff may spend fewer hours on rework while payroll stays the same. Finance can help distinguish time made available for other tasks from an actual reduction in spending.

Include the implementation cost

Record the training, setup and staff time required to put the change in place. Separate one-off costs from those that repeat. Ask which assumptions have the largest effect on the result and show what happens if the benefit takes longer than expected.

Look for costs transferred to another team

Ask who will handle exceptions, extra calls or corrections once the process changes. Agree what you will measure and when you will review it. Escalate decisions affecting clinical care through your organisation’s approved processes.

Read the related guide →

Model a first-year example

Suppose an administrative change could avoid 1,000 currency units in monthly contractor charges from month four. With nine months of savings and a one-off setup cost of 4,000, the illustrative first-year net saving is 5,000. If the contract cannot change until month seven, six months of savings reduce that figure to 2,000. Ask finance to confirm the treatment before using it in a proposal.

Name the risks reviewers can check

Record who can change the contract, what happens during the transition and which assumption would invalidate the estimate. If extra corrections fall to reception, agree how the service will measure that workload and who will help if it rises.

Agree the review before approving the change

Set a baseline for invoice spend and processing time. Name the owner of each measure and the review date. Ask what would prompt the organisation to revise or stop the change.

Identify which benefit the proposal is claiming

Ask the person proposing the change to name the activity, its current cost and what would change in the ledger or in available staff time. If a routine task takes fewer minutes, the team may have more capacity for other work. If an external invoice would actually fall, ask when and how that would happen. If the proposal relies on avoiding future spending, identify the spending that would otherwise occur and what supports that assumption. Put these types of benefit on separate lines and review them with finance.

Record the scope, including the teams and period covered. If several projects expect to claim the same improvement, ask which assumptions overlap. A faster form and a new roster may both release time in the same workflow. Adding the two estimates could overstate what can be achieved if both rely on the same work disappearing. Agree how to measure the combined effect if both go ahead.

Check how the numbers move if assumptions change

In the fictional contractor example, ask when the agreement can be changed, who can authorise that and whether setup costs are incurred before any saving begins. Make a small table for the expected case and a delayed case. Show which months include costs and which months include benefits. If the proposal depends on reducing a volume of work, explain what happens if demand stays higher than expected. Record the assumption that matters most to the conclusion and how you would confirm it before committing.

Try a second example. A process change could save ten minutes per request and affect 30 requests a week. That is five hours in an illustrative week if each request receives the full benefit. Check whether staff can use the time for another agreed task and whether part of the work moves to another group. If the change only applies to half the requests, the expected time released is two and a half hours before accounting for any extra work. Show both cases and say what you would measure in a trial.

Make the review decision clear before implementation

Agree who owns the change, what evidence will be collected and when it will be reviewed. Track the financial effect and the effect on the service. A team could spend less on an activity while workloads rise elsewhere, so decide which balancing measure would reveal that. Ask the responsible people what would make them adapt or stop the change. Use the organisation’s approval routes where it could affect clinical work or safety.

At the review, compare actual costs and activity with the assumptions approved at the start. Record benefits that occurred, benefits still expected and costs that were missed. If you cannot verify the effect, say which information is missing and whether the proposal needs another trial. Ask finance to confirm how any saving will be recorded. The decision note should say what happened, who accepted the conclusion and when it will be checked again.

For the monthly follow-up, use the budget variance guide to trace the difference between planned and actual spending.

If you present annual figures, include the months covered and show any early setup cost separately. This lets reviewers distinguish the first-year decision from the ongoing commitment.

Explore more resources →