Indian listed companies are publishing more climate and sustainability claims in BRSR narratives, annual reports, and investor presentations. The same claims are now being read by large buyers, lenders screening transition risk, activist investors, and, increasingly, regulators who have signalled interest in misleading environmental statements. The practical problem is not the absence of a policy. It is the absence of a short, board-owned protocol that flags a claim before it is published when the supporting evidence is incomplete, outdated, or dependent on assumptions that have not been minuted. This briefing is for boards, audit and risk committees, CFOs, and the finance and sustainability officers who prepare the papers.
The setting is India under BRSR and the phased BRSR Core assessment-or-assurance requirement. The same discipline applies to unlisted groups answering European or Japanese customer questionnaires. A claim that cannot be re-performed from documents already in the system is not a governance decision. It is a communications choice that becomes expensive when challenged. Boards that wait for the first external query will discover that the evidence they need was never collected, or was collected under a different boundary.
1. Why greenwashing claims arrive after the BRSR is published, not before
Most Indian companies still treat the BRSR narrative as a year-end compilation exercise. Sustainability teams gather numbers, finance reviews the indicators that sit inside BRSR Core, and the board sees a short paper that compares the company with sector peers. The paper rarely contains a column that asks, for each quantitative or comparative claim, “what document would an outsider need to re-perform this number six months from now?” When that question is not asked, claims that rely on one-off calculations, supplier self-declarations without contracts, or intensity improvements that will be overwhelmed by volume growth pass into the public domain. The first external challenge then arrives when the company is least prepared: after the report is filed, the investor presentation is circulating, and the assurance provider has already signed off on the Core indicators.
Indian boards already know this pattern from financial reporting. A non-GAAP measure that is not reconciled to the audited numbers is challenged by analysts. A forward-looking statement that is not accompanied by the assumptions the board has already stress-tested is later treated as a restatement risk. Sustainability claims should face the same test. The difference is that the evidence is distributed across plants, projects, suppliers, and external ratings rather than sitting in one general ledger. That distribution is not an excuse for skipping the test. It is the reason the test must be designed as a standing protocol rather than a one-time review before publication.
The cost of getting this wrong is not only an assurance finding on BRSR Core. Large buyers already ask suppliers to show the capital path or the supplier data behind a claim. Lenders that have begun to price climate risk treat an unexplained residual as a data-quality issue. Activist investors and rating agencies can amplify a single poorly supported sentence into a broader greenwashing narrative. All three audiences can reprice or reallocate before the company has time to rebuild the file.
Further reading on DrDPKlass: how boards should test a net-zero pledge against the capital allocation cycle and how finance teams should prepare BRSR Core for limited assurance. The early-warning protocol sits between those two files.
2. Building a short list of high-risk claim signals that Indian boards can actually monitor
A usable protocol does not try to review every sentence. It focuses on a short list of claim types that have already produced challenges in India and other emerging markets. The list is short enough to fit on one page and stable enough that the same signals can be checked every quarter.
| Claim type | Why it is high-risk in the Indian setting | Minimum evidence the board should require |
|---|---|---|
| Absolute or intensity reduction versus a base year | Base year often chosen for convenience; production volumes have changed; boundary may differ from BRSR Core. | Reconciliation to BRSR Core energy/GHG indicators under the same boundary; volume bridge minuted. |
| Net-zero or science-based target | Horizon longer than capital plan; residual path not linked to approved projects. | One-page bridge to committed or pipeline capex; residual explicitly stated. |
| Percentage of renewable energy or green finance | Definition of “green” not aligned with BRSR or lender criteria; power purchase agreements still under negotiation. | Contract or PPA reference; classification consistent with the company’s own green-finance policy. |
| Supplier or value-chain engagement coverage | Percentage based on number of suppliers rather than emissions or spend; no data-sharing agreement. | Spend- or emissions-weighted coverage; sample of contracts or data-sharing terms. |
| Third-party rating or score improvement | Rating methodologies change; company may have changed boundary or data provider. | Prior-year and current-year methodology notes; confirmation that the same boundary was used. |
The board does not need to invent new metrics. It needs to decide which of these claim types appear in the current narrative and which documents already exist that would allow an outsider to re-perform them. Claims that cannot be mapped to an existing document are either dropped, softened to qualitative language, or held until the evidence is built. Holding a claim is cheaper than withdrawing it later.
3. Assigning owners so the protocol does not sit only with sustainability
Indian companies that leave greenwashing defence solely with the sustainability team create two problems. First, the team rarely controls the capital plan, the supplier contracts, or the general-ledger boundaries that determine whether a number can be re-performed. Second, when a challenge arrives, the board and the CFO discover that the supporting file was never designed for external scrutiny. The practical fix is a three-owner structure that uses roles the company already has.
Finance / Controller
Owns the claim register, the reconciliation to BRSR Core indicators, and the confirmation that any capital or operating spend supporting a claim is already in the approved plan.Sustainability / ESG lead
Identifies the claims that are material to buyers, lenders, or ratings; maintains the technical notes on boundaries and methodologies; flags when a methodology changes.Legal / Company secretary
Reviews the final language for statements that could be read as factual rather than aspirational; ensures the board minute records the residual risks that were accepted.Internal audit or risk
Performs a light quarterly sample of high-risk claims; reports exceptions to the audit committee before the assurance window opens.The protocol does not require a new committee. It requires that the existing audit or risk committee sees a one-page exception report once a quarter. The report lists only the claims that failed the evidence test and the decision taken (drop, soften, or hold). Claims that passed do not need to be discussed unless the methodology has changed. This keeps the board conversation short and focused on residual risk rather than on the entire narrative.
A greenwashing protocol that lives only in the sustainability team is how claims detach from the documents the board and the CFO already control.
4. Running a quarterly claim-to-evidence test before the assurance window opens
The test itself is deliberately mechanical so that it can be re-performed. For each high-risk claim on the register, the owner confirms three things: the source document still exists and is dated, the number in the source document matches the number in the narrative (or the difference is explained), and the boundary used in the source document is the same boundary used in the BRSR Core indicators that will be assured. The test is run at least once before the assurance provider begins work and again before the investor presentation is finalised.
Three common failure modes appear in Indian files. First, the base year used in the narrative is not the base year used in the assured indicators, and no bridge has been prepared. Second, a renewable-energy percentage includes power that is contracted but not yet delivered, or includes certificates that the company has not yet decided to retire. Third, a supplier-engagement percentage counts the number of suppliers that attended a workshop rather than the share of spend or emissions covered by a data-sharing agreement. Each of these can be caught by the mechanical test. Each becomes an easy finding or an easy external challenge if it is not caught.
The test also forces a conversation about what the company will do if a claim fails. Options are limited and should be decided in advance: remove the claim, change it to qualitative language, or postpone publication until the evidence is complete. Deciding the option in the moment, under time pressure, is how weak claims survive. The protocol simply makes the decision rule explicit.
5. What the board minute must record so the protocol can be re-performed
Assurance providers and, later, external parties will ask how the board satisfied itself that the claims were supportable. A minute that says only “the BRSR was reviewed and approved” does not answer the question. The minute should record four items that are short enough to be written in one paragraph.
- The claim register was presented and the high-risk claims were identified.
- Exceptions were either resolved or accepted with a named residual risk and an owner.
- The boundary used for any quantitative claim is the same boundary that will be used for the assured BRSR Core indicators, or the difference is explained.
- The next review date is set, normally the quarter before the next assurance window.
The minute does not need to reproduce the entire register. It needs to show that the board saw the exceptions and made a conscious decision about residual risk. That decision is what allows the company to answer a later query with “the board accepted this residual on this date, with this owner, and the evidence file is here.” Without the minute, the company is left reconstructing intent after the challenge has already been made public.
6. Handling investor and regulator queries without inventing new evidence
When a query arrives, the protocol determines the response speed and the quality of the answer. The first step is to locate the claim on the register and retrieve the source document that was already identified. If the document supports the claim under the same boundary, the response is a short extraction plus the board minute that accepted any residual. If the document does not support the claim, or the boundary has changed, the company has two honest options: correct the public statement or explain the residual that the board already accepted. Inventing a new calculation or a new supplier survey after the query arrives is how a limited challenge becomes a broader greenwashing narrative.
Indian companies should also prepare a short holding statement that can be used while the file is retrieved. The statement confirms that the claim is supported by documents already reviewed by the board and that a detailed response will follow within a stated number of days. The holding statement is useful for both investor relations and for any regulatory or stock-exchange query. It buys time without creating new commitments. The underlying file must already exist; the holding statement does not create the file.
Sector and size matter. A large manufacturer with multiple plants will have more boundary and volume issues than an IT services company. Both can use the same protocol. The difference is the length of the claim register, not the structure of the test or the minute. Consistency of structure is what allows the assurance provider, the board, and later an external party to re-perform the judgement without starting from scratch.
7. Field checklist before the next BRSR cycle
- Claim register exists and is owned by finance, with sustainability and legal as co-signatories.
- High-risk claim types (absolute/intensity reductions, net-zero targets, renewable percentages, supplier coverage, rating improvements) have been mapped.
- Each high-risk claim has a named source document, owner, refresh date, and residual-risk note.
- Quarterly claim-to-evidence test is scheduled in the same week as the BRSR Core indicator close.
- Exceptions go to the audit or risk committee as a one-page paper; no open exceptions when assurance begins or the investor presentation is locked.
- Board minute records that the register was seen, exceptions were resolved or accepted, and the next review date is set.
- Holding statement for external queries is drafted and available to investor relations and the company secretary.
- Boundary used for public claims matches the boundary that will be assured under BRSR Core, or the difference is explained in the register and the minute.
The protocol is deliberately light. It does not require new systems, new consultants, or a parallel ESG committee. It requires that the documents the company already produces—capital plans, BRSR Core workbooks, supplier contracts, and board minutes—are used to test the claims the company is about to make public. Companies that install the protocol before the next assurance cycle will find that the first external challenge is answered with a file that already exists rather than with a file that must be built under pressure. That difference is the difference between a manageable residual and a greenwashing narrative.