The Rounds Journal · Healthcare finance
How to write a business case for additional hospital staff
Set out the workload, compare realistic options and make a staffing request finance can evaluate.
Set out the workload, compare realistic options and make a staffing request finance can evaluate.
Describe the decision in one sentence
State the service, the capacity problem and the decision you need. Include the demand period, the workload you can currently cover and the implications of leaving the gap unresolved. Check assumptions with the people responsible for operations and finance.
A monthly average can hide a recurring Monday backlog. Compare the pattern by day or shift before assuming that adding the same hours every day will help.
Compare options using the same assumptions
In an illustrative administrative service, 60 additional files a week at 15 minutes each imply 15 hours of processing before meetings, leave or training. Check whether the time estimate reflects straightforward and complex cases. Use measured workload where available.
Set out options such as moving existing hours to the busiest period, removing avoidable rework or requesting additional paid hours. Separate recurring costs from setup costs and ask finance to confirm how they should be calculated.
State what you will review after approval
Show who owns implementation and when you will review backlog, turnaround and the effect on other teams. Explain what would make you revise the proposal. Attach calculations where reviewers can see the inputs.
Use your organisation’s staffing and escalation procedures for clinical safety decisions. This costing example uses administrative work and does not set a clinical staffing level.
Read the hospital budget guide for more context.
Write the opening for a decision-maker
A concise request names the service, the additional capacity, the period and the reason for asking now. A fictional office might request a time-limited trial of extra administrative hours to test whether a recurring backlog can be cleared without shifting work to reception. Put the calculation and assumptions immediately below the request.
Include a downside case
If an estimate assumes 60 files but demand could fall back to 40, show the implied processing time at both levels. At 15 minutes per file that is 15 hours or 10 hours of processing. Add allowances only where justified by local evidence and distinguish paid hours from productive processing time.
Close with an approval question
State who will review the trial, when they will report and which signs would justify ending or extending it. Ask the budget holder to decide on the duration and funding route.
Give the reviewer enough information to challenge the request
State where the demand estimate came from, which dates it covers and whether some files are likely to take longer than others. If you used a sample, describe how it was selected. Compare activity with the available hours in the same period. A request may be delayed because staff have to wait for missing information, even if the total time spent processing each file is low. Check where the delay occurs before deciding whether more capacity would address it.
Make the supporting information short enough to check before the meeting. Include the workload table, an explanation of how you converted tasks into time, and costs checked with finance. Give one figure for the trial and show when it would be incurred. Label amounts that recur and any costs that only apply during setup. If funding is only available for a defined period, explain who will decide whether the arrangement can continue afterwards.
Compare the alternatives through the same questions
- How many hours would the option make available, and when?
- What work would move or stop as a result?
- Which other people or teams would be affected?
- Who can approve it, and what would delay implementation?
- Which measures would help the service decide whether to continue?
In the fictional file-processing example, reorganising existing hours might help if work builds up at a predictable time. If the backlog is driven by repeat requests for missing documents, improving the process could reduce work throughout the week. If the workload remains higher after those options are considered, you can explain which gap the extra hours are intended to cover. Ask each affected team to confirm the assumptions that depend on its work.
Set the review date and the decision criteria
Start with the backlog at the beginning of the trial, how long requests have been open and the expected inflow. Agree what should improve over the period and how you will know if the work has shifted elsewhere. Measure the hours used as well as the service outcome. A reduction in open files might reflect work temporarily moved to another queue, so check completion and any unresolved transfers before giving the trial credit.
At the review, record whether the data supports continuing, changing or ending the trial. If the service was unable to test the option as planned, explain why and say which assumptions are still untested. Keep the decision and its owner in the business case. This gives the next reviewer a record of what was approved and what the organisation got for the additional resource.
Send reviewers the smaller preliminary question if your baseline is still too weak for a funding decision. Ask whether they will support collecting missing workload information, and name who would do it.