Utility Vegetation Management Data for Targeted Trimming in 2026

A 2026 distribution work plan filed in Kentucky projects $20,848,248 for 1,646.14 planned miles of cycle maintenance. Dividing the expense by the planned mileage gives $12,664.93 per mile in operating and maintenance expense. Attachment 2 of the April 2026 filing separately lists $1,042,412 in clearing-related capital, bringing that table’s total to $21,890,660.

A faster trimming cycle can carry a higher mileage rate. A Texas filing for a 2026 to 2028 resiliency plan estimates about $11,859 per mile for 35 kV circuits and $21,855 for 12 kV circuits in narrow easements over that three-year period. It describes accelerating a five-year cycle to three years. These figures price different scopes and periods; they do not establish savings from condition-based trimming.

I would use those records to challenge a flat mileage allowance. The purchasing question is which spans need attention, what the crew must do there, and how much time access will consume. A wooded creek crossing deserves its own estimate.

Asset Search by PorchRocket finds visible vegetation near lines and returns reviewed locations with dated evidence and parcel context. Utility vegetation managers and qualified contractors can use that inventory to direct inspections and prepare work, from one service area to a program across the contiguous United States.

Which lines fall under NERC FAC-003 in 2026?

NERC FAC-003-5 covers specified overhead transmission facilities; ordinary distribution feeders need their own applicable state rules and utility requirements.

As of November 2026, NERC lists FAC-003-5 among its mandatory FAC reliability standards. Its applicability includes overhead transmission operated at 200 kV or higher and certain designated lower-voltage lines. Generator-owned facilities have additional applicability conditions. Ask the utility for its applicable-facility register before building a transmission line vegetation mapping scope.

Under FAC-003-5, requirement R6 calls for inspection of all applicable lines at least once each calendar year, with no more than 18 calendar months between inspections on the same right of way. R7 requires completion of the annual vegetation work plan; changes must be documented and must prevent encroachment into the minimum clearance. A targeted review needs to fit inside those obligations.

The standard’s Minimum Vegetation Clearance Distance, or MVCD, is a flashover clearance floor. Maintenance planning must account for conductor movement and vegetation growth. A map buffer drawn around a centerline does not establish that clearance.

Put the rule reference and version beside each circuit identifier, with the utility contact who resolves disputed classifications. The screening rule tells the reviewer which locations to flag. The treatment specification tells an authorized crew what work the utility has approved.

If two circuits share a corridor, hold ambiguous matches for utility review until the identifiers establish which rule applies to each line. The asset inventory guide explains how to connect an observed feature to a durable asset record.

State wildfire plans need their own work queue

California’s 2026 municipal and cooperative planning schedule illustrates why vegetation records need a jurisdiction field alongside the circuit and observation date.

Public Utilities Code section 8387 changed in September 2025. After January 1, 2026, publicly owned utilities and electrical cooperatives submit wildfire mitigation plans at least once every four years on the advisory board’s schedule. The San Francisco Public Utilities Commission explains the amendment, and the state’s revised schedule adopted March 4, 2026 assigns submission years. Check the utility’s row rather than adding four years to its last filing date.

Keep the dates separate. The plan submission calendar does not set a four-year vegetation inspection interval. Assign an employee to the administrative deadline and carry field obligations in the operating schedule.

California also has location-dependent clearance requirements. CAL FIRE’s utility guidance explains that Public Resources Code sections 4292 and 4293 must be read with related sections, regulations and exceptions. Avoid copying one distance from a summary into every California corridor record.

Ask the utility’s vegetation manager which geographic overlays and treatment priorities from its approved wildfire plan belong on the map. Describe what the image shows. The utility supplies the consequence assessment.

Give each obligation a place in the work queue: action, responsible employee, due date and closure evidence. If a local requirement changes, preserve the previous rule and mark the records that need another decision. Asset Search can re-answer previously searched sites against a changed requirement, often using evidence already collected. The utility can then identify which findings need fresh field information.

Cycle trimming vs condition-based vegetation management

A hybrid program keeps required cycle work scheduled while using current observations to direct supplemental inspections and treatment between those visits.

