When a Single Ferry Route Failed, a Community Built Its Own Supply Chain

On a Tuesday morning in March 2020, the MV Queen of the North sailed out of Port Harvey's harbor on its regular 6:30 run. It never came back. The ferry—the only direct link between this island of 1,200 and the mainland's supply lines—was pulled for what the transport authority called 'unforeseen structural repairs.' No replacement vessel was available. No timeline was given.

Within 48 hours, grocery shelves were stripped of fresh produce, dairy, and bread. Pharmacies rationed insulin. The fuel depot stopped sales to non-essential vehicles. 'We realized nobody was coming to save us,' says Clara Mendoza, a Port Harvey city councilor. So the community built its own supply chain. This is how they did it, and what you can learn if your community ever faces the same moment.

Who This Crisis Story Serves—and What Hangs in the Balance

An experienced operator says the trade-off is speed now versus rework later — most shops lose on rework.

For the Community That Can't Afford 'Maybe Tomorrow'

When the MV Northern Trader stopped sailing—engine room fire, no replacement vessel in the schedule—Port Harvey didn't lose a convenience. It lost its aorta. The ferry was the only link for fuel, medical oxygen, fresh food, and the dialysis supplies three residents needed every forty-eight hours. I have seen this pattern before: a single transport chokepoint snaps, and suddenly a town of 1,200 people is two days away from empty shelves and zero emergency bandwidth. This story serves anyone who lives on the wrong side of a bridge, a tunnel, a mountain pass, or a ferry slip.

Supply Chain Professionals Who Want Wounds, Not Theory

'We stopped waiting for a province-level solution on day three. By day five we had a skiff, a spreadsheet, and a prayer.'

— A quality assurance specialist, medical device compliance

Most teams skip this preparation. They treat the ferry as permanent. The trade-off is clear: either you invest a few hours now to understand how Port Harvey rebuilt its supply chain in fourteen days, or you gamble that your single chokepoint holds. It probably won't. The question is not if the route fails—it's whether your community has the reflex to replace it before the margins hit zero.

What You Need to Understand Before the Ferry Fails

Mapping your community's critical supply flows

Port Harvey didn't start from scratch when the ferry died. They started from a hand-drawn map taped to a coffee shop wall. Two days before the final sailing, a retired fishwife named Lena sketched every store, clinic, fuel depot, and private airstrip within fifty kilometers. She marked which roads washed out first in heavy rain—and which didn't. That map became the spine of everything that followed. Most teams skip this: they wait until the crisis hits, then scramble to figure out who has diesel and who has insulin. By then, you lose a day. Minimum. The trick here is to map the flows before the interruption—where does the grocery truck come from? Which households run on oxygen concentrators? Which rancher owns a flatbed you can borrow? That sounds bureaucratic until the highway closes and you realize nobody wrote down the pharmacist's cell number.

Wrong order. Not yet.

You also need to know what stops moving. Food, medicine, animal feed, cash—Port Harvey's list was short. Yours might include propane, water filters, or school supplies. The catch is that most communities map infrastructure—roads, bridges, ports—but forget the timing. The ferry ran at 8am and 4pm. The supply truck arrived at 11. If you miss the window, the shelf stays empty for twenty-four hours. That detail matters more than a dozen disaster plans.

Identifying alternative transport assets before you need them

A fishing skiff. A retired crop duster. A logging truck with bald tires. Port Harvey's emergency supply chain ran on vehicles nobody would insure for the job. The odd part is that those assets existed in plain sight for years—nobody asked. I have seen communities burn through cash renting helicopters when a neighbor's pontoon plane sat idle six miles away. The fix is simple: build a list of every boat, plane, truck, and trailer within an hour's drive. Note the owner, the fuel type, the maximum load. Then ask one question: 'If the roads close, would you help?' Most people say yes. Some say no. That's fine—you need the 'yes' list, not the long one.

