Retirement Didn't Stick: Why I Still Advise After 40 Years

I thought I was done. Forty years is a long time to be on construction sites — the early starts, the winters, the weight of keeping a job moving when everything is pushing against you. When I stepped back from full-time site management, I was ready for the quiet. And for a while, the quiet was fine.

Then the phone started ringing.

Not straight away. But it didn't take long before people I'd worked with over the years started getting in touch. A project in trouble. A programme that didn't add up. A young manager who couldn't work out why the job wasn't moving the way it should. Could I take a look? Could I have a conversation? And I found, sitting in my chair at home, that I still had answers. The knowledge hadn't gone anywhere. It was just waiting.

That's the thing nobody tells you about forty years of experience. You don't retire from what you know. You can walk off the last site and hand in the last set of keys and it's all still there — every problem you ever solved, every situation you read correctly, every time the programme said one thing and the ground told you something different and you trusted the ground because you'd learned to. That doesn't switch off. It just needs somewhere to go.

What I see in the industry now is what I've always seen, if I'm honest. The same problems turning up in different clothes. Programmes that drift from reality because nobody's walking the job properly. Young managers who are sharp, technically capable, well-trained — and who are still making the mistakes that experience would have warned them about, because that experience isn't available to them. It walked out the door when the last generation retired and didn't look back.

That's the part that bothered me. The industry is not good at holding onto what it knows. A man or woman with thirty or forty years on sites carries an enormous amount of practical knowledge — not theory, not what the textbook says should happen, but what actually happens and why, and what you do about it. When they go, that goes with them. Nobody writes it down. Nobody passes it on in any organised way. It just disappears.

Advising is my way of not letting that happen. When I talk to a project team now, I'm not managing them — that's not my job and I wouldn't want it to be. I'm giving them access to a way of thinking about problems that only comes from having seen those problems play out over decades. Sometimes that's a conversation about sequencing. Sometimes it's helping someone see that the issue on paper isn't the real issue at all. Sometimes it's just asking the right question and letting them find the answer themselves, because they're more than capable — they just needed someone to point them at it.

What's different now from managing is that I work on my own terms. Remote. Flexible. No site hut, no early alarm, no fighting the traffic to be on the ground at seven. I can look at a programme, talk through a problem, give an honest assessment — and then close the laptop and go for a walk. That balance is something I never had in forty years of full-time work. I won't pretend it isn't welcome.

But what hasn't changed is why I do it. I still care about the work being done right. I still find it genuinely satisfying when a team works something out that was giving them grief, or when a project that was slipping gets back on track. That part of me didn't retire. It just stopped wearing a hard hat. I don't need to be on site every day to see what's happening. I've seen it before. That's the point.

The work still means something to me because it always did. Not the status, not the title — the work itself. Getting a complicated thing built properly, on time, without cutting corners. Forty years of that leaves a mark. And as long as people want to draw on it, I see no reason to pretend I've nothing left to give.

This story was adapted with assistance from AI