Who audits whom: independence when the QA/QC provider also fields crews

No California rule names the employer of the person grading a span. Public Utilities Code section 8386.3(b)(2)(B) puts one independent layer above the program, engaged by the utility and directed by Energy Safety. Below that layer, independence is a contract term: a documented reporting line, an assignment rule, and a record naming the auditor.

A crew clears 14 spans on a distribution circuit on a Tuesday. On Thursday somebody walks the same 14 spans with a rangefinder and grades them pass or fail. This page is about who that second person works for.

The question has teeth because the vegetation industry consolidated. One provider can hold the pre-inspection contract, the trim contract and the quality contract on the same circuit, and in many programs one does. A utility buying QA/QC then needs an answer to a plain question from its regulator: who audited whom, and what stopped the auditor from protecting their own company's invoice.

What the audit covers once the auditor is on the span belongs to what a QA/QC audit actually covers. What follows is the other half: the relationship between the grader and the graded, what California requires of it, and what the record has to carry so that somebody reading it a year later can tell.

Four roles stand over one span, and two of them can share an employer

Every completed span has four roles attached to it. Somebody wrote the prescription, somebody made the cuts, somebody graded the work against the prescription, and somebody graded the program that produced both. PG&E names three of the four in two lines of a published standard. SW-0003, the quality control standard for routine electric distribution, publication date May 31, 2024, opens this way:

Stakeholders All Quality Control (QC) Specialist personnel of the Quality Management teams. Scope Distribution Routine VM locations in High Fire Threat District (HFTD) that have been completed by the VM Inspector (VMI), and tree crews (TC) as documented in the system of record.

The graded parties are named in the scope. The grading party is named in the stakeholders, and it is a different organization: a Quality Management team, whose document owner line reads "Director, Quality Control Vegetation Management" and whose approval clause reads "Approval from QC leadership is required." The separation is structural before it is procedural. Impartiality goes unmentioned because the org chart has already settled it.

Role	What it produces	Who commonly holds it
Pre-inspector	The prescription for the span	Contractor, sometimes a separate consulting firm
Crew	The cuts, the debris, the completion record	Line clearance contractor
Quality control	A pass or fail on the completed span	Utility quality team, or a contractor
Quality assurance	A grade on the program and its records	Utility QA organization, or a contractor

Two of those rows collapsing into one employer is the ordinary case, not the exception. The prescription and the cuts routinely share one. So can the cuts and the pass or fail.

California leaves the grader's employer to the contract

Read General Order 95, General Order 165 and Public Resources Code section 4293 looking for the employer of the person who grades a span, and you will come away empty. Those rules bind the electrical corporation and the person doing the work.

The state's audit reach follows the work outward from the corporation rather than naming the contractor: Public Utilities Code section 8386.3(b)(5)(A) lets Energy Safety "conduct audits of the vegetation management work performed by, or on behalf of, the electrical corporation." Performed on behalf of. Accountability stays with the corporation when the work moves outward.

PG&E's own published quality standards are silent on the same point. SW-0003, SW-0006, SW-0038 and SW-0045 define the auditing role by team and by title, and stop there. In PG&E's structure the auditor is a PG&E employee and the crew works for a contractor, so the org chart answers the question before the standard has to.

So the answer to "may a provider grade the work of its own crews" is that California leaves it open, and the decision belongs to the utility. It gets made twice, in two documents:

• In the wildfire mitigation plan, where the QA/QC commitment becomes something the state can audit.

• In the contract, where independence becomes a term somebody can be held to, or stays a word in a bid.

Where the program itself is what the state is auditing, the choice surfaces in a filing. Energy Safety issued its report on Liberty Utilities' 2023 Substantial Vegetation Management audit on June 26, 2025, and the quality assurance and quality control initiative was one of the 13 it graded. Liberty substantially complied on 12 of the 13.

The one auditor the statute does define, and who directs it

California writes down exactly one independence requirement for wildfire mitigation work, and it sits above the whole program rather than over any span. Public Utilities Code section 8386.3(b)(2)(B)(i):

Each electrical corporation shall engage an independent evaluator listed pursuant to subparagraph (A) to review and assess the electrical corporation's implementation of its approved plan. The engaged independent evaluator shall consult with, and operate under the direction of, the office. The independent evaluator shall issue a report on or before July 1 of each year in which a report required by paragraph (1) is filed.

Four mechanics hold that arrangement together, and each one is worth stealing for a QA contract:

