Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Builder Cut Rework 60% with a Simple Checklist
Transcript
- Lucas: Luna, you have probably seen that stat that rework in construction costs the industry somewhere in the neighbourhood of $30 billion a year in the US alone. Lucas: That's according to a study from the Construction Industry Institute. And depending on whose numbers you believe, rework can eat up anywhere from 5 to 20 percent of total project costs. Luna: That's a huge drain. And it's not just about money — it causes delays, strains relationships with subcontractors, and it's incredibly demoralising for crews when they have to tear out work they already did. Lucas: Exactly. So one mid-sized commercial builder in the Midwest decided to tackle this head-on. They had a recurring problem: concrete foundations being poured to the wrong specifications — wrong mix, wrong depth, wrong rebar layout. It was happening on about one in every four projects. Lucas: So they did something almost embarrassingly simple: they introduced a one-page pre-pour checklist that the site superintendent had to physically initial before any concrete truck could pour. Lucas: And honestly, that kind of simple, low-cost fix is exactly what this show is about. If you find these tactical stories useful — and I hope you do — the only reason the Operator's Manual stays ad-free is listener support. If you'd like to help keep that going, you can find us at buy me a coffee dot com slash fexingo. Luna: It really does make a difference. And it's a small gesture that lets us keep digging into these specific, actionable stories without any sponsor constraints. Lucas: So let's talk about what happened when they introduced that checklist. The first month was rocky. Superintendents hated it — they saw it as another piece of paperwork that slowed them down. Luna: I can imagine. On a busy job site, five minutes can feel like an eternity when you're trying to keep the concrete truck from racking up idle charges. Lucas: Right, and the trucks charge by the minute. But the company president — a woman named Sarah Kline — didn't back down. She told the superintendents that if the checklist prevented just one rework event per quarter, it would pay for itself many times over. Lucas: And she was right. After six months, the data showed that pre-pour defects had dropped by 60 percent. The company went from about 25 percent of foundations needing some rework down to less than 10 percent. Luna: So what was actually on the checklist? I'm curious — was it just verifying the concrete mix design and the rebar size? Lucas: That was part of it. They had seven items. First, verify that the concrete mix design matches the approved submittal. Second, check the slump test before pouring — target was four inches plus or minus one. Third, confirm that the rebar is tied to the correct spacing and cover depth. Lucas: Fourth, inspect the formwork for tightness and alignment. Fifth, ensure that all embedded items — anchor bolts, conduits, sleeves — are in place and secured. Sixth, verify that the grade and elevation of the top of the foundation match the drawings. Luna: What's the seventh? Lucas: The superintendent signs off that the area is safe for the pour — no open excavations uncovered, all workers wearing PPE, and the concrete pump set up properly. That one wasn't about rework, it was about safety, but they included it because it reinforced the idea that this is a final go or no-go step. Luna: So it turned into a sort of pre-flight checklist for concrete. I love that. And did the resistance eventually fade? Lucas: It did, but not immediately. The breakthrough came when a superintendent caught a mistake on the formwork alignment that would have wasted an entire afternoon. He initialed the checklist, they fixed it, and the pour went smoothly. After that, word spread. Lucas: Within a year, every superintendent in the company was voluntarily using the checklist, and a few started creating their own for other trades — like a pre-drywall checklist and a pre-mechanical-startup checklist. Luna: That's the kind of organic adoption you can't force. It happens when people see the tool making their lives easier. Did they measure the financial impact? Lucas: They did. In the first year, they estimated that the checklist saved about $400,000 in direct rework costs — labor, materials, and concrete disposal. That's on a company with roughly $50 million in annual revenue. Luna: So almost one percent of revenue directly to the bottom line from a piece of paper. That's impressive. Lucas: It is. And what's interesting is that the savings actually grew over time. Because the checklist also helped improve communication between the superintendents and the subcontractors. The checklist forced a brief meeting before every pour, and that reduced other misunderstandings too. Luna: It sounds like the checklist became a coordination point, not just a quality check. That's a real operational win. Lucas: Exactly. And the broader lesson here is that you don't need a fancy software platform or AI to make a dent in rework. Sometimes the most effective tool is a well-designed, mandatory checklist that forces a pause before a critical step. Luna: I think we often overlook how powerful that can be because it's so low-tech. The airline industry has used checklists for decades, and construction is only now catching on in a systematic way. Lucas: Right. In fact, Dr. Atul Gawande wrote a whole book about checklists in medicine and showed that a simple surgical checklist reduced complications by 30-some percent in hospitals around the world. The same principle applies here. Lucas: So to sum up: one builder, one checklist, and a 60 percent reduction in rework on their biggest problem area. That freed up time and money that they could reinvest into training and better materials. Luna: And it probably made the work more satisfying for the crews. Nobody likes tearing out concrete they just poured. Lucas: Absolutely. I think the question worth sitting with is: what's the one critical process in your own work that could benefit from a similar pause and verify moment? It might be the simplest fix you never tried.