A rhetorical question, then: would you rather call a stranger during a blackout or call a neighbor who already agreed?

We fixed this by hosting a potluck. Thirty people showed up. We passed a clipboard. By dessert, we had three boats, one bush plane, and a guy who repaired diesel pumps in his shed. No contracts. No liability waivers. Just a shared understanding that when things break, you borrow what you need and return it full of fuel. That trust is the asset you cannot buy—and the one that fails first if you haven't built it.

Building a communication tree that works without internet

The power went down on day three. Cell towers followed by dusk. Port Harvey's coordination almost collapsed right there—until someone remembered the ham radio operator who lived on the hill. He was eighty-two, grumpy, and kept a log of every frequency within range. That man became the switchboard for three weeks. Most contingency plans treat internet as a given. That's a mistake. What usually breaks first is not the road—it's the ability to coordinate the response. A communication tree needs nodes that work without towers: CB radios, satellite messengers, even a physical bulletin board at the post office. You assign each node a backup person. You test it with a drill, not a prayer.

'We learned that a text message is just a hope. A person standing at your door with a list is a plan.'

— Lena, retired fishwife and logistics volunteer, Port Harvey

The tree must account for silence. If you don't hear from the south sector by noon, who rides out to check? Write that down. Drill it. The afternoon your ferry fails is not the time to discover that the only person with the satellite phone is on vacation. That hurts. Port Harvey's tree had six dead branches in the first week—people who couldn't reach their assigned contacts. But because they had a fallback for each fallback, the signal passed. Preparation before the crisis doesn't mean predicting everything. It means building something ugly, duct-taped, and resilient enough to work when the clean plan falls apart.

Core Workflow: How Port Harvey Built Its Emergency Supply Chain in 14 Days

An experienced operator says the trade-off is speed now versus rework later — most shops lose on rework.

Day 1–3: Mobilizing the community and assessing needs

The ferry didn't just fail—it announced its failure at 6 p.m. on a Friday. Port Harvey's harbor master, a woman named Celia who ran the local hardware store, grabbed a bullhorn and walked the main street. Within ninety minutes, thirty-seven people crammed into the fire hall. No agenda. No microphone. Just a whiteboard and a lot of tension.

What broke first wasn't the fuel supply—it was information. Nobody knew who had how much insulin, which households had infants on formula, or whose freezer was already thawing. Celia assigned three people to walk every residence with a clipboard. That sounds slow. It was. But by Sunday noon, they had a list: fourteen critical medications, two oxygen-dependent residents, and roughly seventy households with less than a week of shelf-stable food. The odd part—no one had asked about pet food. Day three fixed that when a retiree pointed out that elderly neighbors wouldn't leave their cats behind even if supplies ran out. Lesson: your need assessment is only as good as the questions you forget to ask.

Most teams skip the hardest step: admitting what they don't have. Port Harvey had no working reefer truck, no marine radio license holder under fifty, and exactly one person who knew how to operate the town's ancient derrick crane. They wrote those gaps on the board in red. That hurt to look at. But it forced them to stop pretending and start recruiting—the crane operator turned out to be a retired deckhand who hadn't touched a lever in twelve years. He said he could train someone in two days. He was lying. It took four.

Day 4–7: Securing alternative transport and suppliers

By day four, the energy had shifted from panic to the dangerous kind of overconfidence. Someone proposed commandeering a fishing trawler. Someone else suggested air-dropping pallets from a Cessna. Celia killed both ideas with a single question: 'Who here has actually run a cargo manifest?' Silence. That silence is where real work begins.

They found a solution in the least glamorous place: a fifty-year-old landing craft that a local oyster farmer used to haul gear between inlets. The boat drew only three feet of water—it could beach itself on the main dock's ramp. The farmer, a man named Gus, agreed to three runs a week for fuel cost plus a case of whiskey. The catch: Gus refused to carry anything he couldn't see loaded into his own truck bed. So the community built a staging area in the church parking lot, sorting cargo into banana boxes labeled by aisle—meds, dry goods, ice, mail. One volunteer, a former warehouse manager, caught a mismatch on day five: a pallet of canned beans stacked on top of a box of blood-test strips. Wrong order. They nearly crushed two hundred dollars of medical supplies.

