What Do Coordination Meetings Miss on the Issued PDF?
Helonic is an AI construction drawing analysis platform for general contractors and VDC teams who say their coordination meetings already catch drawing conflicts. "Our coordination meetings already catch this" is a fair objection. Weekly meetings with the trades and a federated model do catch a lot. They mostly catch what the model shows, though, and the contract documents are the issued PDF.
Direct answer. Coordination meetings resolve conflicts in the model, so they miss problems that live only on the issued PDF: wrong detail callouts, schedules that disagree with plans, notes that contradict specs, unmodeled consultant sheets, and late revisions. Helonic reads the issued set itself, sheet by sheet, so those reach the meeting before the set goes out.
Which problems get past the meeting?
| Miss | Why the meeting misses it | Example |
|---|---|---|
| Detail callouts that point to the wrong sheet or a detail that does not exist | Callouts are sheet annotations, not model geometry | Section 5/A-501 cut on the plan, but A-501 has only four sections |
| Schedules that disagree with plans | Nobody walks the door schedule in a clash meeting | Door 214 shown as a pair on the plan and a single leaf in the schedule |
| Notes that contradict the specs | The spec book is not in the model | Plan note says gypsum sheathing; spec section 06 16 00 calls for plywood |
| Consultant sheets that were never modeled | Civil, low voltage, and some specialty trades often issue CAD or PDF only | Site utility invert that conflicts with the plumbing building exit |
| Changes made after the last model export | The meeting coordinated last week's model | Duct resized on M-201 in the final issue, after the clash run |
None of these are clashes. They are document errors, and they become RFIs once a sub prices or builds from the PDF.
Why is the issued PDF different from the model?
Three reasons. Annotations, schedules, and general notes are added on sheets. Some consultants draw in CAD and issue PDFs that never enter the model. And the final issue often carries changes made after the last coordination export. Subs bid and build from the PDF, so that is the version that has to be right. What a 2D check covers next to a model check is in AI vs BIM clash detection.
Should the review replace the meeting?
Keep the meeting. Run the review on the issued set a few days before it, and sort findings into two piles:
- One discipline can fix it alone. Send it to that designer and keep it off the agenda.
- Two disciplines have to agree. Put it on the agenda with both sheets attached.
The meeting gets shorter because single-discipline fixes never reach it. Agenda prep is in how to prepare for a coordination meeting, and the wider pattern is in cross-discipline coordination.
How do you prove this to the VDC team?
Take a set that already went through coordination and was issued. Run it, and count the findings the team keeps that the meeting minutes never mention. If that count is near zero, your meetings are covering the PDF and you may not need the tool. Set that rule up front using how to pilot AI drawing review software. A VDC manager's likely objections are in what a VDC manager will challenge in the demo.
Where does Helonic fit before coordination?
Helonic reviews the issued PDF set, including detail cross-references, schedules against plans, and spec conflicts. Revision comparison catches what changed after the last model export. The full criteria for a review tool are in what to look for in an AI construction drawing review platform.
Practitioner insight
“We had the model clean. Zero hard clashes. Then the first RFI was a detail callout pointing at a sheet that didn't exist. That never shows up in Navisworks.”
Conversations with VDC managers at general contractors that run weekly model coordination meetings on commercial projects.
Frequently Asked Questions
What do coordination meetings miss on the issued drawings?
Why is the issued PDF different from the model?
Should AI drawing review replace coordination meetings?
When should the review run relative to the meeting?
Manas Gandhi
Co-founder & CTO, HelonicManas is the co-founder and CTO of Helonic, where he leads engineering and AI research for construction drawing analysis. He works directly with structural, MEP, civil, and fire protection engineers to translate the way they review drawings into AI systems that flag the issues that actually matter in the field. Before Helonic, he built machine learning pipelines for technical document understanding and has spent the last several years interviewing licensed design engineers and discipline leads to ground product decisions in real practice rather than industry assumptions.
- AI for technical document understanding
- Cross-discipline coordination workflows
- Code compliance automation (IBC, NEC, NFPA, IPC, IMC, ASCE)
- Structural and MEP drawing review systems
Last reviewed by Manas Gandhi · November 2026