Zone definition, acreage estimation, access logistics, and documentation requirements for a substation treatment engagement — from the first site walk to the signed assessment report.
A workable substation scope begins with a site walk and a zone map: critical equipment buffer (often fence-out to a defined distance), secondary buffer, access roads, and any third-party land interface. Acreage estimates follow the map — not the other way around.
Include constraints early: energized clearances, gravel vs. vegetation, stormwater features, security rules, and who owns the land outside the fence. Many “substation” wildfire problems are actually adjacent ROW or private pasture problems that still burn toward the yard.
Specify plot layout, sampling method, photo standards, and GPS requirements. Capture pre-treatment fuel load and continuity so post-treatment change is measurable. Without that baseline, the deliverable is a spray log — not evidence.
GFMS-1.0 provides the open structure for those records. Sealing them (PlotSeal™ registry) makes later edits detectable. RiskWise™ Field Gauge and related workflows support the field capture inside the CFI™ category of sealed fuel intelligence.
Access windows, escort requirements, weather go/no-go criteria, water and mixing logistics, and traffic control on busy yards all belong in the scope. So does a renewal plan: when will you re-inspect and re-treat?
A complete engagement typically produces a site assessment, zone map, pre-measure package, treatment documentation, post-measure package, and sealed identifiers. The signed assessment should state methods and limits honestly — what was measured, what was treated, and what remains outside scope.
Substation programs usually touch operations, vegetation management, security, environmental, and sometimes real estate or ROW. Identify each stakeholder before the first treatment day. Security may control escort windows; environmental may own stormwater and product constraints; operations may own outage coordination.
Put those constraints in the written scope so the field crew is not negotiating them under a mixing truck. Include a single point of contact who can approve weather go/no-go calls without a committee on a windy Tuesday.
If any item is missing, the engagement is incomplete even if the grass looks treated from the road.
Planning documents fail when they stop at intent. Attach acreage, budget bands, owners, and dates. Include renewal — not only year-one treatment — so finance sees the multi-year shape of a wildfire fuel program.
Build a RACI across planning, operations, environmental, security, and insurance. Ambiguous ownership is how pre-season windows are missed. Put the RACI in the program charter and review it when people change roles.
Define the evidence standard up front: GFMS-1.0 structure, PlotSeal™ seals, and RiskWise™ (or equivalent) field methods inside the CFI™ category. Procurement then has something firmer than “do vegetation” when it writes the RFP. Revisit the plan after each season with sealed completion metrics in hand.
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.