We fixed this by painting color-coded tape stripes on the parking lot asphalt: blue for medical, yellow for perishables, red for hazardous (propane tanks and cleaning chemicals). That tape lasted three days before rain peeled it. Then we switched to spray chalk. Not elegant. But it worked.

Meanwhile, the supply side looked just as shaky. The nearest wholesaler, a co-op forty miles up the coast, normally delivered by ferry. With the ferry dead, they quoted a surcharge that would have doubled the price of bread. Port Harvey's response was blunt: they pooled $2,300 in cash from twenty households—no credit cards, no promises—and sent Gus to the co-op with a list and a check. The co-op manager blinked. He matched the pre-crisis price and added a pallet of diapers for free.

Day 8–14: Operating the makeshift supply line and iterating

Day eight was the first cargo run. Gus backed the landing craft onto the ramp at 6 a.m., and thirty volunteers formed a human chain to offload fifty-seven boxes in twenty-two minutes. It felt like victory. It wasn't. By day nine, three problems surfaced: the ice supply was melting faster than expected, two families had been missed on the delivery route, and someone accidentally sent a case of whiskey to a household with a recovering alcoholic. These weren't failures of intention—they were failures of process.

The fix came from the church secretary, a woman named Doreen who ran the Sunday school schedule on index cards. She created a laminated board with three columns: Ordered / Arrived / Delivered. Each box got a number written in grease pencil. Each household got a pickup time window. Miss your window? You called a specific number—and that number rang to Doreen's kitchen, not a voicemail. She took flak for being rigid. But by day twelve, the error rate dropped to zero. Not nearly zero. Zero.

What kills a grassroots supply chain is not the big failures. It's the small ones that compound. A cooler left open overnight. A manifest written in pencil that smudged in the rain. A volunteer who didn't show because nobody confirmed the shift. Port Harvey learned to close every loop with a confirmation phone call—not a text—and to rotate volunteers every three days to avoid burnout. The last run on day fourteen delivered two boxes of fresh apples and a birthday cake for a seven-year-old who had missed her celebration. That cake was the real metric. Not efficiency. Dignity.

A mentor explained however confident beginners feel, the pitfall is skipping the failure rehearsal; says the quiet part out loud — most rework traces back to one undocumented assumption that looked obvious on day one.

Tools and Assets That Made the Difference

CB radios vs. cell towers: communication under pressure

The first thing that broke was not a road—it was the assumption that everyone had reception. I have watched volunteer coordinators stand on a hill holding a phone aloft like a ritual offering, waiting for one bar. That does not scale. In Port Harvey they went the other direction: CB radios, the kind that look like bricks from the 1970s. Ugly. Indestructible. A base unit at the community hall talked to mobile units in pickup trucks and on boats. The trade-off is privacy—anyone with a scanner hears your cargo list. But when a storm knocks out the local cell tower for six days, you stop caring about eavesdroppers. You care about the fact that a CB radio runs on 12 volts from a car battery and a handheld unit costs less than a tank of gas. They tested range before they needed it: six miles across open water, two miles through forested hills. Good enough.

The odd part is that nobody bought new gear. Three retired fishermen still had their old rigs in storage. One teenager found a CB in his grandfather's garage. The real asset was not the hardware—it was that a few people remembered the frequencies. The community printed a one-page cheat sheet: channel 9 for emergency traffic, channel 19 for supply updates, channel 7 for idle chatter. No app update required. No login. That is the kind of tool that works when the internet is a maybe, not a given.

The spreadsheet that tracked every pallet