Cycle work gives the planner a recurring coverage commitment. Condition-based work starts with an observed issue and a decision about when it needs attention. I would use both calendars, joined by the same circuit identifiers, so a supplemental job does not disappear from the next cycle estimate.

The distinction appears in current public records. A May 2026 Florida Public Service Commission audit describes transmission vegetation scheduling based on threats and conditions. Its workflow includes field inspections and annual planning, with field quality checks after treatment. That separates inspection findings used to scope work from evidence that a contractor finished the approved work.

Planning approach	Trigger for the work	Record I would require	Cost question to answer
Cycle maintenance	The circuit reaches its scheduled treatment period	Last treatment, next due date and approved scope	What is included in each treated mile?
Condition-based review	A new observation crosses the utility’s screening threshold	Dated finding and the inspection needed next	How many dispatches will resolve the flagged locations?
Required corrective work	The utility identifies an obligation needing action	Responsible operator, instruction and closure record	Which resources and access arrangements are needed now?
Integrated vegetation management	The site needs a longer-term treatment strategy	Desired vegetation, treatment decision and follow-up	What repeat work will this method require?

The EPA’s integrated vegetation management guidance describes site-specific assessment and treatment, followed by evaluation and maintenance. It includes promoting compatible low-growing vegetation. That gives a planner a reason to record the desired condition, rather than labeling every green patch as a cutting job.

For the first change to an established program, I would keep approved cycle commitments in place and test the imagery on supplemental scouting, where inspectors can compare its findings with their field observations before the utility commits to a larger territory. Record the result by location. If the review merely redistributes the same driving into smaller visits, revise the routing before expanding it.

Compare both methods over the same period. Include scouting and mobilization, plus traffic arrangements and follow-up visits. The Kentucky filing flags its overall spending recap in Attachment 4 as prepared before the commission’s February 28, 2026 order. Use its tables to understand cost categories, then check the buyer’s current budget and treatment specification before estimating a new contract.

What should utility vegetation management data contain?

A usable utility worklist links each finding to a stable span or circuit identifier, its dated evidence and one clearly assigned next action.

Start with the utility’s line layer where it is available. Ask whether the supplied geometry represents the route, individual circuits or another asset class. Keep the original identifier in the delivery. A renamed export should still join back to the source without somebody matching rows by eye.

I would specify these fields before buying a territory search:

Field group	What belongs in the record	Decision it supports
Location and asset identity	Coordinates, parcel, circuit ID and span endpoints where supplied	Assign the finding to the correct utility asset
Evidence	Capture date, reviewed view and observation description	Decide whether the information is recent enough for the task
Vegetation observation	Canopy beside or apparently over the mapped route; visible corridor change	Select locations for closer examination
Review result	Fits, rejects with reason, or unresolved with one settling field check	Separate supported findings from remaining questions
Access observations	Visible approach, gate location, road or water crossing	Plan an access survey and initial equipment needs
Property context	Parcel and owner information; contact where applicable	Start the utility’s access and notification process
Utility-supplied requirements	Applicable rule, work priority and due date	Place the finding in the authorized program
Field outcome	Inspector’s determination, approved scope and closure evidence	Feed the next planning edition with verified information

Asset Search sets the search rules with the buyer’s experts and reviews every candidate before delivery. It returns all dispositions. Keep rejected locations in your inventory with their reasons, so the next analyst does not spend another morning asking the same question.

Write the acceptance rule in ordinary words: flag canopy overlapping the agreed screening corridor in the dated view, or a newly obstructed approach. If reviewers cannot settle the classification from the evidence, return it as unresolved with the question a field visit must answer. A decimal score cannot replace missing evidence.

For programs that also cover station boundaries, connect the vegetation file to the substation and transformer inventory. Keep the line-span observations separate from station-site observations. Each can retain its own work instruction while sharing the appropriate location and utility references.

What can imagery show, and when is lidar needed?

Overhead imagery supports screening for visible canopy and access changes; three-dimensional clearance decisions require evidence suited to measuring vegetation against conductors.

The February 2026 national laboratory review distinguishes satellite coverage over broad areas from aerial imagery suited to more detailed, targeted investigations. Resolution and collection timing matter, as do atmospheric conditions. Request a view of your territory. Check whether the feature you need to assess is visible in that view.

