February 20, 2026

California 2025 Energy Code for Controlled Environment Horticulture: Lighting Efficacy, LPD, and Acceptance Testing for Grow Ops

California 2025 Energy Code for Controlled Environment Horticulture: Lighting Efficacy, LPD, and Acceptance Testing for Grow Ops

Why California’s 2025 Title 24 CEH rules matter (and when they hit)

California’s Building Energy Efficiency Standards—better known as Title 24, Part 6—update on a three‑year cycle, and the 2025 Energy Code becomes effective January 1, 2026 for projects that submit for permit on/after that date. For controlled environment horticulture (CEH), the 2025 cycle continues a clear policy direction: treat high‑intensity cultivation lighting as a major building load that must be designed, controlled, verified, and documented like other high‑impact nonresidential systems.

The practical takeaway for operators is simple: if your facility is planning a new build, a tenant improvement, or a lighting retrofit that triggers energy code scope, you should assume that lighting efficacy targets will be harder to meet, lighting power allowances will be tighter, and acceptance testing documentation will be scrutinized.

Key references for compliance teams and designers:

Note: This article is informational and focuses on compliance planning. Always confirm your exact obligations with your project’s energy consultant, the Authority Having Jurisdiction (AHJ), and the applicable adopted code language.

What’s changing in 2025 for CEH lighting: the three pressure points

Stakeholder materials for the 2025 cycle—especially the CASE report package—signal three areas where projects feel the squeeze:

  1. Lighting efficacy expectations continue to ratchet upward (measured in photosynthetic photon efficacy or similar horticultural metrics rather than “lumens per watt”).
  2. LPD (Lighting Power Density) / power allowances become less forgiving, meaning “just add fixtures” becomes harder to justify.
  3. Acceptance testing and documentation becomes more central to passing final inspection, especially for lighting controls.

Each of those interacts with typical cultivation constraints: high humidity, corrosive environments, frequent washdowns, dense overhead infrastructure, and the need for reliable emergency lighting and egress.

Understanding the metrics: efficacy vs. power density (and why both can fail you)

Lighting efficacy: think “PAR photons per joule,” not lumens

Most building lighting standards historically revolve around visual lighting: lumens and watts. CEH flips the script: your performance target is tied to photosynthetically active radiation (PAR) and the photons delivered to the canopy.

The Statewide CASE materials for CEH discuss minimum efficacy requirements for horticultural luminaires and emphasize efficiency improvements as the primary savings mechanism. In cultivation terms, efficacy is usually expressed as μmol/J (micromoles of photons per joule). Higher is better: you get more usable photons for the same electrical input.

Compliance planning implications:

  • If you rely on older HID or early‑generation LED fixtures, the efficacy gap is the first place you may get hit.
  • Cutting wattage without maintaining canopy targets can cause production issues. This is why designers should model canopy PPFD targets alongside energy compliance.

LPD/power allowances: the code is forcing design discipline

Even when you choose high‑efficacy fixtures, your project can still fail if the overall installed lighting power is too high for the allowed method.

In practice, tighter LPD/power allowances force:

  • better photometric layouts (reduce overlap and hot spots)
  • zoning and dimming strategies that match growth stages
  • more attention to reflectance, mounting heights, and aisle strategy

When stakeholders mention “removal of legacy compliance methods,” what they are usually warning about is the loss (or narrowing) of paths that previously allowed overly generous lighting power assumptions without strong performance justification.

Compliance pathways you should expect to use in 2026 permitting

Your energy code compliance documentation generally flows through:

  • Certificates of Compliance (design/plan stage)
  • Certificates of Installation (as‑installed verification)
  • Certificates of Acceptance (acceptance testing)

The CEC hosts the official forms and instructions; Energy Code Ace also mirrors organized form libraries widely used by practitioners.

Start here:

One example that will look familiar to project teams is the CEC-NRCI-LTI-E “Indoor Lighting Certificate of Installation,” which explicitly calls out controls categories (time-switch, occupancy sensors, daylighting, demand response, institutional tuning, etc.). See: https://www.energy.ca.gov/filebrowser/download/8489?fid=8489

Performance modeling tools: CBECC and approved software

If your compliance approach uses performance modeling, the CEC lists approved tools for the 2025 cycle. The public domain suite is California Building Energy Code Compliance (CBECC). This matters because some CEH projects will be forced into performance approaches once prescriptive assumptions no longer pencil.

CEC resource: https://www.energy.ca.gov/programs-and-topics/programs/building-energy-efficiency-standards/2025-energy-code-compliance-software

