How long a California vegetation record is kept, and by whom
A California vegetation file runs on several retention clocks. GO 95 Rule 18A(1)(b) holds the corrective action record ten years from completion of the work. GO 165 Section III.C holds patrol and detailed inspection records ten years and intrusive pole records for the life of the pole. FAC-003-5 holds transmission vegetation evidence three calendar years.
James Miller of the CPUC's Electric Safety and Reliability Branch audited the City of Needles Electric Department from March 10 to March 14, 2025. The findings letter went out on June 25, 2025 as EA2025-1291, signed by Fadi Daye, and gave the city until July 25 to report its corrective measures. Several findings say the same thing in different words:
The City of Needles was unable to provide CPUC staff with a current inspection program or procedure for its overhead facilities and was unable to provide any patrol or detailed inspection records for calendar years 2023 or 2024. The city of Needles was also unable to provide any vegetation management records nor intrusive testing records for its poles in calendar year 2024.
There was no file to be wrong. Staff cited the two rules in the California stack that say how long the records should have been sitting there, and those two rules set different periods that start on different days.
The retention periods, side by side
A single trimmed span leaves entries that become deletable on separate dates. Some of those dates come from a rule, one comes from an event nobody schedules, and one row has no date to compute at all.
Record | How long | Measured from | Named holder | Source |
Corrective action on a GO 95 nonconformance | At least 10 years | Completion of the corrective action | "the company" | |
Notice of a safety hazard on another company's facility | At least 10 years | The notification | "all parties" | GO 95 Rule 18B |
Distribution patrol and detailed inspections | At least 10 years | Unstated | "the utility" | |
Wood pole intrusive inspections | Life of the pole | Unstated | "the utility" | GO 165 Section III.C |
Transmission inspection and maintenance | Unstated | Unstated | "each utility" | GO 165 Section IV |
FAC-003-5 evidence for R1, R3, R5, R6, R7 | 3 calendar years | The calendar year | Transmission Owner, Generator Owner | |
FAC-003-5 evidence for R4 | 12 months of operator logs, 3 months of voice recordings | Most recent | Transmission Owner, Generator Owner | FAC-003-5 section 1.2 |
Maintenance work orders and job orders | 5 years | Unstated | FERC public utility or licensee | |
Substation and transmission line logs | 3 years | Unstated | FERC public utility or licensee | 18 CFR 125.3 item 14(a) |
Exempt Tree database | Current, with no end date | Annual inspection | "the utility" | |
PRC 4292 and 4293 field work | No period | Not applicable | Nobody | 14 CCR 1250 to 1258 |
Read the third column before the second. Two rules both say ten years and start counting on different events, which is how a program holding one retention policy ends up with two destruction dates for one span.
The ten years in Rule 18 starts when the work ends
Rule 18A(1) is one paragraph about the fix and one sentence about the file:
Upon completion of the corrective action, the company's records shall show, with sufficient detail, the nature of the work, the date, and the identity of persons performing the work. These records shall be preserved by the company for at least ten (10) years and shall be made available to Commission staff upon 30 days notice.
The clock hangs off the opening clause. Preservation runs from completion of the corrective action, and the day the condition was found starts a different clock in a different system.
The gap between those two days is as long as the correction window allows, and Rule 18A(2)(a) allows a lot of it. A Level 2 nonconformance that creates a fire risk in Tier 2 of the High Fire-Threat District carries a ceiling of 12 months. Every other Level 2 carries 59 months. Take a 12 kV span with 30 inches of clearance found on March 3, 2026, classified Level 2 in Tier 2, and cleared by a crew on February 20, 2027.
The corrective action record is reachable until February 20, 2037. Written up as an ordinary Level 2 and closed in the fifty-ninth month, the same record would run into 2041. What the level and the correction date do to each other fixes the retention end date years before anyone reads it as one.
Rule 18B attaches the same ten years to a different document and gives it more than one owner:
The notification shall be documented and such documentation must be preserved by all parties for at least ten years.
That is the only retention clause in the California stack naming more than one holder. On a jointly used pole, the inspecting company, the pole owner that relayed the notice and the facility owner that received it each hold the same document for the same decade. Which of them owes what on a pole with two owners is a separate question, and the retention duty falls on all three alike.
GO 165's ten years is a window of activity
Section III.C states the period in a sentence whose grammar decides how much has to survive:
The utility shall maintain records for (1) at least ten (10) years of patrol and detailed inspection activities, and (2) the life of the pole for intrusive inspection activities. Such records shall be made available to parties or pursuant to Commission rules upon 30 days notice.
Read one way, each record survives ten years from its own date. Read the other way, the utility holds a rolling ten year window of activity. On a five year detailed cycle the two readings part company:
Under the first, a detailed inspection performed in 2016 becomes deletable in 2026.
Under the second, the two most recent detailed inspections of every asset stay in the file whatever their dates.
The order leaves this open, and so does every decision amending it. What settles it in practice is the company's own auditable maintenance program under Rule 18A(2)(a), because that document is what the Safety and Enforcement Division measures the file against. A program stating which reading it follows has answered the question in advance. A silent program answers it on the spot, in an audit, under a 30 day clock.
Needles failed under either reading. Calendar years 2023 and 2024 sit inside any ten year window drawn from a 2025 audit date.
Section III.C leaves one more thing open: which of its two categories a dedicated vegetation patrol belongs to. GO 165 defines patrol and detailed inspections, and neither of them is a vegetation inspection. The Needles audit nonetheless quoted Section III.C and then recorded the absence of vegetation management records underneath it. Staff read the section as reaching the vegetation file. The order, on its face, says something narrower.
Life of the pole has no end date on it
The second half of Section III.C is the longest obligation anywhere in the stack, and the only one whose end is an event rather than a date:
the life of the pole for intrusive inspection activities
A wood pole set in 1996 and first bored in 2014 carries that 2014 record for as long as it stands. Still standing in 2046, it carries a 32 year old record that is still required. The obligation ends when a crew pulls the pole, an event recorded in the plant system rather than the inspection system, by people thinking about a hole in the ground.
Three consequences follow from a period defined by an object.
Age alone is the wrong key. A retention rule expressed in years has nothing to compute against here, so an archive purging on record age will eventually destroy a live record.
The pole identifier is load bearing. It is the only field linking the record to the object whose retirement ends the period, which makes the identifier the spine of the file rather than a convenience.
Transfer breaks the chain. When a pole is sold or transferred to another owner, GO 165 says nothing about the bore record traveling with it, so the transfer agreement has to.
Needles could produce no intrusive testing records for calendar year 2024. Those are the records with no expiry at all.
The Commission's records order is from 1912
California does have a general records preservation order. General Order 28, In the Matter of the Preservation of Records of Public Utilities and Common Carriers, was approved September 10, 1912, took effect October 10, 1912, and was reissued December 22, 1947. It sits on the Commission's current list of general orders. It carries a destruction rule stricter than anything in GO 95 or GO 165:
It is further ordered, That no records, memoranda or papers which come within the scope of this order shall be destroyed, except on the written authority of this Commission.
Then it says what comes within its scope, and the scope is a set of account books:
Voucher register or accounts payable ledger, accounts receivable register, and vouchers and papers supporting all deeds and title papers.
Trial balances of all ledgers, general and auxiliary ledgers, journals and cash books, and all cash papers and journal entries.
Capital stock ledger and journal stubs, annual reports, and minute books.
Records, contracts, estimates and memoranda pertaining to original cost of property and to Additions and Betterments.
Records pertaining to depreciation and replacement of equipment and plant.
An inspection record, a field work order and a clearance measurement are all absent from that list. Routine line clearance is expensed operating work rather than an addition or a betterment, which puts it outside the property clause as well. Whether GO 28 reaches a vegetation file at all is a question for the Commission. The practical answer today is GO 95 Rule 18 and GO 165 Section III.C, and both of those let a company delete on its own authority once the period runs.
One sentence in GO 28 has outlived its subject matter:
The manner in which these records, memoranda and papers shall be preserved must be such that this Commission may readily examine the same at its convenience.
Written for ledgers in a vault in 1912, it describes exactly the standard a retired field application fails.
Every retention clause names the company, and none names the contractor
The work is done by contract crews. The duty stays with the utility.
Rule 18A(1)(b): "the company's records shall show," and "preserved by the company."
GO 165 Section III.C: "The utility shall maintain records."
FAC-003-5 section 1.2: "The applicable Transmission Owner and applicable Generator Owner retains data or evidence."
18 CFR 125.2(b): "Each public utility or licensee subject to the regulations in this part shall designate one or more persons with official responsibility."
Public Utilities Code section 314 draws its boundary in the same place. Subdivision (a) reaches "the accounts, books, papers, and documents of any public utility." Subdivision (b) extends that to a subsidiary, an affiliate or a holding corporation, and only "with respect to any transaction between the water, electrical, gas, or telephone corporation and the subsidiary, affiliate, or holding corporation." An independent vegetation contractor is none of those things. Commission staff inspect the utility's records, and the contractor answers to the utility alone.
So the inspector who measured 30 inches to a conductor works for a company that owes the Commission nothing, entering the reading into an application that company owns, under a contract with an end date. Nearly every field observation in a vegetation file arrives that way. The contract is the instrument that moves the data into the utility's custody, and it has to carry three terms the general orders will not supply:
Delivery as a readable export, rather than access to a system the contractor hosts.
Delivery on termination as well as during the term.
The retention period the utility itself owes, so the contractor's own purge schedule runs at least as long.
The test of whether that worked is the production clause. Rule 18A(1)(b) and Section III.C both allow 30 days. Thirty days is measured from a letter like the one Needles received, at a point when the vendor may be three vendors ago.
The federal schedule that also sits on an investor-owned utility
A California investor-owned utility is also a public utility under the Federal Power Act, which puts it inside 18 CFR Part 125 and its schedule of records and retention periods. A municipal utility or an irrigation district sits outside it. Needles is outside Part 125 entirely.
Two items in the schedule land near vegetation work.
Item | Record | Period |
14(a) | Substation and transmission line logs | 3 years |
14(b) | System operator's daily logs and reports of operation | 3 years |
15(a) | Authorizations for expenditures for maintenance work to be covered by work orders, including memoranda showing the estimates of costs to be incurred | 5 years |
15(b) | Work order sheets to which are posted in detail the entries for labor, material, and other charges in connection with maintenance | 5 years |
Neither item names vegetation, a tree or a clearance. The schedule sorts by accounting class, so a vegetation work order is reached as a maintenance work order or it is reached by nothing, and the person who makes that call is the records official the utility designates under 125.2(b). FERC decides it if anyone disputes the answer.
The effect is a third number on the same job. A single trim on a 115 kV line, performed under a work order, closing a Rule 35 nonconformance, on a line applicable to FAC-003-5, produces three periods at once:
The work order, released by the federal schedule at five years.
The corrective action record, held by GO 95 for ten years from completion.
The vegetation evidence, held by the reliability standard for three calendar years.
The longest of the three governs the file. A shorter federal or NERC period releases the federal or NERC copy and leaves the state obligation standing.
What stops the clock, and what has no stop clause at all
Three provisions in the stack suspend an otherwise lawful deletion. They belong to different regimes, and GO 95 and GO 165 contain none of them.
18 CFR 125.2(l). The broadest of the three, reaching back over the whole schedule:
Notwithstanding the minimum requirements, if a public utility or licensee is involved in pending litigation, complaint procedures, proceedings remanded by the court, or governmental proceedings, it must retain all relevant records.
A CPUC order instituting investigation is a governmental proceeding. So is a CAL FIRE cause investigation naming the utility. The trigger is the proceeding itself, which means the obligation attaches on a date the records group may learn about weeks later.
FAC-003-5 section 1.2. Two clauses, working in opposite directions. An entity found non-compliant keeps the related information until it is found compliant or for the stated period, whichever runs longer. And where the file covers less ground than the interval back to the last audit, the Compliance Enforcement Authority may ask for other evidence spanning it. Three calendar years is therefore a floor on what is kept and a ceiling on nothing. What the rest of that standard requires is its own subject.
General Order 28. Destruction on written authority of the Commission, for the account books it covers.
GO 95 Rule 18 and GO 165 Section III.C have no equivalent. Each says "at least," sets a floor and stops there. Litigation, an open audit and an incident under investigation are all outside their text, so the hold on a vegetation record comes from a rule other than the one that created the record. Which body is asking, and under what authority decides which of the three clauses above is even available.
The Public Resources Code sets no period because it asks for no record
Neither PRC 4292 nor PRC 4293 requires anyone to write anything down, and nothing in 14 CCR sections 1250 to 1258 supplies the omission for the firebreak and clearance work itself. A ten foot pole firebreak cleared in June 2026 and a four foot radial clearance cut on the same day generate no statutory record, and a retention period needs a record to attach to.
The one exception in that article is a currency duty. 14 CCR 1257(a)(3)(B) requires a utility claiming the Exempt Tree exemption to inspect Exempt Trees annually and to maintain a database about them. A database last verified in 2023 is not a stale record, it is a failed exemption, and the tree it describes reverts to the PRC 4293 clearance distance.
What an Exempt Tree has to satisfy and who confirms it is the substance behind that row. The retention consequence is narrow and worth stating on its own: this is the one file in the stack where age destroys the record's legal effect rather than merely permitting its deletion.
So the retention period on a PRC 4292 or 4293 artifact comes from whichever other regime the utility filed it under. Where the same span also carries a GO 95 nonconformance, the clearance evidence rides the ten year clock attached to the corrective action that closed it. Where it carries none, the only floor is the one the company wrote into its own program.
What the record has to name
Retention is a property of the file, so the fields that make it work belong in the file rather than in a policy document.
The record class, in the rule's own words. "Corrective action record, GO 95 Rule 18A(1)(b)" and "detailed inspection record, GO 165 Section III.C" are different classes on different clocks. A system storing both as "inspection" has discarded the field the retention rule keys on.
The event the clock starts from, with its date. For a corrective action record that is the completion date, which is a different date from the finding date already in the file. For an intrusive inspection record it is the pole identifier, because the pole is the clock.
The earliest lawful destruction date, computed and stored. A stored date can be reported on, queried against a records request, and shown to a stranger. A rule reference gets re-interpreted by whoever inherits the system.
The system of record and its custodian. Which application holds the original, which company operates it, and where the export lands when that contract ends.
Whether a hold is active, and what opened it. The proceeding, its docket or incident number, and the date the hold attached. 18 CFR 125.2(l) attaches on the existence of a proceeding, so the date the utility learned of it is worth a field of its own.
On one span that reads:
Pole 4118, 12 kV, detailed inspection April 9, 2026, GO 165 Section III.C, hold to April 9, 2036.
Rule 35 nonconformance, Level 2, Tier 2, corrective action completed February 20, 2027, GO 95 Rule 18A(1)(b), hold to February 20, 2037.
Vegetation data of record in the contractor's system, export received March 4, 2027, no litigation hold.
Every date there is computed from a cited rule, and they fall on different days.
The Needles audit also recorded field violations: corroded transformers, a damaged ground moulding, High Voltage signs missing or damaged on twenty poles. A crew fixes those in a morning and the finding closes. The records findings close differently, because the years they cover have already gone by, and under Rule 18A(1)(b) and Section III.C the absence is itself the violation.
Further reading
Documenting clearance work so it survives an audit: What each artifact has to contain before the retention period is worth anything.
GO 165 inspection cycles, and the one thing they do not cover: The inspection duty the ten year and life of the pole clocks are attached to.
NERC FAC-003-5: what the transmission vegetation standard requires: The three calendar year federal clock, and the requirements it runs under.
Frequently asked questions
How long does a California utility have to keep vegetation clearance records?
It depends which record. GO 95 Rule 18A(1)(b) requires corrective action records to be preserved for at least ten years. GO 165 Section III.C requires at least ten years of patrol and detailed inspection records, and records of intrusive pole inspections for the life of the pole. On an applicable transmission line, FAC-003-5 requires three calendar years of evidence for most of its requirements. The Public Resources Code and 14 CCR sections 1250 to 1258 set no period, because they require no record of the work.
When does the ten year clock under GO 95 Rule 18 start?
On completion of the corrective action. Rule 18A(1)(b) opens with the words "Upon completion of the corrective action," and the preservation sentence follows in the same paragraph. A Level 2 nonconformance identified in March 2026 and corrected in February 2027 produces a corrective action record reachable into 2037. The inspection record that found it runs on GO 165's separate clock, which starts on a different day.
Does the vegetation contractor have to keep the records?
No rule in the California stack says so. Rule 18A(1)(b) names "the company's records." GO 165 Section III.C says "The utility shall maintain records." FAC-003-5 says the applicable Transmission Owner and applicable Generator Owner retain the evidence. A contractor's field application sits outside all three, and outside Public Utilities Code section 314. The contract is the instrument that moves the data, and it has to say so before the contract ends.
Can a utility destroy a vegetation record once ten years have passed?
GO 95 and GO 165 both say "at least," which sets a floor and leaves destruction to the company. Two other clauses interfere. 18 CFR 125.2(l) requires a FERC public utility involved in pending litigation, complaint procedures, remanded proceedings or governmental proceedings to retain all relevant records. FAC-003-5 requires an entity found non-compliant to keep the related information until it is found compliant, or for the standard period, whichever runs longer.
Which retention rule covers a dedicated vegetation patrol record?
The order leaves it open. GO 165 defines patrol and detailed inspections, and neither of them is a vegetation inspection, so a dedicated vegetation patrol record sits outside the plain words of Section III.C. The Safety and Enforcement Division's June 25, 2025 audit of the City of Needles nonetheless recorded missing vegetation management records under a Section III.C citation. Until that is settled, the answer is whatever the utility's own auditable maintenance program under Rule 18A(2)(a) says it is.



