Skip to content HVAC AI Agents home

Private beta · Compliance

Auto-generated HVAC compliance reports — LL97, ASHRAE, ISO 50001.

Pulled from every building you operate. Full audit trail of every setpoint + override. Anomalies flagged with remediations. Reports in hours, not weeks.

Join the waitlist →

hours

to a full report

not weeks of spreadsheet work

every

setpoint + override logged

with the agent / person who made it

flagged

anomalies with remediations

audit-ready, signed and timestamped

Three modes — autonomous leads here

Primary for this page

Continuous audit log

Every setpoint change, override, alarm, and remediation is logged with reason + actor. Report templates assemble these on demand.

Compliance copilot

Ask: 'why did our LL97 report flag building 4?' Copilot drills into the anomaly + suggests the remediation note.

MCP for your ESG stack

Push reports + raw audit logs into your ESG / sustainability platform via MCP.

Compliance reporting

Audit-ready LL97, BERDO, Title 24, and GRESB reports generated in hours — every aggregate traceable to raw telemetry.

HVAC AI Compliance Reports pulls energy and carbon data straight from your building telemetry, applies jurisdiction-specific templates, and hands your ESG team a defensible report package in hours — not the weeks it used to take your energy consultant.

The core problem with manual compliance reporting isn't skill — it's data provenance. An energy team can calculate LL97 penalties or Title 24 compliance margins, but when an auditor asks where a number came from, the honest answer is often 'an energy model, extrapolated from utility bills, adjusted for occupancy assumptions.' That answer doesn't hold up under scrutiny. It leads to findings, re-submissions, and consultant fees to defend work that should have been defensible from the start.

HVAC AI Compliance Reports starts at the telemetry layer. Energy consumption figures come from real kWh readings at the meter and submeter, timestamped and stored in the same time-series database that drives the operational dashboards. When a report says the building consumed 1.2 million kWh in the compliance year, an auditor can drill from that number to the monthly rollup, to the daily total, to the raw point reading that contributed to it — without leaving the platform. That back-traceability is what 'audit-defensible' means in practice.

Jurisdiction coverage spans the major North American compliance frameworks: LL97 (New York City Local Law 97), BERDO (Boston Building Emissions Reduction and Disclosure Ordinance), Title 24 (California Building Energy Efficiency Standards), ASHRAE 90.1 and 100, NYC Energy Star benchmarking, BC OEER (British Columbia Office of Energy Efficiency Reporting), and GRESB for institutional real estate portfolios. Templates are maintained and updated as ordinances change — you don't chase the regulation, we do.

Scope 2 greenhouse gas calculations use actual HVAC electricity consumption combined with your grid's marginal emissions factor for the compliance period — not an industry-average assumption. Scope 3 data export is available in formats compatible with the GHG Protocol tools your upstream/downstream calculation vendors already use. For multi-jurisdiction portfolios, each building is tagged to its applicable ordinances, so a 40-building portfolio spread across New York, California, and Boston produces separate jurisdiction-compliant outputs in the same report run.

Where it pays off

Concrete scenarios from compliance-driven real estate teams.

Four patterns we see repeatedly across building owners, portfolio ESG leads, corporate sustainability, and regulatory audit defense.

NYC building owner (LL97)

450,000 sq ft Class B office tower. First LL97 compliance year approaching. Energy team is manually reconciling utility bills against an energy model that hasn't been validated since 2019. Penalty exposure is unclear.

Compliance Reports ingests three years of submeter telemetry, produces the LL97 carbon intensity calculation from real kWh data, and surfaces the penalty gap versus the 2024 and 2030 thresholds — with the improvement levers ranked by $/tonne CO2e.

Annual report generation from 6 weeks to under 8 hours; penalty exposure quantified to ±3%

Multi-state portfolio ESG lead

38-building portfolio across NYC, Boston, and California. Three separate ordinances — LL97, BERDO, Title 24 — each with different calculation methodologies, formats, and submission deadlines. Energy team spends Q4 on compliance instead of improvement.

Each building is tagged to its applicable jurisdiction. A single report run generates jurisdiction-specific outputs for all 38 buildings, flags which assets are out of threshold, and exports the board-level ESG summary in GRESB-compatible format.

Compliance reporting labor down 70%; zero missed submission deadlines

Corporate sustainability team (Scope 2 inventory)

Global real estate portfolio needs market-based Scope 2 emissions for the annual sustainability report. HVAC is the largest electricity consumer. Current approach uses utility-bill averages and EPA grid factors — auditors are flagging the methodology.

Compliance Reports calculates Scope 2 using actual HVAC submeter kWh, paired with marginal grid emissions factors for each meter's utility service territory. Every calculation cell cites its source reading and emissions factor vintage.

Scope 2 inventory audit pass on first submission; methodology accepted without findings

Auditor / regulator defense scenario

A regulator has issued a data request challenging the LL97 carbon intensity figure submitted for a 12-building portfolio. The energy team needs to show that the numbers came from real measurements, not modeled estimates.