Lighting controls: where many CEH projects will trip (even with efficient fixtures)

The 2025 Energy Code continues to treat lighting controls as a mandatory and enforceable component—not an optional add‑on. At a high level, the mandatory requirements for lighting controls appear in Section 110.9 (as published in code access platforms), and include categories like time-switch controls, daylight responsive controls, dimmers, and occupant/automatic controls.

For code text navigation (reference access): https://codes.iccsafe.org/content/CAEC2025P1

For CEH spaces, controls often collide with operational reality:

  • “Occupancy sensors” don’t always align with staff workflows (frequent short entries)
  • Daylight controls in greenhouses must be tuned so they don’t destabilize plant response
  • Networked controls add commissioning complexity (and acceptance testing scope)

The better approach is to treat controls as part of the cultivation recipe:

  • Zone by function: canopy zones, aisles, support rooms, dry storage, processing
  • Program by phase: propagation, veg, flower (or your internal staging)
  • Implement high/low modes: maintenance lighting vs. production lighting

Acceptance testing: plan for it early, budget for it, and document it cleanly

Acceptance testing is where projects that “look fine” on paper can fail at final.

What acceptance testing is (in Title 24 terms)

Acceptance testing is a required verification process—performed by a qualified technician under the Energy Code Compliance (ECC) program rules—intended to prove that installed controls and systems actually function as required.

CEC’s acceptance testing overview document (lighting controls acceptance testing procedures are referenced in the nonresidential appendices): https://www.energy.ca.gov/filebrowser/download/8651?fid=8651

Why CEH projects are especially exposed

CEH spaces are control-dense:

  • multiple lighting zones per room
  • staged dimming schedules
  • interlocks with HVAC/dehumidification strategies
  • daylight integration in greenhouses

Each of those can create failure points:

  • misaddressed control zones
  • dimming drivers not matching specified protocol
  • sensor placement compromised by racking and overhead piping
  • “temporary” bypasses left in place after troubleshooting

A practical acceptance testing checklist for operators

Before final inspection, make sure your GC, electrician, controls contractor, and consultant can answer these without searching emails:

  • Where are the as‑built sequences of operation?
  • Which spaces require acceptance tests, and which specific NRCA forms apply?
  • Who is the certified acceptance test technician, and are they scheduled early enough?
  • Are control zones labeled physically (panels/controllers) and logically (software)?
  • Do you have screenshots/exports showing tuned setpoints and schedules?

If acceptance testing is treated as an end-of-project paperwork step, it tends to become a rework step.

“LPD vs. canopy targets”: how to redesign without sacrificing production goals

A common operator fear is that a tighter code means lower yields. In reality, the code is pushing teams toward a more measurable, modern design process.

Step 1: define canopy targets by area (not one number for the whole building)

Instead of “this room is 900 PPFD,” define:

  • target range (min/typical/max)
  • uniformity expectations
  • edge conditions and walkways

This lets designers reduce wasted overlap and keep wattage within allowances.

Step 2: pick luminaires based on verified photometric files and efficacy metrics

Make sure your luminaire selection can be defended with:

  • manufacturer spec sheets showing efficacy metrics (e.g., PPE)
  • tested photometric distributions
  • compatible dimming/control interfaces

Even if a product is excellent, you still need it to be documentable.

Step 3: design for dimming as a first-class strategy

Dimming is not just energy savings—it’s operational flexibility:

  • reduce power during acclimation
  • match lighting to HVAC/dehumidification capacity during peak utility periods
  • maintain production while staying compliant with control requirements

Step 4: coordinate with mechanical early

Lighting watts become heat. When you reduce lighting power density, you may also change:

  • sensible heat load
  • latent performance needs (if plant transpiration shifts with light intensity)
  • dehumidification runtime assumptions

Aligning lighting and mechanical avoids the classic “we passed plan check but the room doesn’t hold setpoints” problem.

Greenhouses: daylighting controls and the tuning problem

Greenhouse projects add a variable that indoor rooms don’t have: the sun.

Even when the exact code trigger language differs by zone type and daylit area thresholds, the compliance direction is consistent: daylight responsive behavior needs to be automatic, measurable, and verifiable.

Operator best practices:

  • Define maximum supplemental lighting power per zone (cap it)
  • Use multi-level control so you can reduce power in steps rather than all-or-nothing
  • Establish commissioning scripts for sunny-day, cloudy-day, and shoulder conditions

