Who signs off on a span, and what that signature means

A utility-designated forester or authorized representative accepts a span. The signature attests that defined work is complete and compliant to the cited spec on the named unit and date, and that any defects have a corrective action with an owner and due date. A valid record links that attestation to evidence and an audit trail.

Who can accept a span

Acceptance authority is assigned in the utility’s program documents. On routine distribution vegetation work, a utility forester, vegetation program representative, or other named designee signs off that a defined unit is complete. California Energy Safety’s Independent Evaluator reported that at PacifiCorp a forester signs off work as it is complete, and that pre-inspections are reviewed during audits of completed work (2022 IE report excerpt). That is a concrete example of role-based authority on a span.

Transmission projects sometimes state stop-work and acceptance authority even more explicitly. New York transmission Environmental Management and Construction Plan narratives grant stop-work authority to inspectors and division foresters, naming the roles that can halt or accept work in the field (NY DPS EM&CP narrative example). Your program should do the same in writing, for the roles you actually use.

What the signature attests to

On Span P13421 to P13422, an acceptance line that stands up reads:

• Scope: the specific work items that were due on the unit.

• Standard: the utility spec section or rule the work was measured against.

• Result: pass, or fail with a defect class and a corrective action ID.

• Time and place: the span identifier, circuit, and the date of acceptance.

• Authority: the role that is authorized to accept and the person’s identity.

State what the signature does not do. It does not waive requirements in the governing rules, and it does not guarantee maintained clearance months later. It attests to the result on the date the signer accepted, based on the evidence in the file. The difference between time of trim evidence and maintained clearance duty is explained in time of trim clearance versus maintained clearance.

Chain of custody for the record

A span acceptance is a record that can be challenged months later. Protect it.

• Lock after sign. Acceptance should change the record state to read-only for the attested fields. Any later change creates a new version or an addendum that preserves the original content and signature.

• Name who can void and replace. Your procedure should state who may rescind an acceptance, under what conditions, and how the system records the reason and the link to the replacement.

• Keep the link to evidence. The acceptance record must point to the photos, measurements, and audit notes that support it. If evidence is added later, the audit trail must show who added it and why.

California’s WMP oversight expects utilities to operate QA and QC controls and to produce records that prove them. The 2025 Independent Evaluator report for PacifiCorp states that its aim includes verification of plan activities and control programs (2025 IE report, PacifiCorp). A clean chain of custody is part of that proof. The inspection order that many vegetation findings start under is summarized in GO 165 inspection cycles, and the one thing they do not cover.

Electronic signatures that hold up

If you accept spans electronically, build to the frameworks and the evidence a reviewer will ask for.

• ESIGN, at 15 U.S.C. chapter 96, establishes that electronic signatures and records have legal effect in interstate commerce when parties consent to use them (Electronic Signatures in Global and National Commerce Act). Most states have enacted a version of the Uniform Electronic Transactions Act, which provides a state law framework for electronic signatures and records (Uniform Electronic Transactions Act, Uniform Law Commission). Check your state’s enactment.

• An audit trail is required. Adobe describes it as a digital log of who signed, when, and where, tied to the document being signed (What is an electronic signature audit trail).

• Use tamper-evidence. OneSpan advises hashing each document and hashing the audit trail to make later alteration evident and reduce repudiation risk (E-SIGN is not enough white paper).

• Preserve the certificate. A complete certificate of evidence contains document metadata, signer identity and contact details, IP addresses where relevant, and a detailed event log (Why a Certificate of Evidence matters).

Your acceptance record should contain or reference these elements. If your work management system cannot export them with the span record, your audit will be slower and harder to defend.

What the audit trail must show for a span-level acceptance

At minimum, the audit trail linked to Span P13421 to P13422 should state:

• Document identity, including a stable hash of the accepted record.

• Signer identity and role authority.

• Date and time of signature, with time zone.

• The device or IP address used, if available.

• Any prior edits, with who, when, and what fields changed.

