Claude Project: Storm Restoration Command Assistant

What This Builds

During a major storm event, you'll have a Claude Project loaded with your circuit maps, feeder lists, switching sequences, and restoration protocols — so when you need to answer "which feeder do we prioritize next?" or "what's the switching sequence to isolate the Oak Street section?" you get an answer in seconds instead of flipping through documents on a table in a staging area at 2 AM. It won't replace your operations center, but it reduces the number of calls you need to make and speeds up your crew's decision-making on the ground.

Prerequisites

• Claude Pro subscription ($20/month at claude.ai)
• Familiar with Claude Projects (Level 3 guide)
• Circuit maps and feeder documentation in PDF or text format (from your utility's engineering department or GIS system)
• Restoration priority guidelines from your operations department
• Cost: Included in Claude Pro subscription

The Concept

During storm restoration, you're managing two types of information: static (your circuit maps, feeder lists, switching sequences — things that don't change mid-storm) and dynamic (which circuits are restored, where crews are, what's still open — things that change constantly). This project handles the static information. It's a searchable version of your documentation stack — like having the circuit binder open to any page instantly.

Think of it as: every operations center has a wall map and thick binders of circuit documentation. This project is those binders in your pocket, searchable by plain English question.

Build It Step by Step

Part 1: Gather your documentation (30-60 min)

Work with your operations or engineering department to get these documents before storm season:

1. Feeder/circuit list — Names, numbers, and primary service areas for each feeder in your service territory
2. Switching sequence summaries — Step-by-step isolation sequences for your most common switching scenarios (not every possible switch, but the 10-15 most common isolation points you actually use)
3. Restoration priority framework — How your utility prioritizes restoration: hospitals and critical facilities first, then by customer count, then by feeder order
4. Known trouble spots — Any feeders or sections known to be problematic (aging infrastructure, vegetation-prone segments, flood-prone underground sections)
5. Mutual aid staging — If your utility participates in mutual aid, the basics of how incoming crews are organized and what information they need

Get these as PDFs from your engineering or operations team. Frame it as "I want to reduce calls to the operations center during storm events." Most ops teams will appreciate the goal.

Part 2: Create the Storm Restoration Project in Claude (20 min)

1. Go to claude.ai → Projects → New Project
2. Name it: "Storm Restoration Reference"
3. In the Project Instructions box, type:

You are a storm restoration reference assistant for a distribution line crew. I am a journeyman lineworker or line foreman.

Your role: Help me quickly look up circuit and feeder information, restoration priorities, and switching sequences from the uploaded documents.

Rules:
1. Only use the uploaded documents for specific circuit, feeder, and switching sequence information. Reference the exact document and section.
2. For restoration prioritization questions, reference the uploaded priority framework if available. If not, apply the standard utility priority order: hospitals/critical facilities → water/sewer facilities → large customer counts → residential feeders by count.
3. Never recommend a switching operation that bypasses formal clearance procedures. Always note: "Verify with operations center before executing."
4. During storm events, I may be under high stress and time pressure. Keep answers brief and clear. Lead with the direct answer, then add details.
5. I may ask about multiple feeders in one message. Answer each one separately and clearly labeled.

1. Click Save
2. Upload your gathered documents using the Add content button

Part 3: Pre-storm testing (20-30 min)

Before the next storm season, test the project with real questions from your service territory:

Test 1 — Feeder lookup:

Expected: Information from your feeder list document.

Test 2 — Priority question:

Expected: Hospital first (critical facility), then 400-customer feeder, then 150-customer feeder, with a note to verify with your ops center.

Test 3 — Shift handoff prep:

Expected: A clear, formatted handoff document ready to send to the incoming crew.

Adjust the project instructions based on what works and what doesn't.

Part 4: Establish your storm use protocol (10 min)

Write a short note (or save it in the project's first conversation) about how you'll use this during events:

• For static lookups (feeder areas, switching sequences): Use the project
• For dynamic status (what's restored, where crews are): Keep a separate running document (Google Docs or paper)
• For all switching operations: Always call the operations center — the project helps you prepare for the call, not replace it

Real Example: Full Workflow

Scenario: It's 1:30 AM during a major ice storm. You're the lead for three incoming mutual aid crews who don't know your service territory. You have 6 feeders open. You need to brief the incoming crews quickly on priorities.

What you ask the project:

What you get:

You have a briefing outline for incoming crews in 30 seconds. That would normally take 10-15 minutes of document searching and phone calls at 1:30 AM.

What to Do When It Breaks

• Can't find feeder info in the docs → The document may not have been uploaded or processed. Check the project's file list. Re-upload if needed. Claude will tell you clearly if it can't find the information.
• Answers seem wrong for your territory → Your uploaded documents may be outdated (old circuit configurations). Verify with operations and re-upload current docs.
• Claude making up switching sequences → The project instructions say to only use uploaded documents for specific sequences. If it's inventing procedures, add to instructions: "Do NOT generate switching sequences that are not explicitly documented in the uploaded files."
• Project not accessible offline → Claude requires internet connectivity. For truly offline field use, print the key circuit reference documents from your project as a physical backup for your truck.

Variations

• Simpler version: Just upload one document — your feeder priority list — and use it only for prioritization questions. Narrow scope, easier to set up and verify.
• Extended version: Add historical outage data (which feeders fail most often in ice vs. wind vs. rain), your GIS export of critical facilities by feeder, and your mutual aid crew briefing template.

What to Do Next

• Before next storm season: Build the project and test it with 10 real questions from your territory
• During storm training exercises: Use it during tabletop exercises to see how it performs under simulated pressure
• After your first storm event using it: Note what worked and what information gaps you discovered — add those documents before the next event

Advanced guide for line foremen and senior lineworkers. Claude Pro ($20/mo) required. This tool assists planning and reference only — all switching operations require formal clearance through your operations center.