Arizona Owner's Rep Case Files.
SABS project chronicles with AHJ, EOR, GC, and finance partner attribution
An owner's rep for SABS construction in Arizona runs a defined chain of relationships on every project: the architect of record, the engineer of record stamping the structural drawings against ICC-ES ESR-1638, the authority having jurisdiction reviewing the alternate-materials path, the GC carrying the panel-set installer crew, and the finance partner underwriting against the system's longer payback and stronger insurance posture. LÏEF Development is the Arizona owner's rep that has run this chain end-to-end on multiple delivered and in-flight projects. The pages below are the project file.
Most "owner's rep for alternative systems" content on the web is a brochure paragraph and a stock photo. There is no operator chronicle. That is the gap this page fills. If you are an owner evaluating whether to run a SABS project, you need to see the chain. If you are a GC bidding alongside us, you need to see the trade lineup. If you are a lender or insurance carrier seeing your first SABS file, the named precedent matters more than the brochure. I run this work. Below is the case file.
The Five Places Owner's Rep Scope Shifts on a SABS Project
The conventional owner's rep scope is well documented. CMAA publishes standard scope language. On an alternative-system project the scope shifts in five specific places. A rep without firsthand experience on SABS misses the same things every time.
Specification language
Wall sections, structural notes, and submittal language reference ICC-ES ESR-1638 and the SABS installation manual, not ICF or CMU code paths. Generic specs get rejected on language grounds before technical review.
AHJ first-contact
Most Arizona building inspectors have approved hundreds of stick-frame jobs and a handful of traditional ICF jobs. They have not inspected a SABS project. First inspection is a code review plus a technical orientation. The rep brings the ESR, the installation manual, and the engineer of record direct line.
Engineer of record selection
The engineer must be willing to stamp drawings that reference the evaluation report rather than retreating to a familiar wall type. Many structural engineers in Arizona have not done this yet. The rep maintains the relationship.
GC and installer crew lineup
Panel-set and cementitious application is one trade, not four. The bid structure, the schedule, and the on-site sequencing all break the stick‑frame template.
Finance and insurance narrative
Lenders and carriers in Arizona are repricing wildfire exposure aggressively. The rep writes the one-page system narrative that goes in front of the underwriter.
The Project Files
Four projects, three jurisdictions, two states, one delivery chain. Named, attributed, and walkable under NDA during bid or feasibility.
301 W Osborn
Midtown Phoenix | City of Phoenix Planning and Development Department
Boutique mixed-use redevelopment on a midtown Phoenix infill site. Adaptive-reuse plus new SABS shell.
Owner's Rep
LÏEF Development
Engineer of Record
Third-party structural firm carrying the SABS stamp. Standing protocol is zero redlines from the EOR before submittal goes to AHJ.
AHJ Path
Alternate materials and methods request filed under IBC Section 104.11 referencing ICC‑ES ESR‑1638.
Architect Coordination
SABS wall sections written into the construction documents at design development, not as a change in CDs. Single biggest avoidable cost on a first-time SABS project.
Trade Lineup
Panel-set installer crew handles assembly and cementitious application. Interior finish trades sequenced after shell completion. Shell trade count materially lower than comparable stick‑frame schedule.
Plan Review Notes
First-cycle comments centered on detail clarity at the foundation-to-wall transition and the parapet condition. Resolved through detail revisions plus an inspector briefing covering the ESR. Subsequent cycles cleaner.
301 W Osborn is the active permitted SABS project file in Midtown Phoenix that operators and AHJ staff can reference. If you are an owner planning a Phoenix infill SABS project, you are building behind a known precedent.
Canyon Corporate Plaza
Phoenix | Maricopa County and applicable municipal AHJ depending on parcel
Phoenix-area commercial program using SABS shell construction.
Owner's Rep
LÏEF Development
Strata International Relationship
Distributor relationship for the SABS technology in this market sits between LÏEF and Strata. Trade documentation, panel manufacturing schedule, and technical support chain flow through that relationship.
Engineer of Record
Third-party stamp. Same zero-redline standard as 301 W Osborn.
Procurement
LÏEF Blocks lead time runs longer than off-the-shelf framing material and longer than typical traditional ICF. Procurement decision sits before the geotech is final, not after the slab is poured. On Canyon the long-lead sequencing was built into the master schedule from week one.
Canyon establishes that the SABS chain operates in a Phoenix commercial program, not just a residential one. Trade lineup, lender conversation, and schedule logic all carry across product types.
Silver Mountain Ranches
Scottsdale | City of Scottsdale Planning and Development. Plan review with WUI considerations.
Boutique residential development in north Scottsdale. Wildland-urban interface exposure relevant to the structural assembly selection.
Owner's Rep
LÏEF Development
Insurance Posture
The 2024-25 cycle saw Arizona carriers non-renew wood-frame homes in Paradise Valley, Cave Creek, and north Scottsdale on a structure-level review, not a cladding-only review. SABS construction with ASTM E-84 Class A 0% flame spread sits on the right side of that underwriting screen. The rep narrative to the carrier referenced the test data plus the wall assembly geometry, not just the cladding spec.
Finance Partner Conversation
Lenders writing to north Scottsdale boutique residential have started asking structure-of-assembly questions on file. The one-page system narrative, the ICC-ES report, and named precedent on 301 W Osborn and Canyon were the file.
Silver Mountain Ranches is the case file for owners running boutique residential in a WUI-exposed Arizona submarket. The insurance and lender file is now built.
440 Basin Avenue
Pahrump, NV | Nye County Building Department
Mixed-use project in Pahrump, Nye County, Nevada. Outside Arizona but inside the LÏEF operating radius.
Owner's Rep
LÏEF Development
Why this project is in the Arizona file
Arizona owners running projects in adjacent Nevada submarkets need a rep who can carry the SABS chain across the state line. The chain works the same way in Pahrump as it does in Phoenix. ESR, EOR, AHJ orientation, panel-set crew, lender narrative. The names change, the work does not.
Establishes that the LÏEF chain travels across the Arizona-Nevada border without losing structure.
What the Case File Establishes
Four projects, three jurisdictions, two states, one delivery chain. The point of publishing the file is that "owner's rep for alternative building systems in Arizona" is not a category of one in the abstract. It is a category of one with a named operator, a known engineer-of-record relationship, an active AHJ orientation playbook, and a finance and insurance file you can show a lender.
Most Arizona builders specifying SABS for the first time hit the same five friction points in the same order. The case file above is what compresses that learning curve from three plan-review cycles to one.
Frequently Asked Questions
Who is the owner's rep for SABS construction in Arizona?
LÏEF Development is the owner's rep operating the SABS chain in Arizona, with active permitted projects in Phoenix (301 W Osborn, Canyon Corporate Plaza) and Scottsdale (Silver Mountain Ranches), plus adjacent-market work in Pahrump, NV. The office holds the operating relationship with Strata International, the SABS technology distributor, for the Arizona market.
What jurisdictions has the LÏEF owner's rep team worked through on SABS projects?
City of Phoenix, City of Scottsdale, Maricopa County, and Nye County (NV) on the projects currently on file. The first-inspection orientation is a documented playbook: ICC-ES ESR-1638, the SABS installation manual, the engineer-of-record direct line, and a brief walking the inspector through the alternate-materials request under IBC Section 104.11.
Does the LÏEF rep carry the GC or is the GC selected separately?
The GC is selected for the project. LÏEF writes a tight enough spec that bidders quote the work as SABS rather than loading it with stick-frame contingency, and brings the installer crew that knows the panel-set sequence. The same panel-set installer typically carries from job to job. The broader GC structure varies by program.
What is the engineer-of-record standard on a LÏEF-repped SABS project?
The structural engineer must be willing to stamp drawings referencing ICC-ES ESR-1638. The internal standard is zero redlines from the EOR before submittal goes to the AHJ. That bar gets the project through plan review cleanly rather than burning two cycles on engineering language.
How does the finance and insurance file get built on a first-time SABS project?
One-page system narrative referencing ICC-ES ESR-1638, ASTM E-84 Class A 0% flame spread, ASTM C578 Type XI thermal performance, and named precedent from delivered or in-flight projects. The carrier or lender sees the wall assembly, the test data, and the project list on one sheet. That conversation typically resolves in one or two underwriter touchpoints.
How is this different from a generic Arizona owner's rep?
A generic owner's rep is excellent on stick-frame and CMU work. The five places the alternative-system scope shifts (specification language, AHJ first-contact, engineer-of-record selection, trade lineup, finance and insurance narrative) are work the generic rep has not done before. A first-time SABS project under a generic rep typically discovers each friction point sequentially, one plan-review cycle at a time. A LÏEF-repped project resolves them at design development.
About the Author
Jesse Fowler is the founder of LÏEF Development and the Arizona owner's rep for SABS construction with LÏEF Blocks. The case file above is firsthand operator content from the four named projects. Project inquiries: hello@liefdev.com