Wildfire ash and residue can alter soil resistivity and affect grounding system performance. An often-overlooked consequence of wildfire exposure at substation sites — and what a pre-season treatment program prevents.
IEEE 80 guides safe grounding practices for AC substation installations, including considerations around soil resistivity and step/touch potentials. Utilities design and test grounding systems against site soil conditions — conditions that are not perfectly static over a facility’s life.
Ash, residue, and heat-altered surface soils after a fire can change local resistivity and surface conditions around a yard. Whether a specific site sees a material change is empirical — which is why post-fire inspection and testing matter. Preventing fire at the fence is still the cleaner outcome.
A pre-season measured buffer reduces the chance that wildfire products ever reach the yard. If exposure occurs anyway, pair grounding inspections with the wildfire event record. Sealed fuel/treatment history (PlotSeal™ / GFMS-1.0) helps explain what mitigation existed before the event; it does not replace IEEE 80 engineering.
RiskWise™ executes buffer programs in the CFI™ category; substation electrical engineering remains with the utility’s standards group.
Define triggers with your standards engineering group: ash deposition on the yard, fence-line burn-in, known changes to surface soils, or firefighter foam/water dumps that alter surface conditions. Triggers should launch grounding and civil inspections on a defined timeline.
Keep wildfire sealed records alongside grounding test records for the same site and season so investigators can reconstruct sequence without hunting across drives.
For new substations in grassfire country, include wildfire buffer requirements in the civil and landscaping package early. Retrofitting access and treatment logistics after energization is harder and more expensive than designing for them.
Translate this topic into three artifacts your team can produce this quarter: a one-page applicability note (what the external standard or regulation does and does not cover), a gap list for your named assets, and a documentation standard for wildfire fuel evidence that sits beside — not inside — the compliance file for the external standard.
Review those artifacts with compliance, operations, and insurance stakeholders in one sitting. Misalignment between those three groups is a common reason wildfire evidence looks strong in a slide deck and weak in an audit binder.
When you engage contractors, attach the documentation standard to the SOW. Acceptance should include sealed record identifiers where your program uses PlotSeal™, GFMS-1.0 field completeness, and a clear statement of out-of-scope acres. RiskWise™ field programs are designed to produce that package inside the CFI™ category without renaming CFI™ as a consensus standards body document.
Wherever fine fuels, wind, and expanding critical infrastructure coincide, wildfire exposure is an operating condition — not a rare emergency. Programs that treat it as an annual operating discipline outperform programs that treat it as a one-week contractor event.
Keep claims modest and evidence heavy. Do not invent patents, customer logos, sealed-archive counts, or market-share leadership. Use illustrative numbers only when labeled illustrative. Prefer sealed measurements on named assets over polished narratives about regional averages.
If you take only one action after reading this page, schedule the retrieval drill for your most consequential site and fix whatever breaks. Everything else in the CFI™ category stack — GFMS-1.0 structure, RiskWise™ field work, PlotSeal™ seals — becomes useful the moment a human who was not on the crew can find and verify the file.