Stress Testing:
A Practical Guide to Testing Resilience Under Severe Pressure

Stress testing is a planning, risk management and decision-making tool used to test how an organisation, project, forecast, system or strategy would perform under difficult, severe or adverse conditions.

At its simplest, stress testing asks:

What happens if things get significantly worse than expected, and could we still cope?

That makes it useful for business planning, cash flow management, forecasting, risk management, charity governance, public sector planning, banking, property development, construction, manufacturing, cyber security, business continuity, project management and board reporting.

Used properly, stress testing helps organisations understand whether their plans are resilient enough. It does not predict that a severe event will happen. It tests whether the organisation could survive, adapt or recover if it did.

What is stress testing?

Stress testing examines the effect of severe but plausible adverse conditions.

It tests what would happen if important assumptions moved sharply against the organisation.

For example:

1. Sales fall by 25%.
2. A major customer is lost.
3. A key grant is not renewed.
4. Interest rates rise materially.
5. Build costs increase by 15%.
6. A critical supplier fails.
7. Customer payments are delayed by 60 days.
8. A cyber attack disrupts operations.
9. Staff absence rises sharply.
10. Energy costs increase significantly.
11. A project is delayed by six months.
12. Demand for a service rises beyond capacity.
13. A major tenant defaults.
14. Funding is delayed.
15. A regulatory change increases costs.

The aim is to understand:

1. What would break first?
2. How much headroom exists?
3. Which assumptions are most dangerous?
4. Which risks could combine?
5. Which controls would be tested?
6. What early warning signs should be monitored?
7. What actions would be needed?
8. Whether the organisation remains within risk appetite.
9. Whether contingency plans are strong enough.
10. Whether the strategy is still viable.

Stress testing is especially useful when normal forecasts look acceptable but management needs to know what happens under pressure.

Stress testing, sensitivity analysis and scenario analysis

Stress testing is closely related to sensitivity analysis and scenario analysis, but it is not the same.

Sensitivity analysis

Sensitivity analysis changes one assumption at a time.

It asks:

What happens if this assumption changes?

Example:

What happens if sales fall by 10%?

Scenario analysis

Scenario analysis changes several assumptions together to create a plausible alternative future.

It asks:

What happens under this different set of circumstances?

Example:

What happens if sales fall by 10%, costs rise by 5%, and customer payments slow by 15 days?

Stress testing

Stress testing applies more severe pressure to test resilience.

It asks:

What happens under serious adverse conditions, and can we survive or recover?

Example:

What happens if sales fall by 25%, a major customer pays late, costs rise, and bank facilities are reduced?

In simple terms:

Sensitivity analysis tests movement.

Scenario analysis tests alternative futures.

Stress testing tests resilience under pressure.

All three are useful. They answer different questions.

History and development of stress testing

Stress testing developed from risk management, banking, financial modelling, engineering, insurance, project appraisal and resilience planning.

Its use became especially prominent in banking and financial services because regulators, boards and investors needed to understand whether institutions could withstand serious economic shocks.

However, the principle is much wider than banking.

Any organisation can fail if a plan is only tested against comfortable assumptions.

A business may look profitable until a major customer is lost.

A charity may look sustainable until a grant is withdrawn.

A property development may look viable until build costs rise and completion is delayed.

A public service may look adequately resourced until demand increases sharply.

A software platform may look stable until usage spikes or systems fail.

A business continuity plan may look credible until the organisation tests whether people can actually operate without its normal systems.

Stress testing developed because decision-makers need to understand not only what is expected, but what could happen under pressure.

The key idea is simple:

A plan that only works in good conditions may not be strong enough.

Why stress testing matters

Stress testing matters because organisations often underestimate downside risk.

Plans can become too optimistic. Forecasts can assume normal conditions. Budgets can assume income arrives on time. Projects can assume costs remain stable. Strategies can assume markets behave sensibly. Boards can receive reports that show a base case without understanding the downside.

Stress testing helps challenge that.

It supports:

