Inside Our Foundation Inspector Training Program
How we train judgment, not just process
People often ask how we train new foundation inspectors—what they’re taught, how long it takes, and how we know when someone is actually ready to work independently.
The short answer is that our training program isn’t about memorizing checklists. It’s about learning how to think clearly in imperfect conditions, ask the right questions, and make defensible decisions when there isn’t a textbook answer.
This post is an overview of how that training works and the principles behind it.
The two principles everything rests on
Before we talk about phases or structure, there are two ideas we repeat constantly.
First: there will always be things you don’t know.
No one sees everything. I still encounter new conditions, edge cases, and combinations of issues. The goal of training isn’t to make someone omniscient—it’s to give them enough grounding to recognize when they’re outside familiar territory and to respond appropriately.
That means learning how to piece information together, make a reasonable first pass, and then ask for help when you hit a wall. Waiting too long or guessing your way through uncertainty is how mistakes happen and how clients get hurt.
Second: curiosity is non-negotiable.
When you don’t know something, the expectation is that you dig first—read, research, review past work—then reach out. That balance matters. It protects the client, and it protects the company. It also prevents small uncertainties from turning into big problems later.
Phase one: self-study and pattern recognition
Training starts away from the field.
New inspectors begin with BearU, our internal library of lectures, videos, and reference material. Everything is structured in a specific order and preloaded so there’s no friction getting started.
From there, we move into past reports. There are many of them. The goal isn’t to read every word, but to get faster at scanning, recognizing patterns, and spotting what’s unusual. Over time, inspectors learn what “normal variation” looks like and what stands out.
We also have inspectors study the inspection template closely. It covers the majority of conditions they’ll encounter. The remaining cases—the odd ones—can’t be predicted in advance, which is exactly why judgment matters.
Finally, we introduce data awareness. Inspectors review our internal inspection map to see how movement patterns vary across regions. It’s not definitive, but it helps build intuition about where problems tend to show up—and where the data is thinner.
Phase two: lecture review and structured questions
The lecture review phase is interactive.
We go through lectures together and new hires flag areas that need more explanation. They’re expected to generate their own list of questions—things they want to understand better, topics they’ve researched but want to sanity-check.
This phase isn’t about passive absorption. It’s about forming a habit of asking better questions.
Phase three: on-site training in layers
Field training happens in stages, each with a different purpose.
Observation inspections come first. New inspectors attend several inspections where they mostly watch. They see the pace, the flow, where attention is focused, how decisions are made quickly, and how reports are built in real time. Speed matters here—not rushing, but efficiency.
Under-instruction inspections come next. The trainee leads the inspection and discussion, with support ready when needed. We review the core of the report together, make edits, and talk through why certain wording works and other wording creates risk or confusion.
Checkout inspections are the transition point. The trainee runs the inspection independently while I conduct my own parallel assessment. We then compare notes—what they caught, what they missed, and why. There’s no fixed number of these. Readiness varies. Some discomfort is expected; that’s part of learning to carry responsibility.
Once someone is ready, they go out on their own—with a constant tie to more senior engineers / inspectors through video chats (including in the crawlspace as needed).
Feedback is constant, not episodic
Training doesn’t stop when someone is “done.”
On-site, feedback happens immediately—how inspectors interact with clients, how they explain things, how they handle questions. In reports, we use structured review systems to flag wording, clarity, and risk exposure.
We also expect inspectors to actively seek and monitor online reviews. Not for ego, but for signal. Patterns in feedback matter.
Learning from near-misses
One of the most important parts of our culture is how we handle near-misses.
Inspectors are expected to tell me when they almost missed something significant. In some cases, those situations are shared with the team so everyone learns from them. The goal isn’t blame—it’s tightening the system.
Near-misses are data.
Why we train this way
Foundation inspections don’t reward rote behavior. They require judgment under uncertainty, clear communication, and the ability to slow down or speed up when the situation demands it.
This training program is designed to build those skills deliberately. Not by pretending we can eliminate uncertainty—but by teaching people how to navigate it responsibly.
That’s the standard we hold ourselves to, and it’s what clients ultimately experience when the system works.
https://www.beareng.com/