Ambulance Fleet Patient Capacity Estimator

Estimate the number of ambulance responses or transports a fleet can support over a selected period using staffed-unit hours and average unit cycle time. The model multiplies available ambulances by staffed hours, applies an availability factor for time that can actually be devoted to calls, and divides by the average minutes a unit is committed per incident.This is a simplified operations-planning model, not an emergency-service deployment standard. Real fleet capacity is shaped by geography, demand peaks, unit posting, hospital offload delays, call priority, mutual aid, maintenance, crew rules, and the need to preserve reserve coverage.

Fleet capacity assumptions

units
hr
%
min
days
Result
Estimated call capacity
Total staffed unit-hours
Call-available unit-hours
Calls per ambulance
Time unavailable for calls

1. Enter staffed units
Use ambulances that will actually have crews and be available within the modeled operation.

2. Set staffed hours
Enter the scheduled hours per ambulance per day; multiply through the number of modeled days with the period field.

3. Apply call-available share
Reduce staffed time for breaks, posting, checks, restocking, maintenance exposure, and other non-call time not already in cycle time.

4. Enter unit cycle time
Use the average time from unit commitment through return to availability for one call.

5. Treat the result as scenario capacity
Compare scenarios rather than using the number as a safe dispatch maximum; reserve coverage and peak demand still matter.

Total staffed unit-hours = Staffed ambulances × Staffed hours per ambulance × Modeled days Call-available unit-hours = Total staffed unit-hours × Call-available share % ÷ 100 Estimated call capacity = Call-available unit-hours × 60 ÷ Average unit cycle minutes

What the result means

The result is a time-based estimate of how many average-cycle calls the staffed fleet could absorb during the selected period.

It does not determine safe fleet size, response-time compliance, clinical coverage, or required reserve capacity. Emergency service planning should use local demand, deployment, and regulatory standards.

Given

  • 10 staffed ambulances
  • 24 staffed hours/ambulance/day
  • 70% call-available share
  • 84-minute average cycle time
  • 1 modeled day

Calculation

Staffed unit-hours = 10 × 24 × 1 = 240. Call-available hours = 240 × 0.70 = 168. Capacity = 168 × 60 ÷ 84 = 120 calls.

Result

Estimated time-based capacity: 120 average-cycle calls for the day.

This does not mean the system can safely accept 120 calls regardless of timing; clustered demand can exhaust available units even when daily average capacity looks sufficient.

What should be included in cycle time?

Use the full period during which the ambulance is committed and unavailable for another call under your operating definition, including response, scene, transport, handoff, and return-to-service time when applicable.

Why use a call-available share if cycle time already includes call work?

The availability factor accounts for staffed time that cannot be assigned to calls for reasons outside an active call cycle. Do not use it to subtract time already embedded in the cycle estimate.

Can I use this for non-transport responses?

Yes if the average cycle time reflects the mix of calls you are modeling. Separate scenarios are better when transport and non-transport calls have very different unit commitment times.

Does the result account for peak-hour demand?

No. It averages capacity across the modeled period. Short demand surges, geographic imbalance, and simultaneous high-priority calls can create shortages well below the daily total.

Is this a response-time calculator?

No. It estimates aggregate call-handling capacity from unit time. Response time requires additional information about demand timing, unit locations, dispatch, travel, and queueing.