The Problem

Manual compliance review is the most expensive bottleneck in architecture.

Building code compliance is handled manually by architects who spend 20 to 30 percent of project time on cross-referencing IBC chapters, local amendments, and accessibility requirements. A non-conformance discovered at permit stage does not cost a note in the margin - it costs months. Redesign. Resubmittal. Re-review. In complex projects, a single flagged issue at the wrong stage can unravel work that took a quarter to produce.

The status quo is reading 700-page documents against drawing sets, line by line, by hand. Architects are exceptionally good at this - but it is slow, inconsistent across reviewers, and dependent on institutional knowledge that is not always documented. When a firm grows, when a project moves to a new jurisdiction, when the code version changes mid-design, the manual process breaks down in ways that are hard to detect until the AHJ tells you about them.

The software solutions that existed before Meridian were fundamentally misdesigned. They were rule lookup tables - databases of code requirements that users queried manually, or that surfaced keywords in documents. That is not compliance review. That is a search function in a regulatory PDF. It does not read drawings. It does not understand spatial relationships. It does not know that a corridor width is measured from finish face to finish face, not from framing.

What Meridian Does

Document understanding, not keyword matching.

Meridian is built around a distinction that sounds simple and changes everything: it reads drawing sets, it does not search them. Reading means understanding the spatial logic of a building, the relationships between elements, the intent encoded in dimensions and notes. Searching means finding the word "corridor" and returning a list of code sections that mention corridors.

Document Parsing

Reads drawing sets natively - DWG, PDF, and Revit exports. Builds a semantic model of the building from the drawing set: spaces, egress paths, occupancy classifications, structural elements, accessibility routes. Does not require drawings to be pre-annotated or formatted for software consumption.

Code Cross-Referencing

Cross-references IBC 2021, state amendments, and local ordinances simultaneously. Maintains a current, jurisdiction-specific code database updated as amendments are adopted. When jurisdictions diverge from the model code, Meridian resolves the conflict correctly - not by flagging it as ambiguous, but by applying the correct hierarchy.

Flag Generation

Categorizes non-conformances by severity (critical, advisory, informational), by code division (structural, fire protection, accessibility, egress, mechanical), and by resolution complexity. Every flag includes the specific code section, the precise location in the drawing set, and a plain-language description of what the resolution requires.

Audit Trail

Generates a compliance summary document that documents what was reviewed, what was flagged, what was resolved, and when. The summary is structured for AHJ submission and provides a defensible record of compliance review. Architecture firms have used Meridian audit trails to substantially accelerate permit review timelines.

Results

60%

Faster Review

Measured across 340+ firms - the average time from drawing set upload to compliance review completion, compared to the same firms' prior manual review timelines. The variance is large; complex projects with multiple jurisdictional amendments see the biggest gains.

340+

Firms Onboarded

Architecture firms actively using Meridian on permit-track projects. Ranges from 4-person residential practices to firms with 200+ staff on mixed-use commercial and institutional work. The common thread is active permit volume - Meridian is built for firms where compliance review is a recurring cost, not an occasional one.

98.2%

Flag Accuracy

Flags validated against AHJ review outcomes across a sample of submitted projects. A flag is accurate if it corresponds to a non-conformance that the AHJ would have identified, or correctly clears an element that would have passed review. The 1.8% represents flags that were disputed or required human judgment to resolve - Meridian shows a confidence score on every flag.

Who It's For

Built for practices where compliance is a recurring project cost, not an afterthought.

Meridian is not a compliance checklist for infrequent users. It is a professional tool for firms and individuals who review building code compliance on active projects, regularly, and for whom the cost of a late-stage non-conformance is real and consequential.

- Architecture firms with active permit work. The primary user. Firms that produce drawing sets for permit submission and need compliance reviewed before submission - not at submission. Meridian integrates into the design development and construction document phases, where corrections are still cheap.

- Compliance officers and plan examiners. Individuals responsible for reviewing drawing sets for compliance, whether in-house at larger firms or as independent consultants. Meridian does not replace professional judgment - it provides a comprehensive first pass that humans can review, modify, and approve.

- Project managers on mixed-use and institutional projects. Complex projects with multiple occupancy classifications, multiple jurisdictional requirements, and long permit timelines. Meridian's ability to track compliance across a project as drawings evolve - re-running review when sheets change - is particularly valuable in these contexts.