Helonic

How to Prioritize Drawing Coordination Issues by Severity

Helonic is an AI construction drawing analysis platform for coordination leads who need to triage drawing issues by severity. A four-question triage method for sorting a long list of drawing conflicts, and how a severity rating with a page location speeds it up.

Prioritizing drawing coordination issues by severity means sorting every conflict in a set by what it puts at risk, life safety first, then cost and schedule, then trade sequence, so the design team fixes the dangerous and expensive items before the cosmetic ones. Helonic, an AI construction drawing analysis platform, rates every finding on a 2D PDF set high, medium, or low and pins it to a page location. This article covers the triage method a coordination lead applies on top of that first rating.

It sits next to two related pieces. Our preconstruction risk findings show where conflicts concentrate across 1,000+ reviews, and RFI quality vs. RFI volume covers how to write the question once you know which issue matters. This one is about the order you work the list.

Quick answer

To prioritize drawing coordination issues by severity, rank each one on four questions: does it touch life safety or code, what does it cost if found in the field, which trade builds first, and who owns the fix. Helonic rates every finding high, medium, or low with exact page coordinates, so the team starts from a sorted list instead of sheet order.

A raw issue count tells you nothing about what to fix first

A full-set review on a large job returns hundreds or thousands of items. On an 800-sheet data center campus, Helonic listed more than 2,100 issues for an owner's rep team of two people with two weeks. The 156 floor-loading conflicts in that list were estimated at $890,000 in change orders if they had surfaced after the slab pour. Read in sheet order, those 156 would have been scattered among sheet-index typos.

BIM coordination tools learned this years ago. Navisworks sorts clash results by severity by default, and Solibri's own clash detection guide gives the example that a small pipe through a bearing wall ranks below a large duct crossing a major beam. A PDF review needs the same discipline, and it needs a method that holds up when two people disagree.

Question 1: Does it touch life safety or code?

If yes, it starts as high and stays high until the design team resolves it. These are the issues that can stop a permit, fail an inspection, or hold up occupancy regardless of what they cost to fix.

  • Egress. Corridor and stair widths, door swing, travel distance, and exit counts under IBC Chapter 10.
  • Fire-rated assemblies with unprotected penetrations, or a rated wall on the life-safety plan that the architectural plan draws as non-rated.
  • Sprinkler coverage blocked by something another discipline drew. The data center set had 89 heads sitting below hot-aisle containment panels.
  • Accessibility clearances at doors, toilets, and counters.
  • Anything in the structural load path, such as a beam landing on a wall another sheet shows as open.

Helonic's fire and life safety checks and code compliance category cover most of this list on the PDFs, and every hit carries its sheet and location so a reviewer can confirm it in a minute.

Question 2: What does it cost if it is found in the field?

Price the field fix, not the drawing fix. Almost every coordination issue is a cheap edit on paper. What separates high from medium is what has to be torn out, re-ordered, or re-poured if nobody catches it until the work is in place.

On a custom home in the Miami area, a finished floor elevation that disagreed with the flood-zone site plan was estimated at about $25,000 in pour and grading rework if found after slab work started. A beam landing on a wall drawn as open great room was about $12,000 after framing. Both were one-line fixes before construction. A useful rule of thumb: structure and anything embedded in it outranks overhead MEP, which outranks finishes.

Question 3: Which trade builds first?

Sequence can promote an issue even when the dollar figure is small. A sleeve missing from a slab pour scheduled for next week has to be answered this week. A ceiling conflict on a floor that will not see drywall for four months can wait for the next revision.

  1. Below grade, foundations, and underslab utilities
  2. Structure, slab penetrations, and embeds
  3. Risers and overhead MEP mains
  4. Branch ductwork, piping, and conduit
  5. Ceilings, partitions, and finishes

Overlay that order on the project schedule and a medium item on step 2 often belongs above a high item on step 5. The coordination lead makes that call. Software does not know your pour dates.

Question 4: Who owns the fix?

An issue with a clear owner moves. An issue between two consultants sits until someone decides whose sheet changes. Tag every high and medium item with the design firm that owns the sheet, and pull the two-owner items into the next coordination meeting as decisions, not RFIs.

On a 340-sheet mixed-use tower drawn by four firms, the critical items went into Procore as RFIs tagged to the firm that owned each sheet, and the team issued 127 RFIs in one batch instead of over several weeks. The clash detection report guide covers the owner and status fields that make this tracking work.

A three-level severity matrix you can use on Monday

Three levels are enough. Five-level scales tend to collapse into arguments about the difference between a 3 and a 4.

LevelCriteriaExamplesMust close
HighLife safety, code, structure, or a field fix that means demolition, coring, or a re-pourDuct through a beam; equipment heavier than the slab live load; egress width short of code; sprinkler head under containmentBefore the next issue, and before the affected pour
MediumRework or a field change with no safety exposure, still fixable on paper before the trade mobilizesOutdoor air on the plan that does not match the mechanical schedule; door schedule that disagrees with the planBefore that trade's shop drawings
LowDocumentation consistency with no effect on installed workSheet index typo; duplicate keynote; a callout pointing at the right detail with the wrong titleNext scheduled revision

