Drawing QA/QC

Find issues in review, not in the field.

Archiboost checks entire multidisciplinary drawing and specification packages for coordination, compliance and constructibility issues, so problems are fixed before they reach the field.

Get a quote
Riverside Tower
Issues on A-201
1 of 4

Corridor clear width below 44 in. minimum

A-201 · Level 2 plan
A-201 · T-518High

Corridor too narrow for its occupant load

Corridor is 36 in. clear and serves 60 occupants. CBC Table 1020.3 requires 44 in. at 50 or more.

Recommendation

Widen to 44 in. clear and check door swings against CBC 1005.7.1.

AssignOpen in Revit
Interactive preview

4 issues found on A-201

Select a ticket to see its location and recommendation.

How it works

From drawing set to actionable review

01

Upload the package

Upload drawings, specifications or other project documents manually, or connect to where they live in Autodesk Forma or Procore.

Submit · Riverside Tower
  • Revit

    100% DD Architectural Set.pdf

    128 sheets · 214 MB · Revit

  • Procore

    Structural Set.pdf

    74 sheets · 96 MB · Procore

  • Autodesk Forma

    Project Specifications.docx

    Supporting document

Start reviewImport from Procore · Autodesk Forma
02

AI reviews everything

Coordination, compliance and constructibility problems are surfaced across the entire package in a single pass, no matter where they occur.

142 sheets · pass 2 of 207:42
  • Cross-sheet coordinationComplete
  • Code and accessibilityComplete
  • Specs and schedulesComplete
  • Firm standardsRunning
03

Resolve findings in context

Issues are marked up directly on your documents with relevant citations, making resolution simpler and faster.

A-401 · T-531Critical

Door D16 vision lite sill above accessible max

ICC A117.1 §404.2.10 · lower lite to 3'-7" or less

AssignOpen in Revit
What we review

Comprehensive review across contract document packages

Archiboost checks entire packages, not just individual pages, finding conflicts across drawings, schedules, specifications, codes and custom project standards, so problems are fixed before they become rework.

01 / 04

Drawing coordination

Example review note

Coordinate minimum door head height with structural brace frame elevations.

02 / 04

Code compliance

Example review note

Provide safety glass at all doors and adjacent lites within 24 inches and above 60 inches.

03 / 04

Firm standards

Example review note

Reduce ADA ramp slopes to 7.5% to ensure built result is within construction tolerances.

04 / 04

Specifications & materials

Example review note

Provide Electro Static Discharge (ESD) flooring in all IDF rooms to prevent damage to telecom equipment.

New featureWeekly coordination

A weekly coordination report, ready Monday.

Every Friday evening, Archiboost collects the latest consultant drawings and extracts your Revit model. It checks the full set for cross-discipline coordination issues, then sends your team a report Monday morning with findings linked to the source drawings.

Friday drawingsMonday report
From project teams

What teams are finding with Archiboost

50K+

Drawing sheets reviewed

100K+

Compliance, coordination and constructibility issues identified

Common questions

What to expect from a review

How does this make review easier?

The review brings possible issues and their source sheets into one place. Your team can verify findings, prioritize them, and move confirmed changes into its markup or Revit workflow.

How is it different from a general chatbot?

It is built for drawing sets and specifications: it compares information across sheets, points to the source of a finding, and supports a review workflow rather than a standalone chat answer.

Do we still need a human reviewer?

Yes. Archiboost supports QA/QC; it does not replace the architect of record. Architects and project teams assess the findings and remain responsible for the professional review and final decisions.

Can it handle code exceptions or variance requests?

It can surface code concerns and citations for your team to investigate. Confirm the applicable jurisdiction, interpretation, exceptions, and any variance strategy with your code specialist or authority having jurisdiction.

Catch errors early,

not in the field.