For an imagery screen, ask for observations such as canopy apparently extending across the mapped route, vegetation bordering a cleared corridor, or a visible approach interrupted by new growth. Have the utility define the screening corridor. Do not label that outline as an easement boundary unless the supplied records establish it.

Flag an overhead overlap for inspection. It does not tell you the vertical distance from a branch to a conductor. Have the responsible engineer specify the measurement method and accuracy before ordering a clearance survey, including how to represent conductor and vegetation geometry under the required operating conditions.

The USGS explanation of lidar and elevation models makes another distinction: lidar point clouds represent objects in three dimensions, while bare-earth elevation models exclude vegetation and buildings. A terrain layer by itself cannot supply the tree geometry you need. Have a qualified survey or engineering team assess whether a proposed dataset captures the relevant conductors and vegetation.

I would keep a short evidence ladder in the specification: imagery observation, field confirmation, measured clearance where required, then the utility’s treatment decision. Record the date at each stage. That prevents a newer office review date from making an older image look freshly captured.

Use the satellite versus aerial imagery guide to frame coverage choices, then test difficult examples from your territory. Include canopy-covered lines and shadows in the pilot. A clean view of an open corridor will not tell you how the review handles the places your inspectors struggle to see.

Access and difficult crossings belong in the estimate

A vegetation record should show the visible approach and crossing constraints before an estimator assigns a crew type or production rate.

I would ask for an access observation on every location selected for field review. Mark the apparent entrance and the last visible connection to a road. Identify a gate if it can be seen, then assign somebody to confirm permission and the usable route. A parcel owner record starts that conversation; it does not grant entry.

Imagery can prompt a check for a creek crossing or a narrow approach. Have the field team establish whether its equipment can use that route under expected job conditions. Put the finding beside the equipment assumption in the estimate. Confirm the route before dispatch.

For a difficult span, I would ask the estimator to record four allowances: access preparation, crew mobilization, work at the span and restoration or cleanup. Put traffic arrangements in their own line item when the scope requires them. Otherwise, the next estimator cannot tell which part of the mileage rate paid for the crossing.

Personnel qualification belongs in the same preparation. OSHA’s 29 CFR 1910.269 establishes application, training and job-briefing requirements for covered utility line-clearance work. Its requirements distinguish qualified employees from other line-clearance tree trimmers. Assign the work through the utility’s procedures and the employer’s applicable safety program.

A general tree-service prospect and a utility line-clearance assignment need different qualification checks. The tree-service prospecting guide covers the broader sales task. For this work, ask the buyer about personnel qualifications and equipment documentation. Get its operating coordination requirements before offering a cutting price.

Finally, route the work from verified entrances. Two pins close together on a map may still belong to different access plans. The route-density calculator can help test travel assumptions once the crew’s permitted route is known.

Rank the next inspection before releasing cutting work

The utility should assign priority using its operating information, then give each flagged location a responsible reviewer and a deadline for the next decision.

I would avoid a single blended score that lets convenient access cancel out an urgent finding. Record the observed condition separately from the utility’s consequence assessment. Add the effort needed to inspect it. Planners can then group visits within a priority band without losing the original reason for urgency.

An escalation instruction needs to be settled before the search starts. Ask the utility who receives a potentially urgent observation, how that person acknowledges it and what the reviewer should do if acknowledgment does not arrive. Keep those contacts with the project instructions. Do not let a location needing prompt attention wait for the next batch export.

For routine candidates, use a short decision queue. One location may need confirmation of line identity; another needs a qualified field measurement. State the required result in the inspection task. The inspector should know whether to return a corrected identifier, a measurement or an access determination, and where to attach it.

Keep uncertainty separate from low priority. If the line disappears under canopy, the record should say what evidence is missing and how to obtain it. It should not quietly fall to the bottom because the reviewer could not see a problem.

I would also sample rejected locations during the pilot. Let the utility’s experts choose the sample and record whether the imagery review missed a finding that mattered under the agreed rules. Use that feedback to revise the search. Measure inspection agreement and unresolved workload alongside the count of matches; a large file alone does not establish that crews have better work instructions.

