De-risk your project by tackling information uncertainty
“Which version is this?” If you hear that question, you know someone is already working from the wrong version of the design. DC+ grabs five minutes with Newforma vice-president of product marketing Dave Wagner to talk about version control, information certainty and risk.

DC+: Newforma’s recent survey found that 38% of construction professionals struggle with version control. Why does identifying the most current drawing or project document remain such a challenge?
Dave Wagner: Because the drawing is rarely in one place. A sheet gets issued from the design team’s server, attached to an email, uploaded to the contractor’s platform, printed for the trailer and marked up on someone’s tablet. Each copy looks official. Only one is.
In our 2025 survey, 70% of firms said they still rely on disconnected tools to manage project data. When a revision goes out, the old one doesn’t disappear. It keeps living in inboxes and download folders. File names don’t save you either. “A-201_rev3_FINAL_v2” tells you someone tried, but it doesn’t tell you whether an ASI replaced it last Tuesday. Storage isn’t the problem: it’s that nobody can see who sent what, when and what replaced it. Nobody has the full context.
Where do communication and information breakdowns most commonly occur between architects, engineers, project managers and contractors?
“Most schedule slips don’t start on site. They start when a drawing stalls between two people and nobody’s sure who has the current one.”
At the handoffs, almost every time. The biggest one is design to site. When drawings leave the architect’s or engineer’s environment and land in the contractor’s, the revision history often stays behind. RFIs and submittals are next. A question gets answered in an email or a quick call, the answer never makes it into the formal log, and the next person builds from the old detail.
Then there’s coordination between consultants. Structural, MEP and the architect each keep their own files, and a change in one set doesn’t flag the others. Email runs through all of it. It’s where decisions get made and where they get lost. In our survey, 73% of firms said they’re losing money to rework caused by miscommunication. Rework at that scale doesn’t come from one bad drawing. It comes from small gaps at every handoff.
Most schedule slips don’t start on site. They start when a drawing stalls between two people and nobody’s sure who has the current one. The signs show up in the logs weeks before they show up on the schedule. RFI response times start creeping past what the contract allows. Submittals come back for resubmission a second and third time. The same question arrives from two different people, which usually means the first answer didn’t reach everyone.
Listen for “which version is this?” in a coordination meeting. If people have to ask, some of them are already working from the wrong one. Site teams keeping their own printed sets is another tell. It means they’ve stopped trusting the system. In our survey, 77% of firms said they miss deadlines because of poor project information management. Those misses rarely come from one event. They come from a pile of open items nobody was watching.
How should project managers balance keeping work moving with making sure teams have accurate, approved information before proceeding?
I’d push back on the idea that it’s a trade-off. Speed and accuracy only fight each other when checking a document takes too long. If a supervisor has to call the architect’s office to confirm a detail is current, of course they’ll be tempted to build first and ask later. The fix is making that check take seconds, not making teams wait.
After that, sort the work by risk. Layout, embeds and anything that gets covered up or poured needs the current, approved document. Rework here is expensive and sometimes permanent. Lower-risk work can move ahead on a clearly flagged pending basis, as long as the project manager writes down the decision and who accepted the risk. What you can’t allow is guessing. Guessing is how a 20-minute question turns into a two-week tear-out.
What practical steps can firms take to reduce information-related delays and prevent small communication issues from becoming larger project setbacks?
Stop asking every partner to work in one system. It won’t happen. The contractor runs Procore, the owner wants Autodesk Forma, consultants send email, and your own team lives in Outlook and on the file server. The information already exists. What’s missing is the connection between it.
The tempting shortcut right now is to point an AI tool at all of it and let it sort things out. I understand why. But an AI agent can search your files. It can’t work out that an email thread triggered an RFI and that RFI changed a submittal, unless someone recorded that link somewhere. A lot of that record is missing to begin with. Our own product data suggests about 40% of project emails never get filed to the project.
AI can’t reason over what was never captured. When the data underneath is messy, AI doesn’t say “I don’t know.” It answers confidently from whatever it finds, including the drawing that was superseded three weeks ago. Autodesk and FMI estimated that bad data caused 14% of all construction rework in 2020. Pointing AI at that data just gets you to the wrong answer faster.
So, connect the record first. And stop treating document control as admin work. It’s how projects get delivered. Capture project email automatically and tie it to the project, so a decision made in someone’s inbox becomes part of the record the moment it’s sent. Link drawings, RFIs and submittals across the platforms your partners use, so a revision in one place shows up everywhere it matters. Set naming and revision standards at the firm level, not project by project.
Make overdue RFIs and outdated drawings surface on their own instead of waiting for someone to notice. Then AI becomes useful, because it’s working from information with context. Your firm has the information somewhere. The firms that avoid delays are the ones that give it context
Keep up to date with DC+: sign up for the midweek newsletter.