• The pool belongs to the state. Subparagraph (A) requires Energy Safety to publish a list of qualified independent evaluators on or before March 1 each year, and the corporation engages from that list.

• Direction is separated from payment. The evaluator operates under the direction of the office. Under subdivision (b)(3), the commission authorizes the corporation to "recover in rates the costs of the independent evaluator," so the audited party pays and the regulator steers.

• The deliverable has a date, and the statute sets it. The report is due July 1.

• The office keeps the last word. Subdivision (b)(2)(B)(ii) says it considers the findings, but that they "are not binding on the office."

The evaluator is itself a contractor. PacifiCorp's is named on the title page of its report: NV5, Inc. and Guidehouse Inc. A commercial relationship exists between the evaluator and the utility it evaluates. The four mechanics above are what carry the independence instead.

The utility's own account of its year sits beside it. Subdivision (b)(1) requires a self-evaluation report each April 1 covering the prior calendar year. Two documents, ten weeks apart, describing the same work. That pairing is the model a QA contract should reproduce at the span level.

The evaluator reads the name on the audit form

Independence reaches the paperwork as a name, and the name gets read. In the 2025 independent evaluator report on PacifiCorp, vegetation post-audits are described at page 73 as "completed annually, primarily by PacifiCorp internal staff." The evaluator then went and checked the forms.

PacifiCorp committed to post-auditing 417 line-miles of transmission patrol inspections and 1,182 line-miles of distribution patrol inspections in 2025. To verify it, the evaluator asked for the underlying documents and received forester audit forms for each of the 11 transmission lines and each of the 42 distribution circuits. Page 74 records what it looked for:

The IE reviewed each of these forester audit forms to verify that it audited the correct type of vegetation work ("FMT"), that it covered all the line-miles reported for the line in the tracking document, that it was completed in 2025, and that it was signed.

Three of the 42 distribution forms carried a distance that was missing, or one that conflicted with the tracker. The evaluator read the form's note of a 100 percent review, concluded the discrepancies were clerical, and validated both initiatives at an implementation verification rate of 100 percent.

The earlier report is blunter about what the reviewer is looking for. The 2022 report, at page 55, records that most of PacifiCorp's QA/QC "occurs in real time with the project lead or Forester signing off work as it is complete," and then says what the evidence established:

A review of PacifiCorp's 2022 VM Audit Exception Report and associated evidence which was reviewed as part of the VM-13 and VM-3 verification, confirms that these audits are being performed and by whom.

And by whom. A signature that identifies a person and their organization is the whole of what a third party can test a year later. What that signature attests to, and what has to sit behind it, is who signs off on a span.

Lines of accountability are a scored dimension

The state's evaluator goes past whether the audits happened. It scores how the audit function is organized, on a zero to four ladder across five dimensions. The interval question and the framework itself belong to monthly audits reviewed with the crew the next day. The first dimension on the ladder is the subject of this page: roles and responsibilities.

PacifiCorp scored a 1 on it in the 2025 report, at page 126:

Roles & Responsibilities Rating = 1 Initiated PacifiCorp staff have some awareness of QA/QC tasks, basic definitions of roles exist, and semi-formal communication channels exist. This remains unchanged from the 2024 IE review.

Two years at the same rating, on a five-point scale, for the question of who is responsible for what. The recommendation at page 131 names the remedy in the vocabulary a contract can use: "Formally document and define QA/QC program roles, responsibilities, and lines of accountability across the Wildfire Mitigation Plan (WMP)."

The ladder is also candid about the failure mode. On the quality culture dimension, the level 1 descriptor reads, in part, "Main quality issues are known, but fear of reporting failures to supervisors/managers." That is the independence problem written as a maturity level. Dishonesty is beside the point. An auditor who reports into the organization that produced the work pays a cost for raising a finding, and the cost falls on one side only. A rate drifts from there.

Two tiers, and the half of the sample that overlaps

The design that answers this is a second pass by someone else over spans the first pass already graded. PacifiCorp runs it on the asset inspection side, and the 2025 report sets out the arithmetic at page 123:

Tier 1 requires contractors to QA/QC audit a minimum of 5% of the total poles scheduled by PacifiCorp for the calendar year. The audits are performed on a computer-generated random 5% sample chosen within a completed section and performed on a weekly basis. Tier 2 of the process is run by PacifiCorp staff, which reviews an additional 2-3% of inspections on top of the 5% performed in Tier 1. Approximately half of the audit sample is derived from those reviewed in Tier 1 and half are randomly chosen.