The biggest risk is “paper compliance” with daylight controls that were never tuned, which can lead to acceptance testing failures or operational complaints.

Retrofits and alterations: don’t assume you’re exempt

Many operators plan lighting upgrades as “simple swaps.” Title 24’s additions and alterations rules can still apply depending on scope. The CEC CEH FAQ page explicitly discusses where CEH requirements live for additions/alterations and new construction.

Start with the CEH FAQ and then confirm with your energy consultant:

  • Does the project scope trigger lighting power recalculation?
  • Are new controls required when replacing a threshold percentage of luminaires?
  • Does your AHJ treat the room as a distinct regulated CEH space in plan check?

Resource: https://www.energy.ca.gov/programs-and-topics/programs/building-energy-efficiency-standards/energy-code-support-center-8/2025

Utility rebates and incentives: align Title 24 compliance with your project finance

California investor-owned utility programs often use qualifying product lists and technical requirements (commonly via the DesignLights Consortium for many commercial lighting segments, including horticultural categories) as part of rebate eligibility screens. While rebate rules are not the same as Title 24 compliance, projects frequently need to satisfy both.

Best practice for finance and compliance teams:

  • Choose fixtures that meet both your code strategy (efficacy/power/controls) and likely incentive requirements
  • Keep a single “evidence folder” with cut sheets, QPL screenshots (if applicable), invoices, and control narratives
  • Confirm early whether your program requires networked controls, specific dimming protocols, or measured savings approaches

Industry overview on QPL use in programs: https://inside.lighting/news/26-01/lighting-controls-get-rebate-boost-latest-dlc-guidelines

Coordination with electrical and fire/life-safety: avoid passing energy and failing inspections

Your research note about conflicts with electrical and fire code is exactly right: energy compliance should never create a life-safety gap.

Common coordination points in humid/wet CEH environments:

  • Wiring methods and equipment ratings suitable for corrosive or washdown conditions
  • Emergency egress lighting that remains compliant even when production lighting is dimmed or scheduled off
  • Control interlocks that do not unintentionally shut off required illumination
  • Clear labeling of control panels and circuits for inspectors

Treat these as design constraints, not field fixes.

What your plan-check packet should include (so the AHJ can approve it faster)

AHJs vary, but most plan check delays come from missing clarity rather than truly noncompliant designs.

A strong packet typically includes:

  • Registered energy compliance documentation (as required)
  • Lighting plans with fixture schedules, wattage, and control zones clearly shown
  • Control narrative describing manual control, automatic shutoff, dimming strategy, and daylight response (if applicable)
  • Commissioning/acceptance testing plan: who, when, and which forms
  • Cut sheets for luminaires and control devices

If you operate multiple sites, standardize this packet so every project starts with the same “compliance spine.”

Timelines: how to sequence a CEH lighting project under the 2025 Energy Code

For projects targeting permit submittal in 2026:

  • 90–120 days pre-submittal: lock canopy targets, pick fixture families, choose a controls architecture
  • 60–90 days pre-submittal: complete energy modeling/prescriptive calcs, draft compliance forms, align drawings
  • During construction: enforce submittal approvals; don’t allow fixture substitutions without re-checking efficacy/power and control compatibility
  • 2–4 weeks pre-final: run pre-functional checks (zone addressing, dimming curves, sensor operation)
  • Final: acceptance testing, closeout documentation, retain evidence for audits

The reason to start early is not just code—it’s procurement. High-performing fixtures and controls can have long lead times.

Actionable takeaways for CEH operators in California

  • Assume stricter lighting compliance for 2026 permits under the 2025 Title 24 cycle; plan your design and retrofit strategy accordingly.
  • Model efficacy and canopy outcomes together. Don’t let compliance drive untested production compromises.
  • Controls are not optional. Treat daylighting, scheduling, and occupancy/automatic shutoff as systems that must be tuned and verified.
  • Budget for acceptance testing. It’s time, labor, coordination, and paperwork—and it can trigger rework if ignored.
  • Crosswalk energy code with incentives and local plan check expectations. The cheapest “compliant” solution on paper can become expensive if it delays approval or misses rebates.

Stay ahead with CannabisRegulations.ai

California’s Title 24 updates are only one slice of the broader compliance stack that cultivation operators manage—building permits, operational compliance, inspections, and documentation retention.

Use https://www.cannabisregulations.ai/ to track California compliance updates, build inspection-ready documentation workflows, and reduce the operational risk of code-driven retrofits and facility expansions.