Build the storm evidence file before RFIs start.
A single hurricane or ice-storm event puts $50M–$500M of FEMA PA recovery and PUC rate-case cost under an 18-month review cycle. PacketUpload turns 72 hours of field chaos into itemized, cross-referenced, auditor-ready documentation — before the first FEMA Region RFI or ALJ data request lands.
Built for VPs of Regulatory, CFOs, and Storm Directors at IOUs, G&Ts, municipals, and co-ops whose recovery dollars depend on documentation integrity.
Storm documentation breaks under time pressure.
In the first 72 hours, field and mutual aid crews generate tens of thousands of work orders, timesheets, invoices, and damage photos — then your team spends 12-to-18 months reconciling them. One mismatched crew code, one contractor invoice without a 2 CFR Part 200 procurement trail, and seven-figure FEMA Project Worksheets get kicked back to Regional.
72 hours of paper, email, and vendor apps
Crews arrive from 14 utilities running 14 different field apps. Your OMS never sees half of it.
Project Worksheets bounce on one missing line
PA Cat B and Cat F demand itemized labor, equipment rates, and materials reconciled to each PW.
Rate cases pick apart the schedule line by line
ALJs demand prudence review of mutual aid invoicing against EEI RMAG guidelines.
Storm teams burn out twice
16-hour field shifts, then 18 months of desk reconciliation — before next season hits.
Defensible documentation, from crew truck to FEMA Grants Portal.
Damage photos, restoration work orders, crew timesheets, and mutual aid invoices — read, classified, and cross-referenced to Project Worksheets in one pass. Gaps surfaced before your PA Coordinator opens the Grants Portal. Low-confidence extractions route to your reviewer with specific reason codes — the final call stays with your team.
Damage packets understood at scale
Geotagged damage photos, handwritten field assessments, restoration work orders, and vendor invoices — extracted, classified by FEMA PA Category (A–G), and cross-referenced to work orders in Maximo, Oracle WAM, or GE Smallworld in a single pass.
FEMA-aligned cost capture on current PAPPG guidance
Labor, equipment, and materials reconciled against FEMA Cost Codes and the current Schedule of Equipment Rates. Mutual aid invoicing checked against EEI RMAG guidelines. 428 Alternative Procedures claims assembled with fixed-cost estimating support — before the PW goes to the State Applicant Agent.
Gaps flagged inside the 60-day RPA window
Missing signed timesheets, unmatched contractor POs, undocumented overtime, Cat F scope creep — surfaced in real time, not after FEMA requests Additional Information and the clock resets. State EMAs see a cleaner PW the first time through.
An audit trail that holds at the PUC
From field photo to final Project Worksheet to rate-case schedule — every step traceable. Stand behind the storm schedule in prudence review. Aligned with 2 CFR Part 200 procurement standards, OIG audit expectations, and IEEE 1366 SAIDI/SAIFI reconciliation.
What a FEMA PA obligation hold reads like.
Three documentation defects. Nine figures of capital trapped in obligation review. These are the kinds of redlines PacketUpload catches before the Project Worksheet ships to the Region.
From the first outage ticket to the Grants Portal submission — one documentation path.
PacketUpload absorbs chaos during the event and resolves it into the formats your PA Coordinator, State Applicant Agent, and regulatory counsel need.
Today The Paper Avalanche
- Event hits, crews mobilize, docs scatter. Mutual aid crews arrive using 14 different field apps. Handwritten forms. Photos WhatsApped. Timesheets on paper. Contractor invoices emailed as PDFs. No single system of record for the event.
- 12+ months of manual reconciliation. Emergency preparedness analysts spend months matching photos to work orders in Maximo or WAM, crew sheets to mutual aid contracts, invoices to FEMA Cost Codes. 30–40% of the effort is renaming files and fixing dates.
- FEMA Cat F Project Worksheet bounces back. Missing signed timesheets. Equipment rates that don’t tie to FEMA’s Schedule. Contractor procurement not documented under 2 CFR Part 200. RFIs from Regional, 60-day clock resets.
With PacketUpload The Audit Trail
- Ingests every format from every source. Handwritten damage assessments, geotagged photos, crew timesheets, contractor invoices, TRV forms — parsed, classified, and aligned to Project Worksheets by event, category, and work order in near real time.
- Cross-references to your OMS and ERP automatically. Field evidence matched to work orders in Oracle WAM, GE Smallworld, Responder, Maximo, or Survalent. Cost detail reconciled against SAP / PeopleSoft GL. Nothing re-typed.
- Gaps flagged inside the 60-day RPA window. Missing signatures, unmatched POs, undocumented overtime surfaced in days, not months. Your PA Coordinator gets a prioritized punch list before the State Applicant Agent does.
Runs alongside your OMS, ERP, and the regulators you report to.
Storm response touches every major operational system in your utility. PacketUpload does not replace them — it stitches field evidence to the records they already hold.
We integrate with the ADMS/OMS, GIS, WAM, and ERP stacks utility storm response teams actually run, and export submission packets in the formats the FEMA Grants Portal, your State Applicant Agent, and your rate case counsel expect. See the EEI Mutual Assistance Playbook and FEMA PAPPG (current edition) for program context.
Grounded in the federal, industry, and state frameworks your storm packet answers to
What storm ops, emergency preparedness, and regulatory leads ask us.
What kinds of storm packets does PacketUpload handle?
Damage assessment packets (IDA and PDA), EEI / APPA / NRECA mutual aid crew reports, restoration work orders and tie-outs, FEMA Public Assistance Project Worksheets (Cat A–G, with emphasis on Cat B emergency protective measures and Cat F permanent work on utility infrastructure), 428 Alternative Procedures fixed-cost estimating packages, overtime and mobilization timesheets, contractor invoicing, and PUC rate-case storm cost schedules.
Can this integrate with our OMS, WAM, or ERP?
PacketUpload reads the file exports and structured outputs your OMS, WAM, and ERP already produce — no API contract required to start. Designed to run alongside Oracle WAM, GE Smallworld, Schneider ArcFM / Responder, IBM Maximo, Survalent ADMS, Esri ArcGIS, SAP ERP, PeopleSoft, and home-grown storm trackers. Exports run straight into the FEMA Grants Portal.
What does PacketUpload decide, and what stays with our PA Coordinator?
PacketUpload flags defects, reconciles costs to FEMA guidance, and assembles the Project Worksheet packet. It does not approve, deny, or submit — your PA Coordinator and regulatory counsel make the final call on every flag. Low-confidence extractions surface with reason codes, not pass/fail verdicts.
Does the output stand up to FEMA PAPPG and OIG audit?
Every flag cites the source document, page, and field. The trail is exportable in the formats FEMA Regional reviewers, the State Applicant Agent, your State EMA, and OIG auditors expect. We align to the current PAPPG, 44 CFR Part 206, and 2 CFR Part 200 procurement standards — including the documentation FEMA requests during 428 Alternative Procedures fixed-cost validation.
How does this support rate case and prudence review?
We assemble NARUC-style schedules tying storm cost by category (labor, equipment, materials, mutual aid, contractor) to the storm rider or deferred accounting filing, pre-build the EEI mutual aid prudence package, and turn ALJ data requests into minutes of work rather than weeks. Your regulatory counsel and rate case witness get the same source of truth as your PA Coordinator.
Will this work during the event itself, not just after?
Yes. PacketUpload runs live during activation. Your Storm Desk, Emergency Operations Center, and PA Coordinator see a real-time dashboard of damage assessment coverage, mutual aid intake, and outstanding documentation — before the restoration bell rings. That shortens the reconciliation window from 12–18 months to weeks.
What about NERC reliability reporting?
We reconcile restoration event data into the IEEE 1366-compliant SAIDI / SAIFI / CAIDI inputs your reliability team reports, including Major Event Day (MED) classification evidence. Consistent with FERC Form 1 storm footnotes and state-level reliability filings.
Build the storm evidence file on defensible ground.
Send us a sanitized PW or damage packet — we’ll come back with fit, the first checks we’d encode, and a pilot scope within two business days.
Tell us your service territory, typical PA Category mix, and the ADMS/WAM stack your storm desk runs. Prioritizing IOUs, G&Ts, and large co-ops heading into storm season.
Request a briefingOr reach regulatory affairs at join@packetupload.com