If you install helical piles, sooner or later someone is going to ask you for a conformity letter. It might be the general contractor closing out a foundation phase. It might be the building department before they sign off. It might be the owner's lender. Whoever asked, the next step is usually the same: you call the helical pile engineer who designed the piles and ask what they can issue.
What you get back depends on three things most installers do not think about until the letter comes back: (1) what exactly was requested by the Owner, (2) what data did you provide the engineer to support your request, and (3) what scope of professional review the engineer was retained to perform. If you lack absolute clarity on any of those, you can expect serious delays in receiving any sealed reports from an the engineer, or it comes back with significant limitations you did not expect, or does not satisfy the party who asked for it.
This article is about how to make that exchange go smoothly.
What Owners Actually Think They Are Getting
Most owners, lenders, and general contractors asking for a conformity letter think they are getting an engineer's certification that the piles were installed correctly and can carry the design loads. They picture an engineer reviewing the work, confirming everything is good, and putting their seal on it.
For the majoity of cases across Canada, that is not what these letters actually are. In fact, it is not even what an engineer can provide unless they were physically on site with a defined inspection scope performing continuous inspection. And on the vast majority of helical pile projects, they are not.
What the engineer is actually providing is whats refered to as a general conformity report, which is a professional opinion, based on limited information you submitted after the fact, that the installation appears to be in general conformity with the design. While that is a real and useful professional statement, it is not a guarantee, nor does it void you of any liability as the installer. A helical pile general confirmity report does not mean the engineer verified every pile. It means they reviewed the data you sent them and concluded the installation generally meets the design intent.
Knowing this is the first step to managing the process. The owner thinks they are getting a stamp of approval. You and the engineer are working with something narrower. The faster everyone understands that, the faster the document gets issued and the less anyone is disappointed by what it says.
Tell the Engineer Up Front What You Need
The biggest mistake installers make is asking for a conformity report at the end of a project when the engineer was never on site and was never retained to be. That creates an impossible situation. The word certification can imply the engineer verified the installation directly, which may require a very different scope than a records-based general conformity opinion. If the engineer was not on site, they cannot certify in that sense. You cannot fix that after the fact.
Always let the engineer know before they seal the design if you or your client will require a conformity report at closeout. That gives them the chance to scope their involvement to match what you will need. And expect a lot of limiting language in the final letter the less the engineer was involved in the construction. That is the system working correctly, not the engineer being difficult.
Provinces handle this differently. Some require general conformance language. Others use different terminology. As helical pile installers migrate across provinces, it is important to understand that the nuances do not apply one-to-one between jurisdictions. If your contract requires certification, that is often not the same as a general conformity report. In some provinces certification may imply continuous inspection, which is a different thing than the engineer providing a professional opinion that the installation appears to meet the design intent.
Here is how to get the closeout document you need with the least back and forth.
What the Engineer Actually Needs From You
The bottleneck in most conformity reports is not the engineer's time to write the letter. It is the back and forth needed to get the data into a form they can clearly understand and defensibly rely on. Field installers consistently underestimate the level of clarity, nuance, and context an engineer needs to complete one of these reports without follow-up.
Project requirements vary across jurisdictions and specifications. The list below is not a universal code requirement. It is what 15 years of reviewing helical pile installations has taught me makes the engineer's job possible without three rounds of emails.
At minimum, a useful field installation report should include:
- Project and location identification tied to the sealed design drawings (project number, address, drawing reference)
- Installer information, including company name, the name of the person who supervised the install, and contact details
- Date or dates of installation
- Equipment information, including drive head make and model, and where applicable the torque indicator make and model
- Per-pile records: pile ID, final depth or embedment, final installation torque, and confirmation that the design termination criteria were met
- Torque reported in engineering units (ft-lbs or N·m), not raw hydraulic gauge PSI
- As-built pile locations: a marked-up plan or sketch showing where each pile actually ended up, with any measured offsets from the design location
The torque unit issue is where most reports go off the rails. PSI is a hydraulic gauge pressure, not a torque value. The accepted engineering unit for helical pile installation torque is ft-lbs or N·m. When the only reading available in the field is PSI, that value has to be converted using the drive head's pressure-to-torque relationship, typically a manufacturer-published calibration chart specific to that drive head. The engineer cannot defensibly issue a conformity opinion against a design torque expressed in ft-lbs based on a field reading expressed in PSI without that conversion being documented somewhere. Convert in the field, or send the calibration chart with the report so the engineer can do it themselves. What does not work is sending only the PSI reading with no equipment information and no chart.
Provide as-built locations, not just pile IDs. A list of pile IDs without locations tells the engineer nothing about whether the piles ended up where the design placed them. Many sealed designs include placement tolerances, and piles installed outside those tolerances may need to be evaluated against the structure they are supporting. Without an as-built sketch, the engineer's letter can only address torque and embedment, not placement. That is not wrong, it is accurately scoped to what you gave them. But the owner reading that letter may not realize alignment was never assessed. If placement matters for the project, send the as-built.
Use specific termination language. The word "refusal" by itself can mean several different things: practical refusal at the rated torque, flat-spin on competent material, suspected obstruction, or the drive unit reaching its operating limit. Each one has different implications for pile capacity. Write down what actually happened, not just that something happened.
Note any deviations. If a pile ended up significantly shallower or deeper than the design anticipated, say so and say why. Engineers can usually accommodate variances with appropriate qualification language. What they cannot do is read your mind about whether something unusual happened on site.
What Not to Submit
Engineers who design helical piles have seen all of it. Back of the napkin notes. Text messages. A screenshot of notes typed on a phone. Mud-stained field notes. Illegible handwriting. Field notes that say "all piles installed to a minimum torque of X" without listing each pile. "All piles installed between 7 and 24 feet" without saying which pile went to what depth. No mention of pile size. No mention of the helix that was installed. No final torque over the last foot. No plan view showing which pile achieved what torque. Total lack of clarity on which piles needed extensions, or whether any bolted extension connections ended up at or near grade where they may be laterally unstable.
And then the request comes in for a document certifying the installation.
These are not rare situations. They happen regularly and more often than the industry likes to admit. Do not put the engineer in an impossible situation. They cannot defensibly issue a useful closeout opinion from a record that does not actually contain the information needed to assess the installation against the design. One clean PDF with per-pile records, drive head conversion chart, and an as-built sketch is what the engineer needs. Anything less than that means the letter takes longer, comes back more qualified, or in some cases cannot be issued at all.
How Installers Can Speed Things Along
Most of the friction in conformity letter requests is preventable.
Establish the engineer's scope early. When you accept a job, ask the helical pile engineer (or the manufacturer providing the engineering) what scope of review they have been retained for and what closeout documentation will look like. Knowing this before installation tells you what kind of records you need to keep.
Capture the right data the first time. If you know the engineer will need ft-lbs, convert from PSI as you go and record both. If you know they will need termination reason, write it down specifically. If you know they will need as-built locations, mark them up on a plan as you install. None of this is harder than what you are already doing, it just has to happen in real time instead of from memory two weeks later.
Match the request to the scope. If the engineer performed a general review, ask for whatever document the engineer is set up to issue under your project's framework. Different provinces use different terminology. If you need something stronger than what the engineer can support based on their actual involvement, that conversation needs to happen before installation, not after.
Send everything in one package. A single PDF beats five emails every time.
Be ready for qualifications. A properly issued letter sometimes has qualifying language about variances, marginal values, alignment that was not assessed, or items outside scope. That is the system working correctly. A letter that hides those nuances does not actually protect anyone.
The Bottom Line
The conformity report at the end of a helical pile project is a professional engineering document. The clearer you are about what is being requested, the cleaner the data you provide, and the better aligned everyone is on the scope of the engineer's review, the faster the letter gets issued and the more useful it is to the parties relying on it.
Most of the slowdowns come from one of three places: the scope was not clarified up front, the field data was incomplete or in the wrong units, or the wrong document was requested for the engineer's actual level of involvement. All three are fixable with a short conversation at the start of the project and a clean submission at the end.
Helical pile work has historically run on tribal knowledge and informal documentation. As the industry grows and as regulators across Canada look more closely at how foundation systems get reviewed and signed off, that approach is shifting. The installers and engineers who adapt to clearer documentation practices early will spend less time chasing paperwork and more time doing the work.
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.