If you have been following this blog series, you already know the story about the client who nearly filed a lawsuit over a decision nobody wrote down. That story was about a conversation. This one is about something worse: a problem everyone saw coming and nobody closed out.
I was working for the HVAC firm on a mid-rise project when a wall came down during demo and exposed a concrete column that was not on the drawings we had been coordinating from. Our super pointed it out to me. It sat right where a main duct run was planned. Someone mentioned it in passing, the general contractor said they would look into it, and the conversation moved on. No one opened a formal issue. No one assigned it to anyone. Weeks later, framing had gone up around the column and the duct run had to be rerouted through a finished wall. That rework added real cost to the project, all of it avoidable. This was 25 years ago, long before mobile apps and construction management platforms existed. A tool like Autodesk Build's Issues feature would not have caught the column itself, someone still has to spot a problem in the field, but it would have sped up everything that happened after. Instead of a conversation that quietly dissolved, that column could have been logged, assigned, and tracked to close out in days instead of weeks. Back then, all we had was a conversation and a shared assumption that someone else had it handled.
What strikes me looking back is that nobody on that project was careless. The super caught the conflict. The GC acknowledged it. Everyone did their part in the moment. What the project did not have was a system that carried the problem forward after the conversation ended. There was no place for that column to live except in the memory of whoever happened to be standing there, and memory is not a project management tool.
Construction still generates the same kinds of problems today that it did 25 years ago. Clearance conflicts, undocumented conditions, damaged materials, safety hazards, quality defects. What has changed is that a project no longer has to rely on someone remembering to follow up. The Issues tool in Autodesk Build gives a problem like that column a permanent home the moment it is found. It gets logged with a location, a type, a priority, prioritized in a meeting or documented in an email, and assigned an owner. It gets tied to the plan sheet or the model where it actually exists, not buried in a conversation that only two people heard. It has a status that moves from open to answered to closed, and every step is timestamped and visible to the whole team. Nothing gets to hide in someone's memory anymore, because nothing has to.
The value shows up in two places. The first is speed after discovery. Someone in the field still has to spot the problem, a tool cannot do that part. But once a condition like that exposed column is found, logging it immediately on the mobile app, with a photo and an issue, before it gets buried under the next fifteen conversations of the day, means the team can move on it while it is still cheap to fix. A conflict flagged and assigned right after framing starts is a short conversation and a quick reroute. The same conflict left undocumented until after framing closes around it is a demo and rebuild.
The second is accountability. An issue with a named owner and a due date behaves differently than a problem mentioned in passing. People close out what is visibly assigned to them. On a project running formal issue tracking, a condition like that column gets flagged, assigned, and resolved in days, not left to resurface weeks later as a surprise.
What makes the tool worth a closer look is that its use does not stop at problems. Issues in Autodesk Build are just as effective for identifying, documenting, and tracking a physical defect through to resolution as they are for assigning day to day work. A project manager can use the same tool to hand a task to a key employee or a specific team, set a due date, and track it through to completion with the same visibility as a clearance conflict. It becomes less a defect log and more a general purpose accountability tool, one that happens to be equally useful for chasing down a construction problem or making sure a task assigned on Monday does not quietly slip through the cracks by Friday.
The broader point applies beyond any one piece of software, and it applies now more than it did 25 years ago, because the tools to solve it finally exist. Every project has a way that problems get raised and a way that problems get resolved. If those two things are not clearly connected, and visible to everyone on the team, the project is running on hope. Hope that the super remembers. Hope that the GC follows up. Hope that nobody is quietly assuming someone else has it covered. Hope was all we had on that project 25 years ago. It does not have to be all a project has today.
If your team wants hands on training in Autodesk Build, Cedar Rock Consulting can help you get there. Visit cedar-rock.net to learn more.