The vegetation system of record: working in the utility's, or bringing one

The system of record is the one system whose entry counts as the utility's record of an inspection. No California or federal rule names a platform, so the contract decides. Energy Safety audits vegetation programs by reading exported spreadsheets, which makes the fields, the dispatching work order and the column dictionary the whole of the record.

An inspector opens a work assignment on a distribution circuit on a Monday morning. Before anything about trees, PG&E's procedure gives them one instruction, and it is the first numbered step in the document:

1.1 CONFIRM access to the system of record.

The document is Utility Procedure TD-7102P-01, "Vegetation Management Distribution Inspection," Revision 4, effective November 15, 2025, and readable outside the company because PG&E attached it to its Base Wildfire Mitigation Plan for 2026 through 2028. Nine further instructions in the same procedure send something into that system. Its Definitions section runs alphabetically from Abnormal Field Condition to Work Assignments and never says what the system of record is.

That silence is deliberate and it is normal. No rule in the California or federal stack names a platform for vegetation records. What follows is what the procedures do require, what a state auditor actually reads, and what a prime has to settle before its first entry rather than after.

Ten instructions point at a system the procedure never defines

The phrase appears ten times in Revision 4. Each appearance is an instruction with an actor and a payload.

Where	What goes into the system of record
Step 1.1	Access itself, confirmed before the inspection starts
Table 2, Elevated work category	All strike trees
Table 3	Secondary conductors and idle lines that are not already represented, drawn in
Table 4, step 4	The reason for a De-Designation or a De-Listing
Step 4.2	The prescribed work
Step 6.1	Every contact attempt, with four named details
Step 6.1	An "ADA alert" selection where the owner raises one
Step 6.1	The details and method of the second and third notification attempts
Step 7.1	Constraint data, for environmental review
Section 8	A Tree Crew's deviation from ANSI A300 Clause 5

The last row is the one to read twice. It is the only appearance of the phrase that carries a qualifier, and the only one whose actor is the Tree Crew rather than the inspector:

IF the Tree Crew (TC) CANNOT comply with ANSI A300 Clause 5, THEN the TC must DOCUMENT the deviation from ANSI A300 Clause 5 in the appropriate system of record.

One word, "appropriate," concedes that there is more than one. The procedure allows the crew's system to differ from the inspector's, in the same document that assumes nine times over that everybody knows which one is meant.

Two forms are named anywhere in the procedure. One is a Tree Risk Assessment form for strike trees, which belongs to the Level 2 assessment. The other is TD-7102P-01-F01, a rangefinder verification form. Both sit alongside the entry; the prescription itself goes into the system of record. Access is step 1.1 because an observation made without it has nowhere to go.

Where the map is wrong, the inspector draws the line in

Table 3 carries a note that most readers skim, and it says more about the system of record than the nine instructions that write into it:

NOTE: DRAW IN all stand-alone secondary conductors and Facilities, including idle lines, if they are NOT represented in the system of record.

The utility's own procedure states that its facilities layer is incomplete and makes the vegetation inspector the person who fixes it. A pre-inspector walking a rural circuit in the fall is doing asset data capture for a map that switching, planning and outage analysis all read from.

Three things follow for a prime, and they are scope questions rather than field questions. The inspection scope of work has to say whether drawing in facilities is in it, because it is inspection time spent on something other than vegetation. The QC sample has to cover drawn-in geometry, which fails differently than a missed tree does. And the inspector's entry becomes an edit to a shared layer, which is the strongest version of the point that everything the inspector produces is the utility's the moment it is made.

One service drop and four systems joined by hand

Appendix D of Revision 4 is new in that revision. It handles one narrow case: an inspector with actual knowledge of strain, abrasion or hazard tree risk on a service drop, which is a facility PG&E is not required to inspect. The path it prescribes crosses four systems.

• The PG&E Report It App, downloaded from the App Store onto the reporter's mobile device.

• An email identity, "Use your firstname.lastname@pge.com email address to report an issue in this program," with Tree Service Worker entered when prompted for what best describes the reporter.

• The asset register, reached by hand: "If you have the SAP ID Equipment Number, please add it to the report description."

• CC&B, where the case is closed, referencing the Report It App case number in the closing comments.