Value per mile on a 186-mile planning area

The base planning model reduces supplemental field-review expense by $23,130 across 186 route miles, before the research quote and internal review costs.

Say a municipal utility is preparing supplemental vegetation work across 186 route miles. Its required inspections and scheduled maintenance remain funded. Both planning options must support the same approved scope; assume they identify 34 work packages totaling 47 treated miles. The comparison covers preliminary field review only, with the treatment budget held constant.

The utility’s internal allowance for reviewing the entire planning area is $235 per route mile, including inspector labor, travel and recording time. The imagery-led option needs 84 field checks at $245 each: 62 flagged locations and 22 checks selected by the utility to assess screening quality. That per-visit allowance includes the same categories of expense. Research and internal desk review are additional.

Here is the arithmetic:

• Full-area supplemental review: 186 miles x $235 = $43,710.
• Directed field checks: 84 visits x $245 = $20,580.
• Difference before research and desk review: $43,710 minus $20,580 = $23,130.
• Difference per route mile: $23,130 / 186 = $124.35, rounded to cents.

The field-review difference allocates to $680.29 per approved work package: $23,130 / 34, rounded to cents. That is a value-per-find measure for this planning exercise. It measures avoided scouting expense before research costs, with cutting work priced separately. Per-mile figures in the sensitivity table are also rounded to cents.

Test the model against a heavier inspection burden. Keep the 186-mile baseline and $245 visit allowance fixed, but change the number of field checks needed to settle candidates and assess screening quality.

Review outcome	Field checks	Field-review expense	Difference from $43,710 baseline	Difference per route mile
Low benefit, more follow-up	118	$28,910	$14,800	$79.57
Base planning case	84	$20,580	$23,130	$124.35
High benefit, fewer follow-ups	66	$16,170	$27,540	$148.06

Calculate planning ROI as avoided field-review expense minus all added research and desk-review expense, divided by those added expenses. Include the office hours spent reviewing rejects and resolving uncertain findings. Leave speculative wildfire losses outside this calculation.

To finish this model, assume 26 added office hours at a loaded labor cost of $63 per hour: 26 x $63 = $1,638. Let Q be the territory research quote, with any pilot credit applied once. Base-case net savings are $23,130 minus $1,638 minus Q, or $21,492 minus Q. Planning ROI is ($21,492 minus Q) / ($1,638 plus Q). Add any separate import or travel expense to the denominator and subtract it from the numerator before using that result.

My decision rule is to expand only when the pilot meets the utility’s evidence requirements and the low-benefit case still pays for the added research and review. If field checks cost more than expected, change that input before approving another territory.

Distinguish cash from capacity. Hours freed for other inspections are valuable, but they do not reduce payroll automatically. Report avoided outside invoices separately from staff hours reassigned to other approved work. The budget owner should be able to trace each claimed saving to an expense or a documented change in workload.

What is a vegetation work package worth to a contractor?

For the 47 treated miles in this model, a $14,180 selling rate and $11,310 direct cost per mile produce $134,890 in gross profit.

Those contractor assumptions cover the specified treatment scope: direct labor and equipment, travel, cutting and disposal. They are estimating inputs for the model, separate from the public planning figures in the opening. The resulting contract revenue is 47 x $14,180 = $666,460. Direct cost is 47 x $11,310 = $531,570. Gross margin is $134,890 / $666,460, or about 20.2%, before company overhead.

Access can change that number quickly. Add $19,800 of unbudgeted crossing and mobilization expense, and gross profit falls to $115,090. Margin falls to about 17.3%. The invoice to the customer has stayed the same.

Send the estimator the difficult spans with their dated views before submitting the price. Each record should state which access question the visit must answer, allowing the estimator to change quantities or production assumptions while there is still time to include the cost in the offer the buyer will evaluate. Price the crossing explicitly.

Cost to serve means everything the company spends delivering the work, including travel between approved entrances and time waiting for access. Track those items by work package. For a separate capacity check within the model, assume 72 avoidable crew-hours at a loaded crew-and-equipment cost of $164 per hour: 72 x $164 = $11,808 of capacity. If those hours reduce the direct-cost budget, lower that budget by $11,808 once. If the crew stays on payroll and does other work, report the reassigned hours separately.

