Building Code and Approval Notice
Last updated: 2026-06-12 ยท Effective: 2026-06-12
1. Project-specific review controls
Lok-N-Blok materials, diagrams, wind references, fire references, installation visuals, and proof pages are not a substitute for signed and sealed project documents. Final use in any project depends on the local jurisdiction, site conditions, final assembly, engineering, permitted plans, and inspections.
Public examples and illustrations may show typical assemblies, training concepts, or proof-path visuals. They should not be copied into permit submissions without review by the project team and without matching the exact product version, connection details, foundation, openings, roof interface, cladding, fasteners, and load path for that project.
2. Approval-path language
- Florida Building Code, Miami-Dade, ICC-ES, IAPMO, and similar references should be read as pathway or review-context language unless a specific issued approval document is linked.
- Wind, fire, moisture, seismic, energy, and durability references apply only to the tested or specified assembly and do not automatically transfer to every project configuration.
- Class A, high-wind, and resilience language must be reviewed against the final wall assembly, finishes, fasteners, foundation, openings, roof connection, and jurisdictional requirements.
When a page uses language such as "path", "under review", "where specified", "eligible", "designed to", or "subject to AHJ review", that language is intentional. It means the final approval outcome is not being represented as automatic or universal.
3. Professional responsibilities
Owners, builders, distributors, installers, architects, engineers, and general contractors remain responsible for verifying that a proposed design complies with all applicable codes and regulations. Lok-N-Blok may provide technical data and documentation for review, but it does not act as the local AHJ or as the project engineer of record unless a separate signed professional-services agreement says otherwise.
Distributors and sales representatives should route technical code questions to the approved documentation workflow instead of giving field interpretations. If a buyer, inspector, engineer, architect, insurer, or lender needs support, the correct next step is to gather the project location, use case, drawings, and question so the documentation package can be reviewed accurately.