Stress-Testing Capacity During Demand Spikes

Author : Daniel Mathew | Published On : 09 Apr 2026

Demand spikes are not anomalies in healthcare. Seasonal illness, public health events, and referral surges place predictable pressure on systems every year. What often turns these spikes into failures is not volume itself, but the lack of prior testing. This case study documents how peak-demand scenarios were stress-tested across services to identify pressure points before disruption occurred.

The initiative began with a simple acknowledgment. Historical performance during high-demand periods was being reviewed only after stress had already surfaced. Instead of reacting to past breakdowns, leadership decided to simulate future ones. The objective was to understand where capacity would fracture under load, while there was still time to adjust.

Designing Realistic Demand Scenarios

Stress-testing began by defining realistic peak scenarios rather than worst-case hypotheticals. Historical demand data was analyzed to identify recurring surge patterns by service line, time period, and geography. These patterns were translated into projected load increases across outpatient, diagnostics, inpatient, and emergency services.

Importantly, scenarios were layered. A diagnostic surge was modeled alongside staffing constraints. Referral inflow spikes were combined with slower discharge assumptions. This approach reflected how pressure actually accumulates in live systems, rather than isolating variables in theory.

The process was overseen by Jayesh Saini, with an emphasis on stress-testing flow and decision speed, not just physical capacity.

Monitoring Pressure Points in Real Time

Once scenarios were defined, facilities were monitored against stress indicators as demand increased. Wait times, referral completion, decision latency, and staff escalation frequency were tracked daily. Rather than waiting for thresholds to be breached, early inflection points were flagged.

This revealed that pressure did not emerge evenly. Certain services showed early strain despite appearing well-resourced. In several cases, diagnostic bottlenecks surfaced long before bed capacity was affected. In others, senior decision dependency slowed throughput under volume, even when staffing numbers were adequate.

These findings confirmed that capacity is functional, not static. It depends on how processes behave under stress, not how they perform in steady state.

Identifying Failure Before It Happens

One of the most valuable outcomes of stress-testing was identifying where failure would likely occur first. For example, referral coordination teams showed signs of overload earlier than clinical units. Minor delays at this stage amplified downstream congestion across facilities.

Similarly, escalation pathways that worked well under normal load became constraints during spikes. Decision-making slowed as approvals concentrated at the top, creating invisible backlogs.

Because these issues were identified in simulation and early live monitoring, they could be addressed before becoming operational failures.

Adjusting Before Demand Peaked

Armed with these insights, leadership made targeted adjustments ahead of peak periods. Diagnostic schedules were smoothed to prevent clustering. Referral protocols were simplified to reduce handoffs. Decision authority was redistributed temporarily to maintain flow.

Crucially, these changes were implemented before demand reached its highest point. There was no need for emergency staffing, service suspension, or crisis communication. The system entered peak periods already adapted to the conditions it would face.

As Jayesh Saini noted during internal reviews, stress-testing was not about predicting exact volumes but about understanding how the system would behave when stretched.

Outcomes During Peak Periods

When demand surged, the expected disruption did not materialise. Services remained operationally stable. Wait times increased marginally but did not spiral. Referral completion held steady. Staff escalation rates remained within manageable limits.

The absence of visible strain was the clearest validation of the approach. Stress had been anticipated, absorbed, and managed without dramatic intervention.

Financially, unplanned expenditure was avoided. Operationally, teams experienced continuity rather than crisis. Patients encountered a system under pressure but not under stress.

Institutionalising Stress-Testing Discipline

Following this experience, stress-testing was embedded as a recurring operational practice. Peak simulations became part of planning cycles. Pressure indicators were reviewed proactively rather than reactively.

Under Jayesh Saini’s leadership, stress-testing shifted from an occasional exercise to a core element of system governance. Capacity planning evolved from counting assets to understanding behavior under load.

A Broader Lesson

This case demonstrates that healthcare systems do not fail at peak demand because they lack capacity. They fail because they have not tested how capacity behaves when pushed.

Stress-testing turns uncertainty into insight. It allows systems to adjust early, quietly, and effectively. In environments where demand spikes are inevitable, preparation is not optional. It is the difference between resilience and disruption.