C-PACE Financing

C-PACE (Commercial Property Assessed Clean Energy) finances defined building improvements through a voluntary special assessment on the property, repaid through the property tax bill rather than a mortgage payment. The mechanism exists only where state law enables it and a local program administers it, which makes the first C-PACE question jurisdictional, not financial. Where it is available and the scope qualifies, it can be a genuinely useful component of a development capital stack. This page describes the mechanism; it does not promise it.

Evoque Commercial evaluates and coordinates C-PACE as one component within the capital stacks it arranges, most often on multifamily, mixed-use residential, and select commercial development from $8 million to $15 million in one of our core ranges.

When C-PACE fits and when it does not

The component fits when four things line up: an active program in the project's jurisdiction, an improvement scope that plausibly qualifies, a senior lender willing to engage on consent, and stack arithmetic that actually improves with the assessment included. No enabling program means no C-PACE, whatever the project's merits. A senior lender with a firm no is a fact to respect, not negotiate around; the stack is then completed conventionally, often through structured capital. And where the assessment does not improve the blended stack, the honest answer is to leave it out.

Where C-PACE sits in the capital stack

C-PACE is a component, never the whole answer: a defined slice of the budget funded alongside a senior construction loan, sponsor equity, and any structured layers. It is an assessment that runs with the property: it does not accelerate like a loan, and payments follow the tax calendar. Its collection priority (installments sit with the property taxes, ahead of the mortgage) is exactly why senior consent and coordination are built into the process rather than appended to it. Used well, the component can replace a slice of more expensive mezzanine or preferred capital with assessment-based capital tied to real improvements.

What C-PACE may fund, subject to program rules

Program rules govern everything here. The recurring eligible categories are energy efficiency (envelope, mechanical systems, lighting, controls), water efficiency, renewable energy systems, and resilience measures such as seismic strengthening or storm and fire hardening, where the jurisdiction includes them. Timing also varies: placement at the construction closing is most common; some programs accommodate placement during construction, and some permit financing after completion, including lookback provisions that can replace capital already invested in eligible improvements within a defined window. Each is a possibility to verify against the specific program, never an assumption.

Senior-lender consent and coordination

Consent is the hinge of every C-PACE placement, and it is a coordination task, not a formality. The senior lender's position is engaged early, with the assessment's mechanics presented alongside the rest of the stack: how installments are escrowed or reserved, how the assessment affects underwriting ratios, and what the intercreditor understanding looks like in practice. Some senior lenders have standing C-PACE policies; others evaluate file by file; some decline. A component raised at the first structuring conversation reads as planning; one introduced after senior terms are set reads as renegotiation.

What gets evaluated

The review runs on parallel tracks. Jurisdictional: the enabling statute, the local program's rules, and its administrator's process. Technical: the improvement scope against eligibility categories, through the program's required engineering or energy analysis. Financial: the assessment's sizing against eligible costs and its effect on carry and the blended cost of the stack. Structural: senior consent, escrow and reserve mechanics, and documentation.

The project itself (sponsorship, budget, market, exit) is underwritten first; a stack component cannot rescue a project that does not otherwise work. All parameters are confirmed during project review.

Exit considerations

Because the assessment runs with the property, the exit plan addresses it explicitly. On a sale, the assessment may transfer with the property or be paid off at closing; buyer expectations differ by market and product. On a refinance, the incoming lender's posture toward the assessment is confirmed before the exit is priced. Prepayment mechanics (whether, when, and on what schedule the assessment can be retired early) are read before closing, so the exit never negotiates against a document nobody re-read.

Documentation to expect

Alongside the standard development file (budget, schedule, sponsor résumé and financial summary, sources-and-uses), expect the C-PACE layer: the defined scope of eligible improvements with costs broken out, the program's required engineering, energy, or water analysis, the program application and administrator correspondence, and the senior lender's consent documentation as it develops. The developer document checklist adds the assessment-specific items when C-PACE is part of the plan.

Where C-PACE files get difficult

The recurring difficulties are procedural: jurisdictions whose programs differ just enough to defeat assumptions, senior consent raised late and priced accordingly, eligibility assumed by analogy and narrowed by the technical review, closing calendars that underestimated the administrator's timeline, and stacks where the component was added for its headline rather than its arithmetic. Most are avoided the same way: treat C-PACE as a jurisdiction-specific component confirmed early (never a given) and coordinate the senior lender from the first conversation.