What Local Law 97 actually requires (and why 2024-2029 is the easy part)

Local Law 97 requires any New York City building over 25,000 square feet, or multiple buildings on one tax lot or condo board totaling more than 50,000 square feet, to cap its carbon emissions and file an annual report proving it, with real financial penalties for missing either the cap or the deadline. That covers roughly 50,000 properties citywide, according to NYC's Department of Buildings, and it's structured in three compliance periods: 2024-2029, 2030-2034, and a net-zero target by 2050.

The first period's caps are deliberately loose. Most building owners who've done minimal retrofit work are squeaking by. The 2030-2034 period is where the law gets teeth: emissions caps tighten sharply, targeting a 40% citywide reduction, and buildings that coasted through the first period on HVAC tune-ups and LED retrofits will find the math doesn't work anymore. Carter Ledyard & Milburn's breakdown of the law puts it plainly: the first period is a warm-up, not a finish line.

Penalties are per ton, not per building. Exceed your cap and you owe $268 per metric ton of CO2e over the limit, every year, until you fix it. Miss the filing deadline and it's $0.50 per square foot per month. File something false and the exposure runs up to $500,000. For a 300,000-square-foot office tower, a missed filing alone costs $1,800 a month before anyone even looks at the emissions math.

Why this is an operations problem, not a legal one

Almost every portfolio owner who calls a law firm or a consultant about Local Law 97 already understands the rule. What they don't have is clean, current utility data across every meter in every building, in a format that produces a reliable emissions number. That's the actual bottleneck, and it's a systems problem, not a legal one.

A single mid-size commercial building can have a dozen or more utility accounts: electric, gas, steam, and in multi-tenant properties, submeters billed separately to tenants with their own account numbers and PDF formats. Multiply that across a 20-building portfolio and you're reconciling hundreds of bills a month, each with its own units, billing cycles, and occasional missing read. Someone has to pull those numbers, convert them to a consistent unit of measurement, map them to the right building, and run them through the emissions factors the law specifies. Do that by hand with a spreadsheet and an analyst, and you're one vacation or one turnover away from a gap in your data trail right before a June 30 filing deadline.

This is the same operational shape as utility billing reconciliation in any other industry: fragmented source data, inconsistent formats, and a compliance deadline that doesn't care how messy the inputs are. We've written about this pattern from the revenue side in how AI agents stop revenue leakage in utility billing; Local Law 97 is the same data problem pointed at a regulatory output instead of a billing one.

What the annual filing actually demands

Every covered building must file its greenhouse gas emissions report through the DOB NOW: BEAM portal, certified by a Registered Design Professional, by June 30 each year, with an extension to August 29 available if requested in time, per the Urban Green Council's tracker. The RDP isn't a formality. They're putting their license on the line attesting that the energy data behind your emissions calculation is accurate, which means they need clean inputs, not a best guess assembled the week before the deadline.

This is where manual processes break first. An RDP reviewing a portfolio with inconsistent submeter allocations, missing months of utility data, or unit conversion errors either kicks the filing back for rework or certifies something they're not fully confident in. Neither is a good position for a building owner. RAND Engineering & Architecture's compliance guide is worth reading for the mechanics of what certification actually checks, but the pattern we see across clients in adjacent industries is consistent: data quality problems don't show up until the person responsible for certifying the number starts asking questions you can't answer fast.

Is Local Law 97 still in effect, and other things owners get wrong

Yes, Local Law 97 is in effect and enforcement is active for the 2024-2029 period; there's no citywide delay or suspension as of this writing. Owners sometimes conflate individual legal challenges or extension requests with a pause on the law itself, but the NYC Accelerator program, the city's own technical assistance resource, is direct about this: non-compliance carries "significant fines," not a grace period.