The deliberate part is the overlap. Half of the utility's sample is a re-read of poles the contractor's own auditor has already passed, which produces a number nobody can get any other way.

Take a program of 60,000 poles scheduled for the year. Tier 1 audits 3,000 of them. Tier 2 at 3 percent audits 1,800, of which roughly 900 are re-reads of Tier 1 poles. Suppose the contractor passed 890 of those 900, and the utility's reviewer fails 45 of the same 900.

The 45 belong to the first auditor rather than to the crews: on 5 percent of the poles both parties looked at, the two graders disagreed. A program that samples without overlap reports a pass rate for years and leaves that figure unmeasured.

Three things make the overlap number usable rather than decorative:

• The re-read has to be blind. The second reviewer's form shows the first reviewer's call only after the second call is recorded.

• The disagreement rate gets reported as its own figure, separate from the crew pass rate, with its denominator.

• Disagreements get adjudicated by a named person, and the adjudication feeds rater calibration rather than a memo.

Two cautions on copying it. PacifiCorp's two-tier design belongs to its overhead asset inspection program, and the same report found the vegetation QA/QC documentation short of equivalent procedures. And the sample sizes above are illustrative arithmetic on a round number of poles. How to draw a defensible sample, and how large it has to be, is sampling versus a full census.

The finding that lowers your employer's invoice

Here is where the conflict stops being theoretical and starts being money. The 2025 report describes at page 125 how PacifiCorp's vegetation pass rate is computed:

The pass rate was calculated by identifying the number of locations identified where vegetation maintenance was needed and the number of locations where a non-billable audit exception was found.

Non-billable. An exception is a quality record and an unpaid line on an invoice at the same time. Where the auditor and the crew share an employer, every exception the auditor writes reduces their own company's revenue. That is an uncomfortable place to put a person, and a contract resting on professional integrity alone leaves them standing in it.

Three controls make it survivable, and all three belong in the contract rather than in a policy statement:

• The billability decision is the utility's. The auditor records the exception; a utility representative sets what is payable. The two acts are recorded separately and by different people.

• The exception record names the auditor and the auditor's employer on every finding, routine ones included.

• A disputed exception goes to a named utility forester, and the outcome of the dispute is recorded against the original finding rather than replacing it.

What happens to the failed unit after that is rework, and the closure the exception eventually receives is unit closed properly.

Grades of independence, already named in a standard

The vocabulary for all of this exists, and it comes from outside vegetation work. ISO/IEC 17020 grades bodies that perform inspection by how far they sit from the work they inspect. The 2012 edition sorts them into three types, which map onto the vegetation question directly. The text below is as printed in the International Accreditation Service course handbook for the standard, published by a US accreditation body in Brea, California.

Type	What it is	What Annex A requires of it
A	Third party, independent of the parties involved	Shall not be engaged in the design, manufacture, supply, installation, purchase, ownership, use or maintenance of the items inspected, and shall not be part of a legal entity that is
B	A separate, identifiable part of the organization that does the work, inspecting only for its own parent	Clear separation of inspection responsibilities from other functions, established by organizational identification and reporting methods
C	An identifiable part of the organization that does the work, which may also inspect for others	Safeguards segregating inspection from other activities, and no single person doing both on the same item

A vegetation QA provider that also fields crews is a Type C body. The standard treats that as a classification rather than a disqualification: it decides which requirements apply, and Annex A.3 states them:

a) The inspection body shall provide safeguards within the organization to ensure adequate segregation of responsibilities and accountabilities between inspection and other activities. b) The design/manufacture/supply/installation/servicing/maintenance and the inspection of the same item carried out by a Type C inspection body shall not be undertaken by the same person.

The same item. The test runs at the level of the thing inspected rather than the contract, the circuit or the customer: one span, one person, one role.

The Type A requirements repay reading in a program that will only ever buy Type C, because of what they treat as a linkage. Annex A.1(d) lists ways a body can be linked to an entity that does the work, and item 3 is "directly reporting to the same higher level of management."

A QA team and a production team inside one company are independent of each other up to the level where their reporting lines meet. The question a utility should ask on a bid is how far up that is, and the answer is a name and a title.

Two practical notes on citing the standard. Accreditation to ISO/IEC 17020 is voluntary in vegetation work, so what the standard offers a contract is language rather than an obligation. And ISO published a 2026 edition, so a clause that says "Type A" has to say which edition it means, the same discipline the contract already owes every standard it names in ANSI standards met.

