How to Catch Design Conflicts Before Construction Starts: A Step-by-Step Workflow

What is the workflow for catching design conflicts?

Use a repeatable workflow: confirm the drawing set, map shared spaces, compare architecture to structure, compare MEP to structure, check code and accessibility assumptions, then document every issue with owner and next action.

The order matters because early document errors can poison the rest of the review. If sheets are missing or revisions are mixed, every downstream conclusion becomes suspect.

What are the six steps?

1. Confirm the current sheet index, title blocks, and revisions. 2. Map high-risk spaces such as corridors, shafts, roofs, mechanical rooms, rated walls, and accessible routes. 3. Compare architectural layouts against structural grids, columns, foundations, and framing.

4. Compare MEP routing against beams, shafts, ceilings, and equipment supports. 5. Check IBC egress, ADA clearances, fire ratings, and fixture counts against the drawings. 6. Convert each confirmed conflict into an issue record with sheet, coordinates, severity, owner, and requested action.

Which conflicts get missed most often?

At schematic and DD phases, teams often miss missing rooms, incomplete equipment assumptions, and structural grid changes. At CD and IFC phases, teams miss schedule drift, detail callouts that no longer resolve, MEP clearances, and rated assembly conflicts.

The later the phase, the less tolerance the project has for vague notes. A 95% CD set needs production-level consistency because pricing and procurement decisions already depend on it.

How should teams prioritize design conflicts?

Prioritize issues by field cost and decision urgency. Life safety, structural conflicts, major MEP routing, long-lead equipment, and code items should come before drafting cleanup.

A useful triage structure is high, medium, and low severity. High-severity items can affect safety, code, cost, or schedule. Low-severity items may still matter, but they should not block decisions that affect procurement or mobilization.

How do findings become action?

Each issue should become one of three things: an internal correction, a coordination meeting item, or an RFI. The deciding factor is who owns the answer.

If the project team can resolve it internally, keep it in the issue log. If it needs cross-discipline discussion, put it on the meeting agenda. If it requires design clarification, write an RFI with the supporting sheet references.

What is the fastest way to catch design conflicts before construction?

The fastest way is to run a structured review before the team starts pricing, procurement, or mobilization decisions. Begin with sheet completeness, then compare architecture, structure, MEP, fire protection, accessibility, and code sheets in the areas where multiple trades converge.

Do not start with random markups. Start with spaces that are expensive to fix: shafts, corridors, rated walls, stairs, roofs, mechanical rooms, electrical rooms, ceiling plenums, utility entrances, and accessible routes.

Which design conflicts should become RFIs?

A design conflict should become an RFI when the contractor cannot answer it without design authority. Missing dimensions, conflicting rated-wall tags, MEP routes through structural members, schedule/spec mismatches, and code ambiguity usually need clarification.

Drafting cleanup, obvious internal inconsistencies, and minor notation issues can stay in a coordination log if the project team can resolve them without a formal design response.

How should a GC structure the issue log?

Use fields that survive handoff: issue title, discipline, sheet, coordinates, description, severity, owner, due date, recommended action, and RFI status. The log should answer three questions quickly: what is wrong, who owns the answer, and what happens next.

When AI produces the first-pass issue list, the human review step should accept, reject, combine, or escalate findings. This keeps the output usable instead of turning it into a pile of untriaged observations.

How Helonic Handles This

Helonic analyzes 2D PDF drawing sets for design conflict detection across coordination, code compliance, missing information, structural, MEP, fire safety, accessibility, constructability, dimensions, and QA/QC categories. Each finding includes a low, medium, or high severity rating and exact sheet coordinates so the reviewer can verify the issue quickly.

Teams can connect Procore or Autodesk Construction Cloud to pull drawings and push accepted findings as RFIs in one click. Most drawing sets finish analysis in about 30 minutes, with no BIM or 3D model required.

FAQ

Key takeaways

• Start conflict review in high-cost shared spaces.
• Separate true design questions from drafting cleanup.
• Use severity and ownership to avoid dead issue logs.
• AI is strongest as first-pass coverage before human triage.
• Helonic helps turn 2D drawing conflicts into located review items.
• Design conflict review needs a fixed workflow.
• Start with sheet completeness and revision control.
• MEP and structural conflicts deserve early attention.
• High-severity issues should move to RFIs or meeting agendas quickly.
• Helonic can produce a first-pass issue list from 2D PDFs.