Apply questions 1 and 2 to set the level, then use questions 3 and 4 to order items inside each level. That keeps life safety at the top without letting a low-cost slab sleeve fall behind a ceiling clash.

How do Helonic's severity ratings feed the triage?

Helonic does the first sort so people spend their time on questions 3 and 4. It reads every sheet of the 2D PDF set and gives each finding a severity (high, medium, or low), one of ten categories from coordination and code compliance to dimensions and QA/QC, and exact page location coordinates. The 2D clash detection findings and the code compliance findings are the place to start working the high bucket, since structure-MEP and life-safety conflicts live there.

  • On a three-school K-12 bond package of more than 1,200 sheets, QA/QC sorted the 841 findings by severity and building, so senior staff reviewed only the locations that needed a correction.
  • On the tower, the team confirmed 94% of 847 findings as real problems and dismissed the remaining 6% as low-confidence items.
  • High items go to Procore or Autodesk as RFIs in one click through RFI generation, with the sheet reference attached.

Treat the rating as the first cut. A reviewer still adjusts it with what the drawings cannot show: the pour schedule, the contract, and decisions the owner already made. How AI handles borderline flags is covered in AI drawing review false positives, and the full review method is in how to review construction drawings.

Four triage mistakes that bury the real issues

  • Working the list in sheet order. A-series problems get fixed first because they are on top, and the MEP conflicts wait.
  • Letting the loudest trade set priority in the meeting.
  • Counting issues per discipline and calling the biggest number the worst discipline. Fifty low items are less urgent than one high one.
  • Never re-rating. A medium item becomes high when its trade starts shop drawings, and stale ratings stop meaning anything to the field.

If you are triaging a large set on a deadline, the 500-sheet PDF coordination plan puts this method on day two. For background on how AI review produces the list in the first place, see AI for construction drawings.

Practitioner insight

“The first thing I do with a long list is find anything that touches a pour in the next three weeks. Doesn't matter if it's rated medium. If the slab goes in Thursday and the sleeve isn't on the drawings, that's my top item. The severity rating gets me most of the way there, and the schedule does the rest.”

Source: Conversations with MEP coordination managers and GC project engineers who triage Helonic findings before weekly coordination meetings on podium and mid-rise projects, synthesized from Helonic's field interviews, Q3 2026.

Drawing Issue Severity FAQ

What makes a drawing coordination issue high severity?
An issue is high severity when it touches life safety or code, affects the structure or its load path, or would need demolition, coring, or a re-pour to fix once built. Egress width, a fire-rated wall with an unprotected penetration, a sprinkler head blocked by containment, and a duct drawn through a beam are all high. So is anything that sits on the critical path of the next pour, even if the fix on paper is small.
Should code issues always outrank cost issues?
Life-safety and code issues go first because they can stop a permit, an inspection, or occupancy no matter what they cost to fix. Inside the high bucket, sort by when the affected work gets built. A code issue on a finish detail six months out can wait a week; a slab penetration conflict before Thursday's pour cannot.
Who should set severity, the reviewer or the software?
Both, in order. Software gives a consistent first rating based on what the issue is. The reviewer adjusts it with project facts the drawings do not show: the schedule, the contract, which trade has mobilized, and whether the owner already accepted a condition. Helonic's high, medium, and low ratings are a starting point for that adjustment.
How does Helonic rate severity on drawing issues?
Helonic reads the full 2D PDF set and assigns every finding a severity of high, medium, or low, one of ten issue categories (coordination, code compliance, missing information, structural, MEP, fire safety, accessibility, constructability, dimensions, and QA/QC), and exact page location coordinates. High-severity findings can be pushed to Procore or Autodesk as RFIs in one click.
How often should drawing issue severity be re-rated?
Re-rate after every revision and every time the schedule moves. An issue rated medium in design development can become high when the trade it affects starts shop drawings, and a high item can drop once the design team issues a sketch that resolves it. Ratings that never change stop meaning anything to the field.
MG

Manas Gandhi

Co-founder & CTO, Helonic

Manas 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.

Areas of focus
  • AI for technical document understanding
  • Cross-discipline coordination workflows
  • Code compliance automation (IBC, NEC, NFPA, IPC, IMC, ASCE)
  • Structural and MEP drawing review systems

How this page was researched: Triage questions reflect how coordination leads sort findings on Helonic reviews of issued 2D PDF sets. Project figures come from Helonic's published case studies. Severity handling in BIM tools is cited from Autodesk's Navisworks 2026 Clash Detective documentation and Solibri's clash detection guide; egress requirements reference IBC 2024 Chapter 10.

Last reviewed by Manas Gandhi · October 2026

Start triage from a sorted list

Helonic reads every sheet and rates each finding high, medium, or low with its page location, so your team spends the week on decisions instead of sorting.