Finished a 14-mile overhead patrol this morning and tagged 11 clearance violations under NESC 232 — mostly vegetation encroachments and a couple of low secondaries over a driveway. Our compliance team wants 30-day corrections after notice; are other districts seeing the same timelines or pushing 60 with crew shortages?
I’ve kept ‘30-day corrections’ on track by calling our veg contractor from the truck as soon as we tag NESC 232 hits and sending span photos, so they can clear before the crew hits the low secondaries over driveways. When we’re stretched, we bump non-traveled driveways to 45–60 and prioritize anything over public driveways or school routes. Do you have authority to schedule veg directly, or does compliance have to release it?
Same 30-day push here, but we got compliance to allow a 45–60 extension if we risk-rank NESC 232 hits and note immediate mitigation. For ‘low secondaries over a driveway’ we tag it hazard and cone it same day, then bundle the raises for a Saturday window — crew shortages are real, . @OpsMike have you tried putting due dates on spans in Field Maps so dispatch bumps them ahead of routine tickets?
And , after a 14‑mile patrol like that, we’ve been getting about a month to fix, but we cut the risk by doing same‑day temp lifts on “low secondaries over a driveway” — quick wedge at the mast and a half‑turn at the dead‑end to gain a few inches until full re‑tension. We also schedule those at first light when the conductor’s coolest, then kick the veg encroachments into the contractor queue. Anyone else had luck getting compliance to start the clock at customer notification instead of the tag time, @lucas_mar20?