1. Better risk management
2. Stronger cash flow planning
3. Better board and trustee oversight
4. More realistic forecasts
5. Better business continuity planning
6. Stronger investment appraisal
7. Better understanding of financial headroom
8. Earlier warning of emerging risk
9. Better contingency planning
10. Improved strategic resilience
11. More honest decision-making
12. Stronger lender or funder conversations
13. Better internal audit focus
14. Better assessment of risk appetite
15. Reduced false confidence

Stress testing is not about being pessimistic.

It is about being prepared.

A sensible organisation does not only ask:

What do we expect to happen?

It also asks:

What would we do if things turned against us?

When to use stress testing

Stress testing is useful whenever an organisation needs to understand resilience under pressure.

Common uses include:

1. Cash flow planning
2. Budget approval
3. Business planning
4. Investment appraisal
5. Property development
6. Construction projects
7. Charity reserves planning
8. Public sector financial planning
9. Bank lending assessments
10. Covenant testing
11. Strategic planning
12. Business continuity planning
13. Project approval
14. Cyber resilience
15. Supplier dependency review
16. Workforce planning
17. Service demand planning
18. Risk appetite review
19. Board reporting
20. Scenario planning

It is especially useful where:

1. The decision is material.
2. The downside could be serious.
3. Financial headroom is limited.
4. Income is uncertain.
5. Costs are volatile.
6. Delivery depends on third parties.
7. A project is long-term.
8. There are major assumptions.
9. The organisation has legal or safeguarding duties.
10. Failure would damage reputation or continuity.

It is less useful when used as a theoretical exercise with no link to action.

What can be stress tested?

Stress testing can be applied to many different areas.

Financial forecasts

Financial forecasts can be stress tested for:

1. Lower sales
2. Delayed customer receipts
3. Higher costs
4. Lower margins
5. Higher interest rates
6. Reduced funding
7. Higher bad debts
8. Lower occupancy
9. Higher payroll costs
10. Loss of a major customer

This helps assess solvency, cash headroom, reserves, covenant compliance and financial sustainability.

Cash flow

Cash flow stress testing is especially important.

A business can be profitable but still run out of cash.

Cash stress tests may include:

1. Major debtor paying 60 days late.
2. Sales receipts falling sharply.
3. Supplier payment terms tightening.
4. VAT or tax payment being higher than expected.
5. Payroll costs rising.
6. Loan repayments increasing.
7. Capital expenditure being required earlier.
8. Stock tying up more cash.
9. Grant income being delayed.
10. Emergency costs arising.

Cash flow is often where stress appears first.

Projects

Project stress testing may include:

1. Cost overruns
2. Programme delay
3. Contractor failure
4. Key staff loss
5. Scope changes
6. Supplier failure
7. Planning delay
8. Funding delay
9. Inflation
10. Stakeholder challenge

This helps test whether contingencies, governance and escalation arrangements are strong enough.

Business continuity

Business continuity stress testing asks whether the organisation could continue operating during disruption.

It may test:

1. Loss of premises
2. IT outage
3. Cyber attack
4. Staff absence
5. Supplier failure
6. Utilities failure
7. Communication breakdown
8. Data loss
9. Transport disruption
10. Loss of key records

A business continuity plan that has not been stress tested may be only a paper plan.

Systems and technology

Technology stress testing may examine:

1. System load
2. Cyber attack response
3. Data recovery
4. Backup restoration
5. Cloud provider failure
6. Failed software release
7. Integration failure
8. Support capacity
9. User spike
10. Security incident

For technology businesses, stress testing can reveal whether systems are resilient enough before customers experience failure.

Strategy

Strategic stress testing asks whether the organisation’s strategy still works under adverse conditions.

It may test:

1. Economic downturn
2. Market decline
3. Competitor disruption
4. Funding reduction
5. Regulation change
6. Technology shift
7. Customer behaviour change
8. Supply chain disruption
9. Workforce shortage
10. Reputational event

This is useful for boards and leadership teams because it challenges whether the strategy is robust.

Stress testing in different industries

SMEs and owner-managed businesses

For SMEs, stress testing should focus on survival, cash and operational resilience.

Small businesses often have limited financial headroom. They may depend on a small number of customers, a few key staff, a limited supplier base, or one owner-manager.

Typical SME stress tests include:

1. Sales fall by 25%.
2. Largest customer is lost.
3. Largest customer pays 60 days late.
4. Gross margin falls by 5%.
5. Payroll costs rise by 10%.
6. A key employee leaves.
7. A supplier demands payment upfront.
8. Bank facilities are reduced.
9. VAT payment coincides with lower receipts.
10. The owner is unavailable for four weeks.

An SME might ask:

1. How long can we survive with lower sales?
2. What cash headroom do we have?
3. Which costs can be reduced quickly?
4. Which customers create concentration risk?
5. Which suppliers are critical?
6. What would happen if the owner could not work?
7. What early warning signs should we track?
8. What action should we take now?

For SMEs, stress testing should be practical. It should lead to specific actions around cash, customers, costs, staffing and contingency.

Manufacturing

Manufacturing businesses need stress testing because operations depend on demand, materials, labour, energy, machinery and supply chains.

Typical manufacturing stress tests include:

1. Raw material costs increase by 15%.
2. Energy costs increase sharply.
3. A critical supplier fails.
4. Production volume falls by 20%.
5. A major machine is unavailable for two weeks.
6. Scrap rate doubles.
7. Customer demand changes suddenly.
8. Labour availability falls.
9. Transport disruption delays delivery.
10. A product recall is required.

A manufacturer might ask:

1. Which inputs create the greatest exposure?
2. What happens if material costs rise?
3. How long can production continue without a key supplier?
4. What stock buffer is needed?
5. What happens if machinery downtime increases?
6. Can customers be served from alternative production routes?
7. What happens to cash if stock builds up?
8. Which controls need strengthening?

For manufacturing, stress testing should connect production, finance, procurement, maintenance and customer delivery.

Retail and ecommerce

Retail and ecommerce businesses are exposed to customer demand, stock risk, returns, delivery, online platforms and advertising costs.

Typical stress tests include:

1. Website outage during peak period.
2. Conversion rate falls by 30%.
3. Advertising cost per sale doubles.
4. Return rate increases sharply.
5. Stock arrives late.
6. Supplier prices rise by 10%.
7. Delivery partner fails.
8. Marketplace account is suspended.
9. Customer demand falls after stock is purchased.
10. Negative reviews reduce conversion.

A retailer might ask:

1. What happens if peak sales underperform?
2. What happens if stock cannot be sold at full price?
3. What happens if returns increase?
4. What happens if online advertising becomes uneconomic?
5. What happens if the website fails?
6. How much cash is tied up in stock?
7. What customer communication plan is needed?
8. Which products are most exposed?

For ecommerce, stress testing should include both revenue and margin. Sales volume alone is not enough.

Professional services

Professional services firms need stress testing around clients, staffing, deadlines, work in progress, billing and professional risk.

Typical stress tests include:

1. Major client leaves.
2. Debtor days increase by 30 days.
3. Staff utilisation falls.
4. Fixed-fee work overruns.
5. Key partner or manager leaves.
6. Professional indemnity premium increases.
7. Regulatory deadline pressure increases.
8. Software failure affects client delivery.
9. Work in progress cannot be billed.
10. Client pipeline conversion falls.

For accountants, solicitors, consultants, architects and advisers, stress testing can ask:

1. What happens if a major client leaves?
2. What level of utilisation is needed to cover costs?
3. What happens if clients pay late?
4. What happens if staff costs rise?
5. What happens if a deadline is missed?
6. How much work in progress is recoverable?
7. Which services are most resilient?
8. Which clients create the most exposure?

Professional services stress testing should link profitability, capacity, quality and cash collection.

Charities and voluntary organisations

Charities need stress testing because they often face uncertain income, rising demand and limited reserves.

Typical charity stress tests include:

1. Major grant not renewed.
2. Donation income falls by 20%.
3. Payroll costs rise by 8%.
4. Service demand increases by 30%.
5. Restricted funding fails to cover full costs.
6. Reserves fall below policy level.
7. Volunteer availability reduces.
8. Funder payment is delayed.
9. Public sector contract is reduced.
10. Safeguarding or reputational incident occurs.

A charity might ask:

1. How long will reserves last under a deficit?
2. Which services are most financially exposed?
3. What happens if a major funder withdraws?
4. What happens if demand rises while income falls?
5. Which costs are fixed?
6. Which services could be protected?
7. What trigger points require trustee action?
8. What early action is needed?

