Sale on Manual & Electric Hospital Beds - Starting from 25 September!

Introduction

A business case is an argument made to people who did not attend the meetings that produced it, will read it alongside a dozen competing submissions, and cannot ask follow-up questions before scoring. That constraint shapes everything about how one should be written. Cases fail far more often for being unevidenced or unclear than for proposing something unwise.

This guide sets out how to build a case that survives that reading. It covers how need is stated so a non-clinician can weigh it, why the risk of not proceeding is usually the strongest section, how options including doing nothing are handled, what whole-life detail reviewers expect, and the practical requirements cases most often omit. It is written for clinical, procurement and finance teams across the UK, Europe, the US, the Gulf and South Africa.

What drives the decision — the short version

Need — Stated as outcome. What care requires this, which patients benefit, what is compromised without it.
Risk — The cost of waiting. What happens if this is deferred another cycle, evidenced rather than asserted.
Whole life — Commitments created: consumables, servicing, training and replacement, not the purchase figure alone.

Why cases fail

The most common failure is asserting need instead of evidencing it. A case that says a service urgently requires a device, without utilisation figures, failure history or waiting time data, gives a reviewer nothing to score. It reads as sincere and ranks below a duller case that came with numbers.

The second failure is omitting the risk of not proceeding. Reviewers are choosing between requests that are all, in some sense, worth funding. What separates them is usually what happens if each is deferred. A case that does not answer that question forfeits its strongest argument, and reviewers often will not supply it on the author's behalf.

The third is treating compliance as an afterthought. Safety notices from bodies such as the MHRA can make a replacement obligatory, transforming a case from desirable to necessary and requiring a prominent statement. Clinical guidance from NICE establishes what a service is expected to provide, and WHO guidance on health technology management explains why whole-life commitments belong in the case rather than emerging afterwards.

What reviewers look for

The clinical need. Stated as an outcome for patients, not as a list of device features.
Evidence behind it—utilisation figures, failure history, waiting times or incident data, rather than assertion.
Risk of deferral. What happens if this waits another cycle, evidenced and quantified where possible.
Options considered. Repair, refurbishment, sharing and doing nothing, each with a stated reason for rejection.
Whole-life implications. Consumables, servicing, training and replacement, agreed with whoever carries the operational budget.
Compliance position. Regulatory standing, including any MHRA notice that makes action obligatory.
Practical requirements. Space, power, installation, IT integration and training, costed rather than mentioned.
Benefits realisation. How the organisation will know afterwards whether the expected benefit materialised.

How the criteria are applied

Criterion	What's assessed	Evidence used
Clinical need	Outcome for patients	Clinical evaluation, service data
Evidence	Substantiation of the need	Utilisation, failure and activity records
Risk of deferral	Consequence of waiting	Incident data, waiting time analysis
Options	Alternatives tested	Options appraisal
Whole-life impact	Recurring commitments	Consumable and servicing estimates
Compliance	Regulatory standing	Registration records, safety notices
Practical needs	Enabling requirements	Estates, IT and training assessments
Benefits realisation	How success is measured	Agreed measures and review point

How the cycle typically runs

The need is established from evidence before any product or supplier is considered.
Options including doing nothing are appraised, with reasons for rejection recorded.
Whole-life implications are estimated and agreed with the budget holder who will carry them.
Practical requirements are confirmed with estates and IT rather than assumed.
The case is written for a reader who was not present and cannot ask questions.
Benefits measures are agreed at submission so that realisation can be checked afterwards.

Advocacy and evidence: a case is not a pitch

There is a persistent temptation to write a business case as persuasion, emphasising strengths and passing lightly over weaknesses. Experienced reviewers read a great many cases and recognise the pattern quickly. A case that concedes nothing tends to be trusted less, not more, because every proposal has trade-offs and a document that shows none has clearly examined them.

Conceding limitations honestly is a strength. Stating that the preferred option costs more in consumables but avoids a servicing dependency, and explaining why that trade is worth making, demonstrates that the analysis was genuine. Reviewers score reasoning as well as conclusions.

What a strong business case contains

The clinical need, plainly stated. What care requires this equipment, which patients benefit, and what is compromised without it.
Evidence rather than assertion. Utilisation, failure history, waiting times or incidents so that a reviewer can weigh the claim.
The risk of not proceeding. Usually the most persuasive section, and the one most frequently left out.
Options appraised honestly. Including repair, refurbishment and doing nothing, each with a reason for rejection.
Whole-life commitments. Consumables, servicing, training and replacement, agreed with the operational budget holder.
Benefits realisation measures. How the organisation will judge afterwards whether the expected benefit appeared.

Writing for the reader you will not meet.

The practical discipline is to write for someone with no context. Avoid internal shorthand, expand every abbreviation on first use, and state the service and setting explicitly. Reviewers frequently score outside their own speciality, and a case that assumes familiarity with a particular clinical workflow will be scored by someone who does not have it.

Length is rarely the problem; density is. A short case with figures beats a long one with adjectives. ISO-published or quality management standards give supporting documentation a recognisable structure.

Disclaimer

This page is for general information only and does not constitute procurement, financial, clinical, legal or regulatory advice. Business case formats, approval thresholds, appraisal methods and governance routes vary by organisation, health system and country, and change over time. Always follow your own governance and financial procedures, and consult qualified procurement, finance, clinical and regulatory professionals for decisions specific to your organisation. medigear.uk accepts no liability for actions taken based on this content.

From decision to delivery Equipment your case can rely on.

We supply medical equipment to healthcare organisations across the UK, Europe, the US, the Gulf and South Africa. Everything is genuine, documented and supported, so approved priorities arrive compliant and stay running.

Get in Touch → WhatsApp Us

Frequently Asked Questions

The clinical need stated as a patient outcome, evidence substantiating it, the risk of not proceeding, options appraised including doing nothing, whole-life commitments agreed with the operational budget holder, the practical requirements for installation and training, the compliance position, and how benefits will be measured afterwards. Cases missing the risk section forfeit their strongest argument.

Most often, they fail because they assert need rather than evidence it. A case claiming urgency without utilisation figures, failure history or waiting time data gives a reviewer nothing to score against competing submissions. The second common failure is omitting what happens if the request is deferred, which usually separates otherwise similar cases.

Enough that the operational budget holder has seen and agreed them. Consumables, servicing, training and eventual replacement all recur for as long as the device stays in use, and a capital approval creates those commitments whether or not the case mentioned them. Optimistic whole-life sections are where cases most often come apart under scrutiny.

Generally not at the case stage. Requirements are better expressed functionally, so that procurement can test the market properly afterwards. Naming a product early narrows competition before evaluation begins and invites the question of how that choice was reached, which is awkward to answer if no comparison was run.

Density matters more than length. A short case with figures outperforms a long one with adjectives, because reviewers read many submissions and score what they can verify. Writing for someone with no context is the practical discipline: expand abbreviations, state the setting explicitly, and avoid assuming familiarity with a clinical workflow the reviewer may not share.

Yes. Every proposal involves trade-offs, and a document showing none has evidently not examined them. Stating that the preferred option costs more in consumables but avoids a servicing dependency, and explaining why that trade is worth making, demonstrates genuine analysis. Reviewers score reasoning as well as conclusions.

How to Build a Medical Equipment Business Case