The Job That Changed How I Think About Quality
- Sam Riddell

- Jun 18
- 4 min read
There's a point on every big project where you realise you're not the same engineer you were when you started. For me, that moment came somewhere on the Peacocke Rising Main in Hamilton, knee-deep in the detail of a $20 million wastewater job, managing three crews across 5 kilometres of pressurised sewer line. I didn't clock it at the time. You rarely do.
This is the story of that project, what it demanded, what went wrong, and what it gave me.

The Project
Around 2020-2021, CB Civil was contracted to deliver the Peacocke Strategic Wastewater Rising Main in Hamilton. This was a dual-pipeline system servicing the new Peacocke subdivision, a significant greenfield development opening up one of Hamilton's major growth areas. One line was 300mm diameter HDPE, the other 630mm — both pressurised rising mains, totalling roughly 5 kilometres of installation.
The scope was broad. Open cut trenching was the backbone of it, but the project also included horizontal directional drilling, pipe jacking under the railway lines, large-diameter HDPE pipe welding, deep excavations with trench shields, extensive service relocations, dewatering in running sands, and all the mechanical fit-out work for the air valves, scour valves, and associated infrastructure.
For a site engineer in his mid-to-late twenties, it was the full shebang.

My Role
I was site engineer on the open cut trenching scope, which was the bulk of the physical work. Day to day, that meant looking after three crews: the main pipe-laying crew, a crop-over machine crew, and an enabling works crew handling service relocations ahead of the dig. On top of that, I was responsible for all the mechanical fit-outs, traffic management facilitation, stakeholder liaison with local residents, and — the thing that consumed more of my headspace than anything else — quality assurance.
It was the first time in my career I'd carried that level of responsibility across that scale of work simultaneously.
Where Quality Got Serious
Here's the honest version of how most construction QA works on big civils jobs: you install a heap of pipe, you scramble to write up the quality records weeks or months later, you reconstruct what you think happened, and everyone pretends the documentation reflects reality. It's a known problem. Nobody talks about it. On this job, I decided I wasn't going to do it that way.
I designed a set of checksheets that were built around the guys actually using them on the ground, not around what an engineer sitting in an office thought they should look like. Drawings on the forms. Fillable fields at each change point. A folder at each station where the crew recorded every layer, every material, every level reading as it happened.
One example: pipe bedding. The spec required 100-150mm of bedding material under the pipe. Nobody records that. Most engineers wouldn't even know how to prove it after the fact. I had the guys take a dumpy level reading on the subgrade, place the bedding, take another reading on top of it, and record both. You could prove the bedding depth from the numbers. Then through the embedment layers, up through the pipe cover. Every layer evidenced.
The result was that every claim we submitted had the quality documentation attached for that month's work. Not a month late. Not six months after completion. As we went. That sounds basic. In practice, on a job this size, it almost never happens.
The client's engineers were impressed. More importantly, it built trust throughout the project that made everything else run smoother.
The Harder Stuff
It wasn't all clean execution. We had major rain events that tested the dewatering setup seriously. Running sands, jetting spears, sump pumping — at times the ground was doing everything it could to make life difficult. We had an environmental incident that required direct engagement with the regional council, which was uncomfortable and time-consuming, but was handled and resolved.
There were moments where I was genuinely out of my depth, managing situations I hadn't encountered before. You make calls. Some of them are wrong. You fix it and you learn faster than you would any other way.
The dewatering complexity alone was a full education. The deep excavation work with large trench shields in difficult ground conditions was another. There was bat monitoring, lizard monitoring, ecology requirements around tree removal — layers of compliance I hadn't dealt with at that level before. Stakeholder liaison with nearby residents. Traffic management plans that had to actually work, not just exist on paper.

The People
I'll say this: I worked alongside some genuinely exceptional people on this project. There was one person in particular who had a way of cutting through noise and focusing on what actually mattered — not getting dragged into the detail that doesn't move anything, but locking in hard on the stuff that does. That approach stuck with me. I still use it.
Being around people operating at that level is its own kind of education. You absorb more than you realise. You start making decisions the same way, without consciously knowing you've changed. You become the sum of the people you surround yourself with.

What I Realised Coming Out the Other Side
I relocated from Auckland to Hamilton for this project. That's how significant it felt at the time, and looking back, that instinct was right.
When it finished, I had a year of high-intensity, large-scale infrastructure delivery under my belt. Three crews. Multiple complex methodologies running simultaneously. A quality system I'd built from scratch that held up under scrutiny. Stakeholder management. Environmental incidents. Deep excavation. Large-diameter HDPE. Pipe jacking. Horizontal directional drilling.
But the bigger shift was in how I saw myself. Before Peacocke, I knew I was capable. After it, I knew how capable. There's a difference. That confidence is what pushed me into the next phase — taking on consultant PM roles, stepping into leadership, giving advice rather than just executing.
I didn't know how much I'd learned until I left the environment I'd learned it in.
What This Project Gave Me Professionally
To close it out plainly: Peacocke gave me large-diameter pressurised pipeline delivery experience across multiple installation methods, a QA approach I've carried into every project since, the ability to manage multi-crew site operations, and the hard-earned confidence that comes from seeing a $20 million job through. It also gave me an environmental incident, some very bad weather, and a healthy respect for running sands in Hamilton.
Worth every bit of it.

Comments