A note that says comply with NESC does not tell a designer which facility condition was checked, which edition governs or how a utility-specific rule changes the answer. Compliance work becomes reviewable only when the route evidence, applicable code, owner criteria and engineering conclusion remain connected at the pole or segment where the decision applies.
This guide uses the 2023 National Electrical Safety Code, IEEE C2-2023, as the current national edition published by IEEE Standards Association as of September 2026. Publication is not the same as local adoption. The engineering scope therefore begins with authority selection, then moves through field sufficiency, clearances, loading, exception disposition and a release record that states exactly what was and was not reviewed.
Select the code basis before measuring the pole
NESC compliance engineering services evaluate a defined facility condition against the adopted safety code, utility standard and supporting field evidence. As of September 2026, IEEE C2-2023 is the current national NESC edition published by IEEE Standards Association, but a jurisdiction or utility may still enforce a different adopted basis or a stricter owner criterion.
The authority stack begins with jurisdiction, facility ownership, applicable code adoption and the utility's published construction standard. Contract criteria may be more restrictive or may require a particular submission format. We do not merge those sources into a single unlabeled clearance value. Each conclusion names the rule and owner criterion that controlled so another engineer can reproduce the review.
The first artifact is a criterion sheet for the facility under review. It lists jurisdiction, adopted NESC edition, IEEE C2-2023 reference, utility construction standard and any contract value that is more restrictive. Conclusions cite the actual controlling entry. This prevents a national publication date from being mistaken for automatic local adoption. An owner preference is not universal code.
NESC compliance engineering services start with the adopted edition
IEEE Standards Association identifies IEEE C2-2023 as the 2023 National Electrical Safety Code. Its published scope includes electric supply stations, overhead supply and communications lines, buried facilities and work rules. That sentence describes the code, not Draftech's service offering. Our pole loading analysis service applies only the criteria relevant to the defined distribution or make-ready condition under review.
A conflict between code adoption and an owner template goes to the utility or jurisdictional authority able to set the basis. We can compare consequences and prepare alternatives. Engineering does not invent a blended criterion. The affected attachment remains on hold or is designed to an expressly directed conservative value. The release statement then identifies that decision instead of claiming compliance with every possible rule set.
National publication is not local adoption
We record both the published national edition and the adopted local basis on the criterion sheet before anyone measures a pole. Our release cites the basis that actually controls the submittal. We will not treat IEEE C2-2023 as automatically in force for every owner simply because it is the current national publication. That distinction is the first engineering decision, not a footnote added after the model already ran.
Supply-station, underground and work-rule chapters in IEEE C2-2023 do not expand Draftech's offering. Power work here remains distribution, make-ready and substations, not transmission. A communications attachment review does not become a station study because the national code table of contents is broader than the facility under review. We state that boundary in the release so a later reader cannot treat a clearance check as a universal code certification. If the owner later adopts a newer edition, the criterion sheet is revised and the affected checks are rerun. We do not back-date a model to look as if it had always used the later text. The release history should show which edition supported each issued opinion.
That history is what a later reviewer uses when an owner template and IEEE C2-2023 disagree. We do not hide the conflict inside a blended clearance number. The hold stays on the attachment until the authority able to set the basis actually sets it.
Collect only the field facts the cited rule needs
Fielding follows the question. A vertical-clearance review needs attachment heights, reference elevations and the applicable crossing or surface condition. A loading analysis needs pole, span, conductor, equipment and guying inputs sufficient for the selected method. Photographs help explain configuration. They cannot repair a missing measurement. The engineering plan lists required evidence before crews collect a route full of attractive but unusable images.
Measure the condition the rule actually addresses
| Review layer | Controlling evidence | Release question |
|---|---|---|
| Authority | Adopted code and utility criteria | Which rules apply |
| Field basis | Measurements, records and uncertainty | Is evidence sufficient |
| Technical check | Clearance and structural evaluation | Does the proposal meet criteria |
| Exception | Condition, ownership and remedy | Who must decide |
| Release | Final design and disposition record | What may proceed |
Field sufficiency is planned in a rule-to-measurement worksheet. Each clearance, separation or loading check names the pole attributes, attachment elevations, spans, conductor or equipment facts and reference surface it requires. Photographs supply context but are not counted as measurements. Owner records remain labeled as records, allowing the engineer to target recollection where an assumption could change make-ready.
The utility pole loading field measurement guide separates observed data from engineering conclusions. That boundary is essential for NESC work. A field technician records conditions and uncertainty. Draftech's in-house engineers apply code, owner criteria and calculation methods to determine whether the proposed design can be released.
A copied pole height or assumed conductor size can make a model run while leaving the conclusion unsupported. We permit an unknown field and stop the dependent check. We stop that check rather than filling a silent default. Targeted recollection is cheaper than defending a complete-looking model built on inherited assumptions. Where owner records supply an input, the record identifies that source rather than describing it as field verified. When a clearance or loading result could reverse because one measured input is missing, the engineer isolates that dependent check and sends a targeted recollection request instead of allowing a catalog default to settle the pole.
The in-house engineer decides whether collected facts support the requested technical check. A field technician owns observation quality. The utility owns owner-specific criteria. The buyer decides whether to fund recollection or hold the location. If a required span or elevation is unknown, the calculation does not advance merely because software accepts a default. The consequence remains attached to that pole. We would rather return a partial package with a named gap than a model that looks finished because a catalog default filled the missing span.
Test the proposed attachment as one coordinated condition
Clearance review and pole loading can affect the same attachment, but they are not one test. A move that improves separation may increase loading or change guying demand. The engineer evaluates the whole proposed condition and records which rules and owner criteria apply. Make-ready is then expressed as a specific modification, not a broad instruction to bring the pole into compliance. When an attachment-height alternative improves separation but increases transverse demand, the in-house engineer reruns the clearance check and loading model from the same proposed geometry before releasing any make-ready instruction to the field.
NESC compliance engineering services keep clearance and strength distinct
Our own review can become too model-centered when the calculation file receives more attention than the source measurements. A precise utilization result does not cure an uncertain span or attachment height. We require the decision schedule to point back to evidence and label sensitivity where a source uncertainty could change the disposition.
Technical review uses a proposed-condition worksheet joining existing geometry, the new attachment, clearance rules, loading model and make-ready action. Clearance and strength remain separate tests but are reviewed together because improving one can worsen another. Sensitivity notes show which measured inputs could reverse the answer, directing reviewers to the field facts that matter rather than every possible uncertainty.
The NESC pole loading compliance guide explains why field inputs, loading district, utility assumptions and attachment geometry must remain connected. IEEE C2-2023 provides the current national code basis. Utility construction standards and adopted jurisdictional requirements still control how the owner receives and approves the result. National publication does not settle that receiving rule.
Self-critical note: we can over-focus on the calculation model because it produces a clean result. That result is only as defensible as its source measurements and authority basis. We force the final schedule to expose uncertain inputs and scope limits, even when doing so makes the package look less complete at first glance.
A split result is still a result
A pole passes only the checks named in scope. If loading succeeds while a crossing clearance remains unsupported, the package states that split and withholds the broader release. Draftech proposes the technical remedy, and the utility or project authority chooses among acceptable options. The resulting make-ready instruction identifies a facility change instead of telling crews generally to make the pole compliant.
That split is useful to a buyer because it shows which work can proceed and which work is waiting on a measurement or an owner decision. A single pass/fail stamp hides the path. We would rather show a clearance hold beside a supported loading result than imply that the whole pole is finished. The next field visit then has a specific job instead of a vague instruction to collect more data. Make-ready language should name the facility change, the governing criterion and the evidence that will prove the change. A note that says bring the pole into compliance is not an instruction a field crew or a utility reviewer can execute.
If the utility picks a different attachment height, clearance and loading are both rerun because the remedy can change separation, guy demand and construction scope together. We keep those results on one proposed-condition worksheet so a favorable clearance cannot be issued while the loading input is still a guess.
Route nonconformance to the party that can resolve it
An exception register states the observed nonconformance and maps it to the affected facility. It also shows whether the proposed work changes the condition. Engineering can define the technical exposure and recommend a remedy, but it cannot create a waiver in a plan note. The owner or jurisdictional authority acts on acceptance, while agreements handle commercial responsibility outside the code opinion.
Nonconformance is handled in an exception routing sheet that separates the observed condition from the effect of new work. Facility ownership and the proposed technical remedy occupy their own fields. Commercial responsibility remains on the agreement path. This keeps a disputed cost allocation from being mistaken for permission to ignore a clearance or loading problem.
Separate existing conditions from new-attacher scope
A general existing-condition note protects nobody because it does not identify the facility or explain whether the proposed design worsens the condition. We map the exception to a stable pole record and cite the evidence supporting the technical path. Cost responsibility stays with the agreement and authorized parties. Engineering does not settle a commercial dispute through a construction note.
The technical remedy remains tied to the adopted code and utility criteria even when the parties disagree about cost. That distinction is easy to lose in a plan review because a single comment may mention both. We answer the safety and design question in the engineering file, then point any payment or responsibility issue to the governing agreement and authorized decision maker. Neither track grants a code waiver.
Closure occurs when the exception has a technically adequate path and the utility or another authorized party has acted on it. A plan note is not a waiver. Rejected remedies stay in the review history only when they explain the chosen design or a recurring owner comment; the construction package shows the approved action, not a debate the crew has no authority to reopen.
Suppose a proposed attachment clears one communications-space criterion but adds load to a pole with uncertain guying. Reporting only the favorable clearance would fragment the proposed condition. The worksheet keeps the clearance finding open beside the loading input gap and identifies the recollection needed. If the utility directs a different attachment height, both checks rerun because the remedy can change separation, loading and construction scope at once.
Release a bounded code opinion, not a blanket certification
A buyer should reject any proposal that promises a blanket NESC certification without naming the facility, adopted edition, field basis and technical checks. The useful product is narrower: a reproducible opinion about the proposed condition, with unresolved evidence and excluded systems stated plainly. Another engineer can then review the same measurements and understand the conclusion.
- Distribution attacher: buy a clearance and loading opinion on the proposed communications attachment, citing the adopted edition and the owner construction standard that actually controls the submittal.
- Cooperative or municipal owner: require the criterion sheet to show whether IEEE C2-2023, an older adopted text or a stricter local template governs before any model is treated as final.
- Program with inherited plant: keep preexisting conditions on a separate exception path so a new-attacher design check is not written as a waiver or a cost settlement.
The pole attachment structural analysis guide covers the structural side of this record. Draftech's engineering team works in-house, so a technical question returns to the people who authored the package rather than to field labor or a downstream design subcontractor.
Read the final statement as if the calculation file were unavailable. It should still identify the proposed attachment, governing criteria, critical measurements, result and exceptions. A phrase such as code compliant is insufficient when the scope checked only one part of a pole. Precision is not a disclaimer. It is the information that makes the opinion reviewable. A receiving engineer should be able to identify the adopted edition and utility criterion, locate the critical field evidence, and understand every excluded condition without opening an unrelated commercial file or calling the original designer.
Draftech's construction offering in this context is distribution, make-ready and substation work, not transmission. If full turnkey make-ready is separately procured, the managed subcontract crew framework operates under Draftech QA/QC and safety controls. Subcontract crews perform approved field activity. They do not author code conclusions or accept utility exceptions.
Start with the proposed attachment and the field fact most likely to reverse the answer. Ask Draftech to define the review boundary, then send the adopted utility standard or missing measurement to the engineering team before a broad certification is written into the scope.