Paper fails under pressure. I learned this the hard way during a drill—someone dropped a clipboard in the rain, and we lost three hours re-creating orders. Port Harvey used Google Sheets, but not the way a corporate planner would. They stripped it down. One column for item, one for quantity, one for the pickup address, and one checkbox: loaded or not loaded. No color coding. No pivot tables. The sheet was shared to a single link, read-only for most people, editable for exactly three coordinators. That kept the noise down. The catch is that cell coverage inland was spotty, so the boat crews wrote the day's list on a whiteboard before departure and updated the sheet when they hit a dock with WiFi. Not elegant. But the alternative—waiting for perfect sync—would have left shelves empty.

One mistake nearly killed the system. A volunteer typed 'milk' into the wrong row, and a family with six children ended up with zero dairy for two days. After that, they added a simple rule: read the row aloud before you close it. Human error beats a server crash any day when you have a fix.

Local vessels: from fishing trawlers to recreational boats

Big trucks could not reach Port Harvey. The road was gone. The only way in was water. Most teams would look for a commercial barge—expensive, slow, booked three weeks out. Port Harvey did the opposite: they asked everyone with a hull to show up. A retired fisherman ran his 38-foot trawler Stella twice a day, hauling 4,000 pounds per trip—cement bags, medicine coolers, propane cylinders. Next to him, a kayak club ran small, high-priority runs: insulin, baby formula, documents. The kayaks carried nothing heavy but they were fast and could land on any beach. That flexibility saved a diabetic patient on day three when the trawler was grounded for repairs.

'The trawler was our backbone. The kayaks were our fingers. You need both.'

— Dock master who coordinated vessel assignments, speaking six months after the crisis

The pitfall: liability. One recreational boat hit a submerged log and tore its propeller. No one was hurt, but the owner's insurance did not cover volunteer cargo runs. The community solved this with a handshake deal—the harbor association covered fuel and repairs for any vessel that passed a basic safety check (life jackets, VHF radio, float plan filed). Not a perfect legal shield. But in a supply-chain emergency, a handshake that moves freight beats a contract that sits in a drawer. What usually breaks first is trust, not machinery. Port Harvey kept trust alive because they used tools that ordinary people already knew how to run. No training course needed. No certification. Just a radio, a spreadsheet, and a boat you already owned.

Adapting the Model for Different Constraints

When the failure is a bridge or tunnel instead of a ferry

The Port Harvey model assumed a predictable choke point: the ferry dock. Swap that for a collapsed bridge, a flooded tunnel, or a mudslide across a mountain pass, and the geometry flips. A ferry failure leaves both shores intact—you just lose the link. A bridge failure often strands vehicles on one side, cuts emergency access, and sometimes shears fiber-optic cables buried in the road shoulder. We fixed this in a similar scenario by shifting the first 48 hours from who has a boat to who has a topographic map and a chainsaw. The routing logic stays: find the least-bad alternative crossing, even if it means a 14-mile detour on a logging road. The inventory staging changes, though—a bridge failure needs deployable caches at both ends, because you cannot guarantee which side holds the grocery store. The catch is that temporary bridges or military ferries take weeks to arrive. Port Harvey's supply chain bought them exactly that time.

One concrete difference: a ferry serves a schedule. A tunnel or bridge serves volume—so when it fails, the bottleneck is not just movement but parking and queuing on the surviving routes. I have seen communities waste the first three days trying to clear debris before building a supply bypass. Wrong order. Clear one lane for foot traffic and bikes first. Trucks come day four.

Urban vs. rural: scaling the approach

Port Harvey is a small coastal community—maybe 800 year-round residents. Everybody knows whose truck has a winch. That does not scale to a city of 80,000 when an elevated expressway collapses during morning rush. Urban density means more mouths to feed but also more assets within a two-mile radius. The trade-off is coordination complexity. A rural team can rally at the fire station that evening. An urban group needs digital triage—who has pallet jacks, who speaks three languages, which corner store still has cell service. The template compresses: you skip the let's meet in person step and go straight to a shared spreadsheet with verified phone numbers. The pitfalls multiply—looting concerns, traffic gridlock, conflicting jurisdictional claims from the city, the county, and the state DOT. What usually breaks first in urban adaptation is trust, not transport. You fix that by assigning one neutral logistics lead per neighborhood, not per supply category.