For charities, stress testing should be linked to reserves policy, risk appetite, funding strategy, service impact and trustee oversight.

Public sector and local government

Public bodies use stress testing to understand service, budget and demand pressures.

Typical stress tests include:

1. Demand for statutory services rises sharply.
2. Savings plans are delayed.
3. Inflation exceeds budget assumptions.
4. Contract costs increase.
5. Grant funding reduces.
6. Contractor fails.
7. Workforce absence increases.
8. Major IT system fails.
9. Legal challenge delays delivery.
10. Public demand rises during an emergency.

A public body might ask:

1. What happens if demand rises above forecast?
2. What happens if savings are not delivered?
3. Which statutory services are most exposed?
4. What happens if contractors fail?
5. What level of reserves or contingency is required?
6. Which services would need prioritisation?
7. Which decisions need member or board approval?
8. What are the public value implications?

For public sector work, stress testing should be transparent, evidence-based and linked to governance.

Property and construction

Property and construction projects are highly suited to stress testing because they involve long timescales, high cost and major uncertainty.

Typical stress tests include:

1. Build costs increase by 15%.
2. Planning approval is delayed by nine months.
3. Interest rates rise.
4. Rental values fall.
5. Sales values fall.
6. Occupancy is lower than expected.
7. Contractor becomes insolvent.
8. Utilities connection is delayed.
9. Funding terms tighten.
10. Exit yield moves adversely.

A property appraisal might ask:

1. What happens if costs rise?
2. What happens if rents are lower?
3. What happens if completion is delayed?
4. What happens if interest rates increase?
5. What happens if sales take longer?
6. What is the minimum viable rent or sale value?
7. How much contingency is needed?
8. At what point does the project become unviable?

For property and construction, stress testing should be part of viability appraisal, board approval and ongoing project review.

Technology and software

Technology businesses need stress testing around growth, systems, cyber risk, customer behaviour and cash runway.

Typical stress tests include:

1. Customer acquisition cost doubles.
2. Churn increases sharply.
3. Monthly recurring revenue growth slows.
4. Hosting costs rise with usage.
5. Product launch is delayed.
6. Key developer leaves.
7. System outage affects customers.
8. Cyber attack disrupts operations.
9. Funding round is delayed.
10. Support tickets increase beyond capacity.

A software business might ask:

1. How long is the cash runway under lower growth?
2. What happens if churn rises?
3. What happens if customer acquisition becomes more expensive?
4. What happens if the product takes longer to develop?
5. Can systems cope with a usage spike?
6. What happens if the platform fails?
7. What customer communication plan is needed?
8. Which metrics provide early warning?

For technology businesses, stress testing should cover both financial resilience and operational resilience.

Healthcare and social care

Healthcare and social care organisations need stress testing because safety, staffing, demand and continuity matter.

Typical stress tests include:

1. Staff absence increases sharply.
2. Agency costs rise.
3. Occupancy falls.
4. Demand rises above planned capacity.
5. Funding rates do not match wage costs.
6. Medication system fails.
7. Care records become unavailable.
8. Safeguarding incident requires urgent action.
9. Inspection outcome creates improvement costs.
10. Supplier failure affects care delivery.

A care provider might ask:

1. What happens if staffing falls below planned levels?
2. What happens if agency costs rise?
3. What happens if occupancy falls?
4. What happens if care needs increase?
5. Can safe service levels be maintained?
6. What happens if key systems are unavailable?
7. What escalation routes exist?
8. What contingency is needed?

In healthcare and care, stress testing should support safety, quality, safeguarding and continuity. It should never be used to justify unsafe levels of service.

Education and training

Education providers can use stress testing for learner numbers, funding, staffing, safeguarding, course viability and technology.

Typical stress tests include:

1. Enrolment falls by 20%.
2. Funding rates reduce.
3. Completion rates fall.
4. Tutor absence increases.
5. Digital platform fails.
6. Employer placements reduce.
7. Learner support needs increase.
8. Assessment deadlines are delayed.
9. Inspection creates additional requirements.
10. Safeguarding pressures increase.

An education provider might ask:

