Disaster Relief Medical Supply Cache Planning

A disaster relief medical supply cache is a different planning problem than any single facility’s supply closet. A clinic or fire station restocks against a known, roughly steady daily consumption rate. A pre-positioned disaster cache instead has to sit unused — sometimes for years — and then, on no notice, cover an unpredictable surge of casualties across a population it can only estimate in advance. That combination (long dormancy, uncertain activation timing, and a scale-driven quantity problem) is what makes cache planning its own discipline rather than a bigger version of routine stocking. This guide covers the two pieces that discipline actually rests on: sizing a cache against the population it’s meant to serve, and running a rotation schedule that keeps a dormant, dated inventory usable when it finally gets opened.

Where to source this: once a cache’s categories and quantities are sized, the actual procurement is a sourcing problem, not a planning one. CASRAI’s sister medical-supply operation, LAC, stocks the core categories a disaster cache is typically built around: emergency, trauma, and crisis-response supplies, first aid kits sized for group and family use, and emergency blankets for exposure and shock management. None of that replaces the sizing and rotation work below — a cache built by dollar amount instead of by planning population is exactly the failure mode this guide is trying to prevent.

Who Actually Needs a Pre-Positioned Cache

Not every organization with a disaster plan needs its own physical cache. Building and rotating one is a real ongoing cost — storage space, environmental control, staff time on inspection cycles, and capital tied up in inventory that (ideally) never gets used before it expires. It’s the right investment for organizations that meet most of the following:

A defined population they’re responsible for that can’t rely on outside resupply arriving fast enough — a county emergency management agency, a healthcare coalition covering a rural region, a faith-based or NGO disaster-response team, a large employer or campus with a business-continuity obligation to its own population.
Credible exposure to an event that outlasts normal resupply timelines — flood, wildfire, earthquake, hurricane, or another hazard where local supply chains and 911/EMS response capacity are themselves likely to be degraded, not just the facility.
A realistic activation and staffing plan to actually deploy the cache when needed. A cache with no one trained to open it, inventory it against a manifest, and distribute it by triage priority is a storage cost, not a capability.

A single clinic, school, or small office is usually better served by the kind of facility-level emergency supply checklist already covered elsewhere on this site (see the cross-links below) than by building a standalone disaster cache from scratch. Cache planning is for the organization one level up — the one that’s expected to support multiple sites, a defined community, or a response period measured in days rather than hours.

Sizing a Cache by Expected Population Served

The single most common cache-planning failure is sizing by budget or by container size instead of by the population and time period the cache is actually meant to cover. A cache sized “however much fits in the storage container we bought” tells you nothing about whether it covers your actual exposure. A defensible sizing approach works backward from three inputs instead:

Planning population. The number of people the cache is meant to serve if the covered hazard occurs — a defined service area’s residents, an employer’s on-site headcount at peak occupancy, a coalition’s member-facility patient census, or a shelter’s rated capacity. Use the number you’re actually responsible for, not an aspirational regional figure you have no obligation or capacity to serve.
Operational period. How long the cache has to bridge the gap before outside resupply (mutual aid, state/federal assistance, commercial resupply) realistically arrives. This is usually shorter than people assume for a well-connected urban area and considerably longer for a rural or geographically isolated one. Size against your own resupply-timeline assumption, documented and revisited, not a generic industry number.
Expected utilization rate, by supply category, not as a single blended figure. Trauma and wound-care consumables get used at a different rate than OTC analgesics, which get used at a different rate than emergency blankets. Sizing the whole cache off one “supplies per person” ratio undersizes the categories that actually spike in a mass-casualty or exposure event and oversizes categories that don’t.

Multiplying planning population × operational period × a per-category utilization assumption gives a defensible starting quantity for each category — and, just as importantly, a documented rationale you can revisit and adjust as your assumptions change, rather than a number nobody can explain two years later. Document the assumptions themselves (population source, resupply-timeline basis, utilization rate per category) alongside the resulting quantities; the number without its rationale is not reusable when it’s time to resize.