Five ways a related party moves a result

The interpretation the handbook prints alongside Annex A is more specific than the standard, and it is the most directly usable paragraph in the whole document. A linked person can influence the outcome of an inspection if that person can do any of the following:

• Influence the selection of inspectors for specific assignments or customers.

• Influence decisions on conformity in specific inspection assignments.

• Influence remuneration for individual inspectors.

• Influence remuneration for specific assignments or customers.

• Initiate the use of alternative work practices for specific assignments.

Those five convert into five contract questions with checkable answers. Who assigns auditors to circuits, and can an operations manager request or refuse one. Who can overturn a fail. Who sets the auditor's pay and bonus, and on what basis. Who prices the audit work itself. Who can authorize a departure from the audit procedure on a particular job.

The pay question has its own clause. Clause 6.1.11 of the 2012 edition reads: "The personnel involved in inspection activities shall not be remunerated in a way that influences the results of inspections." The obvious version is a bonus tied to the pass rate. The less obvious one is a per-location rate, which pays for speed rather than for findings, and the handbook flags exactly that: remuneration methods that reward inspecting quickly can degrade the outcome.

What the audit over your transmission program already requires

The electric industry has written this rule down once, for a different audit. NERC's Appendix 4C to the Rules of Procedure, effective May 19, 2022, governs compliance audits of registered entities. Section 4.1.4.2 sets the requirements for team members:

Be free of conflicts of interests in accordance with the CEA policies. Employees or contractors of the Registered Entity being audited shall not be allowed to participate as auditors in the Compliance Audit of the Registered Entity.

Employees or contractors. The bar covers both, which is the distinction a vegetation contract usually leaves out.

Three more mechanics sit around it, and each is a clause a utility can lift:

• Advance disclosure of the team. At least 90 days before a scheduled audit, the compliance enforcement authority "identifies the Compliance Audit team members and their recent employment history."

• A right to object. Under section 4.1.4.4, the audited entity "may object to any member of the Compliance Audit team on grounds of a conflict of interest," in writing, no later than 30 days before the start.

• A staff team leader. Contractors and industry subject matter experts may serve on the team, but section 4.1.4.1 requires that the leader be a staff member of the authority, responsible for the conduct of the audit and for the report.

This governs a regional entity auditing a utility, and it reaches transmission compliance rather than distribution trim quality. It is cited here because the shape is right and it is domestic, published and already familiar to anyone who works under FAC-003. A QA contract that discloses its auditors and their recent employment, lets the audited party object on conflict grounds, and requires the audit lead to be a utility employee has borrowed a structure the industry already defends in front of a federal regulator.

One company, both contracts: disclose at bid, exclude at assignment

When the provider that grades the work also fields crews, independence is bought in two moments, and both of them happen before anybody reaches the field.

At bid, the utility should get the relationship in writing:

What to require	What a sufficient answer looks like
Corporate relationship	Which legal entities hold the trim contract and the QA contract, and their common parent
Reporting line	The title of the lowest-level manager to whom both the QA lead and the operations lead report
Pay basis for auditors	Salary or per-unit, and every variable component with its trigger
Prior role disclosure	Whether proposed auditors have worked as pre-inspectors, foremen or supervisors on the circuits in scope, and when
Objection procedure	How the utility removes a named auditor, and within how long

At assignment, the control is an exclusion rule enforced by the work management system rather than by a memo. The system withholds a span from any auditor who pre-inspected it, worked it, supervised it, or accepted it. It already knows all four facts, because all four are in the record.

PG&E's transmission audit standard shows how prosaic this looks once it is a control rather than a principle. SW-0045 names the audit lead as responsible for the sample and requires them to ensure "that no audit locations have been reviewed in duplicate." That is one assignment rule, enforced with a tracker. A prior-role exclusion is the same kind of object with a different join.

The routing of a finding is the other half. SW-0038 puts the corrective action on the organization that did the work rather than on the auditor who found it.

Its purpose is documenting actions "to be taken by Vegetation Management (VM) Execution due to findings from QAVM-Asset audits," and the audit report has to be approved by the Quality Assurance Manager before the corrective action is opened. Three people touch one finding: the auditor who writes it, the quality manager who approves the report, and the execution organization that owns the fix. The cycle closes only once all three have acted.

