India's CCTS Is Live: Who Is Covered, What Are the Penalties, and How to Prepare Now

India's compliance carbon market is no longer a policy discussion. It is a 2025 business reality for 294 designated consumers in energy-intensive industries.

The Prakriti portal launch in March 2026 changed that posture from optional to mandatory. The market is now operational. The BEE registry is live. RECPDCL is accredited as a verifier. The April 2026 sector expansion means companies that were not Designated Consumers six months ago may be now. And the first compliance period is running.

This guide is not a policy summary it is an operational document. We explain who is covered, what the intensity target framework means in practice, how the PAT-to-CCTS transition actually works mechanically, how NbS credits fit into the compliance framework, and what BEE's registry does at each step of the credit lifecycle.

Who Is Covered: The 294 Designated Consumers and Sector Logic

The CCTS notification identified 294 Designated Consumers (DCs) from eight initial sectors: aluminium, cement, chlor-alkali, fertilisers, iron and steel, petroleum refining, pulp and paper, and textile (man-made fibres and filament yarn). These sectors were selected based on their energy intensity, their economic significance, and their existing familiarity with BEE's regulatory framework through the PAT scheme. The 294 entities are not a fixed list BEE can add or remove entities as production capacity and energy consumption thresholds change.

The threshold for DC classification is typically tied to energy consumption at the plant level, not the corporate entity level. A company with multiple cement plants may have some plants classified as DCs and others not, depending on each plant's size. This creates a fragmented compliance picture for large conglomerates each DC unit has its own emission intensity target, its own compliance account, and its own credit purchase or sale position.

The April 2026 sector expansion adds new segments to this framework. Companies in those segments should verify their DC status immediately with BEE the obligation is statutory from the date of notification, meaning the compliance period begins at notification, not at the point when the company registers on Prakriti. Retroactive registration does not eliminate the compliance obligation for the period prior to registration.

The PAT to CCTS Migration: What Actually Changes and What Does Not

For the majority of the 294 DCs, CCTS is not their first encounter with BEE's regulatory framework. Most have been operating under the PAT (Perform Achieve Trade) scheme for multiple cycles since 2012. PAT created the institutional memory, the plant-level energy audit infrastructure, and the BEE relationship that CCTS builds upon. But the migration from PAT to CCTS is not a simple rebranding the unit of account, the compliance mechanic, and the market structure are fundamentally different.

PAT issued Energy Saving Certificates (ESCerts) denominated in metric tonnes of oil equivalent (MTOE) units of energy efficiency improvement. A plant that reduced its specific energy consumption below its target received ESCerts that could be sold to plants that missed their targets. The scheme rewarded relative efficiency improvement within a peer group. A plant that was inherently energy-efficient but improving slowly could receive ESCerts even while remaining a high-emitter in absolute terms.

CCTS operates in tCO₂e actual greenhouse gas emissions, not energy efficiency proxies. The target is an emission intensity benchmark (tCO₂e per unit of output) measured against a specific baseline year. The compliance obligation is to reach or fall below that benchmark by the end of the compliance period. Plants that outperform their intensity target generate surplus carbon credits. Plants that underperform must purchase credits either from surplus-generating DCs or from NbS offset projects to cover their shortfall.

The most important migration issue is the baseline year. CCTS emission intensity targets are calculated relative to a specific baseline year of production and emission data. BEE has used historical energy and emission data to set initial targets, but companies should verify which baseline year applies to their plant and whether the baseline data BEE holds accurately reflects their actual operating conditions. Disputes about baseline data can be raised through BEE's formal review process, but the window for doing so before the first compliance period closes is limited.

How Nature-Based Offsets Fit Into the CCTS Compliance Framework

CCTS is a compliance market, not a purely exchange-based scheme. DCs that cannot reach their emission intensity targets through operational improvements process efficiency, fuel switching, energy procurement can purchase carbon credits to cover their shortfall. These credits can come from two sources: surplus credits generated by other DCs that outperformed their targets, or offset credits generated by projects in non-obligated sectors including nature-based solutions.