Do not value every flagged span as a signed contract. A utility program may buy the research, approve only part of the treatment scope or procure the cutting through another process. For the sales manager, the next event to track is a qualified scope discussion or authorized survey. For the estimator, it is the buyer’s accepted quantity and specification.

How to map encroachment and build a crew plan, step by step

Run an eight-step pilot through one planning area, from utility-approved search rules to field feedback, before applying the method across the territory.

1. Define the decision and the area. Pick the circuits or corridor miles for the pilot and state the decision the file must support. Supplemental inspection planning, a trimming estimate and a clearance survey require different deliverables. Supply the utility’s identifiers and record the scope’s owner. Keep mandatory inspection dates visible in the project instructions.

2. Agree on what counts. Have the utility’s vegetation specialists define the screening corridor, visible conditions to flag and rejection reasons. Include examples of ambiguous canopy and uncertain line identity. Name the person who resolves disputed classifications. Write the field check that would settle each unresolved category before review begins.

3. Request the territory in Asset Search. Use Asset Search’s vegetation request to describe the area, vegetation observations, visible access features and required file format. Ask for dated views and every disposition, joined to your supplied identifiers. Start with a paid pilot credited toward the full order and agree on its acceptance criteria.

4. Review difficult examples with the utility. Compare the pilot findings with the specialists’ expectations. Include rejected and unresolved records in this review. Test a sample import into the utility’s GIS or work-order process. Fix missing identifiers and unclear observations while the file is small enough to inspect row by row.

5. Assign the field checks. Give each selected location an authorized inspector, the specific question to settle and an appropriate due date. Record access arrangements before dispatch. Use the agreed escalation route for potentially urgent observations. Return the field determination against the same identifier so the office can reconcile it without manual guesswork.

6. Build work packages around approved access. Group field-confirmed work by the utility’s priority, equipment needs and permitted approach. Attach crossing requirements and any operating coordination supplied by the utility. Keep unresolved access separate from released work. Let the responsible supervisor approve the package before it reaches the crew schedule.

7. Price and release the defined scope. Estimate the quantities confirmed for treatment and the production rate for each type of work. Include mobilization and disposal. Compare the resulting cost with the budget allowance and resolve material differences with the buyer. Record who approved the work instruction and which revision the crew received.

8. Close the record and set its next review. Return the work date, accepted evidence and any unfinished item to the utility’s system. Preserve the earlier observation so a later reviewer can follow the change. Set the next imagery review around the program’s needs, then carry field corrections into the next search edition.

I would schedule the first office review during the opening week, field checks after that review, and a pilot decision once the utility has enough verified records to judge the method. Allow the work’s access and operating requirements to set the release date. A calendar promise made before those checks will not help the foreman.

Choosing vegetation management software and data

Start with the missing job in your workflow: Asset Search supplies reviewed findings, while your operating system needs to assign work and preserve closure evidence.

For a small utility, I would first test whether the existing GIS and work-order process can accept the new records. Replacing software adds another decision to the project. A sample import will show whether the immediate problem is missing evidence, inconsistent identifiers or a workflow the field team cannot maintain.

Option to evaluate	Job to give it	Pilot acceptance question
Asset Search	Review visible vegetation and access candidates against your rules	Can each disposition be traced to dated evidence and a next action?
Existing GIS and work-order system	Store the utility’s assets and assigned work	Can planners join the delivery and return field outcomes without losing identifiers?
Dedicated vegetation management software	Manage the operating workflow you specify	Can it handle your permissions, work stages and required reporting in a sample project?
Survey or lidar engagement	Supply specified three-dimensional measurements	Does the proposed collection and analysis answer the engineering clearance question?

Run a sample import. Ask a planner to assign one finding to a field supervisor and return the field result to the office system. Check whether the original capture date and closure evidence survive the round trip. Inspect the export too.

Asset Search can deliver CSV, Excel or GIS-ready files. Specify the coordinate reference system and the field names with your GIS team. Keep the wider energy asset inventory on the same identifiers where appropriate, so vegetation planners can work from the utility’s agreed asset records.

