<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	xmlns:media="http://search.yahoo.com/mrss/"
>

<channel>
	<title>emergency preparedness - modSTORAGE | Blog</title>
	<atom:link href="https://blog.modstorage.com/tag/emergency-preparedness/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.modstorage.com</link>
	<description>Self Storage Tips Boxed Up!</description>
	<lastBuildDate>Sun, 30 Aug 2026 09:34:06 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<image>
<url>https://blog.modstorage.com/wp-content/uploads/2024/05/modSTORAGE-Blog.svg</url>
<title>modSTORAGE | Blog</title>
<link>https://blog.modstorage.com</link>
</image>
<copyright>© modSTORAGE 2025. All rights reserved.</copyright><generator>https://kerosin.digital/rss-chimp</generator>	<item>
		<title>Before the Storm: The Self-Storage Facility Shutdown Walk</title>
		<link>https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=self-storage-facility-storm-shutdown-walk</link>
					<comments>https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/#respond</comments>
		
		<dc:creator><![CDATA[Jared Mastroianni]]></dc:creator>
		<pubDate>Sun, 30 Aug 2026 06:47:35 +0000</pubDate>
				<category><![CDATA[Business Storage]]></category>
		<category><![CDATA[Self Storage]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[emergency preparedness]]></category>
		<category><![CDATA[Facility Operations]]></category>
		<category><![CDATA[operational resilience]]></category>
		<guid isPermaLink="false">https://blog.modstorage.com/?p=12165</guid>

					<description><![CDATA[<p>A practical seven-part storm shutdown walk for self-storage operators: authority, people, site exposure, access, systems, communication, and handoff.</p>
<p>The post <a href="https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/">Before the Storm: The Self-Storage Facility Shutdown Walk</a> first appeared on <a href="https://blog.modstorage.com">modSTORAGE | Blog</a>.</p>]]></description>
										<content:encoded><![CDATA[<p><strong>A self-storage facility should not wait for the first hard gust, flooded road, or evacuation order to decide how it will shut down.</strong> By then, the safest work window may already be closing.</p>
<p>A storm shutdown is not one switch. The office can close while customer gate access remains active. A manager can leave while doors, loose exterior items, cameras, alarms, payment channels, and customer messages remain in different states. If those states are not intentionally aligned, the team inherits an avoidable incident during the period when staffing, travel, and vendor response are most constrained.</p>
<p>The practical answer is a shutdown walk: a short, evidence-based record that turns an official warning or local operating decision into seven coordinated checks. It does not replace an emergency action plan, local instructions, or qualified technical work. It gives the facility team one controlling view of what has been changed, what remains open, and what must be independently checked after the storm.</p>
<h2>Set the trigger before conditions deteriorate</h2>
<p>The shutdown decision should begin with a source, a threshold, and an authority. The National Weather Service distinguishes watches from warnings and notes that outdoor preparations may become unsafe once tropical-storm-force winds begin. OSHA&#8217;s hurricane preparedness guidance likewise emphasizes activation conditions, chain of command, evacuation procedures, and accounting for workers, customers, and visitors.</p>
<p>Translate that guidance into a facility-specific trigger. It might be an evacuation order, a local road-closure threshold, a named leadership decision, or a deadline in an approved emergency plan. Record the source, the time observed, who made the operating decision, which facility it covers, and any limitations. “Storm shutdown started” is not enough. “Local evacuation order verified at 2:10 p.m.; customer access ends at 3 p.m.; staff departure follows the approved site plan” can be operated and reviewed.</p>
<p>Do not turn a general forecast into a claim about one property. Use the official local forecast, local emergency-management direction, and the facility&#8217;s approved plan. When those sources conflict or remain unclear, escalate rather than improvise.</p>
<h2>The seven-part shutdown walk</h2>
<p>Each check needs an owner, evidence, a timestamp, and a result. The result should be one of three states: complete, limited with a named exception, or hold.</p>
<h3>1. Authority and timing</h3>
<p>Capture the official source, the decision authority, the shutdown deadline, and the conditions that would cause the deadline to move earlier. Include the next scheduled weather or leadership review. A watch, warning, evacuation order, road closure, and facility operating decision are different facts; keep them separate.</p>
<h3>2. People and movement</h3>
<p>Account for staff, contractors, and any customers known to be on site. Follow the facility&#8217;s approved evacuation and accountability procedures. Define when new entries stop, who checks occupied work areas, and how the final employee confirms departure. Never extend outside work merely to complete a checklist after conditions become unsafe.</p>
<h3>3. Site exposure</h3>
<p>Inspect only what can be safely observed within the authorized preparation window: entrances, drainage paths, doors, fences, roofline visible from the ground, exterior signs, carts, waste containers, and other loose or exposed items. Photograph material exceptions before they are changed. Suspected electrical, structural, fire, gas, or flood hazards belong with the appropriate qualified party, not an improvised repair.</p>
<h3>4. Physical and digital access</h3>
<p>Set the intended state for the customer entrance, exit, pedestrian doors, office, keypad, remote-open functions, staff credentials, vendor credentials, and emergency overrides. Confirm that the physical equipment and the access platform report the same state. If one path must remain available, name the reason, authorized users, expiration time, and person responsible for removing the exception.</p>
<p>A locked office with an active gate is not a closed facility. A disabled public keypad with an unrestricted remote-open function is not a complete access change. The record should describe the actual access promise, not the appearance of the property.</p>
<h3>5. Utilities, equipment, and data</h3>
<p>Record the intended safe state for office equipment, nonessential loads, elevators where present, environmental monitoring, cameras, alarms, phones, network equipment, and any approved backup-power arrangement. Only authorized and qualified people should operate or isolate equipment. Do not create electrical, generator, or life-safety instructions inside a general manager checklist.</p>
<p>Preserve the information needed for later readback: device status, alarm state, the most recent successful communication, open work orders, vendor case numbers, and the time of the last verified data. A system that goes offline during the storm should not erase the last known condition or the fact that later observations are missing.</p>
<h3>6. Customer and staff communication</h3>
<p>Issue one message that matches the facility&#8217;s actual operating state. State what is changing, when it changes, what customers should not attempt, when the next update is expected, and which official channel will carry it. Avoid promising a reopening time before local authority, site condition, utilities, access, and operating systems have been read back.</p>
<p>Use the same controlling facts across the website, phone message, email, text, social channel, call center, and property signage that the facility has approved. If one channel cannot be updated, record the mismatch and owner rather than assuming customers will find the newer message elsewhere.</p>
<h3>7. Closure and handoff</h3>
<p>Close the shutdown walk with the exact unresolved items: equipment left in a limited state, temporary credentials, missing observations, vendor visits, customer cases, damage already known, and the next review time. Name the person who owns each item during the closure period and the person authorized to begin the reopening assessment.</p>
<p>The final record should survive a shift change. The next manager should not have to reconstruct the facility state from text messages, memory, and separate system timestamps.</p>
<h2>Use three operating states</h2>
<p>A binary open-or-closed label hides too much. Three states are more useful:</p>
<ul>
<li><strong>Preparing:</strong> normal services are being reduced under a documented deadline, with people and access still controlled.</li>
<li><strong>Limited:</strong> named services remain available under explicit restrictions, owners, and expiration times.</li>
<li><strong>Closed for assessment:</strong> customer operations have stopped, exceptions are governed, and reopening requires a separate post-storm readback.</li>
</ul>
<p>These labels should describe the services customers and staff can actually use. They are operating states, not weather forecasts, structural findings, or promises about when the property will reopen.</p>
<h2>Keep the evidence small enough to use</h2>
<p>The shutdown walk can fit on one page with seven rows and eight fields:</p>
<ul>
<li>control area;</li>
<li>required state;</li>
<li>action owner;</li>
<li>evidence or readback;</li>
<li>time completed;</li>
<li>result;</li>
<li>exception owner; and</li>
<li>next review time.</li>
</ul>
<p>Ready Business treats communications, IT support and recovery, continuity planning, training, and exercises as connected parts of preparedness. The shutdown walk applies that same discipline at the facility level. It connects the decision to close with the physical, digital, and communication states that must change before the last person leaves.</p>
<h2>A better shutdown sentence</h2>
<p>“The facility closed for the storm” is easy to write and difficult to operate.</p>
<p>A more useful record sounds like this:</p>
<blockquote>
<p>Customer entry ended at 3 p.m. under the approved storm plan after the local warning was verified. Staff and contractors were accounted for by 3:18 p.m. The office, public keypad, remote-open permissions, and customer messaging match the closed-for-assessment state. Camera and alarm communications were last read back at 3:24 p.m. One drainage exception is assigned to the regional manager for the 7 p.m. review. Reentry remains prohibited until local authority and the post-storm facility assessment permit it.</p>
</blockquote>
<p>That statement is not longer for the sake of documentation. It is specific enough to protect the operating boundary. It tells the team what changed, what was verified, what remains unresolved, and what must happen next.</p>
<p>For a multi-location operator, the shutdown walk also creates a shared language without pretending every facility faces the same hazard or uses the same equipment. The seven checks stay stable. The sources, thresholds, owners, and technical steps remain local.</p>
<hr>
<p><em>Jared Mastroianni is Chief Operating Officer of modSTORAGE and CEO and Founder of Facily.ai. He writes about facility operations, operating controls, and responsible use of AI in physical environments.</em></p>
<h2>Official sources</h2>
<ul>
<li><a href="https://www.weather.gov/safety/hurricane-ww">National Weather Service: Hurricane and Tropical Storm Watches, Warnings, Advisories and Outlooks</a></li>
<li><a href="https://www.osha.gov/hurricane/preparedness">OSHA: Hurricane Preparedness and Response — Preparedness</a></li>
<li><a href="https://www.ready.gov/business">FEMA Ready.gov: Ready Business</a></li>
<li><a href="https://www.weather.gov/safety/hurricane-after">National Weather Service: After a Hurricane</a></li>
</ul>
<p><script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ImageObject",
  "@id": "https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/#stormShutdownImage",
  "name": "The seven-part self-storage storm shutdown walk",
  "url": "https://blog.modstorage.com/wp-content/uploads/2026/08/jared-mastroianni-self-storage-storm-shutdown-walk.png",
  "contentUrl": "https://blog.modstorage.com/wp-content/uploads/2026/08/jared-mastroianni-self-storage-storm-shutdown-walk.png",
  "width": 1600,
  "height": 900,
  "caption": "The seven-part shutdown walk aligns authority, people, site, access, systems, communication, and handoff before a facility closes for storm assessment. Graphic by Jared Mastroianni.",
  "description": "Seven-part self-storage storm shutdown walk covering authority, people, site exposure, access, systems, communication, and handoff.",
  "creator": {
    "@type": "Person",
    "@id": "https://jaredmodstorage.github.io/#person",
    "name": "Jared Mastroianni",
    "url": "https://jaredmodstorage.github.io/"
  },
  "copyrightNotice": "© 2026 Jared Mastroianni. All rights reserved.",
  "creditText": "Graphic by Jared Mastroianni",
  "representativeOfPage": true,
  "isPartOf": {
    "@id": "https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/#webpage"
  }
}
</script></p><p>The post <a href="https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/">Before the Storm: The Self-Storage Facility Shutdown Walk</a> first appeared on <a href="https://blog.modstorage.com">modSTORAGE | Blog</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://blog.modstorage.com/self-storage-facility-storm-shutdown-walk/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<enclosure url="https://blog.modstorage.com/wp-content/uploads/2026/08/jared-mastroianni-self-storage-storm-shutdown-walk-300x169.png" length="24449" type="image/png"/><media:content url="https://blog.modstorage.com/wp-content/uploads/2026/08/jared-mastroianni-self-storage-storm-shutdown-walk-300x169.png" medium="image" type="image/png" />	</item>
		<item>
		<title>The Reopening Gate: Seven Checks Before a Self-Storage Facility Returns to Normal Operations</title>
		<link>https://blog.modstorage.com/self-storage-facility-reopening-gate/?utm_source=rss&#038;utm_medium=rss&#038;utm_campaign=self-storage-facility-reopening-gate</link>
					<comments>https://blog.modstorage.com/self-storage-facility-reopening-gate/#respond</comments>
		
		<dc:creator><![CDATA[Jared Mastroianni]]></dc:creator>
		<pubDate>Fri, 28 Aug 2026 08:31:45 +0000</pubDate>
				<category><![CDATA[Business Storage]]></category>
		<category><![CDATA[Self Storage]]></category>
		<category><![CDATA[business continuity]]></category>
		<category><![CDATA[emergency preparedness]]></category>
		<category><![CDATA[Facility Operations]]></category>
		<category><![CDATA[operational resilience]]></category>
		<guid isPermaLink="false">https://blog.modstorage.com/?p=12149</guid>

					<description><![CDATA[<p>A practical seven-part reopening gate for self-storage operators: authority, site, utilities, access, systems, communication, and reconciliation.</p>
<p>The post <a href="https://blog.modstorage.com/self-storage-facility-reopening-gate/">The Reopening Gate: Seven Checks Before a Self-Storage Facility Returns to Normal Operations</a> first appeared on <a href="https://blog.modstorage.com">modSTORAGE | Blog</a>.</p>]]></description>
										<content:encoded><![CDATA[<p><strong>A self-storage facility is not ready to reopen because the rain stopped, the lights came back on, or the gate started moving.</strong> Those are useful signals. They are not a reopening decision.</p>
<p>After a storm, utility failure, fire response, flood warning, or other disruption, a facility can look normal while its operating controls remain out of alignment. The gate may accept credentials while a damaged fence line is still unsecured. Cameras may appear online while their clocks are wrong. The office may have power while elevators, payment terminals, alarms, and customer communications have not been tested. Reopening on one green signal turns a recovery problem into a customer-access problem.</p>
<p>The practical answer is a reopening gate: a short, evidence-based decision that separates permission to return from proof that the facility can safely resume each service.</p>
<h2>Start with authority, not appearance</h2>
<p>The first question is not “Does the building look fine?” It is “Who has authority to say people may return?” The National Weather Service advises people to return after a hurricane only when officials say it is safe, and to stay out of buildings affected by floodwater, gas odors, fire damage, or unresolved structural concerns. That boundary belongs at the top of the facility checklist, not buried in a manager’s notes.</p>
<p>Local emergency management, fire officials, utilities, building professionals, ownership, and the facility operator may each control a different part of the decision. A public reentry notice does not certify a private building. A utility restoration notice does not prove every circuit or device is safe. A manager’s walkthrough does not replace a required professional inspection.</p>
<p>Record the exact authority, the time of the decision, the affected property, and any limitations. “County reentry permitted at 8:20 a.m.” is better than “All clear.” It says what was actually established and what still needs to be checked.</p>
<h2>The seven-part reopening gate</h2>
<p>A useful reopening record fits on one page and answers seven questions. Each line needs an owner, evidence, a timestamp, and a result: pass, limited operation, or hold.</p>
<h3>1. External authority</h3>
<p>Confirm that applicable evacuation, road, public-safety, and utility restrictions allow the team to return. Capture the source and scope. If officials permit reentry but a route remains flooded, the facility is still a hold for normal customer access.</p>
<h3>2. Site and structure</h3>
<p>Inspect the approach, perimeter, roofline visible from the ground, doors, fences, drainage areas, standing water, debris, and signs of impact. Photograph exceptions before cleanup changes the evidence. If there is suspected structural, electrical, fire, gas, or flood damage, stop and escalate to the appropriate qualified party.</p>
<h3>3. Utilities and life-safety systems</h3>
<p>Verify the actual state of electrical service, emergency lighting, fire and intrusion alarms, communications, water, elevators, and any other site-specific critical service. A restored utility feed is an input. The facility still needs device-level readback.</p>
<p>Generator use deserves its own control. The National Weather Service warns that portable generators produce deadly carbon monoxide and must be used outside, away from doors, windows, and other openings. A generator should never become an improvised shortcut around the facility’s electrical and safety procedures.</p>
<h3>4. Physical and digital access</h3>
<p>Test the complete access path, not just one successful gate cycle. Check the entrance, exit, pedestrian doors, office door, elevators where present, call station, keypad, remote-open function, credential rules, and any temporary override. Confirm that the access platform and the physical equipment agree about what happened.</p>
<p>If a manual or emergency override was used, name the person who can remove it and the deadline for doing so. Temporary access that survives the emergency becomes an unowned exception.</p>
<h3>5. Operating systems and records</h3>
<p>Confirm that the property-management system, payment channels, phones, internet connection, cameras, environmental monitoring, work-order records, and customer-contact tools are available and current enough for the services being restored. Check clocks and timestamps. A camera system that is twelve hours off can turn a later incident review into guesswork.</p>
<p>Do not backfill missing events as though they were observed. Mark the gap, preserve the available logs, and identify what must be reconciled later.</p>
<h3>6. Customer and staff communication</h3>
<p>State what is open, what remains limited, and when the next update will be issued. The message should match the services that passed the gate. If the office is open but customer gate access remains suspended, say exactly that. Avoid “back to normal” until every customer-facing service included in that phrase has been verified.</p>
<p>FEMA’s business guidance treats crisis communications, emergency response, business continuity, and IT recovery as connected plans. For a storage operator, the reopening message is part of the control system: it determines who arrives, what they expect, and how exceptions reach the team.</p>
<h3>7. Reconciliation and handoff</h3>
<p>Close the reopening record with the unresolved items: damaged components, temporary credentials, offline devices, customer cases, vendor visits, missing logs, insurance evidence, and the next review time. Assign each item to a named owner. If the shift changes before full recovery, the handoff should preserve the decision trail without requiring the next manager to reconstruct it from texts and memory.</p>
<h2>Use three operating states</h2>
<p>A binary open-or-closed decision is too coarse for many recoveries. Three states are more useful:</p>
<ul>
<li><strong>Hold:</strong> people or services may not return because an authority, safety, access, utility, or evidence requirement is unresolved.</li>
<li><strong>Limited operation:</strong> named services may resume under documented restrictions, with an owner and review time for every exception.</li>
<li><strong>Normal operation:</strong> the defined customer and staff services have passed, temporary measures are removed or governed, and remaining follow-up work does not change the operating promise.</li>
</ul>
<p>This structure also prevents a familiar failure: one successful test being repeated as proof of the whole facility. “The gate opened” can support the access line. It cannot support the roof, alarm, elevator, camera, payment, or communications lines.</p>
<h2>The evidence should be small enough to use</h2>
<p>A reopening gate does not need to become a large incident-management platform. It can be a one-page record with seven rows:</p>
<ul>
<li>control area;</li>
<li>required check;</li>
<li>evidence or readback;</li>
<li>result;</li>
<li>exception;</li>
<li>owner; and</li>
<li>next review time.</li>
</ul>
<p>OSHA’s emergency-planning guidance emphasizes worksite-specific plans, defined responsibilities, reporting procedures, evacuation arrangements, and trained people who can coordinate action. The same operating discipline belongs on the recovery side. A plan explains how to leave safely. A reopening gate explains how to return without confusing a visible recovery signal with restored operational control.</p>
<h2>A better reopening sentence</h2>
<p>“The facility reopened at 10 a.m.” is easy to write and often too vague to manage.</p>
<p>A better record sounds like this:</p>
<blockquote>
<p>Public reentry and the exterior walkthrough were verified by 8:40 a.m. Power, alarms, primary access, cameras, phones, and the property-management system passed by 9:35 a.m. Elevator service remains unavailable pending vendor readback. The office and ground-floor customer access reopened at 10 a.m. under that limitation. The manager owns the noon review and customer update.</p>
</blockquote>
<p>That statement is not longer for the sake of documentation. It is specific enough to operate.</p>
<p>For multi-location teams, the reopening gate creates a shared language without pretending every site has the same hazards or systems. The seven questions stay stable. The evidence remains local. That is the balance a recovery process needs: one operating discipline, applied to the actual facility in front of the team.</p>
<hr>
<p><em>Jared Mastroianni is Chief Operating Officer of modSTORAGE and CEO and Founder of Facily.ai. He writes about facility operations, operating controls, and responsible use of AI in physical environments.</em></p>
<h2>Official sources</h2>
<ul>
<li><a href="https://www.osha.gov/emergency-preparedness/getting-started">OSHA: Emergency Preparedness and Response — Getting Started</a></li>
<li><a href="https://www.osha.gov/etools/evacuation-plans-procedures/eap">OSHA: Emergency Action Plan</a></li>
<li><a href="https://www.ready.gov/business/emergency-plans">FEMA Ready.gov: Emergency Plans</a></li>
<li><a href="https://www.weather.gov/safety/hurricane-after">National Weather Service: After a Hurricane</a></li>
</ul>
<p><script type="application/ld+json">
{
  "@context": "https://schema.org",
  "@type": "ImageObject",
  "@id": "https://blog.modstorage.com/self-storage-facility-reopening-gate/#reopeningGateImage",
  "contentUrl": "https://blog.modstorage.com/wp-content/uploads/2026/08/featured-graphic.png",
  "url": "https://blog.modstorage.com/wp-content/uploads/2026/08/featured-graphic.png",
  "name": "The seven-part self-storage reopening gate",
  "caption": "The seven-part reopening gate separates permission to return from proof that facility services are ready.",
  "description": "Seven connected checks for authority, site, utilities, access, systems, communication, and reconciliation before a self-storage facility resumes normal operations.",
  "width": 1600,
  "height": 900,
  "creator": {
    "@type": "Person",
    "name": "Jared Mastroianni",
    "url": "https://jaredmodstorage.github.io/"
  },
  "creditText": "Graphic by Jared Mastroianni",
  "copyrightNotice": "© 2026 Jared Mastroianni. All rights reserved."
}
</script></p><p>The post <a href="https://blog.modstorage.com/self-storage-facility-reopening-gate/">The Reopening Gate: Seven Checks Before a Self-Storage Facility Returns to Normal Operations</a> first appeared on <a href="https://blog.modstorage.com">modSTORAGE | Blog</a>.</p>]]></content:encoded>
					
					<wfw:commentRss>https://blog.modstorage.com/self-storage-facility-reopening-gate/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
		<enclosure url="https://blog.modstorage.com/wp-content/uploads/2026/08/featured-graphic-300x169.png" length="13693" type="image/png"/><media:content url="https://blog.modstorage.com/wp-content/uploads/2026/08/featured-graphic-300x169.png" medium="image" type="image/png" />	</item>
	</channel>
</rss>
