How StructionSite Reduces Rework Through Automated Site Capture | StructionSite

Reducing Rework: A Key StructionSite Value-Add

October 22, 2019

Chris Jervey

StructionSite is deeply committed to customer engagement. We prioritize truly listening to the feedback (good and bad) we get from the people that use our application every day. We are constantly looking to better understand and define the places that we create real value for our customers. That could be anything from time savings in the field on a specific project or money savings that the enterprise sees as a result of more comprehensive implementation across many projects or business units. 

Adding value by slashing rework

One of the most consistent themes we’ve heard from our users is that StructionSite is providing huge value in the area of reducing rework. Thinking broadly, of course, this makes sense. 

StructionSite provides project teams with the time and location context they need to find all sorts of different construction elements, usually long after those elements have been hidden by other construction elements like wallboard or concrete slabs. With the comprehensive, contextual documentation our application provides, everyone from project owners to subs stays on the same page. This minimizes the need to go back and fix an issue someone spotted too late. 

We knew that this would help projects run more smoothly by avoiding glaring issues. For example, one of our customers recently told us about a leak they found that could’ve caused far greater trouble and incurred much higher costs had they not used StructionSite to quickly locate the source of the leak and minimize rework. We anticipated our tool being used to avoid those types of large-scale headaches. 


Saving hours, cutting costs

What we didn’t expect was the total volume and frequency of this avoided rework. And it wasn’t just big things, like fast leak location and questions about MEP systems installations. It was the little things, too, like the tens of buried outlets on each project and find out whether or not backing had been installed. 

Without photos, teams are stuck making large holes to locate those outlets or that backing, and then spend unnecessary time and money repairing those newly damaged areas. Without context-based photos (like the ones StructionSite provides), teams spend way too much time digging through photo albums or folders or, even worse, various devices to locate those important pieces of visual information.

Everyone wants to use site documentation to avoid the big mistake —, and we have certainly heard our share of stories where we’ve helped minimize big damage. Recently, one of our customers told us about a leak they found that could’ve caused far greater trouble and incurred much higher costs had they not used StructionSite to quickly locate the source of the leak and minimize rework. But let’s not forget the many little things that slowly but surely add up to big hours and big costs.