A second common mistake is treating the first compliance period as the baseline to plan around. Owners who hit their 2024-2029 cap with minor efficiency work often assume they're in good shape through 2034. They're not. The caps step down hard in the second period, and a building that's compliant today with no retrofit roadmap will likely be out of compliance in 2030 without intervention. Planning for Local Law 97 compliance means planning for the tighter cap, not the current one.

A third misconception: treating this as a one-time filing event instead of a recurring data operation. The report is due every year, which means the data pipeline that feeds it needs to work every year, not just survive one filing cycle through heroic manual effort.

This isn't just a New York problem

Local Law 97 is the most mature version of a regulatory pattern that's spreading fast across US cities and into the EU. Boston's Building Emissions Reduction and Disclosure Ordinance (BERDO) imposes a similar structure: emissions caps, a disclosure requirement, and penalties for buildings over a size threshold. Denver's Energize Denver program follows the same logic with its own compliance pathways and reporting cadence. Washington State's Clean Buildings Act applies energy performance standards to commercial buildings statewide, not just one city.

In the EU, the recast Energy Performance of Buildings Directive (EPBD), effective since 2024, requires member states to set Minimum Energy Performance Standards for their worst-performing building stock and publish national renovation plans. The mechanism differs from Local Law 97's per-ton penalty, but the underlying demand on building owners is identical: produce accurate, auditable energy and emissions data on a recurring schedule, across a portfolio, or face regulatory consequences.

If you own or manage property across multiple jurisdictions, which is increasingly the normal case for mid-market real estate portfolios and PE-backed operators, you're not solving "the Local Law 97 problem." You're solving a building performance standards problem that's going to keep multiplying by city and by country. A reporting pipeline built to handle one jurisdiction's quirks and nothing else is a pipeline you'll be rebuilding in two years when the next city adopts its own version.

Build vs. buy vs. augment: picking the right approach for your portfolio

The right answer depends on portfolio size and data complexity, not on which vendor has the best sales deck. Here's a rough framework we use when a client brings us a compliance reporting problem:

• Under 10 buildings, standard metering: A compliance software subscription or a consultant doing manual aggregation is usually fine. The data volume doesn't justify custom engineering, and the annual cost of a SaaS tool is lower than a build.

• 10-50 buildings, mixed submetering, multiple utilities: This is the zone where off-the-shelf tools start to strain. Submeter allocation logic, tenant billback reconciliation, and inconsistent utility bill formats across accounts usually need custom normalization logic that generic compliance software doesn't handle well out of the box. This is also where the manual-analyst approach starts costing more in labor than it would cost to automate.

• 50+ buildings, multi-jurisdiction, or frequent portfolio changes (acquisitions, refinancing, tenant turnover): At this scale, a custom data pipeline that ingests utility data automatically, normalizes it, and feeds both your Local Law 97 filing and your BERDO or Energize Denver filing from the same underlying dataset pays for itself quickly. You're not filing once; you're filing every year, in every jurisdiction you operate in, and the cost of a bad manual process compounds annually.

The mistake we see most often is buying a point solution scoped to exactly one law, then having to bolt on another tool when the portfolio expands into a second city. If you're already weighing build-versus-buy decisions for adjacent CRE operations problems, the logic tracks closely with what we've laid out for lease abstraction software on non-standard CRE portfolios: generic tools work until your portfolio's complexity exceeds what the tool was designed for, and the signal is usually submetering, multi-jurisdiction filing, or frequent portfolio changes.

Where AI agents genuinely help

The honest version of this: AI agents don't change the law, and they don't replace the Registered Design Professional who has to certify your filing. What they're good at is the grinding, error-prone work between "we have utility bills" and "we have a certified emissions number," which is exactly where manual processes break down at scale.