• Attachments added after acceptance, by whom and when.

• Any void or replace action, with reason and replacement link.

These are the events an internal reviewer or Independent Evaluator will read first. If they cannot be produced, the signature is only a name on a screen. What a QA/QC audit checks and records on the span itself is described in what a QA/QC audit actually covers.

Conformed signatures, delegation, and stop-work authority

A conformed signature using the /s/ notation can be acceptable in workflows that rely on document management systems, provided the document is access controlled and the audit trail identifies the signer, time, and content signed. If you use delegation, the record has to say so. Write “Signed for Jane Smith, Utility Forester, by Alex Lee under Delegation 2026-04-17,” and attach the delegation memo.

Field authority should be just as clear. If inspectors or utility foresters have stop-work authority on vegetation tasks, state that in the program document and on the form. New York transmission EM&CP narratives are an example where inspectors and division foresters are explicitly granted stop-work authority (NY DPS EM&CP narrative example). Use that level of clarity in your own jurisdiction.

Linking the signature to its evidence

An acceptance without evidence is a claim. Link it.

• Photos. At least one photo per work item or per finding closed, labeled with span ID and timestamp. If a clearance distance is asserted, show the measurement method in the frame.

• Timestamps. Acceptance date and time, and the trim or correction date and time. If the acceptance relies on a corrective action, the CAPA ID and closure date belong on the acceptance record.

• IDs. The circuit, span, work order, and CAPA identifiers must carry through the acceptance and into any later reporting.

The audit evidence set and defect classes your auditors use are laid out in what a QA/QC audit actually covers.

How refusals, exemptions, and exceptions are attested

When acceptance relies on an exception or an exemption, the signature must point to the artifacts that make the exception valid and must be issued by a role authorized to attest those conditions.

• Name the rule and the exception, for example “GO 95 Rule 35, Exception 2, current refusal.”

• Attach the two artifacts the exception requires and date them. The refusal evidence requirements and limits are detailed in landowner refusal, the two artifacts Exception 2 requires, and its limits.

• If a utility spec creates an exemption or modified practice for covered conductor or specific equipment, cite that spec section in the acceptance and attach the evidence that the condition was met on the acceptance date.

Acceptance is a statement that, on the span and date named, the work was completed to the cited spec or exception, and anything left open is under control with a corrective action, owner, and due date. That is the level of precision a reviewer expects to see in the file.

Further reading

• What a QA/QC audit actually covers: Define the auditable unit, the evidence to collect, and how findings are graded and routed into corrective action.

• Sampling versus a full census, and when each is defensible: Choose a sample plan and acceptance rules you can defend, and know when 100 percent inspection is required.

Frequently asked questions

Who is authorized to sign off completed vegetation work on a span?

Utilities typically delegate acceptance to a utility forester or similar role. An example on the record is PacifiCorp, where a forester signs off work as it is complete, with pre-inspections reviewed during audits of completed work, as noted by California Energy Safety’s Independent Evaluator.

What does the signature legally attest to?

It attests that the defined scope on the named unit was completed to the cited utility spec, that any nonconformances are recorded with a corrective action, owner, and due date, and that the signer had authority to accept. It does not waive future compliance or guarantee growth outcomes.

Are electronic signatures acceptable for span acceptance?

Yes, if your procedure allows and the system produces a tamper-evident audit trail that shows who signed, when, and on what document. ESIGN and UETA provide the legal framework for electronic signatures. Your record should include the audit log and document integrity details.

Can a sign-off be changed after the fact?

Not silently. Corrections should create a new version or addendum that preserves the original record, identifies the editor, time, reason, and links to new evidence. The audit trail must show the sequence of events. Void-and-replace requires authority at the level your procedure states.

How are refusals, exemptions, or exceptions documented in the signature record?

Reference the specific rule and exception, attach the required artifacts, and have an authorized person attest that the conditions were met. For California Rule 35 Exception 2, see how refusal evidence is built in the guide to landowner refusal and its limits.