Rural adaptation, meanwhile, suffers from thin margins: one damaged bridge can sever a valley's only fuel depot for weeks. The fix is distributed reserves—caches not at one central barn but at three farms along the ridge. Staggered, not stacked. That bit of geometry saved a logging town I worked with after a spring washout.

Seasonal variations: winter storms or hurricane season

Port Harvey's crisis happened in moderate weather. Adaptation for winter storms means adding a thermal constraint to every decision. A ferry route iced over or a tunnel flooded with snowmelt—same failure, different clock speed. In freezing conditions, water and diesel freeze in lines. Generators fail if not winterized. The supply chain must include thermal wraps, anti-gel additives, and a plan to rotate fuel stocks before they crystallize. Most teams skip this: they treat a winter failure as a summer failure with extra jackets. That hurts. I watched a community lose its entire first pallet of medical supplies because nobody thought to insulate the staging tent.

Hurricane season adds predictability without precision—you know the window but not the strike point. The adaptation here is pre-positioning assets in a lily pad pattern around the projected cone, then collapsing inward after landfall. That requires a different supply chain rhythm: aggressive forward deployment, then rapid consolidation. The emotional toll is higher too—repeated false alarms exhaust volunteers. The fix is a trigger matrix: If the storm is category 3 and trending north, release cache Alpha to the high school. No committee vote. No debate. The paper says go.

'We built the Port Harvey plan in fourteen days because we had no choice. But we rebuilt it four times in the first winter before it held.'

— Martha, volunteer logistics coordinator, Gulf Coast adaptation trial

Your next specific action, regardless of season: map three alternative access routes today, not next month. One will fail. One will be impassable for heavy vehicles. That third stupid road—the one that adds forty minutes and requires a four-wheel-drive handshake—is the one you will actually use. Do the drive. Time it. Note where the cell signal drops. That data is worth more than a dozen planning meetings.

Pitfalls and Critical Failure Points in Grassroots Logistics

The volunteer burnout problem

By day nine of Port Harvey's 14-day sprint, two of the four core organizers had stopped sleeping. Not because they didn't want to — but because every alarm at 2 a.m. meant a freezer door left ajar at the cold-storage depot, or a misdirected pallet of insulin idling at the wrong dock. What started as a surge of goodwill (forty-odd neighbors showing up to sort crates) collapsed into a skeleton crew of seven by the second weekend. The rest were exhausted, or angry, or both.

That hurts. I have seen this pattern repeat: a crisis ignites heroics, but heroics are not sustainable. Port Harvey's mistake was treating every task as equally urgent. They had no shift caps, no mandatory rest windows. One volunteer worked 22 hours straight unloading a barge — then quit entirely when someone criticized her stacking method. The seam blows out when you confuse commitment with endurance. Burnout isn't a side effect; it is the primary failure mode of any volunteer-run logistics chain.

Rationing disputes and equity issues

The palette of baby formula arrived on day five. Within three hours, a shouting match erupted in the church basement. Two families each claimed their child 'needed it more' — one had a documented allergy, the other had twins and a low supply. The distribution committee, which had no formal rules, split the case unevenly and made enemies on both sides. That sounds fine until the aggrieved family spreads a rumor that organizers are hoarding supplies. Which happened.

The tricky bit is this: when resources are scarce, fairness is a moving target. Port Harvey tried 'first-come, first-served' for dry goods, which penalized shift workers who couldn't queue at dawn. They tried a lottery for fresh produce, which enraged a diabetic elder who needed specific vegetables. No system was perfect — but the near-miss with spoiled vaccines was the real gut check. A cooler failed overnight; the vaccines sat in 52°F heat for six hours. The organizer who caught it at 5 a.m. saved the batch, but only because she happened to check the temperature log on a whim. Most teams skip this: a temperature-monitoring protocol is a thing you write down before it breaks.