The platform's audit-trail export produces a PDF + CSV package: rolled-up annual total, monthly breakdown, daily time-series, and the raw BMS point readings that populated every aggregate — all timestamped and signed. Regulator accepts the submission.

Zero re-submissions; audit defense resolved in 2 business days vs. typical 3–4 week cycle

FAQ

Compliance reporting — common questions.

  • Which compliance frameworks are templated out of the box?

    Production templates exist for LL97 (NYC Local Law 97), BERDO (Boston Building Emissions Reduction and Disclosure Ordinance), Title 24 (California Energy Efficiency Standards), ASHRAE 90.1 and 100, NYC Energy Star benchmarking, BC OEER (British Columbia Office of Energy Efficiency Reporting), and GRESB for institutional real estate. Templates are maintained and updated when ordinances change — the 2026 LL97 threshold revisions, for example, are already reflected. If your jurisdiction isn't on the list, see the customization question below.

  • How are rolled-up compliance figures back-traceable to raw telemetry?

    Every aggregate in a report is computed from time-series readings stored in the platform's immutable telemetry database. When an auditor questions the annual kWh figure for a building, you can export a drill-down package: annual total → monthly rollup → daily total → the individual BMS point readings that contributed to each day — all timestamped and referenced by their source sensor ID. Nothing in the report is estimated or modeled after the fact; it's computed from the same telemetry that drives your operational dashboards.

  • What does the agent do for Scope 2 versus Scope 3 emissions?

    Scope 2 calculations are fully automated: the agent uses actual HVAC electricity consumption from your submeters, multiplied by the marginal grid emissions factor for each meter's utility service territory, for the applicable compliance period. You get location-based and market-based Scope 2 figures in the same output. Scope 3 is a data export — the platform surfaces the upstream consumption figures (electricity by building, fuel by system) in GHG Protocol-compatible formats so your Scope 3 accounting vendor or internal model can ingest them without manual re-entry.

  • Can we customize a report template for a jurisdiction that isn't on your list?

    Yes, with a scoping call. If you can share the ordinance's calculation methodology and the required output format, we build the template and validate it against a sample dataset from your portfolio before your first submission. Custom jurisdictions added this way are maintained going forward — we don't charge per-update for templates we've built. Common near-term requests include Chicago's EBEWE ordinance, Seattle's Building Tune-Up program, and provincial programs in Canada outside BC.

  • How long does annual report generation take compared to the manual process?

    For buildings that are already connected and have a full compliance year of telemetry in the platform, report generation is typically 2–8 hours depending on portfolio size — mostly elapsed time for the export job, not labor. The manual approach — reconciling utility bills, running energy models, formatting jurisdiction-specific outputs, and QA-ing the numbers — typically takes an energy team 3–6 weeks of concentrated effort per reporting cycle. The delta is roughly weeks-to-hours, and the output is more defensible because it traces to real measurements.

  • Does it work for a single building or only for multi-building portfolios?

    Both. Single-building owners use it most often for LL97 compliance in NYC and Title 24 compliance in California, where the penalty exposure on one large building can exceed six figures annually. Portfolio customers get additional value from the cross-portfolio benchmarking view — seeing which buildings are most at risk for threshold crossings and where capital investment delivers the most compliance benefit per dollar. The platform doesn't have a minimum building count.

  • Can the platform calculate penalty exposure before the compliance period ends?

    Yes. The platform runs a real-time compliance projection: given year-to-date energy consumption and the current trend, it models whether the building will finish the year above or below the applicable threshold. If a building is on track for a penalty, the projection surfaces the gap in tCO2e and the levers — setpoint adjustments, equipment scheduling, fuel switching — ranked by their ability to close the gap before the compliance year closes.

  • How is compliance reporting billed?

    Per building per year, with portfolio tiering. The annual fee covers all jurisdiction templates applicable to that building, unlimited report runs, audit-trail exports, and template updates when ordinances change. There's no per-submission or per-export charge. Onboarding includes a validation run against your most recent compliance year's utility data to confirm the telemetry-derived figures are within acceptable tolerance before your first live submission. Contact us with your building count and jurisdictions for a specific quote.

Speaks to your existing kit

Carrier, Trane, Daikin, Mitsubishi, LG, Lennox, York, Samsung — 20+ HVAC, home-automation, and BMS brands.

63 brands across 3 categories — HVAC (31), Home Automation (18), BMS (14). Protocols: BACnet, KNX, MQTT, Matter, Modbus, REST, WebSocket, Z-Wave, Zigbee.

How it stays out of your way

Secure

Sealed data plane. Per-site auth. Audit log on every setpoint touch.

Runs on the edge

Deploys at the building edge — your data doesn't leave the site to be useful.

BYO LLM

Works with Claude, ChatGPT, and any MCP-compatible client. You pick the brain.

Private beta

See your first auto-report.

Designed for ESG leads, sustainability VPs, and LL97-impacted owners.