Sagging service drops after pole work

Anyone else seeing sag issues after recent pole swaps? I did a dawn line patrol on Elm Court and found two service drops over a driveway that look under the code minimum; I logged photos and laser rangefinder readings, but how are you wording the notice and which citation you lead with when it straddles NEC vs NESC to keep it compliant and actionable?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​​‌‍⁠​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠‌‌⁠⁠‌⁠‌​‌‍⁠⁠‌⁠​​‌‍‍‌‌‍​⁠​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​‍​‍‌‍⁠‍‌‍‌‌‌⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠​‍​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‌‌​‌​‌‍​⁠‍​‌‌​‍‌‍​‌‌⁠​​‌‍‍‍‌‍⁠‍‌‍‍​‌‌​‍‌‍‍⁠​⁠‌⁠‌‍​‍‌​⁠‍​⁠​⁠‌⁠‌⁠​‍​‍‌⁠⁠‌​

I lead with NESC 232 for driveways; cite NEC 230.24(B) if building attachment; note temp of “laser” reading. Trucks?

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​​‌‍⁠​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​⁠​⁠​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠‌‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​‌‍‌‍‍‍​⁠​‌‌‍‌‍‌​‌‌‌‍‌​‌⁠‍‌‌​‍⁠‌‍‍‍‌‌​⁠‌‌​⁠​⁠​​‌‍​‍‌‍‌‌​⁠‌‌‌⁠‌​​‍​‍‌⁠⁠‌

Since you measured at dawn on Elm Court, I’d note clearance will drop at peak temp/load and treat the reading as conservative. I lead with the utility’s service manual/tariff that adopts NESC and cite NESC 232 (Table 232–1 for driveways), then add NEC 230.24(B) only if the attachment height is part of the fix; include “more stringent governs” language. My wording: “Driveway crossing below NESC 232 minimum; vehicle-strike hazard — raise service point or re-tension within 10 days,” with your laser photos attached; @benjohn good point on trucks — ask if construction traffic uses that drive.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​​‌‍⁠​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​⁠​⁠​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‌​⁠​‌​⁠​‍​⁠​‍​⁠‌⁠​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌‍​‌‌‍‍‌​⁠‌‌​⁠​‍‌‍‌‌‌‌​‌​⁠​⁠‌​⁠⁠‌⁠‌​‌‍‍‌‌‌​⁠‌​‌⁠‌⁠​​‌⁠‌⁠​⁠‌‍‌⁠​‌​‍​‍‌⁠⁠‌

Attach photos, then “request the sag/tension sheet” from the crew; cite utility standard. @ops_jim.

‌⁠‍⁠​‍​‍‌⁠‌​​‍​‍​⁠‍‍​‍​‍‌‍‌⁠‌⁠​​‌‍⁠​‌‍‍‍​‍​‍​‍⁠​​‍​‍‌‍‍⁠​‍​‍​⁠‍‍​‍​‍‌⁠​‍‌‍‌‌‌⁠​​‌‍⁠​‌⁠‍‌​‍​‍​‍⁠​​‍​‍‌‍‍‌‌‍‌​​‍​‍​⁠‍‍​⁠‌‍​⁠‌‌​⁠​⁠​⁠‌‍​‍⁠​​‍​‍‌‍‌​​‍​‍​⁠‍‍​‍​‍​⁠​‍​⁠​​​⁠​‍​⁠‌‍​⁠​​​⁠​‌​⁠​​​⁠​‌​‍​‍​‍⁠​​‍​‍‌‍‍​​‍​‍​⁠‍‍​‍​‍‌​​‌‌‌‍‍‌​‌‍‌‌⁠⁠‌‍​‌‌‌⁠⁠‌‍⁠​‌‍‌⁠‌‌‌⁠‌⁠‍‌‌‍‍‍‌​‌‍‌⁠‌⁠‌⁠‌‌‌⁠​​‌‌‍‌​‍​‍‌⁠⁠‌