1. How many learners are needed for a course to remain viable?
2. What happens if enrolments are lower?
3. What happens if funding is reduced?
4. What happens if completion rates fall?
5. What staffing contingency exists?
6. What happens if online delivery fails?
7. What support pressures could increase?
8. Which courses or programmes are most exposed?

For education, stress testing should link financial sustainability with learner outcomes, safeguarding and quality.

How to carry out stress testing properly

1. Define the purpose

Start by deciding why the stress test is being done.

Possible purposes include:

1. Test cash resilience.
2. Test business continuity.
3. Test project viability.
4. Test financial sustainability.
5. Test risk appetite.
6. Test a strategic plan.
7. Test an investment proposal.
8. Test reserves adequacy.
9. Test operational capacity.
10. Test system resilience.

A stress test should support a decision.

Without a clear purpose, it becomes a theoretical exercise.

2. Define the object being tested

Be clear about what is being stress tested.

It may be:

1. A cash flow forecast
2. A budget
3. A business plan
4. A project
5. A property appraisal
6. A charity reserves plan
7. A service model
8. A technology platform
9. A business continuity plan
10. A strategic plan

The stress test should match the object.

For example, a cash flow stress test should focus on receipts, payments, headroom and timing. A service stress test should focus on capacity, quality, staffing and continuity.

3. Identify key vulnerabilities

Before applying a stress, identify where the plan is vulnerable.

Ask:

1. What assumptions matter most?
2. What could change quickly?
3. What are we dependent on?
4. Where is financial headroom limited?
5. Which costs are fixed?
6. Which income is uncertain?
7. Which suppliers are critical?
8. Which people are essential?
9. Which systems are critical?
10. Which risks are already high?

This helps ensure the stress test focuses on the right pressures.

4. Design severe but plausible stresses

A stress test should be challenging, but not absurd.

Examples include:

1. Sales fall by 25%.
2. Customer receipts are delayed by 60 days.
3. Build costs rise by 15%.
4. A major funder withdraws.
5. A key supplier fails.
6. Staff absence doubles.
7. Interest rates rise by 2%.
8. System outage lasts three days.
9. Service demand rises by 30%.
10. Major customer contract is lost.

The stress should be severe enough to reveal weakness.

If the stress is too mild, it may provide false reassurance.

5. Test individual and combined stresses

Some stress tests examine one severe event.

Others combine several pressures.

For example:

Single stress: Sales fall by 25%.

Combined stress: Sales fall by 25%, debtor days increase by 30 days, and costs rise by 8%.

Combined stresses are often more realistic because adverse events can interact.

For example, an economic downturn may reduce sales, increase bad debts, tighten credit and increase pressure on cash at the same time.

6. Calculate the impact

The stress test should show the effect clearly.

Possible outputs include:

1. Closing cash balance
2. Minimum cash headroom
3. Profit or loss
4. Reserves level
5. Funding gap
6. Debt covenant position
7. Break-even point
8. Project viability
9. Service capacity
10. Recovery time
11. Staffing shortfall
12. System downtime
13. Customer impact
14. Regulatory impact
15. Reputation impact

The output should be relevant to the decision.

For example, if the question is survival, cash headroom may matter more than accounting profit.

7. Identify breaking points

Stress testing should identify where the organisation or plan fails.

Breaking points may include:

1. Cash falls below zero.
2. Reserves fall below policy level.
3. Debt covenants are breached.
4. Service standards cannot be maintained.
5. Staffing levels become unsafe.
6. Project return becomes negative.
7. Contingency is exhausted.
8. System recovery exceeds tolerance.
9. Regulatory deadlines cannot be met.
10. Risk appetite is exceeded.

This is one of the most valuable parts of stress testing.

It shows how much pressure the organisation can absorb.

8. Identify early warning indicators

A good stress test should identify warning signs.

Examples include:

1. Sales enquiries falling
2. Conversion rate reducing
3. Debtor days increasing
4. Cash headroom reducing
5. Grant decisions delayed
6. Supplier lead times increasing
7. Staff absence rising
8. Project milestones slipping
9. Support tickets increasing
10. Customer complaints rising
11. Stock turn slowing
12. Covenant headroom reducing
13. Website performance weakening
14. Demand exceeding capacity
15. Reserves falling