Tiering the cache by response phase sharpens this further. A “first 72 hours” tier — trauma and hemorrhage-control supplies, airway and breathing basics, wound care, emergency blankets — needs to be sized for immediate, high-intensity utilization and staged for fast access. A “sustainment” tier covering days 3 through however long your operational period runs — general first aid consumables, OTC medications, basic hygiene and water-purification supplies — can be sized against a lower, steadier utilization rate and doesn’t need the same immediate-access staging.

Core Supply Categories in a Disaster Relief Cache

What belongs in the cache depends on the population and hazard profile, but most disaster relief caches organize around a similar set of categories:

Trauma and hemorrhage control — tourniquets, hemostatic dressings, pressure bandages, chest seals. Sized against the highest-acuity, lowest-tolerance-for-shortfall scenario the cache covers.
General wound care — gauze, adhesive bandages, antiseptic, burn dressings, splinting material. Highest-volume category by unit count in most mass-casualty and general-injury scenarios.
Airway and breathing basics — barrier devices, basic airway adjuncts, if within the deploying team’s scope of practice and medical-direction authorization. A cache should never include items beyond what the people activating it are actually credentialed and authorized to use.
Exposure and thermal management — emergency (space) blankets, which matter for shock management and hypothermia prevention as much as for general shelter comfort, and are consumed in volume relative to their unit cost.
OTC medications — analgesics, antihistamines, GI symptom relief, oral rehydration supplies. High shelf-stability makes this category relatively forgiving on rotation, but it’s still dated stock.
PPE — gloves, masks, eye protection, for the responders working out of the cache, not only for casualties.
Basic hygiene and water treatment — water purification tablets or filtration, hand sanitation, sanitation supplies for a shelter or field environment where normal facilities may be degraded or unavailable.

A disaster relief cache, as scoped here, is not a field hospital’s pharmacy or surgical inventory — it’s a first-response and sustainment bridge, built around consumables a trained first-aid or EMS-level responder can use without a physician on site. Anything requiring prescribing authority, controlled-substance handling, or a licensed clinician’s direct involvement is a separate planning track with its own regulatory and security requirements, not an extension of this cache.

The Rotation Schedule: Keeping a Dormant Cache Usable

A cache that sits unopened between events is exactly the scenario dated medical supplies are worst suited to. Without an active rotation discipline, a cache doesn’t fail gradually — it fails silently, passing every visual inspection right up until the day it’s opened during an actual response and a meaningful fraction of its contents are expired.

A working rotation schedule needs three elements:

First-in, first-out (FIFO) shelving and issuance. New stock goes behind existing stock, never in front of it. This is the single highest-leverage practice in the whole system and the one that fails most often in practice, simply because it’s easier to put a new case wherever there’s open shelf space.
A tiered inspection cadence by shelf-life category, not one blanket interval for the whole cache. Short-shelf-life items (many liquid medications, some wound-care products with adhesive components) need more frequent checks than long-shelf-life items (most gauze, blankets, PPE, water-purification tablets). Auditing the whole cache on one interval means either over-auditing stable categories or under-auditing volatile ones.
A tracked expiration manifest, checked against physical stock, not memory or a static packing list. The manifest is what turns “we think everything’s current” into a documented, verifiable fact. Every rotation check should reconcile the manifest against what’s physically on the shelf, flag anything inside its final rotation window, and route it for use, donation, or disposal before it lapses — not after.

Large-scale operators face the same problem at bigger scale. The U.S. federal Strategic National Stockpile, for instance, runs its dated pharmaceutical inventory through the Shelf-Life Extension Program (SLEP), a joint FDA/DoD program that re-tests selected stockpiled lots against their labeled expiration dates and, where the testing supports it, extends the usable date rather than discarding still-viable material. An organization running a facility-scale cache won’t have SLEP’s testing infrastructure available to it, which is exactly why FIFO discipline and a real inspection cadence matter more, not less, at smaller scale: rotating stock into active use before expiration, rather than extending it after, is the practical substitute available to an organization without a federal testing program behind it.

Storage, Staging, and Pre-Positioning

Where and how a cache is physically stored affects both its shelf life and how usable it is on the day it’s actually needed:

Environmental control. Temperature extremes and humidity degrade most dated medical supplies faster than their labeled shelf life assumes. A cache stored in an uncontrolled outbuilding or unconditioned trailer should be inspected on a shorter cycle than one in climate-controlled space, and any temperature-sensitive category should be flagged for tighter monitoring or excluded from that storage location entirely.
Centralized vs. dispersed staging. A single large cache is easier to inventory and rotate but represents a single point of failure if the storage site itself is inaccessible or damaged in the same event the cache is meant to respond to. Dispersing a cache across multiple sites trades some inventory-management simplicity for resilience against exactly that failure mode — the right balance depends on the hazard profile (a flood plan should generally assume the primary site may be unreachable; many other hazards are less site-specific).
Access and mobility. A cache staged in containers or cases sized for the vehicles and personnel actually available to move it, with a documented manifest attached to each container, deploys faster than one that has to be repacked from bulk storage at activation time.

Activation and Deployment

Sizing and rotation only pay off if the activation process itself is defined in advance, not improvised in the moment. At minimum, a cache plan should document: who has authority to activate the cache and under what triggering conditions; who is trained to inventory it against the manifest and stage it for use; how it integrates with the organization’s broader emergency action plan and, where applicable, with mutual-aid or incident-command structures; and how post-event replenishment gets funded and executed so the cache doesn’t sit partially depleted going into the next rotation cycle.

How This Relates to Other Emergency Supply Planning on This Site

A disaster relief cache sits at a different scale than most of the facility-level emergency supply planning covered elsewhere on this site, but the underlying logic overlaps considerably:

A single facility’s own continuity planning should still start with an emergency action plan covering evacuation, shelter-in-place, and immediate response roles — the cache described here is what a larger organization builds to support multiple such facilities or a broader community, not a replacement for facility-level planning.
The rotation and par-level logic in this guide is the same discipline covered in more tactical, vehicle-specific form in the EMS jump bag restocking checklist — a jump bag is a fast-cycle, single-unit version of the same FIFO and expiration-tracking problem a cache handles at much larger scale and lower turnover.
Organizations already running a facility-level surge stockpile should see the PPE stockpile and surge demand planning guide for the equivalent burn-rate and par-level sizing logic applied specifically to PPE.
Facilities serving populations with specific evacuation and continuity needs during a disaster — residents who can’t self-evacuate quickly, for example — should also see the assisted-living facility supply checklist and nursing home supply checklist, which cover routine and continuity supply planning for those settings specifically.
A workplace or campus building disaster-response capability into its existing first-aid program can see the corporate first aid station and workplace wellness clinic supply checklists for the facility-scale baseline this guide’s cache-level planning builds on top of.
A community shelter site frequently ends up being a school; the school nurse office supply checklist covers that facility’s own baseline stock, separate from any cache staged there during an activation.

Frequently Asked Questions

How much medical supply should a disaster relief cache actually hold?

There’s no single correct quantity — it depends on the planning population you’re responsible for, the operational period you’re sizing against (how long before outside resupply realistically arrives), and a per-category utilization rate rather than one blended ratio. See the sizing methodology above for the actual calculation logic; treat any generic “supplies per person” figure you find elsewhere with caution unless it states the population and time period it assumes.

How often should a disaster cache be rotated or inspected?

On a tiered schedule matched to shelf life, not one interval for the whole cache — shorter-shelf-life categories need more frequent checks than stable ones like gauze, blankets, and PPE. The schedule should reconcile a tracked expiration manifest against physical stock at every check, not rely on a visual scan alone.

What’s the difference between a disaster relief cache and a facility emergency supply kit?

Scale and activation model. A facility kit covers that facility’s own population on a routine or immediate-response basis. A disaster relief cache is sized for a broader population (a service area, a coalition, an employer’s full population), meant to bridge a longer operational gap before outside resupply arrives, and typically activated under a defined incident-command or emergency-management structure rather than used day to day.

Does a disaster cache need pharmaceuticals requiring a prescription?

Not as part of the core cache described here. A cache built around OTC medications and first-aid/EMS-level consumables avoids the additional regulatory, security, and clinical-oversight requirements that prescription and controlled-substance stock carries. Organizations that need prescription medical countermeasures in their response plan are working a separate, clinically supervised track, not an extension of this cache.