Where to find utility tree trimming contracts

Search municipal utility procurement records and cooperative purchasing pages by service area, then distinguish vegetation pre-planning opportunities from contracts for cutting work.

The difference is visible in the City of Austin’s distribution vegetation pre-planning solicitation. Its scope includes assigning work to third-party contractors, quality control and planning. This closed solicitation accepted responses through October 14, 2025. Use it to understand the scope; check the purchasing portal for current opportunities.

Build the buyer list around districts your crews can support. Save each utility’s service area and purchasing route beside the qualifications required for the work. An estimator can then screen a new opportunity without repeating the registration research. Ask purchasing to resolve gaps.

Bid Control by PorchRocket covers the public side, with bid documents, due dates and addenda in one place. Use its landscaping and grounds public-work page as a starting point, then check that a particular solicitation fits your utility qualifications. The government service contracts guide explains how to assess recurring public work.

For a packet that needs hands-on preparation, Bid Team’s bid-writing service fills out the forms, works the estimate with you and tracks changes and deadlines. You make the final call on your number, sign and send.

Use the imagery work to sharpen the scope discussion. Present the areas that warrant an authorized survey and the access questions affecting the estimate. Ask the buyer how those findings should enter its procurement process. Keep unsolicited territory research separate from a promise that the utility has authorized a treatment package.

Refresh dates that match the utility’s decision

Quarterly editions can support territory planning, while selected locations may need monthly or weekly review according to the utility’s program and available imagery.

I would begin with the next decision date and work backward. An annual budget discussion needs a territory view early enough to influence its scope. A supervisor preparing a near-term work package needs current access information. Give each refresh a stated purpose so the recipient knows what to review when it arrives.

Asset Search offers one-time searches and scheduled monitoring. Where daily satellite coverage exists, near-real-time alerts can support a storm, outage or change watch. Set the coverage and evidence requirements during scoping. A scheduled review date and the date of a usable image belong in separate fields.

For vegetation monitoring, request the before-and-after dates for reported changes. Compare the current observation with the previous accepted record and the latest field outcome. When the evidence cannot settle whether a visible difference needs action, return a field-check instruction. Do not mark a work order closed solely because a later view looks clearer.

The asset-monitoring guide covers recurring editions. For vegetation, maintain a queue for new findings and another for unresolved items awaiting inspection. Track previously treated locations needing review as well. Put the required inspection schedule alongside those queues.

Measure the age of unresolved findings. If a location keeps returning without a field decision, assign someone to obtain the missing information. Carry its original observation date into each edition until the utility records a disposition.

Building a vegetation worklist with Asset Search

Asset Search gives utility vegetation teams a reviewed territory file with dated observations, parcel context and the field questions needed to prepare work.

The fastest way to build that starting inventory is to define your screening rules with Asset Search, supply the area and available line identifiers, and review a paid pilot. We cross-reference aerial and satellite imagery with property records and public datasets, then have people review every candidate. The return includes fits, rejects with reasons and unresolved locations with the field check that settles them.

For a vegetation program, the scoped delivery gives your team:

• Reviewed locations showing the visible conditions that meet your screening rules, with the dated views supporting each finding.
• Parcel and owner information, with decision-maker contact where applicable, to support the utility’s access and notification work.
• Observations of visible approaches and difficult crossings for the estimator’s field-verification list.
• Every disposition, including rejection reasons, so the inventory preserves what was examined and what remains undecided.
• CSV, Excel or GIS-ready delivery arranged around the identifiers and fields agreed with your team.
• Refresh editions and re-review when requirements change, allowing the utility to carry its existing evidence into the next planning decision.

For a defined corridor investigation, I would choose pricing per completed investigation because the buyer needs the rejected and unresolved records too. Use a subscription when the job includes continuing monitoring. Per accepted result is available when acceptance can be defined clearly; success-based terms can be tied to an agreed outcome. Most buyers begin with a small paid pilot credited toward the full order.

Describe what to find and where in the two-minute Asset Search request. We return a scope and quote, then ship the pilot in your format. Your planners get a record they can review, and your field team gets a specific question to settle at each location.