A confirmation email carries the case number back. Somebody downstream reads the description field and creates the 540 notification, which is why the comment string is fixed text rather than free prose.

Read as an integration, this is four systems joined by a person retyping an identifier into a text box. Each join has a failure mode a program manager can name in advance. A contract partner's inspector may not hold a pge.com address, and the procedure gives no alternative.

An equipment number the inspector lacks travels no further than the description field, so the report arrives located by prose. The Report It case number lives in a comment field, which means the link between the notification and the closed case is unsearchable by anything except text.

The design works. What it asks of a program manager is to know, before the contract starts, which joins are typed and which are keyed, because the typed ones are where a record goes missing.

An inspection that shares a work order did not happen

The Office of Energy Infrastructure Safety reported on San Diego Gas & Electric's 2023 Substantial Vegetation Management audit on April 21, 2025. One finding concerned Century plants, which SDG&E had committed to inspect twice a year:

The documentation provided demonstrated that of the 63,616 inventory Century Plants, 68% had two inspection dates, while 32% had only one inspection date.

SDG&E's position was that the second inspection happened. Its corrective action plan of January 31, 2025, explains why the file cannot show it. The targeted species patrol runs in a compressed window of about two months in the spring, when the plant blooms, so in several Vegetation Management Areas it lands in the same month as the routine detailed inspection.

As such, the Century plants in these VMAs are not inspected under a separate, unique dispatch work order that would represent the second inspection activity.

Then the second half, which is the data model rather than the schedule:

Additionally, during the detailed inspection, all Century plant records are updated, whereas, during the targeted species patrol, only the Century plants that require work before the next scheduled inspection activity are updated. Therefore, not all Century plant records receive two distinct inspection activities.

Updating a plant's record proves what the plant is. It does not prove that somebody walked up to it, because a plant needing no work produces no change to update. Two design rules come straight out of that, and both are set at dispatch rather than in the field.

An inspection event needs a row of its own, keyed to the work order that sent somebody out. And a visit that finds nothing has to leave that row behind, which is the same requirement a blank finding field imposes on a span record.

SDG&E's commitment was a dispatch change: "Each detailed inspection and targeted species activities will have a separate and distinct work order to effectively evidence these activities." The schedule moved and the work orders split, and the field work stayed as it was.

One more detail from the same exchange is worth carrying. The audit report counted 63,616 inventoried Century plants from the 2023 documentation. The corrective action plan, written in January 2025, gives an inventory population of approximately 33,800 units across 129 of SDG&E's 133 Vegetation Management Areas. It adds that "this number changes over time as new units are added to the system and others are removed from inventory." An inventory count is a statement about a date. A count quoted with the date attached saves somebody a reconciliation later.

The same plant as an inventory row and as a phone call

Revision 4 of PG&E's procedure added a Century plant row to Section 8 in the same revision cycle. It reads in full:

If a mature Century plant is identified and has the possibility of blooming and Impacting PG&E electrical Facilities, then contact the local supervisor for guidance.

Two California utilities, the same plant, two answers. SDG&E carries Century plants as an inventory with per-unit records, inspection dates and a targeted species patrol on a schedule. PG&E routes them to a conversation with a supervisor. Both are compliant. SDG&E's inventory exists because SDG&E committed to it in a wildfire mitigation plan, and a commitment in an approved plan is auditable from the day it is made.

The consequence is asymmetric and it lands on the contractor. A program with an inventory can be audited against it, and SDG&E was. A program that routes to a supervisor has nothing to audit and nothing to miss. What counts as "in the system" is a program design decision, and an evaluator comparing two bids is comparing two of those decisions before they are comparing any tree work.

The regulator reads an export rather than your screen

The same SDG&E audit had a second finding that resolved differently, and it is the clearest demonstration available of what a vegetation system of record actually delivers to a regulator.

SDG&E's 2023 target was clearance work on 11,200 tree units. Energy Safety read the file and found 8,855:

Energy Safety determined this by reviewing work completion dates in the Excel file and filtering out any "N/A" and blank line items in columns labeled "TT_ActivityDate," "TT_Condition Code," and "TT_WorkOrderID."

The filter was reasonable and the conclusion was wrong. SDG&E's corrective action plan explains the convention behind those cells:

If a clearance was achieved through removal, the cell for trimming clearance was marked as N/A, and vice versa, to avoid a clearance being counted twice.

