The real retirement problem
Every GC knows what it costs to lose a senior estimator in salary terms. Recruiting fees, onboarding time, months of reduced output while someone new finds their footing. Those numbers are real and they hurt.
But they are not the biggest cost. The biggest cost is what walks out the door that nobody ever put a number on: the reasoning behind the estimate.
A veteran estimator does not just know what things cost. They know why they cost that. They know which subcontractor always sharpens their number at the last minute. They know what a radiused room does to carpet waste. They know that the structural steel allowance needs to be wider when the drawings are still at 30% because this particular architect always changes the columns. That knowledge took decades to build. And in most organizations, it lives exclusively in one person's head.
"So-and-so has been doing it this way for 25 years. That's just how we do it." — A phrase Troy Simon hears in GC conversations more than he would like
The follow-up question no one is asking loudly enough: what happens when so-and-so is not there anymore?
Three things that disappear with them
The logic
Every factor, allowance, and assumption in their estimate had a reason. Without documentation, the next estimator inherits the number but not the reasoning behind it.
The system
When your process lives in one person's workflow, their retirement is not just a personnel event. It is a systems failure. You lose the estimator and the method at the same time.
The confidence
Clients and owners trust numbers because they trust the person behind them. When that person is gone, so is the track record. The next team has to rebuild credibility from scratch.
The spreadsheet trap
Most GCs store their estimates in spreadsheets. This is not inherently a problem. Spreadsheets are flexible, familiar, and fast. The problem is what spreadsheets cannot do: they cannot explain themselves.
Open a spreadsheet that someone else built two years ago and try to understand it. You will find hard-coded numbers with no label. Formulas referencing cells three tabs away. A waste factor of 1.083 with no note about why. You can reverse-engineer the math. You cannot reverse-engineer the judgment.
"Spreadsheets carry math, but they don't carry meaning." — Trey Darnell, Proper Precon
This is the trap. The estimate looks complete because the numbers add up. But the institutional knowledge that produced those numbers is gone, and the organization does not find out until a job goes sideways and no one can explain why the original assumptions were what they were.
Why it compounds over time
One retirement is a problem. A wave of retirements is a crisis. And the construction industry is heading straight into one.
The estimators who built their careers on the tools and workflows of the 1990s and 2000s are now in their late fifties and sixties. They are the ones carrying the deepest institutional knowledge. They are also the ones least likely to have documented it in any transferable way, not because they are careless, but because the tools they worked in were never built for that.
Meanwhile, the junior estimators coming up behind them are stretched thin covering the work. There is no time to sit down and do a proper knowledge transfer. There is barely time to answer questions. The mentorship that should be happening is getting crowded out by the next deadline.
What actually gets lost at retirement
- Years of subcontractor intel — who bids tight, who pads, who disappears when the job gets hard
- Cost library context — the why behind every factor, allowance, and unit rate in the estimate
- Market pattern recognition — how costs move in this region, on this project type, at this time of year
- Client and owner nuance — what they actually care about versus what they say they care about
What to do about it
The answer is not to panic when someone announces their retirement. By then, most of the knowledge is already too hard to extract in the time you have. The answer is to build systems now that capture reasoning as work happens, not after the fact.
Where to start
- Stop treating knowledge transfer as a retirement gift. Make it a daily habit. Reasoning gets documented when the estimate is built, not two months before someone leaves
- Look critically at your estimating tool. If it can only store numbers and not the context behind them, you are one retirement away from starting over
- Get junior estimators into the room for client conversations, not just the takeoff. The context you absorb in those meetings cannot be taught from a spreadsheet
- Build cost history into your workflow so every estimate references what came before it, with enough context to understand why those numbers were what they were
- Treat your senior estimators' last few years as a knowledge extraction project, not just a countdown to replacement
The goal is not to replace the veteran estimator. You cannot. The goal is to make sure the organization does not have to start from zero when they are gone. That means building a culture and a toolset where knowledge compounds instead of disappearing, where the next generation of estimators inherits context alongside the numbers.
Progress over perfection, as they say. You will not solve this overnight. But the teams that start now will have a considerable advantage over the ones that wait until someone puts in their notice.
--
This post is drawn from Episode 2 of Proper Precon, a podcast about the problems precon teams are trying to solve every day. Powered by Ediphi.
