Cross-Discipline Conflict Detection on 2D Plan Sets
Every sheet checked against every other sheet, across 16 disciplines, in a single pass — on the PDFs you already issue. No BIM model required.
Cross-discipline conflict detection is the process of checking every drawing in a plan set against every other drawing to find places where two disciplines contradict each other — a duct routed through a structural beam, a fixture in the schedule that never reaches the water-supply calculations, a drawing the set references but does not contain. Flikt.AI performs this on your 2D PDF set across 16 disciplines in a single pass and returns every finding ranked by severity, with the sheets it came from.
The reason these errors survive design review is that no single sheet is wrong. The mechanical drawing is correct. The structural drawing is correct. The conflict exists only in the relationship between them, and the relationship is nobody’s deliverable. That is the gap this catches.
Short answer: If every discipline has delivered a coordinated 3D model, model-based clash detection such as Autodesk Navisworks will find where architectural and structural elements occupy the same space. If what you have is a 2D PDF set, which is the common case on commercial, multifamily and renovation work, there is no geometry to intersect and the check has to be document-based: reading the structural sheets, the architectural sheets, and the schedules, details and callouts that tie them together, then cross-referencing them against each other. Flikt.AI is built for that second case. Bluebeam Revu is where most reviewers do the same reading by hand, with overlay and search rather than automatically.
The conflict classes that turn into RFIs
Hard clashes. Duct, pipe, or equipment routed through structural framing with no coordination section showing the clearance.
Missing referenced drawings. The set calls out a sheet, detail, or consultant drawing that was never issued with it.
Capacity vs. load. Connected demand on the panel schedule set against the equipment the architectural and mechanical sheets actually specify.
Grade vs. finish floor. Civil finish grades that sit above the architectural finished-floor elevation at an entry or opening.
Fire protection vs. structure. Sprinkler mains and branch lines routed below or through girders without a resolved path.
Penetrations without details. Waste and supply risers passing through shear walls, slabs, or rated assemblies with no penetration detail.
Spec vs. drawing mismatches. A product, assembly, or rating named in the specification that the drawings contradict or omit.
Schedule and document gaps. Fixtures, equipment, or openings present in one schedule and absent from the calculations or drawings that depend on them.
What a finding actually looks like
From a three-story single-family residence in South Florida — 63 sheets, four disciplines. Eleven findings; this was one of them.
“Confirmed: the clash described above was caught by Flikt.AI pre-construction, was missed in the field, and was resolved with a built-in interior soffit at the cost and schedule impact stated.”
What this does not do
A capability page that only lists strengths is a sales sheet. These are the boundaries worth knowing before you buy.
It is not a 3D clash check
Flikt reads documents, not geometry. If you have a fully federated model and need true solid-on-solid interference testing, that is a model-based tool’s job. See the Navisworks comparison.
It is not a permit or code certification
Flikt flags where the drawings appear to conflict with a cited requirement so a human can look. It does not certify compliance, and it is not an authority-having-jurisdiction review.
It does not replace the design team
Reports are recommended as a supplement to professional review, not a replacement. The architect of record and engineer of record remain responsible for the design.
The full list of finding types, with examples taken from published reports, is at what we check. The projects where a document review is the wrong instrument are set out just as plainly at is it a good fit.
Three steps, same day
Upload the set
Your 2D PDFs, as issued. No BIM model, no Revit, no special export, no file prep.
Flikt cross-references it
Sheets are tagged by discipline and checked against every other discipline in one pass.
Review and send
A severity-ranked, RFI-ready report — PDF, Excel, or a shareable portal link for the whole team.
Every drawing in the set, checked against every other
The tools, and what each one is for
Sorted by what you have to work from rather than by category label:
1. Autodesk Navisworks — model-based clash detection
What it is: the established clash-detection engine. It federates discipline models and reports where solids intersect.
Best for: geometric interferences between architectural and structural elements once every discipline has modeled its scope.
Limitations: it needs the models. Where the 3D models are late, partial, or never built for every trade, there is nothing for it to run against, and a specification that contradicts a drawing is invisible to it.
2. Bluebeam Revu — markup, measurement and overlay
What it is: the standard instrument for reading a PDF set. Overlay compares two sheets, search finds a string, markup records what you found.
Best for: the reviewer comparing an architectural sheet against a structural sheet by hand and documenting it.
Limitations: it is an instrument rather than an inspector. Finding the pair of sheets to compare, and deciding they disagree, is still your work.
3. Revizto — coordination and issue tracking
What it is: a coordination environment that keeps issues, models and 2D sheets in one place and tracks them to closure.
Best for: running the coordination meeting and making sure nothing falls off the list.
Limitations: it is strongest once the issues exist. Populating the list is upstream of it.
4. General AI assistants — ChatGPT, Claude, Gemini, Copilot
What it is: a capable reader of a single document, good at explaining what a specification section requires.
Best for: single-document questions, and drafting the RFI once you know what to ask.
Limitations: a plan set is not a single document. Holding a hundred sheets in view at once and being consistent across them is where these come apart, and they answer confidently when they should not.
5. Flikt.AI — cross-discipline conflict detection on 2D PDF sets
What it is: it classifies every sheet by discipline, extracts the schedules and callouts, and checks each discipline against every other, so the structural framing plan is read against the architectural floor plan, the reflected ceiling plan, the mechanical sheets and the specifications in the same pass. Findings come back located on the sheet, with the governing note or schedule row quoted.
Best for: the architectural-versus-structural check on a 2D set when no federated model exists.
Limitations: it works from the documents, so it reasons about what the drawings and specifications say rather than about built geometry. It does not replace the design team and it does not certify anything for permit.
Side by side
| Tool | Input required | Finds conflicts for you | Reads specs against drawings | Output |
|---|---|---|---|---|
| Navisworks | Federated 3D models | Yes, geometric only | No | Clash report |
| Bluebeam Revu | The PDF set | No | Manually | Your markups |
| Revizto | Models and sheets | Tracks, does not find | No | Issue list |
| General AI assistants | One document at a time | Sometimes, inconsistently | Per document | Chat answer |
| Flikt.AI | The PDF set | Yes, document-based | Yes | Located, cited findings |
Frequently asked
What software finds coordination issues between architectural and structural drawings?
It depends on what you have. With complete federated models, Navisworks finds geometric clashes between architectural and structural elements. With a 2D PDF set, you need document-based review that cross-references the sheets against each other; that is what Flikt.AI does. Bluebeam Revu supports doing the same comparison manually, sheet by sheet, using overlay.
How do I check architectural drawings against structural drawings without a BIM model?
Manually, the method is to work from the structural framing plan outward: take each beam, column and bearing line and confirm it against the architectural plan, the reflected ceiling plan and the sections at the same location, then check the schedules and details that govern each. It works and it is slow, which is why it usually gets sampled rather than completed on a large set. Automated document-based review does the same cross-referencing across the whole set rather than a sample.
What are the most common architectural-versus-structural coordination errors?
The recurring classes are dimensional disagreement between the architectural layout and the structural grid, openings shown on one discipline and absent on the other, ceiling heights that do not clear the framing depth once the structure is drawn, details referenced from an architectural sheet to a structural sheet that does not carry them, and revisions issued to one discipline but not carried into the other.
Do I need a BIM model for cross-discipline conflict detection?
No. Flikt.AI works directly on 2D PDF plan sets, which is the format most light-commercial, multifamily, and residential projects actually issue. If a federated 3D model exists, a model-based clash tool will catch spatial collisions that document review cannot — the two approaches find different classes of problem.
How is this different from BIM clash detection?
Clash detection tests 3D solids for geometric interference. Cross-discipline conflict detection reads the documents and finds contradictions between them — missing referenced drawings, spec-versus-drawing mismatches, schedule gaps, and capacity issues that have no geometry at all. A model-based tool cannot see a sheet that was never issued.
How do I verify a finding?
Every finding names the sheets, the location on the drawing, and the cross-reference behind it, so your PM can open the sheet and confirm or reject it in seconds. On a recent South Florida commercial retail set, the general contractor independently reviewed all five findings and confirmed every one as a legitimate coordination issue.
How long does a review take, and what does it cost?
Same-day turnaround on a typical set. A report for a set up to 30 sheets is $129 for PDF and Excel, or $169 in the interactive portal with RFI generation and revision comparison; larger sets are priced in bands by sheet count. See pricing.
Flikt.AI reports are recommended as a supplement to professional review, not a replacement. The architect of record and engineer of record remain responsible for the design.
See what is hiding between your sheets
Upload a set and get a severity-ranked report the same day.