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.
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 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.
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.
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.
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.
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.
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.
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.
Three levels are enough. Five-level scales tend to collapse into arguments about the difference between a 3 and a 4.
| Level | Criteria | Examples | Must close |
|---|---|---|---|
| High | Life safety, code, structure, or a field fix that means demolition, coring, or a re-pour | Duct through a beam; equipment heavier than the slab live load; egress width short of code; sprinkler head under containment | Before the next issue, and before the affected pour |
| Medium | Rework or a field change with no safety exposure, still fixable on paper before the trade mobilizes | Outdoor air on the plan that does not match the mechanical schedule; door schedule that disagrees with the plan | Before that trade's shop drawings |
| Low | Documentation consistency with no effect on installed work | Sheet index typo; duplicate keynote; a callout pointing at the right detail with the wrong title | Next 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.
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.
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.
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.
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.
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
More on finding, sorting, and closing drawing coordination issues.
Where preconstruction risk concentrates across issue types and discipline pairs.
How evidence-backed RFIs get answered faster than a stack of vague ones.
Report structure, entry fields, owners, and status tracking.
A day-by-day plan where severity triage is Tuesday's job.