So N/A meant the clearance was achieved the other way. Blank meant an absence of data. Filtering both out discarded 4,597 removals.

The correction came from a phone call. SDG&E's plan records an informal conference call with the Environmental Sciences Division on January 14, 2025:

During that call SDG&E demonstrated how specific filtering of the data sheet validated that SDG&E exceeded the target by completing clearance on 13,452 tree units compared to the 8,855 units identified in ESD's initial analysis of the data.

Energy Safety reanalyzed and found 13,452. A program that met its target spent a year in a published deficiency because three column headings traveled without a dictionary.

Energy Safety's audit of Southern California Edison's 2020 vegetation work, published April 13, 2022, shows the same mechanism from the other side. It assessed inspection completion from "an Excel file named, 'WSD_007_Q2_Trees_Inspected.xlsx,' which provided inspection records of 766,404 trees adjacent to distribution and transmission lines," summing column D for the count and reading column E for species. In both audits the regulator worked from a spreadsheet and a footnote naming the column.

So the exported view is the record, for the purpose that matters most. Three things belong in the contract as deliverables rather than as favors.

• A data dictionary, versioned with the extract it explains.

• A stated distinction between blank, N/A and zero.

• A named person who can explain a filter on a phone call three years after the crew has gone.

No rule names a system and one regulator names the accounts

Somebody writing a technical specification wants a citation for the system requirement. There is not one, and the honest version of that answer has three parts.

CPUC General Order 165 Section III.C sets contents and stops:

For all inspections records shall specify the circuit, area, facility or equipment inspected, the inspector, the date of the inspection, and any problems (or items requiring corrective action) identified during each inspection, as well as the scheduled date of corrective action.

Five fields, an access window, and no opinion about where they live. What that standard reaches and which clock it starts is set out separately, and the retention clause is the part that outlives any platform.

NERC Reliability Standard FAC-003-5 hands the choice of format to the entity. Its supplemental material says evidence of annual work plan execution depends on "the planning and documentation format used by" the Transmission Owner or Generator Owner. Seven forms follow as examples, running from a signed-off work order to a paid invoice, and any of them will do.

The closest a California regulator has come to naming a system was to name its contents. Energy Safety's SCE audit describes 2020 Wildfire Mitigation Plan initiative 5.3.5.19 as covering "the utility's efforts toward having a 'centralized inventory of vegetation clearances' that includes species, growth forecast, and grow-in, blow-in, or fall-in risk." An inventory, with three things in it, specified by its contents.

The contrast sits inside the same company's filings. FERC requires jurisdictional entities to keep their books and records in accordance with the Uniform System of Accounts, and 18 CFR Part 101 prescribes the accounts down to the requirement that a Major utility maintain records of annual additions and retirements for each plant account. FERC revised that system by Order No. 898 on June 29, 2023. A utility's money runs through a federally specified chart of accounts. Its tree records run through whatever the utility bought.

Which leaves the question of who decides. The utility decides, by issuing the procedure, and then again by issuing the work assignment. A prime cannot resolve it from the published procedure, because the published procedure says "the system of record" and moves on.

Bringing one: four questions that decide whose entry is the record

Utilities already run other people's software. SCE's 2020 plan said so plainly: "SCE maintains several digital tools for Vegetation Management, including Collector/Survery123 for compliance inspections and FULCRUM for HTMP." Collector and Survey123 are Esri field applications and Fulcrum is a commercial data collection platform, all three bought rather than built.

Energy Safety audited what was inside one of them, reviewing "an example from SCE's FULCRUM system that includes data on tree ID, inspection date, last trim date, species, growth rate, tier location, and latitude and longitude," and found SCE compliant with that initiative. The fields were the question.

So a contractor-hosted system can hold the record. It becomes the system of record, or fails to, on four answers that belong in the contract.

Which system's entry is authoritative, field by field. Two systems holding a prescription will eventually disagree about it, and the tiebreak has to exist before the disagreement does. The honest version is usually a split: the utility's system is authoritative for the unit and its status, the contractor's for the field observation and the photograph.

What identifier joins the two. The span, pole or vegetation point ID is the spine, and a system that generates its own keys without carrying the utility's has produced an island. The PG&E service drop path is the cautionary version, where the join is an equipment number typed into a comment.

