The development team had already run a Title 24 compliance model through their usual consultant: it passed, on schedule, nothing flagged. What it didn't do was look for money. On a 140-unit garden-style project, that's a common and expensive gap: a model built to clear the prescriptive path doesn't automatically go looking for every incentive the same building qualifies for.
The problem: passing code and capturing incentives are two different questions
A standard compliance run answers one question: does this building pass? It doesn't answer a second, more valuable one: what's the cheapest way to pass, and what's left on the table if it doesn't try? For garden-style multifamily specifically, that second question usually touches utility new-construction rebate programs and IRA credit eligibility that require a different pass through the same underlying model, not a second building.
What Buildwiser's model found
Re-running the project's own inputs (unit count, envelope spec, climate zone) through Buildwiser's AI energy modeling surfaced two things the original compliance run wasn't built to look for: the project's utility service territory ran a richer new-construction rebate tier than the team had priced in, and the building's actual performance margin (22% below the Title 24 baseline, not just a pass/fail) qualified it for a deduction tier the team's original consultant hadn't flagged as relevant to a residential project.
Why this got found at schematic design, not at permitting
The re-run happened before the unit mix locked, which is what turned a compliance afterthought into a design input: the incentive eligibility informed a small envelope adjustment the team could still make cheaply, instead of a change order after permit submittal. That timing is the actual mechanism behind the 3-week schedule number: catching an incentive-affecting spec question at schematic design costs a redline; catching it at plan check costs a resubmittal.
None of this required a second model, a second consultant, or a second review cycle: the same inputs, run through a system built to ask both questions at once.