How a Simple Conduit Size Calculator Saved Our Project (and What I Learned About Total Cost)

The Call That Changed How I Approve Specs

It was a Tuesday afternoon in early 2024 when I got the call. A project manager I'd worked with before—let's call him Jack—was frantic. They'd pulled 1,200 feet of cable through a new industrial building, only to realize half the conduits were undersized. The cable bundle wouldn't fit. The electricians were on site, the client was breathing down their neck, and the fix meant cutting open drywall, replacing the conduit, and repulling everything. Total rework cost? Roughly $18,000—plus a two-week delay.

Jack's first question to me was: “Can you overnight me a smaller-diameter cable that still meets the ampacity?”

I could hear the stress in his voice. But the real problem wasn't the cable—it was how the conduit fill had been calculated. Or rather, not calculated.

The Mistake I Make Too Often

Jack had ordered the cheapest THHN he could find from a discount supplier. The price per foot was 15% lower than what we (Southwire) quote. He thought he was saving money. But in his rush (Jack Gold Rush, we joked later—though he didn't think it was funny at the time), he skipped the step of verifying conduit fill using a proper sizing tool.

Like most beginners in procurement, I've made a similar assumption: that all THHN is the same diameter. Turned out the discount cable had a thicker insulation, pushing the fill percentage over 40% for the 2-inch EMT they'd installed. NEC says you can't exceed 40% for three or more conductors. They were at 43%.

“I assumed the conduit was fine,” Jack told me. “The online quote said the cable was ‘standard.’”

What I mean is—he didn't check. And I hadn't flagged it because I wasn't involved in the initial spec.

The Southwire Calculator That Could Have Prevented It

I walked him through Southwire's conduit size calculator (free on our website). I'd used it myself dozens of times. You punch in the conductor type, quantity, and insulation material—it gives you the minimum conduit size instantly. It also shows the fill percentage based on NEC Chapter 9 tables.

“If you'd used this before ordering,” I said, “you'd have seen that your 2-inch EMT was undersized for 9 conductors of #10 THHN at 43%. It would have recommended 2.5-inch.”

He was silent for a second. Then: “I saw the calculator on your site but figured it was just marketing fluff.”

That's the assumption failure we see all the time. People think a vendor's tool is self-serving. But this calculator (southwire conduit size calculator) is based on NEC tables—the same ones inspectors use. It's not marketing.

Why the Cheap Quote Was Actually Expensive

Let's do the math on total cost of ownership for that job:

The $84 difference in cable cost turned into a $17,716 nightmare. Seeing that side by side made me realize why total-cost thinking matters so much.

Lessons I Carry Now

In my Q1 2024 quality audit, I flagged three similar jobs where the spec didn't include a conduit fill check. All three were using non-Southwire products that offered different dimensions. I implemented a new verification protocol in 2024: every order over $500 must include a fill calculation from a recognized source (NEC table or a reputable calculator like Southwire's). The vendor can use their own tool, but they have to show me the numbers.

Since then, we've rejected only 2% of first deliveries for spec mismatches—down from 11%. The rework avoidance alone saved our company about $40,000 this year (unfortunately, I can't share exact figures, but it's significant).

The Takeaway

If you're specifying cable for a project, do yourself a favor: use a conduit size calculator before you commit to a product. It's free (Southwire's is at southwire.com/calculator). And when a vendor tells you their cable is 'standard,' ask for the exact diameter—in inches, not just 'THHN.' Don't assume. That assumption cost Jack $18,000.

I'll never skip that step again. And now I always calculate TCO before comparing vendor quotes. The lowest per-foot price rarely wins when you factor in rework, delays, and stress.

Though I should note—that was a particularly bad example. Most projects go fine. But when they don't, it's usually because someone made an assumption they didn't verify. (this was back in February 2024, and I still bring it up in every team meeting.)