AI for Cable Sizing and Voltage Drop: What It Can and Cannot Do

Last updated: August 2026

Sizing a conductor is two checks in a trench coat. The cable has to carry the load current without overheating, and it has to deliver the voltage the load needs at the far end. Ask a chatbot to do it and you will get a confident answer in seconds, which is exactly the problem: the number looks right, cites no table, and may be wrong. This guide is an honest account of AI for cable sizing and voltage drop: the parts a language model genuinely speeds up, the parts where it will quietly get you in trouble, and the line you should never let it cross.

The short version is that AI drafts and explains, while the adopted code table, the derating factors, and a qualified engineer’s sign-off decide the answer. It pairs with our wider guide to AI tools for electrical engineering and our broader look at whether AI can do engineering calculations at all.

The two checks every cable has to pass

Cable sizing is not one calculation. It is two, and a conductor only passes if it clears both.

Ampacity. The conductor must carry the design current continuously without exceeding its temperature rating. Under the US National Electrical Code (NFPA 70), the starting value comes from an ampacity table in Article 310, such as Table 310.16. That raw table value is then reduced by the correction and adjustment factors in 310.15: an ambient-temperature correction and a factor for the number of current-carrying conductors bundled together. These factors multiply, so a conductor rated for a comfortable current in free air can lose a large share of that rating once it is hot and grouped with others. The result is then checked against the termination temperature limit. International work uses the same idea through IEC 60364-5-52 or, in the UK, BS 7671.

Voltage drop. Even a conductor with plenty of ampacity can be too small if the run is long, because resistance eats voltage along the way and the load sees too little at the end. This is the check that most often forces you to a larger size than ampacity alone would suggest.

The voltage-drop rule almost everyone gets wrong

Here is where naive AI answers, and plenty of human ones, go astray. In the NEC, the familiar 3 percent branch-circuit and 5 percent total figures are recommendations, not requirements. They appear in informational notes, and under NEC 90.5 an informational note is explanatory and not an enforceable rule. Your local authority having jurisdiction can adopt them as a mandatory local amendment, so they often function as hard limits in practice, but the base code treats them as guidance.

There are specific places where voltage drop is mandatory in the NEC, and these are worth knowing precisely:

• Fire pumps (695.7). The voltage at the controller line terminals must not drop more than 15 percent during motor starting, and the voltage at the motor terminals must not drop more than 5 percent when running at 115 percent of full-load current.
• Sensitive electronic equipment (647.4). A branch circuit is held to a tighter 1.5 percent, with an even tighter combined limit across the feeder and branch circuit.

Outside the NEC the picture differs by region. UK design under BS 7671 treats voltage drop as a regulation, not a suggestion: Regulation 525 sets 3 percent for lighting and 5 percent for other circuits of a 230 volt supply. The international standard IEC 60364-5-52 gives similar 3 and 5 percent figures, but in an informative annex, so it reads as recommended guidance that national rules may override. If an AI answer states a single global voltage-drop limit, it has already lost the plot: the correct figure depends on your code and your jurisdiction.

The voltage-drop formula, stated correctly

For a three-phase circuit, the line-to-line voltage drop is approximately:

Vd = 1.732 x I x L x (R x cos(phi) + X x sin(phi))

For a single-phase circuit the leading factor is 2 instead of 1.732, because current flows out and back along two conductors. In both, I is the load current, L is the one-way run length, R and X are the conductor resistance and reactance per unit length, and phi is the load power-factor angle. UK practice often skips the trigonometry and uses the tabulated method from BS 7671 Appendix 4: a millivolt-per-amp-per-metre value for the cable, so that Vd equals that value times the design current times the length, divided by a thousand.

This is exactly the kind of algebra a language model handles well. It will set up the formula, rearrange it to solve for the maximum run length or the minimum conductor size, and lay out the steps cleanly. What it cannot safely supply is the R, X, or ampacity values themselves. Those belong to a specific conductor in a specific installation, and they come from the code tables or the manufacturer, not from the model’s memory.

Where AI helps, and where it will get you in trouble

Kept in its lane, a language model earns its place in this workflow:

• Explaining the method and the difference between the two governing checks.
• Setting up the voltage-drop formula and rearranging it for whatever you need to solve.
• Listing which derating factors apply and explaining why, so you do not forget the ambient or grouping correction.
• Drafting a first-pass calculation spreadsheet you then populate with real table values.
• Sanity-checking your own answer and catching an arithmetic or unit slip. Unit slips are common enough that we wrote a whole piece on why ChatGPT gets units wrong.