Early warning indicators help management act before the stress fully arrives.

9. Agree management actions

Stress testing should lead to action.

Possible actions include:

1. Reduce discretionary spending.
2. Increase cash monitoring.
3. Renegotiate supplier terms.
4. Strengthen credit control.
5. Build reserves.
6. Reduce customer concentration.
7. Secure alternative suppliers.
8. Increase contingency.
9. Pause or re-scope a project.
10. Strengthen business continuity plans.
11. Update the risk register.
12. Adjust risk appetite.
13. Review staffing plans.
14. Improve cyber controls.
15. Prepare stakeholder communication.

A stress test without action is only information.

10. Report and review

Stress testing should be reported clearly to the right audience.

For example:

1. Management team
2. Board
3. Trustees
4. Audit committee
5. Risk committee
6. Finance committee
7. Project board
8. Lender
9. Funder
10. Regulator where relevant

The report should explain:

1. Purpose
2. Base case
3. Stress applied
4. Result
5. Breaking point
6. Key risks
7. Mitigating actions
8. Decisions required
9. Owner
10. Review date

Stress tests should be updated when conditions change.

Common stress testing techniques

Reverse stress testing

Reverse stress testing starts with failure and works backwards.

It asks:

What would have to happen for the organisation, project or plan to fail?

For example:

1. What would cause cash to run out?
2. What would make the project unviable?
3. What would cause reserves to fall below policy?
4. What would cause service failure?
5. What would cause a covenant breach?
6. What would make the strategy fail?

Reverse stress testing is useful because it identifies critical vulnerabilities.

It can be more revealing than simply applying a standard downside case.

Severe but plausible scenario

This method creates a realistic but challenging adverse scenario.

For example:

A downturn reduces sales by 20%, customer payments slow by 30 days, and gross margin falls by 3%.

This helps test whether the organisation can survive a difficult but credible situation.

Combined stress test

A combined stress test applies several adverse movements at once.

For example:

1. Income falls
2. Costs rise
3. Cash receipts slow
4. Funding is delayed
5. Project costs increase

This is useful because real-world pressures often happen together.

Liquidity stress test

A liquidity stress test focuses on cash.

It asks:

Can the organisation meet payments as they fall due under stress?

This is especially important for SMEs, charities, property businesses, construction projects and highly leveraged organisations.

Operational stress test

An operational stress test focuses on delivery capacity.

It asks:

Can we continue operating if people, systems, suppliers or premises are disrupted?

This is useful for business continuity planning.

Technology stress test

A technology stress test examines whether systems can cope with pressure.

It may include:

1. Load testing
2. Cyber incident simulation
3. Backup restoration
4. Disaster recovery testing
5. Access failure testing
6. Supplier outage simulation

This is essential for digital businesses and organisations dependent on IT.

Common mistakes in stress testing

Mistake 1: Making the stress too mild

If the stress is comfortable, it will not reveal much.

A stress test should challenge the plan.

Mistake 2: Using unrealistic shocks

The stress should be severe but plausible.

If it is completely unrealistic, decision-makers may ignore it.

Mistake 3: Ignoring combined effects

Many pressures happen together.

Testing one issue at a time may understate the real danger.

Mistake 4: Focusing only on profit

Profit is important, but cash, capacity, compliance, service quality and reputation may matter more under stress.

Mistake 5: Ignoring timing

Timing can be critical.

A business may survive a loss over a year but fail if cash outflows happen before receipts.

Mistake 6: Not identifying breaking points

A stress test should show where the plan fails.

Without that, the organisation may not understand its true limits.

Mistake 7: Not linking to action

Stress testing should lead to decisions.

If no action follows, the test has limited value.

Mistake 8: Ignoring risk appetite

A plan may survive a stress but still move outside risk appetite.

For example, reserves may fall below the agreed minimum.

Mistake 9: Not involving the right people

Finance may understand the numbers, but operations, sales, HR, IT, safeguarding and service teams may understand the practical consequences.

Stress testing should involve relevant people.

Mistake 10: Not updating the test

A stress test becomes stale when assumptions change.