What comes back at the end of the contract, and in what shape. An export becomes a handover once somebody can read the columns. The deliverable is the data, the dictionary and the history of amendments, in a format readable with the vendor long gone. Every retention clause in the stack names the company and none names the contractor, which means the obligation to hold the record never moves, only the storage does.

Who can answer a question about it in year eight. GO 165 and GO 95 Rule 18 both measure in years, and a records request arrives on a clock. The SDG&E conference call happened two years after the work. The equivalent call in 2033 will be made to somebody who was not there, reading an archive from a platform that may not exist, and the column headings are all they will have.

What the system has to be able to do

The requirements a vegetation system of record carries are scattered across a procedure, a general order and a reliability standard, so here they are in one place. Each is traceable to something quoted above.

• Grant and evidence access per named user before the inspection starts, because step 1.1 of the utility procedure makes access a precondition rather than a convenience.

• Hold every field GO 165 Section III.C names, for every inspection, including the ones that found nothing.

• Create a distinct row per inspection event, keyed to the work order that dispatched it, so that two visits in one month are two records.

• Distinguish blank from N/A from zero, and say which is which in a dictionary that travels with the export.

• Carry the utility's own identifier on every object, so the record joins to the asset register without a person retyping it.

• Record an amendment as an event with a date, an author and a reason, alongside the entry it corrects.

• Accept geometry the inspector draws in, where the facilities layer is missing a secondary conductor or an idle line.

• Produce a complete span-level history for a named circuit, in a readable format, long after the contract that created it has ended.

The inspector confirming access at 8:30 on a Monday is doing the first of those. The eighth is being done by somebody in 2035, reading what they typed. Everything between the two is a design decision somebody makes once, usually while writing a contract, and usually without being asked.

Common questions

Further reading

• What a pre-inspection produces: The unit of work that goes into the system in the first place.

• How long a California vegetation record is kept, and by whom: The clocks that keep running after the platform is retired.

• Documenting clearance work so it survives an audit: What a records request asks for, and the fields that answer it.

Frequently asked questions

Does any rule say which software a utility's vegetation records have to live in?

No. CPUC General Order 165 Section III.C names the contents of an inspection record and an access window, and stops there. NERC FAC-003-5 says in its supplemental material that acceptable evidence depends on "the planning and documentation format used by" the entity. The contrast inside the same company is visible at FERC, which prescribes the accounts its plant records are kept in under 18 CFR Part 101 and prescribes nothing about the system holding its tree records. The platform is a contract question.

If our crews use our own application, whose entry is the record?

Whichever one the utility's procedure and the work order point at. PG&E's TD-7102P-01 Revision 4 opens with "CONFIRM access to the system of record" and then sends ten instructions into it, without naming it. The procedure will not settle it for a prime. The contract and the work assignment do, and the answer has to be written down before the first entry is made rather than after.

What does a state auditor actually look at?

An export. Energy Safety's 2023 audit of SDG&E worked from an Excel file and filtered out N/A and blank line items in columns labeled "TT_ActivityDate," "TT_Condition Code," and "TT_WorkOrderID." Its 2022 audit of SCE worked from a file named WSD_007_Q2_Trees_Inspected.xlsx holding inspection records for 766,404 trees. Neither auditor logged into the system. The column names and what a blank cell means are the part of the record a regulator reads.

Two inspections happened on the same tree in the same month. Why does the file show one?

Because the second one had no work order of its own. SDG&E told Energy Safety that its Century plant targeted species patrol and its detailed inspection fell in the same month in several Vegetation Management Areas, so the plants were "not inspected under a separate, unique dispatch work order that would represent the second inspection activity." Of 63,616 inventoried plants, 68 percent carried two inspection dates and 32 percent carried one. The corrective action was a dispatch change, not a field change.

Can a contractor's platform hold a utility's compliance evidence?

Utilities already run vendor platforms. SCE's 2020 Wildfire Mitigation Plan named Collector, Survey123 and FULCRUM as its vegetation management digital tools, and Energy Safety audited the fields inside FULCRUM rather than the vendor behind it. What matters is which system's entry is authoritative, what identifier joins it to the utility's asset data, what comes back at the end of the contract and in what format, and whether somebody can read it for the full retention period.