The failure modes are specific, and every one of them can undersize a cable:

• Hallucinated ampacity. The model will state a precise ampere figure that matches no real table row. Always read the value from the adopted code table yourself.
• Wrong or outdated code edition, or the wrong jurisdiction entirely. It may blend NEC and IEC values or cite a superseded edition, and it does not know your locally adopted code or its amendments.
• Ignored derating. A naive answer quotes the raw table ampacity and skips the ambient and grouping factors that shrink it, so the conductor runs hot in service.
• Recommendation confused with requirement. It may treat the 3 and 5 percent figures as a hard limit, or miss the cases where voltage drop truly is mandatory.

Undersizing is not a cosmetic error. It leads to overheating, insulation damage, nuisance tripping, and in the worst case a fire. That is why the code table and a qualified engineer, not the model, own the final number.

The tools, and how much AI is really in them

Most products marketed as an AI cable calculator are ordinary deterministic calculators with the letters AI in the domain name. That is not a criticism of the math, which is often solid, but the intelligence is a form, not a model. A few tools are worth naming, and pricing changes often, so check each official site.

• ELEK Cable Pro Web is the clearest genuine case. Its standards-referenced sizing engine, covering AS/NZS 3008, NEC, and IEC methods, can now be driven in plain language from inside ChatGPT and Claude, with the deterministic engine doing the math and citing the tables. The natural-language workflow sits on a paid plan.
• Southwire Voltage Drop Calculator is a free, reliable NEC voltage-drop and wire-size tool that produces a clean report. No AI, and none needed.
• myElectrical offers free IEC cable-sizing and voltage-drop calculators with reference notes, and jCalc provides a library of standard engineering calculators.
• ETAP and SKM PowerTools are enterprise power-system platforms that automate cable sizing across IEEE, NEC, and IEC methods. The automation is rule-based rather than a language model.

Frequently asked questions

Can I use ChatGPT to size a cable?

Use it to explain the method, set up the voltage-drop formula, and check your own working, but not to produce the final size. A language model hallucinates ampacity values, can cite the wrong code edition, and does not apply derating unless prompted. Read ampacity from your adopted code table, apply the correction and adjustment factors yourself, and have a qualified engineer confirm the result.

Is the NEC 3 percent voltage drop a requirement?

Not in the base code. The 3 percent branch-circuit and 5 percent total figures appear in NEC informational notes, and under 90.5 an informational note is not enforceable. Your local authority having jurisdiction may adopt them as a mandatory amendment. Voltage drop is genuinely mandatory in specific cases, such as fire pumps under 695.7 and sensitive electronic equipment under 647.4.

What is the formula for voltage drop?

For a three-phase circuit, the voltage drop is about 1.732 times the current, times the one-way length, times the quantity resistance times the power factor plus reactance times the sine of the power-factor angle. A single-phase circuit uses a factor of 2 instead of 1.732. UK designers often use the millivolt-per-amp-per-metre method from BS 7671 Appendix 4 instead of the trigonometric form.

Why does voltage drop often decide the cable size?

On long runs, resistance consumes voltage along the conductor, so a cable with enough ampacity for the current can still leave too little voltage at the load. The longer the run, the larger the conductor you need to stay within the voltage-drop limit, which is why voltage drop, rather than ampacity, frequently sets the final size.

Do AI tools account for derating?

A general chatbot usually does not unless you explicitly give it the ambient temperature, the number of grouped conductors, and the installation method. Dedicated software such as ELEK, ETAP, or the Southwire calculator applies the correction factors within its standards engine. Even then, confirm the inputs and the adopted code edition before trusting the output.

Sources

• NFPA 70, National Electrical Code
• Mike Holt: voltage drop calculations and the NEC recommendation
• NEC 695.7 fire pump voltage drop limits
• BS 7671 voltage-drop limits (Regulation 525)
• ELEK: AI-driven cable sizing via ChatGPT and Claude
• Southwire voltage drop calculator
• ETAP cable sizing software

Written by the CognitiveFuture editorial team. We build our guidance from published standards and official product documentation, and we label recommendations and vendor statements as such. We do not independently benchmark any tool, and we do not treat AI-generated ampacity or property values as reliable. Cable sizing is a safety-critical calculation that a qualified engineer must verify against the adopted code before it is used.