Say you have spent ten years building a helical pile business. You know your equipment, you know your soils, you know what a good install feels like through the machine. The franchise is growing, the calls are coming from farther away, and now there is a real project on the other side of the border. Maybe you are a Canadian outfit looking south at the size of the US market. Maybe you are a US installer getting pulled north on a client's expansion. Either way, you are about to learn something that nobody warns you about until you are standing in front of a building official: the pile is the same, and almost nothing else is.
The steel does not care which country it is in. A helix is a helix, torque is torque, the soil under your feet does not check your passport. The physics travel just fine. What does not travel is the rulebook wrapped around the work, and that rulebook is so different between the two countries that experienced people on both sides routinely talk past each other without realizing they are doing it.
This is not a piece that is going to make you a code expert. It is a piece meant to do one thing: show you that the systems really are different, so that the first time you run into the difference, it is something you expected instead of something that blindsides you.
The thing nobody says out loud
Here is the conversation that happens at every cross-border job, just under the surface. Somebody references a number, a capacity, an approval, a test, as if it is settled fact. And the person across the table nods, because the words sound familiar, except they are quietly hearing something completely different.
A US installer says "it has an ESR and it is good per the IBC," and to them that is a clean, complete answer. A Canadian engineer hears it and thinks, that document has no standing here, what does the CCMC listing say and who is sealing this. Neither one is wrong. They are both fluent in their own system and assuming the other system works the same way. It does not.
That is the real reason the industry struggles to have one conversation about helical piles. It is not that anyone is uninformed. It is that everyone learned the trade inside one national framework, the references, the manuals, the marketing, the approvals, and that framework is so consistent within its own borders that you stop noticing it is a framework at all. It just becomes "how piles work." Then you cross the border and discover it was "how piles work here."
What actually has authority, and why that is the whole game
Before you can speak the other country's language, you have to understand the one thing both languages are built on, which is the question of what document is actually in charge.
On any project there are three kinds of documents, and they carry very different weight. There is the building code, which is law once a government adopts it. There is the standard, which is expert good practice but is only legally binding when a code or a contract points at it. And there is the product evaluation report, the ESR in the US, the CCMC report in Canada, which is a third party's opinion that a specific product works a specific way under specific conditions.
The mistake that causes most of the cross-border friction is treating that third one, the evaluation report, as if it were the first one, the law. It is not. An evaluation report does not create authority on its own. It borrows authority from the code underneath it, and only in the places where that code has been adopted and the local official is actually relying on it. Understand that one idea and most of what follows makes sense.
Why the American system feels so clean
If you came up in the US, you are used to a system that points you where to go. The International Building Code speaks fairly directly about helical piles, and it coordinates with a dedicated acceptance criteria, AC358, that lays out how a helical pile system gets evaluated. A manufacturer runs the gauntlet, and the result is an ICC-ES evaluation report with a number on it.
So a US spec tends to read like a recipe. Use a system with an ESR. Pull the capacities from the report. Install within the conditions the report lists. Provide the inspection and the logs. The code speaks more directly to helical piles, the criteria says how it is judged, the report says this product passed. Clean line from top to bottom.
Special inspections: the part that changes the jobsite rhythm in the US
There is one piece of the US system that surprises Canadian installers more than any other, because there is often no direct equivalent at home, and that is the special inspection.
Under the IBC, certain types of work are flagged as important enough that the building department's own inspector is not considered sufficient on their own. Those items require a separately retained, qualified inspector, the special inspector, who watches the work as it happens and reports independently to the building official. Helical pile foundations are one of those items. They have their own dedicated provision in the code, and on most projects the inspection is required to be continuous, meaning the inspector is present and observing while the piles go in, not dropping by afterward to look at the result.
In plain language: in the US, a helical pile job is often not complete just because the pile is in the ground. It is complete when the pile is in the ground and the inspection record says the installation matched the approved documents.
What the inspector is really checking
On a US job, the special inspector is typically there to record and verify the things that matter most to the code and the engineer:
- The installed pile matches the approved product and configuration on the submittal.
- The installation equipment used, captured on the record.
- The final depth, tip elevation, and embedment meet the design.
- The final installation torque on each pile meets the required value.
- The pile went in at the right location and orientation.
- Any field conditions that affect capacity were documented.
- The installation logs and the observed work agree.
That last point is why special inspection feels so different from ordinary contractor QA. Your crew may already be recording torque, depth, and refusal. But in the US there is often an independent person whose job is to verify those same things for the code official. That does two things. It raises the level of documentation, and it changes who the final sign-off is really for. Your field logs are not just for you anymore, they are part of the compliance package.
The mechanics around it are worth knowing too. Before construction, the design professional prepares a Statement of Special Inspections that lists what has to be inspected and by whom. The owner retains the special inspector or inspection agency. The inspector files reports as the work proceeds, flags anything that does not conform, and submits a final report to the building official, and on most projects that final report has to be in before the building gets its certificate of occupancy.
Canada usually works differently
Canada does not generally run helical pile projects through the same uniform special-inspection model that US building-code projects often use. The Canadian process tends to lean more on:
- the engineer's design,
- the product's evaluation path where applicable,
- the contractor's installation records,
- and the engineer's or the authority's review of the completed work.
That does not mean Canadian jobs are loose. It means the verification model is usually different. In many Canadian projects the professional engineer is the one carrying the sign-off responsibility, and the field verification is more project-specific rather than being built into the code as a formal, uniform special-inspection framework. So a US installer used to a dedicated inspector on site can find the Canadian job more familiar in one sense, but also more dependent on engineering judgment, project documentation, and local municipal expectations.
The practical takeaway for a crew crossing the border: in the US, expect formal inspection requirements, often including a special inspector present during installation, with your logs, torque data, and product submittals all checked against the approved design, and the final code sign-off depending on that inspection record. In Canada, expect a more engineering-led process unless a particular project or municipality requires something more formal, and do not assume a US-style special inspection requirement exists just because the pile system looks the same. That one difference can change how you staff the job, how you schedule it, and how you prepare your documentation.
That clarity in the US is genuinely useful, and it is also the thing that sets you up to be surprised, because you start to assume every country gives you a line that clean. Canada does not.
Why the Canadian system feels broad and a little open-ended
If you bring that expectation north, the first thing you notice is that the code does not seem to talk about your pile specifically. The National Building Code of Canada, and the provincial codes built from it, handle helical piles inside the general world of piles, foundations, structural steel, welding, and geotechnical design. The pile is covered, but it is not singled out with its own section the way the IBC singles it out.
So where did all the specific detail go? It moved out of the code and into three other places, and you need to know all three.
Some of it lives in CCMC evaluations, the Canadian equivalent of an ESR, issued for particular proprietary systems. Some of it lives in the engineer's project-specific design, because on anything beyond the simplest structures a Canadian engineer is expected to design the foundation for the actual conditions rather than lean on a product listing. And some of it lives at the municipal level, where individual cities and towns have written their own permit requirements and bylaws because the national code left enough room that they felt they had to.
That municipal layer surprises people the most. You can satisfy the provincial code in principle and still walk into a city that wants a geotechnical report, an engineer's letter, specific installation records, and a sign-off in a particular form before it will issue the permit. A bylaw usually does not replace the building code; it adds local permit and documentation requirements on top of it. The reason some municipalities do this is worth hearing, because it is the same problem your better competitors complain about: screw piles are popular, heavily marketed, and sometimes treated as a one-size-fits-all shortcut. Municipalities that saw the same issues repeat, piles installed without enough engineering, products used outside their approved scope, sign-offs that did not match the job, respond by adding local permit requirements, documentation rules, or review steps. The bylaw tends to formalize what good installers already know: this needs more rigor than a brochure.
The CCMC report is not a passport, and neither is an ESR
Whichever direction you are crossing, carry this with you: an evaluation report only covers what it actually covers.
A CCMC report assesses a specific product under specific conditions, certain structure types, certain assumptions about soil and corrosion, certain installation details. That scope is the box. If your project is inside the box, the report is a powerful, recognized reference. If your project is outside the box, the report does not stretch to fit it. Some CCMC reports are limited to specific building types, load conditions, or installation assumptions, so you have to read the scope carefully, and on many projects the moment you step beyond what the report covers, the listing stops carrying you and an engineer has to design the foundation directly.
The exact same logic applies to an ESR in the US. It is an opinion bounded by its own conditions, borrowing its authority from the code beneath it. Neither document is a universal sticker that makes a pile legal everywhere. The installers who get burned are the ones who treated a report as a passport instead of as what it is, a bounded, borrowed, conditional approval.
Even the design language is different
Suppose you get past approvals and into the actual numbers. Here is another place the two countries quietly diverge, and it changes what people are even asking you for.
Canada designs in limit states. The engineer is thinking in factored loads and resistance factors, in ultimate limit states and serviceability limit states, asking not just whether the pile holds but how it behaves at the design load and what margin the code demands. When a Canadian engineer talks, you will hear "factored resistance."
The US, in the helical pile world especially, still leans visibly on allowable stress design, an ultimate capacity divided down by a factor of safety to a working load, even though load and resistance factor design is also in use. So an American sheet may hand you a single allowable capacity, while a Canadian sheet talks in factored resistances. Same steel, same screw, two different vocabularies for describing what it can do.
For you in the field, this is not academic. It changes what number someone is asking you to hit, how your torque gets interpreted, and what a load test result is taken to mean. If you do not realize the language changed, you can think you are agreeing with someone when you are actually describing two different things.
And sometimes the building code does not even apply
One more boundary, because it catches people who have gotten comfortable. Building codes do not govern everything you might put a pile under.
Take your crew onto a telecom tower, a pipeline, a transmission line, a rail structure, or a bridge, and the controlling document may not be a building code at all. These sectors are usually governed by their own standards, owner criteria, and project-specific engineering requirements, and the helical pile is just one engineered component inside that larger system. On those jobs, your clean CCMC report or your tidy ESR can be the wrong document set entirely, not because it is bad, but because the project was never under the building code that gives it meaning. The authority is the sector's standards and the owner's specification, and the pile is engineered to those.
Learning to speak both languages
Here is where it comes back around to that conversation that keeps going sideways.
The reason a Canadian and an American installer struggle to talk about the same pile is not a knowledge gap. It is a translation gap. Each one is fluent in a complete, internally consistent system and is assuming the other system maps onto theirs word for word. It does not. The code speaks at a different volume about the pile, the approvals run through different bodies with different scopes, and the design is expressed in a different language of safety. And the authority itself can sit in a different place depending on the job: a national code, a provincial code, a municipal bylaw, or a sector's own standards.
Once you can see that, you stop being surprised, and you start being useful in both places. You learn to ask, on any project, in either country, the few questions that locate you in the right framework. What code governs this, if any. Is this a building-code job or a sector job. Does the product approval actually cover this use, or just the small version of it. Will there be a special inspector assigned to watch the install, and do my torque and depth logs need to line up with theirs. Is the local municipality going to want more than the province does. Is the engineer working in limit states or allowable stress, and have they translated the numbers accordingly.
Those questions are the same on both sides of the border. The answers are what change. An installer who knows to ask them can walk onto a job in either country and figure out the rules instead of assuming them, and can talk to an engineer or an official in their own language instead of his own.
The pile does not change when you cross the border. You do, a little, every time you learn that the way you have always done it was the way it is done in one place, not everywhere. That is not a setback. That is what it takes to build something that works on both sides of the line.
PileConnect keeps a curated reference of the codes, standards, and evaluation documents behind all of this at pileconnect.com/codes-and-standards. Use it to get oriented, not as a substitute for the adopted code in your jurisdiction or the judgment of a licensed engineer.
Cory Goulet is a P.Eng. with 15 years of helical pile design experience and the founder of PileConnect, a free directory of helical pile installers across North America.