Concretely, that means an agent that ingests utility bills across accounts and formats (PDFs, portals, EDI feeds) and extracts usage data automatically, instead of someone copying numbers into a spreadsheet. It means normalization logic that converts everything to consistent units and maps usage to the correct building and meter, including submeter reconciliation in multi-tenant properties where tenant and owner usage need to be separated correctly. It means the emissions calculation itself, run against the latest published factors, with exceptions flagged automatically when a bill is missing, a read looks anomalous, or a building's usage pattern shifts in a way that needs a human look before the RDP signs off. And increasingly, it means feeding that same normalized dataset into retrofit and ECM prioritization, so a portfolio manager can see which buildings are closest to breaching the 2030 cap and where a capital dollar buys the most emissions reduction.

None of this is hypothetical capability. Genta AI Solutions has built utility billing automation that handled the full flow from field data to invoicing for an energy services firm, recovering revenue that manual processes were leaking (see the C&G Energy Services case study), and separately built a prospecting pipeline that profiled energy efficiency opportunity across 18 million square feet of commercial property using utility-rate data and vision AI (detailed in how we mapped 18 million square feet). To be precise: neither of those is a Local Law 97 compliance filing in itself. They're the same underlying capability, aggregating and normalizing messy utility and building data at portfolio scale, applied to a different output. That's the honest proof point here, not a claim that we've filed BEAM reports for anyone.

If you're building AI into a real estate or property operations stack more broadly, our piece on what enterprise PropTech teams actually build with AI agents covers the wider pattern of where this capability shows up across the industry, from leasing to maintenance to exactly this kind of regulatory reporting.

What to do before the next deadline hits

Start by auditing your data, not your compliance strategy. Pull every utility account across your portfolio and check for gaps, format inconsistencies, and submeter allocation logic that nobody's documented. Most owners find the law is the easy part to understand; the data behind it is where the actual risk lives. Second, model your 2030 exposure now, not in 2029. If your buildings are compliant today only because the first-period caps are loose, you need a retrofit and reporting plan years before the tighter caps bite, not months. Third, decide deliberately whether a subscription tool, a consultant, or a custom pipeline fits your portfolio's complexity, using scale and jurisdiction count as the deciding factors rather than which vendor called first.

If you're working through this decision, this is exactly what Genta AI Solutions' Discovery phase maps out before any engineering starts: what your data actually looks like, where it breaks, and whether the fix is a tool, a process change, or custom automation on your AI automation stack. We're happy to compare notes.

Frequently asked questions

How do I comply with Local Law 97?

Comply by staying under your building's emissions cap for the current compliance period and filing an annual greenhouse gas emissions report through DOB NOW: BEAM, certified by a Registered Design Professional, by the June 30 deadline (extendable to August 29). The real work is maintaining accurate, complete utility data across every meter year-round so that report is correct, not scrambled together under deadline pressure.

What are the penalties for not complying with Local Law 97?

Exceeding your emissions cap costs $268 per metric ton of CO2e over the limit, every year it remains uncorrected. Failing to file costs $0.50 per square foot per month. Submitting a false statement can carry penalties up to $500,000. These aren't one-time fines; cap violations recur annually until the building comes into compliance.

Is Local Law 97 still in effect?

Yes. As of this writing, Local Law 97 is active and enforced for the 2024-2029 compliance period, with no citywide suspension. Owners sometimes mistake individual legal challenges or extension requests for a broader pause, but NYC's own technical assistance program confirms non-compliance still carries significant fines.

What other cities have building performance standards like Local Law 97?

Boston's BERDO, Denver's Energize Denver, and Washington State's Clean Buildings Act all impose similar emissions caps or energy performance requirements with disclosure obligations on commercial buildings. The EU's recast EPBD requires member states to set equivalent minimum performance standards nationally. This is an accelerating multi-jurisdiction pattern, not an isolated NYC rule.

How is a building's Local Law 97 emissions limit calculated?

The cap is based on your building's occupancy classification (office, residential, retail, and so on) multiplied by a square footage-based emissions intensity limit set by the city for each compliance period, then compared against your actual annual emissions calculated from utility usage and the relevant emissions factors. Mixed-use buildings calculate caps per occupancy type within the same structure, which is where manual math most often goes wrong.