Search

Non-Compliance Fines: A Cautionary Audit Breakdown

By Glazix | June 4, 2025

Non-compliance fines are often viewed as unfortunate but rare. In reality, they’re red flags that signal deeper flaws in documentation, oversight, or process alignment. This blog unpacks a cautionary audit involving building code violations that resulted in serious financial consequences for a glass distributor.

The Incident: Incorrect Fire-Rated Assemblies Installed in a Public Building

A US-based distributor supplied interior fire-rated glass panels for a municipal office renovation. The panels were fabricated with a 20-minute rating and installed in hallway partitions. However, the local code required a minimum of 45-minute rated assemblies due to the hallway’s egress classification.

The error was discovered during a routine fire inspection three months after installation. Because the building was already in use, the city issued a compliance violation along with a fine—and demanded immediate remediation.

Audit Findings

The distributor used an outdated code matrix from a previous jurisdiction

No independent compliance verification was performed during the submittal stage

The contractor relied on the distributor’s certification without cross-checking

Consequences

$150,000 in fines and mandatory replacements

30-day deadline to correct the violation imposed by city inspectors

Suspension from future municipal bid invitations for 18 months

Post-Audit Corrective Actions

Compliance Verification Workflow Created

All submittals now require a documented code check by a certified compliance specialist based on local jurisdictional rules.

Code Matrix Digitized and Localized

Code requirement tables are now updated per state and city codes, stored in a centralized compliance portal.

Signed Code Review Required at Bid Stage

Estimators must complete a code compatibility review sheet signed off by project management before quote finalization.

Takeaway

Fines are never “just financial.” They erode trust, reduce future eligibility, and expose systemic blind spots. Code compliance must be a baked-in phase—not a post-installation discovery.


Book A Demo