How VoltDrop checks its numbers

Multiple sources, before it ships

VoltDrop doesn't type numbers in from memory. Every electrical table built into these calculators is compared against at least two independently produced reproductions of the published table before it goes live, row by row. They all have to agree, on every cell, or it doesn't ship.

This is not theatre. One draft ampacity value in an early build disagreed between sources. The check caught it, the value was corrected before it shipped, and that is the whole reason the step exists.

Sealed, so they can't drift

After a table passes, we take a fingerprint of it and store that fingerprint in the repository. From then on, if a single digit in that table changes, the verification suite stops before the browser checks and reports the mismatch. Re-verifying the data and deliberately updating the fingerprint are separate human steps, not something the seal can enforce by itself.

We've tested that the seal fires on a one-digit edit.

The seal proves a number hasn't changed without somebody noticing. It doesn't prove the original was right. That's what the multi-source check is for. They're separate protections and they do separate jobs.

When we don't know, we say so

The easiest thing in the world would be to fill every gap with a plausible-looking number and say nothing about it. When a country-specific table has not passed, we label the boundary or refuse the answer in the place you would be about to rely on it.

The Canadian conduit-fill page shows what happens when a gap closes. It used to carry a warning because its Canadian conductor and conduit tables had not passed the multi-source check. CSA C22.1:24 Tables 6A/6K and 9A–9H have now passed, so the warning is gone and the page computes from sealed Canadian data. We would rather leave a visible gap than fill it early, and remove the warning only when the evidence changes.

So read the labels rather than assuming. Where the data behind a result hasn't passed for your country, the page tells you so in plain language instead of quietly presenting it as a verified answer.

Translations get read back

VoltDrop ships in six editions across four languages. A safety warning that quietly loses its meaning in translation is a real hazard, so we screen for it: the translated text is turned back into English on its own, without the original in view, and the result is compared against what we actually meant.

We also watch the screen itself. An early version of this check reported almost everything as perfect because the English original had leaked into the process and was simply being echoed back. That run was thrown out. The check was rebuilt so the source is sealed out of it. Runs that show signs of leakage are rejected rather than trusted.

Back-translation catches missing warnings and mangled meaning. It is a screen, not proof.

What runs automatically

• Every calculator is driven in all six editions, not just English, and the answer is checked against an expected value — hand-worked for the core voltage-drop cases, and derived from the sealed tables for the rest. We learned this one the hard way: a test run that drove only English once reported a clean pass while the main calculator was dead in four other editions.
• The English pages are compared byte-for-byte against the previous build, so nothing changes by accident.
• The numeric-parity check covers the translated guides, the Terms page, and three newer pages, including this one. On those pages, every visible number is compared with its English twin, except for a value explicitly marked as a legitimate locale-specific difference.
• Terms that must never be translated — code names, wire types, and units — are checked for survival in every language.

The limits, plainly

• No licensed electrician reviews or approves VoltDrop. Nobody here is holding a licence over this work. If a page ever claims otherwise, it's wrong — tell us.
• VoltDrop is not affiliated with, endorsed by, or approved by NFPA. No calculator is “NEC certified,” including this one. That isn't a thing.
• Results are planning estimates using simplified, normal-conditions methods. Real installations have conditions our inputs don't ask about.
• Codes are adopted locally and amended locally. The edition in force where you're standing may not be the one a table came from.
• Your local inspector (AHJ) decides, not us. Confirm the result against the rules actually adopted in your area before you install anything.

The data edition

US ampacity data reflects NEC Table 310.16 and the 310.15(B)(1) correction factors as published in the 2023 edition (NFPA 70). Small-conductor caps come from 240.4(D), conduit fill from Chapter 9 Tables 4 and 5, and box fill from 314.16. These particular tables have been stable across editions. That is why a slightly different adopted edition usually does not change the answer. State and municipal adoption varies; confirm the edition adopted locally.

Tell us — we'd rather know

If a number here looks wrong to you, say so. You don't need to be polite about it. Corrections to safety data get priority over everything else on the roadmap.

The correction route is Feedback.