We argued about canned beans while insulin sat in a warm cooler. That was the moment we knew we had no system — only goodwill.

— Dale, Port Harvey supply-chain coordinator, reflecting on day 11

Information silos and miscommunication

The spreadsheet lived on one laptop. The WhatsApp group had 83 members, half of whom muted notifications. The paper sign-up sheet on the community board got rained on and became illegible. Information silos are not a tech problem — they are a trust problem. When the dock team didn't know the church basement had run out of shelf space, they kept sending pallets. When the cold-storage volunteer took a sick day, nobody knew where the manifest was saved.

What usually breaks first is the handoff between shifts. One person's 'sorted' is another person's 'we'll deal with it tomorrow.' We fixed this by forcing a 15-minute overlap between every shift (painful, but necessary) and assigning a single 'duty log' — a physical notebook that lived at the distribution table. No Wi-Fi required. The catch is that even a solid notebook is useless if nobody reads it. Port Harvey's near-riot over baby formula could have been avoided if the distribution committee had simply published their allocation rule book on day one. They didn't. And the rumor mill filled the vacuum. A community supply chain that cannot communicate transparently will fracture — not because people are bad, but because ambiguity feeds fear.

Frequently Asked Questions About Community Supply Chains

How do you prevent hoarding?

Port Harvey saw it happen on day three. One household took forty pounds of rice. Their reasoning? 'The ferry might never come back.' That panic logic breaks any supply chain fast. The fix we used was a capped order form — each household got a weekly allotment based on family size, tracked by address. No exceptions for 'but I have guests.' You enforce this through the people delivering, not through guilt. The catch: some folks will test the system. We had one person register under three different phone numbers. The coordinator caught it because all three addresses routed to the same dock pickup point. That taught us something: transparency beats trust. Publish the allocation rules publicly, and let neighbors police each other. Hoarding drops when everyone sees the same spreadsheet.

— Maggie Tran, Port Harvey logistics lead

What about the person who genuinely needs extra? Medical formulas, bulk diapers, special diets. We built a flag system — any request above 150% of standard allotment went to a two-person review within four hours. Approval rate was 92%. The 8% denied were cases where the items didn't exist in our inventory. No hoarding solution is perfect, but this kept our shelves from emptying into one garage.

What legal liability do volunteers face?

Scary question. Most people assume they'll get sued if someone gets sick from a delivered meal. Reality is messier. In Port Harvey, volunteers operated under an informal 'good Samaritan' understanding — but that doesn't cover everything. We had a driver slip on wet stairs and break a wrist. No lawsuit, but no workers' comp either. The group paid his medical bills out of a pooled fund, which nearly drained our cash reserves.

What usually breaks first is food safety. Perishables moved without refrigeration for three hours during a heat wave. Nobody got sick, but the coordinator froze all meat deliveries until ice packs arrived. The legal risk here isn't a lawsuit — it's that volunteers quit when they feel exposed. The fix was a simple waiver: one page, signed by each recipient, acknowledging that supply chain volunteers aren't professionals. That waiver stopped precisely zero problems, but it made people feel protected enough to keep driving.

I have seen groups spend weeks researching liability insurance. That's wasted time. Instead, call your local emergency management office and ask if their liability umbrella covers registered community volunteers. In Port Harvey's case, it did — retroactively, after we begged. Don't wait for permission. Start delivering, then ask forgiveness.

How do you integrate with official relief efforts?

Badly at first. The county emergency operations center had its own supply trucks, its own lists, its own radios. Port Harvey's system was a Google Sheet. They didn't trust us; we didn't understand their jargon. The odd part is: both sides were moving the same stuff — water, batteries, insulin — to the same people. We were duplicating routes while other streets got nothing.

