An Indian textile manufacturer has been paying ₹6 lakh per year to a compliance consultant. The consultant visits twice a year — once mid-year to gather data, once in Q4 to compile and file the report. The output is a BRSR document: professionally formatted, Scope 1 and Scope 2 figures included, submitted to the exchange on time.
This worked for annual disclosure. The SEBI compliance box was checked. The audit committee received the report. Life continued.
Then CCTS arrived — and the same data infrastructure that produced the BRSR report is now supposed to support a continuous, verifiable emission intensity position on the Indian Carbon Market registry.
It cannot. Not because the consultant is incompetent. Because the model was designed for a different job.
The Old Model — What It Was Built For
The annual ESG consultant model operates on a simple workflow:
- Consultant contacts factory utility manager, purchase team, and HR
- Data requested: energy bills, fuel purchases, fleet logbook, refrigerant records
- Data compiled into spreadsheet — typically by source type
- Emission factors applied from a reference document
- Total Scope 1 and Scope 2 calculated
- Report produced, formatted, verified internally
- Submitted to the regulatory database
- Process complete for 12 months
For BRSR annual disclosure to SEBI, this model is functional. It produces a number. The number gets filed. Penalties for soft errors in BRSR are limited, and the verification standard for most BRSR disclosures is internal sign-off by management, not third-party audit.
The model was built for a world where compliance meant annual disclosure. CCTS is not that world.
Why It Breaks Under CCTS
1. The Audit Trail Problem
CCTS verification requires every tCO₂e to trace to a specific, immutable record. Not a summary table — a specific record. For each emission source, the verifier expects to see:
- The original activity data: the fuel purchase invoice, the electricity meter reading, the refrigerant top-up log
- The emission factor applied, with the specific IPCC table reference (e.g., IPCC 2006 Volume 2, Chapter 2, Table 2.2)
- The global warming potential used, with the AR version stated (e.g., AR6 100-year GWP for CH₄ = 27.9)
- The date the data was recorded, and by whom
An annual spreadsheet compiled months after the fact fails this standard — not because the consultant made up numbers, but because the source-to-result chain cannot be reconstructed and independently verified. There is no immutable record of when the data was entered, what the original source document said, or which factor version was applied at entry time.
The audit trail requirement is binary: either the chain of evidence exists, or it does not. Reconstructed chains do not satisfy ISO 14064 Part 3 verification requirements.
2. The Timing Problem
CCTS is a continuous compliance year. The emission intensity calculation covers April 2025 to March 2026 — 12 months of continuous data. A manufacturer seeking to demonstrate quarterly intensity improvement (to support a mid-year credit claim, or to demonstrate trajectory to the registry) needs month-level data.
Annual data collection — two visits per year — does not support this. If a verifier asks for July 2025 activity data separately from the full-year aggregate, an annual compilation cannot provide it. The data was never collected at monthly resolution; it was reconstructed from annual totals.
This is not an edge case. Credit issuance on the ICM exchange involves submitting intensity data for defined periods. Manufacturers who cannot demonstrate continuous tracking face both credibility risk and practical exclusion from the credit market.
3. The Verification Problem
ISO 14064 Part 3 defines the third-party verification standard for GHG inventories. CCTS credit issuance will require third-party verification from BEE-accredited verifiers. The verification standard looks for:
- Immutable, timestamped records (not editable spreadsheets)
- Consistent methodology application (same IPCC version used throughout, not mixed)
- Complete source coverage (no emission sources selectively excluded)
- Documented organisational boundary (which facilities, which consolidation approach)
- A written methodology statement signed by management
Consultant-produced BRSR spreadsheets typically cannot satisfy any of these criteria in their current form — because they were never designed to. The BRSR submission standard at most listed companies is management attestation, not ISO 14064 Part 3.
4. The Cost Multiplication Problem
As compliance requirements multiply — CCTS, BRSR, EU buyer questionnaires, lender ESG covenants, SBTi target-setting — the annual consultant model multiplies in cost. Each new requirement is a new engagement:
- BRSR: ₹4–8 lakh/year (established engagement)
- CCTS compliance: new engagement, additional scope
- EU buyer questionnaire: new engagement, different format
- Lender ESG review: new engagement, quarterly
Four separate compliance engagements drawing from the same underlying data — each producing a different document, none of them having access to a single source of truth. The same data re-collected four times by different teams, at different points, from different departments.
The cost does not just multiply in rupees. It multiplies in management time, in coordination overhead, in the risk of inconsistency between reports.
5. The Ownership Problem
When the consultant leaves — end of contract, firm change, consultant resignation — the institutional knowledge of how the GHG numbers were derived leaves with them. The manufacturer has a PDF. They do not have:
- The underlying activity data in queryable form
- The emission factor library and which versions are in their history
- The methodology rationale for how specific sources were classified
- The audit trail that would allow a new consultant to verify the prior year’s numbers
This is not hypothetical. When CCTS verification requires access to FY 2023–24 baseline data — the compliance year baseline — a manufacturer whose consultant relationship ended in early 2025 may find that the underlying data is not recoverable in verifiable form.
What CCTS Verification Actually Checks
A BEE-accredited CCTS verifier will assess the following:
Completeness: Every Scope 1 emission source at the facility is captured. No selective exclusion of inconvenient sources (e.g., backup diesel generators running during grid cuts).
Accuracy: The emission factor applied is from the correct IPCC table, for the correct fuel type, at the correct heat value. Factor versions are declared and consistent throughout.
Consistency: The same methodology is applied to the baseline year and the compliance year. If operational control consolidation was used in 2023–24, it must be used in 2024–25.
Transparency: The calculation is derivable from source data to final intensity figure. An independent verifier can reproduce the result.
Production denominator: The denominator (tonnes of fabric produced) is supported by production records — not management estimates. The unit of production matches the BEE sector-defined unit.
Period coverage: No gaps in monthly data. If electricity bills are quarterly, they must be prorated correctly.
What Sustaineve Does Differently
This is not an argument against using compliance consultants. Consultants provide interpretation, regulatory intelligence, and client-specific guidance that no platform replaces.
The argument is against the data infrastructure model. The consultant relationship should be built on top of a permanent data layer — not substituted for one.
Sustaineve provides that data layer. Every activity entry is timestamped. Every emission factor is cited by IPCC table reference. Every calculation is derivable from the raw entry. The data is owned by the manufacturer, not the consultant. It is queryable at any aggregation — monthly, quarterly, facility-level, source-level. The emissions measurement module applies IPCC 2006 and 2019 Refinement factors at source level — the same calculation chain a CCTS verifier will expect to trace.
When a CCTS verifier arrives, the data is not reconstructed. It is retrieved.
When a new consultant engagement starts, the underlying data is intact and portable. The consultant works with it; they do not recreate it.
When a buyer sends an ESG questionnaire, the export comes from the same verified source used for CCTS and BRSR — not a third round of data collection from the utility manager.
The consultant model was built for annual disclosure. CCTS requires continuous, verifiable data infrastructure. The difference is not the consultant — it is the data underneath.
Download the cost analysis → — a structured comparison of the annual consultant model vs permanent ESG data infrastructure.