How Indian Boards Should Test a Net-Zero Pledge Against the Capital Allocation Cycle Before They Approve the BRSR Narrative

Indian listed companies are under pressure to publish net-zero or science-based targets in their BRSR narratives. The pressure comes from large buyers, lenders screening climate risk, and the simple desire to look comparable with global peers. The risk is that the target is approved as language long before it is tested against the capital allocation cycle the board already runs for capacity, maintenance, and returns. When the trajectory cannot be traced to approved projects, expected returns, or a clear residual path, the assurance provider for BRSR Core has an easy finding, and external parties have an easy greenwashing claim. This briefing is for boards, audit and risk committees, 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 that ask for a net-zero pathway. A pledge that is not anchored in the capital plan is not a governance decision. It is a communications choice. Boards that treat the two as separate will eventually face a restatement, a qualification, or a lender request for more data than the company can produce.

1. Why net-zero language appears in BRSR before the capital plan does

Most Indian companies still set capital budgets on a one-to-three-year horizon driven by demand visibility, return hurdles, and liquidity. Net-zero targets, by contrast, are often written as 2040 or 2050 aspirations. The gap between the two horizons is where language outruns evidence. A sustainability team drafts a target that looks ambitious relative to peers. The board sees a short paper that compares the target with sector averages and approves the narrative for the BRSR. The capital plan for the next three years, already approved or about to be approved, contains little or no spend that would change the emissions trajectory in a measurable way. The target remains an aspiration until someone asks how the company intends to close the gap.

Indian boards already know this pattern from other long-horizon claims. A growth target that is not supported by capacity additions is treated with scepticism by the audit committee. A dividend policy that is not stress-tested against the cash-flow forecast is challenged. Climate targets should face the same test. The difference is that the evidence is distributed across plants, projects, and suppliers rather than sitting in one financial model. That distribution is not an excuse for skipping the test. It is the reason the test must be designed before the narrative is approved.

The cost of getting this wrong is not only an assurance finding. Large buyers in Europe and Japan are already asking suppliers to show the capital path behind a target. Lenders that have begun to price climate risk into working-capital lines treat an unexplained residual as a data-quality issue. Both audiences can reprice or reallocate before the company has time to build the evidence.

Further reading on DrDPKlass: how credit committees should treat climate risk in working-capital lines and how finance teams should build a Scope 3 boundary without inventing supplier emissions. The capital allocation test sits between those two files.

2. Mapping the pledge onto the existing capital allocation calendar

The simplest way to test a target is to use the calendar the board already runs. Most Indian groups have a mid-year or year-end capital review in which projects above a stated threshold are ranked by return, strategic fit, and cash requirement. Climate-related projects should enter that same review rather than a parallel sustainability process. The board paper for the target should therefore contain three columns: projects already approved that reduce emissions, projects under active evaluation, and residual emissions that will remain after those projects are executed at the assumed rate.

The mapping does not require a full internal carbon price on day one. It requires that every material emissions reduction claimed in the narrative can be traced to a project code, a plant, or a contract that already exists in the capital system. If the reduction comes from a technology that has not yet been piloted, the narrative should say so and state the decision gate at which the board will revisit the claim. Silence on the gate is how aspirations become targets that later need restatement.

Finance must own the mapping. Sustainability officers can identify the projects that have climate benefits. Only the controller or the capital-planning team can confirm that the project is in the system, has a cost code, and has cleared the return hurdle the board applies to other spend. A joint sign-off forces the conversation into the same language used for ordinary capital allocation. The resulting bridge is short enough for a board paper.

3. Separating committed capex from contingent aspirations

Indian capital systems already distinguish between committed and contingent spend. Committed projects have board or investment-committee approval, a signed contract or purchase order, and a cash-flow forecast that is included in the liquidity plan. Contingent projects have a concept note and a target return but no approval and no cash reserved. The BRSR narrative should use the same distinction. A reduction that depends on a contingent project is not a committed reduction. It is a scenario.

The practical test is simple. For every quantitative reduction claimed in the next five years, the paper should state whether the spend is already committed. If it is not, the claim should be moved to a scenario box rather than the base trajectory. Boards that allow contingent spend to support base-case language create two problems. First, the assurance provider cannot re-perform the number because the underlying project may never be approved. Second, the company has made a public statement that later requires either an unplanned capital allocation or a restatement. Both outcomes are more expensive than writing the distinction clearly in the first place.

The same logic applies to value-chain claims. A supplier engagement programme that has no contracted volume, no data-sharing agreement, and no cost in the capital or operating plan is not a committed reduction. It is an aspiration. The Scope 3 boundary work already done for BRSR Core should be used to identify which categories have data quality high enough to support a claim and which do not.

A capital allocation cycle that treats climate projects as a separate queue is how net-zero language detaches from the numbers the board actually controls.

4. Stress-testing the trajectory against BRSR Core energy and emissions indicators