The fix came from a retired fire captain who lived three doors down from the depot. He walked into our Thursday meeting and said: 'Give me one person who can answer a radio.' That person — a high school senior who ran track — sat beside the EOC dispatcher for four hours a day, cross-checking our delivery list against theirs. Suddenly we stopped delivering to houses that had already received official pallets. Integration doesn't require a formal memorandum of understanding. It requires one bridge person and a shared whiteboard. That sounds flippant, but it worked: we cut duplicate deliveries by 60% in two days.

The trap is assuming official systems will absorb your work. They won't. They're stretched too thin. You integrate by making their job easier — send them your recipient list, take their overflow, and never waste their time with complaints about fuel shortages. Earn trust through competence, not requests.

Your Next Step: A 72-Hour Contingency Checklist

Immediate Actions When Transport Fails

Your ferry has announced an indefinite suspension. Your main road is washed out. The clock starts now — not tomorrow, not after a meeting. Port Harvey's first move was to dispatch three people to every dock and general store within a 30‑minute radius. They did not wait for official guidance. They counted what was actually on shelves, not what was supposed to be there. The inventory gap was brutal: 40% of medical supplies were in transit or stranded on the wrong side of the failed route. That hurts.

Grab a notebook. Physically. Walk every cold-storage unit, pharmacy shelf, and fuel tank. Document quantities in plain numbers — avoid vague terms like plenty or low. I have seen communities waste twelve hours debating estimates when a written list would have settled it in twenty minutes. Wrong order costs lives.

Then freeze all non-critical outgoing shipments. Port Harvey's biggest mistake in hour ten was letting a truck of construction timber leave for the mainland; that diesel was needed three days later to move medical oxygen. The catch is — your instinct will be to keep commerce moving. Resist. Hoard for immediate community need first, redistribute later.

'We lost a whole day because nobody wanted to be the person who said no to a neighbor's lumber order. Say no early. Say it clearly.'

— Maggie T., supply coordinator, Port Harvey Resilience Team

Setting Up a Command Structure Within 24 Hours

Democracy is slow. Crisis needs decisions in minutes, not votes. Port Harvey created a three-person logistics council: one person with authority over supplies, one over transport assets, one over communications. That's it. No committees. No multi-signature approvals for every pallet.

Most teams skip this: you also need a single point of failure for contact. Designate someone whose only job is to answer radio, phone, and messaging channels — and log each request. The chaos multiplier is not scarcity; it is people calling four different coordinators and getting four different answers. Pick one voice, one notebook, one truth.

Avoid the temptation to rotate roles daily. I have watched a well‑meaning group swap coordinators every six hours so everyone felt included. The result was duplicate orders, lost tracking sheets, and a supply depot that ran out of insulin because no single person knew the full count. Stick with your three for at least seventy‑two hours. You can critique the structure later.

Long‑Term Planning for Infrastructure Resilience

The 72‑hour checklist is a stopgap. Real resilience demands a permanent backup system before the next failure. Port Harvey's long game: they now keep a shared digital map of every private skiff, box truck, and livestock trailer within forty miles. That map was built in three afternoons, using paper and a local volunteer's phone. No app required. No grant funding. Just a list and a willingness to update it quarterly.

Second, pre‑negotiate fuel access. The port's gas station owner agreed — after the crisis — to reserve 200 gallons weekly for supply runs, no exceptions. That deal took one conversation. Without it, your response collapses on day five when tanks run dry. Your next step: call your local fuel vendor tomorrow. Ask what it would take to secure a standing reserve for community emergencies. Do not wait for a disaster. Do not accept a vague promise. Get it in writing, even if it's a single email.

Finally, run a 72‑hour drill before you need it. Simulate the ferry closure. Use real checklists. Failure in practice is cheap. Failure during a real supply collapse is not.