It should be reviewed regularly.

Limitations and weaknesses of stress testing

Stress testing is useful, but it has limits.

It does not predict the future

A stress test does not say the stress will happen.

It shows what would happen if it did.

It depends on the stress chosen

If the wrong stress is selected, the analysis may miss the real vulnerability.

It depends on model quality

A stress test cannot fix a poor model.

If the forecast, cash flow or project appraisal is wrong, the stress test may also be wrong.

It can create false confidence

Passing one stress test does not mean the organisation is safe.

Other stresses may still cause serious problems.

It can be too financial

Some stress tests focus only on numbers and miss operational, legal, people, safeguarding or reputational impacts.

It can be too pessimistic if misused

Stress testing should inform decisions, not paralyse them.

The aim is resilience, not fear.

It can be ignored

If the findings are uncomfortable, organisations may avoid acting.

Leadership and governance matter.

It does not replace judgement

Stress testing supports decision-making.

It does not make decisions by itself.

Stress testing compared with other strategic and management tools

Stress testing and sensitivity analysis

Sensitivity analysis tests how changes in assumptions affect outcomes.

Stress testing applies more severe adverse conditions.

Use sensitivity analysis to understand key drivers. Use stress testing to test resilience.

Stress testing and scenario planning

Scenario planning explores different plausible futures.

Stress testing examines whether the organisation can withstand a severe adverse situation.

Use scenario planning for strategic uncertainty. Use stress testing for resilience.

Stress testing and forecasting

Forecasting estimates likely outcomes.

Stress testing tests what happens if the forecast is badly wrong or conditions deteriorate.

Use forecasting for the base case. Use stress testing for downside resilience.

Stress testing and assumptions log

Stress testing identifies assumptions that could create serious exposure.

Those assumptions should be recorded, owned and reviewed in the assumptions log.

Stress testing and risk register

Stress testing can reveal risks or increase risk ratings.

The results should feed into the risk register, risk matrix and action planning.

Stress testing and risk appetite statement

Stress testing helps assess whether adverse conditions would push the organisation outside appetite.

For example, cash reserves, service standards or cyber recovery times may breach tolerance limits.

Stress testing and business continuity plan

Business continuity planning explains how operations will continue during disruption.

Stress testing checks whether those plans work under pressure.

Stress testing and internal audit

Internal audit can review whether stress testing is being performed, whether assumptions are reasonable and whether actions are followed up.

Stress testing and bow-tie analysis

Bow-tie analysis maps causes, consequences and controls.

Stress testing can test whether those controls are strong enough under severe conditions.

Stress testing and investment appraisal

Investment appraisal assesses whether a project is worthwhile.

Stress testing assesses whether the project remains viable under adverse conditions.

Alternatives and complementary frameworks

Sensitivity analysis

Use sensitivity analysis to test individual assumptions.

Best used before stress testing to identify the most important drivers.

Scenario analysis

Use scenario analysis to test plausible combinations of assumptions.

Best used for alternative future conditions.

Reverse stress testing

Use reverse stress testing to identify what would cause failure.

Best used when resilience and survival are central.

Business continuity planning

Use business continuity planning to prepare operational responses to disruption.

Best used where continuity of services, systems or sites matters.

Risk register

Use the risk register to record and manage risks identified through stress testing.

Assumptions log

Use an assumptions log to record key assumptions tested under stress.

Forecasting

Use forecasting to create the base case that stress testing challenges.

Cash flow modelling

Use cash flow modelling to test liquidity under pressure.

Best used for SMEs, charities, property projects and organisations with limited headroom.

Monte Carlo simulation

Use Monte Carlo simulation where many variables interact and probability ranges are useful.

Best used for complex financial, project or risk modelling.

A practical stress testing template

A useful stress testing template should include:

1. Stress test name
2. Purpose
3. Area tested
4. Base case
5. Key assumptions
6. Stress applied
7. Reason for stress
8. Output measure
9. Result under stress
10. Breaking point
11. Minimum headroom
12. Risk appetite impact
13. Early warning indicators
14. Mitigating actions
15. Contingency actions
16. Owner
17. Decision required
18. Link to risk register
19. Review date
20. Version control

Example:

