System Architecture

How It Works

From project intake to approval-ready output. A deterministic compliance validation pipeline with full audit trails and code-level citations.

Normiz operates as a structured compliance validation system. Every check traces back to a specific code section, local amendment, or jurisdiction requirement. Every output includes the rule ID, source document, and reasoning chain.

The system does not make judgment calls. It applies rules from a curated regulatory database to your project parameters and documentation, then reports what passes, what fails, and exactly why.

Jurisdiction Resolution

The system identifies which regulatory authorities govern your project based on location, scope, and trade type. This determines which code editions, local amendments, and special requirements apply.

  • Geographic mapping to AHJ (Authority Having Jurisdiction) boundaries, including municipal, county, and state overlays
  • Code edition identification: NEC 2023, FBC 8th Edition, local amendments with effective dates
  • Special district detection: flood zones, historic districts, coastal construction control lines, and overlay requirements

Requirements Assembly

Based on the resolved jurisdiction and project scope, the system assembles the complete set of applicable requirements. This includes permit application items, required attachments, and code compliance criteria.

  • Permit checklist generation with jurisdiction-specific forms, fees, and submission requirements
  • Attachment requirements: plans, specifications, calculations, product data, certifications
  • Code criteria extraction for the specific work scope, with rule IDs and section references

Document Analysis

Submitted documents are parsed and indexed. The system extracts relevant data points, identifies document types, and maps content to the requirements framework.

  • Document classification: plans, specifications, calculations, product data, certifications
  • Data extraction: equipment specifications, load calculations, material ratings, dimensions
  • Cross-reference mapping between submitted values and requirement thresholds

Deterministic Validation

The system executes compliance checks by comparing extracted data against requirement criteria. Each check produces a pass/fail result with the specific rule applied.

  • Rule-based checks: each validation tied to a specific code section (e.g., NEC 210.52(A))
  • Conflict detection: identifies contradictions between submitted documents or with code requirements
  • Gap identification: flags missing documentation, incomplete data, or unaddressed requirements

Citations & Fix Guidance

For each issue identified, the system provides the exact code reference, explains the requirement, and specifies what action resolves the issue.

  • Code citations: exact section numbers, edition year, and jurisdiction-specific amendments
  • Requirement explanation: plain-language description of what the code requires and why
  • Resolution path: specific action items to address each issue (add document, update calculation, etc.)

Approval-Ready Output

Once all checks pass, the system produces the complete permit package in the format required by the jurisdiction, with a compliance summary and full audit trail.

  • Validated package: all required documents assembled and verified complete
  • Compliance summary: checklist of all requirements met with rule IDs and verification status
  • Audit trail: timestamped log of all checks performed, results, and document versions

System Characteristics

Built for Regulatory Trust

Deterministic

Same inputs always produce the same outputs. No probabilistic decisions. Every result is reproducible.

Cited

Every requirement traces to a code section. Every flag includes the rule ID. Full transparency on why.

Auditable

Complete validation history with timestamps, document versions, and reasoning chains for compliance review.

Implementation Note

The Normiz system uses machine learning components for document parsing and data extraction tasks. These components assist in processing unstructured documents into structured data that can be validated against rules.

All compliance decisions are made by the deterministic validation engine against the structured regulatory database. The system does not use probabilistic models for compliance judgments. When uncertainty exists in document extraction, the system flags the item for human review rather than making assumptions.

See the System in Action

Request early access to see how Normiz validates permit packages for your jurisdiction and trade type.

Early Access