By Greg Allan, tradesman and creator of Data First Coaching
Why do cracking callbacks hurt more than they look like they should?
A cracking callback on a render job costs a renderer twice: once in the crew hours spent on the original texture coat or acrylic render, and again in the crew hours spent back on site re-bagging, patching or recoating the same wall. The quote looked fine. The invoice looked fine. But the second visit is rarely billable, so those hours are paid for out of the business with nothing coming back in.
Picture a renderer who quoted a straightforward acrylic render finish on a two storey home, scaffold up, crew in for three days, job invoiced and marked done. Three weeks later a crack opens along a corner where the mesh wasn't lapped properly, and the crew goes back for half a day to patch and recoat it. The original job still looks profitable on paper because nobody has gone back and added that half day against it.
Most renderers track a job by whether the invoice got paid, not by how many hours the crew actually spent on that address from first scaffold to final sealer coat. A patch repair after cracking, or a recoat because the colour didn't cure evenly, gets absorbed into the cost of doing business rather than charged against the job that caused it.
Why can a renderer be fully booked and still losing money on cracking repairs?
A renderer can have scaffold up on every site and a full board of quotes and still post a loss once callback hours for cracking or patch repairs are counted properly, because being busy only measures the hours sold, not the hours actually spent delivering the job, including the ones spent fixing it.
Weather is the other half of this pattern. A run of good texture coat days, where render goes on clean and cures without drama, can be followed by a stretch lost to rain, recoat waiting time or humidity that makes cement render or acrylic render crack before it has fully cured. Zoomed out over a quarter, that boom followed by bust can cancel out what looked like a strong fortnight, especially if the callback hours it generates never get attributed to the jobs that caused them. A renderer who only checks the bank balance each month sees the dip but not where it came from.
What number actually shows where the profit is leaking?
The number that tells the truth is gross profit margin measured job by job, including every hour the crew spent on that address, not the margin the owner assumed was locked in when the quote was accepted. Checked at the moment of quoting, then checked again once the job, including any callback, is finished, it shows whether cracking repairs are a one off or a pattern eating a specific crew's jobs.
Memory says a job went fine. The data says how many hours were actually spent on it, including the patch visit when a crack opened along a control joint that wasn't detailed properly. Treating gross profit margin as a one off quote calculation misses this completely, because the margin that mattered was never the quoted one, it was whatever was left once every hour on that job, including the comeback, was counted. A renderer who reviews this margin regularly, not just at tender stage, starts to see which crews, which substrates or which weather windows are generating the callbacks that quietly wipe out the good jobs.
How can AI agents stop callback hours disappearing into the job cost?
You can use AI agents, software that does a job the way you would, with your own prices, wording and rules, to catch callback hours at the point they happen instead of losing them inside general costs. An agent built around your jobs can flag every return visit against the original job number, so a patch repair after cracking shows up against the job and crew that produced it, not against nothing.
This matters because the fix can't be a spreadsheet column you have to remember to fill in during a busy week on scaffold. It is an agent sitting quietly in the background, doing the attribution you never have time to do by hand, every time, the same way, using your own job numbers and pricing rules. Data first, this is what separates a renderer who finds out about a margin problem at tax time from one who sees it the week it happens, while there is still a job coming up where the price, the crew allowance or the weather buffer can be adjusted.
How should you price for the crew you actually have, not the crew you wish you had?
You price for the crew doing the work, not for how carefully you would do it yourself, because a crew that moves faster, trowels less evenly or doesn't always wait for full cure between coats will generate more cracking callbacks than you would on your own tools. A price built on your own best case will not survive contact with theirs.
This is where good, better, best pricing earns its keep on a render job. A base acrylic render finish, a texture coat with extra colour coats, or a job with foam cladding and extra mesh and sealer detail each carry a different real chance of cracking, and each should carry a margin that has already allowed for it, not a margin that assumes nothing goes wrong. Pricing per square metre around the crew you have, informed by what callback hours have actually cost on past jobs, means a run of cracking on one tricky wall doesn't quietly cancel out the margin earned on three straightforward ones.
How does Data First Coaching approach this?
Data First Coaching starts with the owner's own numbers, not a conversation about what happened. For a renderer, that means looking at job profitability, including every callback hour, crew by crew and job by job, through the Trade Business Intelligence, to find where cracking and patch repairs are actually starting, whether that's a substrate, a crew habit, a weather pattern or a pricing gap. Greg Allan built this after running his own trade business, and he often puts it simply: “Callbacks are massive and rework that you have to do because of mistakes. And you can't charge for them sometimes.” The how of fixing it, the agents, the pricing models, the attribution systems, gets worked through inside the Academy, with members, because the Trade Business Intelligence is powered by every member who is open minded, innovative and willing to share what they find.