Stress test: 13-week cash flow downside stress

Purpose: Test whether the business can meet payroll, VAT, suppliers and loan repayments if receipts are delayed.

Base case: Minimum cash headroom of £85,000.

Stress applied: Sales receipts fall by 20%, largest customer payment of £75,000 delayed by six weeks, and supplier payments remain due on original terms.

Result: Minimum cash headroom falls to £12,000 in week seven.

Breaking point: Cash becomes negative if one additional customer payment above £20,000 is delayed.

Risk appetite impact: Cash headroom is below the board’s minimum tolerance of £50,000.

Actions: Increase credit control, delay non-essential expenditure, discuss temporary facility with bank, review supplier payment timing, update weekly cash monitoring.

Owner: Finance Director.

Review date: Weekly until headroom improves.

Questions to ask during stress testing

Purpose questions

1. What are we trying to test?
2. What decision will this support?
3. Who needs the results?
4. What would make the stress test useful?
5. Is this about survival, resilience, viability or control?
6. What area is most exposed?
7. What time period matters?
8. What output matters most?
9. What action may follow?
10. How often should the test be repeated?

Stress design questions

1. What severe but plausible event should we test?
2. What has happened before?
3. What is happening in the sector?
4. What risks are already high?
5. What assumptions are most uncertain?
6. What would cause the greatest pressure?
7. Which risks could happen together?
8. Are we testing enough downside?
9. Is the stress realistic?
10. Is the stress challenging enough?

Financial questions

1. What happens to cash?
2. What happens to profit?
3. What happens to reserves?
4. What happens to debt?
5. What happens to covenant headroom?
6. What happens to working capital?
7. What happens to funding?
8. What costs become unavoidable?
9. What costs can be reduced?
10. What is the breaking point?

Operational questions

1. Can critical activities continue?
2. Which services would be affected?
3. Which staff are essential?
4. Which systems are essential?
5. Which suppliers are critical?
6. What workarounds exist?
7. Are workarounds realistic?
8. What capacity is available?
9. What quality risks arise?
10. What customer or service user impact occurs?

Risk questions

1. Which risks become more serious?
2. Which controls are tested?
3. Which controls may fail?
4. Does the stress move us outside risk appetite?
5. Which risks should be escalated?
6. Which risks need more mitigation?
7. Which assumptions need monitoring?
8. Which early warning indicators matter?
9. What contingency is required?
10. What should be added to the risk register?

Action questions

1. What should we do now?
2. What action would be taken if the stress begins?
3. Who owns the action?
4. What trigger point starts the action?
5. What decision is needed?
6. Is board approval required?
7. Is external support needed?
8. Should spending be paused?
9. Should the plan be changed?
10. When will this be reviewed?

The best way to think about stress testing

Stress testing is not about predicting disaster.

It is about testing resilience.

A good stress test should be:

1. Clear
2. Severe but plausible
3. Linked to a decision
4. Based on key vulnerabilities
5. Evidence-informed
6. Connected to risk appetite
7. Focused on breaking points
8. Linked to action
9. Reviewed regularly
10. Understood by decision-makers

A weak stress test says:

“Here is a downside number.”

A strong stress test asks:

“What would happen under serious pressure, where would we break, and what action should we take now?”

The key question is not simply:

Can we survive this stress?

The better question is:

What does this stress reveal about our cash, capacity, controls, risks and readiness?

Conclusion: stress testing turns resilience from assumption into evidence

Stress testing remains useful because every plan looks stronger before it is put under pressure.

Forecasts can look healthy. Projects can look viable. Budgets can appear balanced. Strategies can feel robust. Business continuity plans can look complete.

The real question is whether they still work when conditions deteriorate.

Used badly, stress testing becomes a pessimistic spreadsheet exercise that produces numbers but no decisions.

Used properly, it becomes a practical management tool. It helps organisations identify vulnerabilities, test resilience, challenge assumptions, protect cash, improve risk management and prepare contingency plans.

The real value is not in creating a severe scenario.

The real value is in understanding what the severe scenario reveals.

A strong stress testing process helps an organisation move from saying, “We think we can cope,” to asking, “What evidence do we have, where are we exposed, and what should we do before the pressure arrives?”