One more source of obligation applies to a subset of programs. A publicly owned utility spending a federal award on vegetation work is a recipient under the Uniform Guidance, and 2 CFR 200.318(c)(2) requires written standards of conduct on organizational conflicts of interest:

Organizational conflicts of interest mean that because of relationships with a parent company, affiliate, or subsidiary organization, the recipient or subrecipient is unable or appears to be unable to be impartial in conducting a procurement action involving a related organization.

Read the scope carefully before relying on it. The rule reaches the procurement action, meaning the decision to award the QA contract. Its reach stops short of the grade an auditor writes on a span three months later.

Whether it reaches a given utility at all depends on the award and on the awarding agency's terms, so read those first. It is worth naming because where it does apply, "appears to be unable to be impartial" is already the legal test, and an undisclosed common parent fails it before anybody looks at a grade.

What the record has to name

A defensible audit record answers the independence question before anybody asks it. Every graded span should carry these fields, populated at the time of the grade rather than reconstructed:

Field	Why it is there
Auditor name and identifier	The evaluator's review confirms that audits are performed "and by whom"
Auditor's employer	Independence is a property of the organization before it is a property of the person
Reporting line at the time of the grade	The linkage test in Annex A.1(d) is about shared management, not shared badges
Assignment method and date	Shows the auditor did not choose the span
Prior-role check result	Records that the exclusion rule ran and what it returned
Pay basis flag	Distinguishes a salaried grade from a per-unit one
Re-audit status	Whether this span was in the overlap sample, and what the second reader called
Dispute outcome, if any	Names who adjudicated and preserves the original finding

Six of the eight already sit in most work management systems as separate facts. What is usually missing is the write-through onto the audit record at the moment of the grade. A reviewer a year later gets a signature and a date, and takes the rest on trust.

The standard to hold this to is the one the state's evaluator applied to 53 forester audit forms: correct work type, correct extent, correct year, and signed. An audit record that also names who the signer works for, and what kept them off their own crew's spans, answers the harder question before it is put.

Further reading

• What a QA/QC audit actually covers in utility vegetation work: The unit under audit, the defect classes, and how two raters are brought to the same call.

• Who signs off on a span: What the acceptance signature attests to, and the audit trail behind it.

• Monthly audits, reviewed with the crew the next day: Who sets the audit interval, and the five-dimension framework the state's evaluator grades it on.

Frequently asked questions

Is it legal for the same company to trim the spans and run the QA/QC audit?

Yes. No California electric safety rule names the employer of the person grading a completed span. General Order 95, General Order 165 and the Public Resources Code bind the electrical corporation, and Public Utilities Code section 8386.3(b)(5)(A) lets Energy Safety audit vegetation work performed by or on behalf of that corporation. The corporation stays accountable whoever holds the pencil, so the restriction, if there is one, comes from the contract.

Where does California actually require an independent reviewer?

At the program level. Section 8386.3(b)(2)(B)(i) requires each electrical corporation to engage an independent evaluator from a list Energy Safety publishes by March 1 each year, and requires that the evaluator consult with and operate under the direction of the office. The evaluator reports by July 1. Under subdivision (b)(3), the utility recovers the evaluator's cost in rates, so the audited party pays and the state directs.

What does an independence problem look like in a QA record?

An auditor grading a span their own organization pre-inspected, trimmed, supervised or already accepted. In PacifiCorp's program the pass rate is calculated from locations where a non-billable audit exception was found, which means every exception reduces somebody's invoice. Where the auditor and the crew share an employer, the finding costs the auditor's own company money, and the record needs to show who decided it anyway.

Is there a published standard that grades how independent an inspection body is?

ISO/IEC 17020 does, and the 2012 edition sorts inspection bodies into types A, B and C. A Type C body may inspect items it also installs or maintains, subject to Annex A.3, which requires safeguards segregating inspection from other activities and forbids the same person from doing both on the same item. No California rule requires a vegetation QA provider to be accredited to it. ISO published a new edition of 17020 in 2026, so a contract clause has to name the edition it means.

What does the electric industry already require of an audit team's independence?

For compliance audits of registered entities, NERC's Rules of Procedure Appendix 4C states that employees or contractors of the registered entity being audited shall not participate as auditors in that audit. The compliance enforcement authority must also disclose team members and their recent employment history at least 90 days ahead, and the entity may object to a member on conflict-of-interest grounds. That governs the regional entity's audit of the utility, not the utility's vegetation contract, but the four mechanics transfer into one.