BRSR Core did not ask Indian listed companies for a prettier sustainability story. It asked them for a short list of numbers that an assurer can test and that a buyer, lender, or regulator can reuse. Finance teams still treat the file as something the ESG cell drafts in March and the statutory auditor glances at in May. That sequence is how value-chain percentages get invented, how energy intensity jumps without a restatement note, and how a limited-assurance letter becomes a public-relations object rather than an audit object. This briefing is a playbook for putting BRSR Core on the same discipline as a segment note: named boundary, named owner, reconcilable source, and a sentence the assurer can fail.
The setting is India after SEBI’s BRSR Core and value-chain disclosure glide path, with limited assurance already on the calendar for the larger listed set and with mid-cap issuers next in line. The same habits travel to other emerging markets that have copied a “core KPI plus assurer” model and then discovered that the plant manager and the consultant do not share a spreadsheet.
1. Why BRSR Core is a finance file, not a sustainability brochure
Annual reports already contain two kinds of non-financial text. One kind is narrative: strategy, culture, community photographs. The other kind is a claim that a third party will later reuse as if it were a number—water intensity, lost-time injury rate, percentage of value-chain partners assessed. BRSR Core belongs to the second kind. Once a number sits in a filed annex and an assurer has put a limited-assurance paragraph next to it, the company has created a capital-market statement. Treating it as brochure copy is an internal-control failure, not a communications choice.
Finance owns three things the ESG cell cannot own alone. First, the organisational boundary that already exists for consolidation, related-party maps, and joint-venture accounting. Second, the year-on-year bridge: if energy use fell because a plant was sold, the note must say so in the same voice as a discontinued-operation line. Third, the archive. Assurers follow paper. If the working file lives in a consultant’s mailbox, the company does not have a file.
This is not an argument for moving every ESG sentence into the CFO’s office. Community programmes and board skills matrices can stay with company secretary and HR. The Core table is different because it is designed to be compared across issuers. Comparability without a ledger discipline is how greenwashing migrates from adjectives into percentages.
2. Draw the organisational and value-chain boundary before you count
Most BRSR fights in year two are not about methodology. They are about last year’s silent change in what “the company” meant. A unit that was inside the energy total is now a lease. A contractor headcount that sat in “workers” has been reclassified as value chain. A joint operation that reported water last year is now “not operationally controlled.” If the boundary note is written after the numbers, the assurer will find the change and the board will discover it in the closing meeting.
2.1 Organisational boundary
Start from the entities in the consolidated financial statements. Then write, in one page, which of those entities are in the Core table, which are excluded, and why. Operational control is a defensible rule if you apply it the same way you apply it to safety incidents. Financial control is a defensible rule if you apply it the same way you apply it to revenue. Mixing the two without a map is how a clean plant stays in the photograph and a dirty associate drops out of the intensity denominator.
2.2 Value-chain boundary
Value-chain rows are where Indian files most often invent coverage. “Top 75 percent of purchases by value” is a sentence an assurer can test only if procurement can produce the ranked vendor list, the same list used for related-party and MSME ageing, and a definition of what “assessed” means. Assessed cannot mean “we sent a Google form.” Assessed means a named questionnaire or audit protocol, a response on file, and a date. If the protocol changed mid-year, say so. Silent upgrades are restatements wearing a sustainability badge.
3. Treat each Core KPI as a ledger claim with an owner
Do not assign “BRSR” to a single sustainability manager and hope the plants email numbers in time. Split the Core table the way you split a consolidation pack: one owner per family of KPIs, a backup, a source system, and a cut-off date.
| KPI family | Natural owner | Source the assurer will ask for |
|---|---|---|
| Energy and emissions (Scope 1 and 2) | Works / utilities with finance reconciling invoices | Fuel purchase ledgers, grid bills, generation logs, factor sheet with vintage |
| Water withdrawal, consumption, discharge | Plant EHS with finance on municipal and tanker invoices | Meter logs, tanker bills, consent limits, discharge reports |
| Waste generated and diverted | EHS plus stores | Manifests, authorised-recycler invoices, yard stock of hazardous waste |
| Workforce and safety | HR / industrial relations | Muster, contractor gate logs, incident register, lost-day calculations |
| Gender and wages where Core requires them | HR with payroll | Payroll extract that matches the financial-statement employee cost |
| Value-chain assessment coverage | Procurement with legal on protocol | Ranked spend, questionnaire file, date-stamped responses |
Intensity ratios need a denominator the financial statements can recognise: output in a unit the plant already uses, revenue that matches a reported segment, or floor area that matches the fixed-asset register. Inventing a “production equivalent” in March is how year-on-year improvement appears without a single tonne moving.
4. How value-chain rows become greenwashing if you estimate in the dark
Greenwashing in BRSR Core is rarely a fake solar plant. It is a coverage percentage that looks precise and rests on a sample nobody can reconstruct. Three patterns show up in Indian mid-cap files.
Pattern one: spend without protocol. The company ranks vendors, stops at 75 percent, and ticks “assessed” because a third-party platform sent an email. The assurer asks for completed responses above a materiality threshold. Half the file is “pending.” The percentage in the table was calculated on emails sent, not on evidence received.
Pattern two: Scope 3 by brochure factor. A single emission factor is applied to all purchased goods because “that is what the consultant used last year.” No category map, no distinction between steel and stationery, no note that 40 percent of spend has no factor at all. The resulting tCO2e is then compared with last year as if the method were stable.
Pattern three: worker counts that float between own and contract. Safety rates improve because high-risk contractor hours were moved into “value chain” and out of the Core workforce table, without a bridge. The board is shown a declining injury rate. The gate log still shows the same people.
A value-chain claim is honest when a sceptical reader can name the population, the test applied, the response rate, and the incomplete slice. Anything smoother than that is design, not measurement.
If you cannot complete the value-chain row this year, publish the population, the coverage you actually hold, and the gap. A 48 percent assessed figure with a method note is more useful to a lender than a 75 percent figure that collapses in the first assurance query. Emerging-economy supply chains are incomplete by nature. Pretending they are complete is the greenwashing.
5. What a limited-assurance team will actually test
Limited assurance is not “we read the PDF.” It is a set of procedures that stop short of a reasonable-assurance sample but still require evidence. Finance teams that prepare as if the assurer will only check arithmetic are surprised by four questions.
- Completeness of sites. Does the site list in the working file match plants in the fixed-asset register, pollution consents, and last year’s table? Missing a small foundry is more damaging than a rounding error on the large campus.
- Factor pedigree. Which emission or conversion factors, which vintage, which authority? A screenshot of a 2018 slide is not a factor sheet.
- Cut-off and estimates. Which months were metered and which were extrapolated? Year-end tanker water that sits in a provision is still water.
- Restatement logic. If last year’s number moved, is there a bridge that a user of the annual report can follow? Silent restatement is a governance event.
Limited assurance will not rebuild your entire Scope 3 inventory. It will test whether the method you disclosed is the method you used. That is why the method note must be written by the same people who built the spreadsheet, not by the design agency that laid out the ESG chapter.
6. The working-paper pack a CFO can defend in one sitting
Build one pack, freeze it on a date, and give the assurer that pack—not a running Google Drive. Eight tabs or folders are enough.
1. Boundary memo
Entities, sites, inclusions, exclusions, value-chain population rule, signed by finance and company secretary.2. Owner map
KPI family, named owner, backup, source system, cut-off date.3. Factor register
Every conversion factor with source, vintage, and who approved a local override.4. Site workbooks
One workbook per material site that reconciles to invoices or meters.5. Group bridge
Site sum to Core table, with acquisitions, disposals, and idle plants visible.6. Value-chain file
Ranked spend, protocol, responses, non-response list, definition of “assessed.”7. Prior-year bridge
Every restated cell with a one-line cause.8. Exception log
Estimates, missing meters, disputed contractor hours, open assurer queries.The CFO does not need to inspect every tanker bill. The CFO does need to see the exception log before the audit committee paper is circulated. Surprises that first appear in the assurer’s management letter are, by definition, a control failure in the pack.
Keep the narrative chapter and the Core table on different clocks. Design can slip a week. The Core freeze date cannot, because every late plant email becomes an untested estimate. If a number arrives after freeze, it goes to next year or to a disclosed subsequent-event note—not into a silent overwrite the night before printing.
7. What the board and audit committee should refuse to sign
Boards that already read ESG rating divergence know that raters disagree. Assurance does not remove disagreement. It only attests that the company’s own method was followed. The committee should refuse four objects.
- A Core table with no boundary memo attached to the same pack.
- Value-chain coverage above the response file the assurer has been shown.
- Year-on-year “improvement” without a prior-year bridge where the method or perimeter changed.
- An assurance scope that quietly excludes the KPI the annual-report headline is celebrating.
Ask one question in the pre-sign-off meeting: “Which cell would we withdraw if the assurer asked for the underlying invoice tomorrow morning?” If the room cannot name a cell, the pack is either unusually clean or unexamined. In Indian groups with multi-state plants and contractor-heavy yards, unexamined is the base rate. Plan for it.
8. Field checklist and closing brief
Use this as a ninety-day run-up, not as a March scramble.
- Freeze organisational and value-chain boundaries in writing; match them to last year’s table or disclose the bridge.
- Name an owner and a backup for every Core family; put utilities and payroll in the room, not only the ESG cell.
- Reconcile energy and water totals to invoice or meter populations before anyone writes intensity ratios.
- Define “assessed” for value-chain partners as a completed protocol, not an email sent.
- Build a factor register with vintage; ban unofficial slides as sources.
- Write the prior-year bridge before you celebrate improvement.
- Give the assurer a frozen pack with an exception log; stop overwriting cells after freeze.
- Align the headline language in the ESG chapter with the actual assurance scope and standard.
- Walk one material plant so the local owner can explain the monthly feed.
- Take the exception log to the audit committee before the letter is signed.
Limited assurance will not make an Indian value chain complete. It will make incomplete measurement visible. That visibility is the point of BRSR Core. Companies that treat the table as a finance file will spend the next three years improving meters, vendor files, and bridges. Companies that treat it as a chapter will spend those years restating quietly and arguing with assurers about what “assessed” meant in a footnote. The first path is slower in year one and cheaper in year four. The second path is how greenwashing survives after the adjectives have been removed.
Further reading on DrDPKlass: How Indian Boards Should Read ESG Rating Divergence · How Indian Credit Committees Should Treat Climate Risk in Working-Capital Lines.