The inclusion of NbS offset credits in the CCTS compliance framework is economically significant. It creates a domestic demand channel for Indian forest carbon, agroforestry, mangrove restoration, and grassland management projects that did not exist before CCTS. Previously, Indian NbS projects could only sell into the international voluntary market at international prices, denominated in foreign currency, subject to international buyer preferences. CCTS creates a domestic buyer base: 294 DCs with statutory obligations who may prefer to buy Indian NbS credits at domestic prices rather than purchasing international credits or competing on the exchange.

The eligibility conditions for NbS offset credits are more restrictive than for voluntary market credits. Projects must use BEE-approved methodologies which currently covers a narrower set of project types than Verra VCS or Gold Standard. Projects must engage BEE-accredited verifiers. The monitoring data standards are set by BEE's CCTS MRV guidelines, which may differ from international standard requirements in specific measurement frequency, uncertainty requirements, and reporting formats.

BEE Registry: How Credits Are Issued, Traded, and Retired

The BEE carbon registry, accessible through the Prakriti portal, manages the complete lifecycle of CCTS credits. Understanding how the registry works is essential for both DCs managing compliance positions and NbS project developers seeking to generate and sell offset credits.

For NbS offset project developers, the registry lifecycle begins at project registration. The developer submits a project design document (PDD) specifying the project type, the BEE methodology being applied, the baseline emission scenario, the monitoring plan, and the expected annual credit generation. BEE reviews and approves the PDD this is the methodology validation step. Once approved, the developer implements the project according to the monitoring plan.

At the end of each monitoring period (typically annual), a BEE-accredited verifier currently RECPDCL, with additional agencies expected audits the monitoring data against the approved plan, verifies the emission reduction calculation, and issues a Verification Report. BEE reviews the Verification Report and issues carbon credits to the developer's Prakriti account. The credits are serialised, carry a vintage year, and are immediately transferable on the exchange.

For DCs, the compliance cycle works differently. The DC submits production output data and emission data to BEE at the end of the compliance period. BEE calculates the achieved emission intensity and compares it to the target. If the DC has outperformed its target, BEE issues surplus carbon credits to its Prakriti account. If the DC has a shortfall, it must purchase enough credits either exchange-traded or bilaterally negotiated to cover the gap, and then execute a retirement transaction on Prakriti to formally discharge the compliance obligation.

Credit retirement is permanent and irreversible. A retired credit is removed from the circulation pool and cannot be resold, re-traded, or reclaimed. The retirement transaction generates a retirement certificate that the DC can use as evidence of compliance in BEE reports, BRSR disclosures, and in any Article 6 corresponding adjustment documentation if the credit has international linkage.

What CCTS Means for Sylithe's NbS Clients

For Sylithe's nature-based solution project clients, CCTS changes the revenue architecture of their projects in three specific ways. First, the domestic demand channel is now open DCs are potential buyers who were not in the market previously. Second, the methodology and MRV requirements create a quality screen that advantages projects already operating with continuous satellite monitoring and rigorous data standards. Third, the dual-market option selling some credits domestically through CCTS and some internationally through voluntary markets or Article 6 requires careful registry management to avoid double-counting.

Sylithe's dMRV pipeline is designed to meet CCTS MRV requirements the monitoring frequency, the verification data standards, and the uncertainty quantification requirements that BEE specifies. Projects monitored through Sylithe can generate Verification Reports structured for both BEE registry submission and international standard reporting, enabling the dual-market approach without duplicating monitoring infrastructure costs.

The most important immediate action for NbS project developers is methodology alignment. BEE's approved methodology list is shorter than Verra's and the specific MRV requirements may differ even where the project type is nominally the same. Developers should conduct a methodology gap analysis before assuming their existing VCS-certified project qualifies for CCTS offset credit generation. The gap analysis can often be completed in 4–6 weeks and identifies exactly what documentation upgrades or monitoring changes are required.

CCTS is live. The registry is open. The compliance period is running. The only question is whether you are prepared or catching up.