BRSR Core requires companies on the glide path to report energy and GHG indicators and to subject them to assessment or assurance. The trajectory in the narrative must be consistent with those indicators. The practical way to enforce consistency is to run the same stress cases the board already uses for liquidity and returns. Three cases are usually enough.

The base case uses only committed projects and the production volumes already in the business plan. The delayed case assumes that one or two large projects slip by twelve months, a common outcome in Indian execution environments. The volume-upside case assumes that demand exceeds the plan and therefore absolute emissions rise even if intensity falls. The narrative should state which case is being used for the published target and what the board will do if the delayed or volume-upside case materialises. Silence on the response is how targets become stranded.

The stress also reveals whether the company is relying on intensity improvements that will be overwhelmed by volume growth. Many Indian manufacturing and infrastructure companies will see absolute emissions rise for several years even while intensity improves. The BRSR narrative should say so rather than imply that absolute emissions will fall on the same schedule as intensity. Assurance providers can compare the narrative with the absolute and intensity numbers already reported under BRSR Core. Inconsistency is an easy finding.

Sector context matters. A cement company and an IT services company will not face the same residual. Both can still use the same structure: committed projects, delayed case, volume case, and residual. The structure is what allows the assurance provider and the board itself to re-perform the judgement next year.

5. Documenting residual emissions and the limited role of offsets in the Indian context

Every net-zero claim has a residual. In India the residual is often large because the electricity grid still contains coal, process emissions in cement and steel are hard to abate, and many suppliers are outside the company’s direct control. The board paper should quantify the residual under the base case and state the levers the company intends to use after the current capital cycle. Those levers may include further technology, product redesign, or value-chain engagement. They should not be described as already secured.

Offsets deserve special treatment. Indian companies have limited access to high-quality domestic credits, and international credits face both cost and reputational risk. The board should set an explicit ceiling on the volume of residual that may be closed with purchased credits and should require that any credit purchase above a stated amount comes back for approval. The ceiling should be expressed as a percentage of the residual, not as an open-ended “we will offset what we cannot abate.” An open-ended statement is how residuals disappear from scrutiny.

The residual note also serves the next capital cycle. When the board next reviews projects, it can see which residual categories remain and which projects would address them. Without the note, climate projects compete with ordinary projects on return alone and the residual grows by default. The note is therefore both a disclosure control and a capital-allocation input.

6. What the board minute must record so assurance providers can re-perform the judgement

Assurance providers under BRSR Core need to understand the basis on which management prepared the information. For a net-zero or science-based claim, the basis is the capital allocation test. The minute should therefore record four items in plain language.

First, the target year and the residual quantity under the base case. Second, the list of committed projects that support the near-term trajectory and the decision dates for any pipeline projects that have been allowed into a conditional claim. Third, the offset ceiling and the quality criteria. Fourth, the date on which the board will revisit the trajectory against actual capital spend and actual emissions. A minute that says only “the board approved the net-zero target” does not allow re-performance. A minute that points to the one-page bridge and the four items does.

The same minute should note any topics that were considered and excluded. If the board decided that a particular Scope 3 category was too uncertain to support a numeric claim, that decision should be recorded. Silence on exclusions is how the claim expands in the next reporting cycle without a fresh test. The minute is short. It is also the document the assurance provider will ask for when the narrative and the BRSR Core indicators appear inconsistent.

A board minute that cannot be used by an assurance provider to re-perform the capital allocation judgement is not a control. It is a record of a conversation.

7. Field checklist before the next BRSR cycle

Boards and the officers who prepare their papers can use the following list before the narrative is locked. Each item can be answered with a document that already exists or with a short note that can be created in one meeting.

1. Does a one-page bridge exist that links the target year, the residual, and the projects already in the capital system?
2. Are committed, pipeline, and aspirational reductions distinguished in the same language the capital plan already uses?
3. Has the trajectory been stress-tested against a twelve-month delay and against a volume-upside case, and is the published claim based on the base case only?
4. Is the absolute emissions number implied by the near-term target reconcilable to the BRSR Core energy and GHG indicators?
5. Has an explicit ceiling been set on the use of purchased offsets, and is any volume above the ceiling treated as unapproved?
6. Does the board minute record the residual, the committed projects, the offset ceiling, and the next review date so that an assurance provider can re-perform the judgement?

The same checklist works for companies that have not yet set a formal net-zero target but are being asked by buyers or lenders for a pathway. The absence of a target does not remove the need for a residual note and a capital mapping. It simply means the mapping is prepared as an internal control rather than as public language. In both cases the discipline is the same: language follows the capital allocation cycle, not the other way around.

Indian boards already apply this discipline to growth, dividends, and leverage. Applying it to climate claims is not a new governance burden. It is the extension of an existing control to a new class of public statement. The companies that make the extension early will find the next assurance cycle and the next buyer questionnaire easier to answer. The companies that treat the target as a communications exercise will spend the following year explaining the gap.