If your market capitalization has moved you into a wider disclosure cohort, the practical question is no longer "what is BRSR" but BRSR Core 2026-27 specifically: does it apply to your listing this year, what value-chain data will you be asked for, and how ready is your evidence trail for assurance? This guide sets out applicability by market-cap cohort, the KPI data architecture behind the nine BRSR Core attributes, how to run value-chain data collection without overwhelming suppliers, and a practical checklist to move from "we report ESG" to "our ESG data would survive assurance."
BRSR, BRSR Core and value-chain disclosures explained
The Business Responsibility and Sustainability Report (BRSR) is SEBI's mandatory ESG disclosure format for listed entities under the Listing Obligations and Disclosure Requirements (LODR) framework. BRSR Core is a focused subset of that report — a smaller set of high-priority, quantifiable KPIs that SEBI has phased into mandatory assessment or assurance ahead of the full BRSR disclosure, precisely because these attributes are considered the most decision-useful and the most auditable.
BRSR Core comprises nine defined attributes — greenhouse gas emissions, water consumption, waste generation, energy consumption, gender diversity, wages and social security, inclusive development, customer/complaint fairness, and openness of business (structure and payments) — subject to a phased assessment-or-assurance requirement based on a listed entity's market-capitalization ranking. Value-chain disclosure extends part of this reporting obligation beyond the listed entity itself to its significant upstream and downstream business partners, which is the element most organizations underestimate the effort for.
SEBI's 28 March 2025 circular renamed the BRSR Core compliance mechanism from "assurance" to "assessment or assurance," reflecting that value-chain-level reporting in particular may proceed on a reasonable-effort assessment basis rather than requiring full assurance in every case. Confirm the exact assessment-versus-assurance distinction that applies to your entity and reporting year against the current SEBI circular, since the applicable standard can differ between the listed entity's own disclosures and its value-chain disclosures.
Applicability and phased coverage for FY 2026-27
BRSR Core applicability has expanded on a defined glide path tied to market-capitalization ranking, moving from a small initial cohort to a much broader set of listed entities. The phased design itself traces back to SEBI's expert committee recommendations on easing BRSR Core implementation, which shaped how the market-cap cohorts and value-chain relief were structured.
| Financial year | Applicable cohort | Assessment/assurance status |
|---|---|---|
| FY 2023-24 | Top 150 listed entities by market capitalization | Phase 1 |
| FY 2024-25 | Top 250 listed entities by market capitalization | Phase 2 |
| FY 2025-26 | Top 500 listed entities by market capitalization | Phase 3 |
| FY 2026-27 | Top 1000 listed entities by market capitalization | Phase 4 (current target year) |
Applicability by market-cap cohort
If your listed entity's market capitalization ranking places it inside the Top 1000 for FY 2026-27, BRSR Core assessment-or-assurance applies to you this year even if it did not in earlier years — market-cap rank is assessed each year, so an entity can enter or, in principle, exit a cohort as its ranking moves. Do not assume last year's applicability position still holds; re-check your ranking at the start of each reporting cycle, and confirm the exact ranking date and data source SEBI specifies for the determination, since this detail sits in the circular text rather than in general commentary.
Value-chain reporting applicability is a separate question layered on top of entity-level applicability: once a listed entity is in scope for BRSR Core, its significant upstream and downstream value-chain partners may be brought into scope for a defined subset of KPIs, based on a value-chain coverage threshold. Confirm the current value-chain coverage threshold (which partners must be covered, and any percentage-of-purchase or percentage-of-sales test) against the latest SEBI circular before scoping your supplier data request — this figure has been the subject of phased relief and clarification, so treat any percentage you have seen elsewhere as unconfirmed until checked against the current circular.
Request a BRSR Core readiness assessment from Himaya Prevention to get a written applicability position for your specific entity and reporting year, rather than relying on a general market-cap list that may already be out of date.
Entities that were already in scope in an earlier phase should not assume their existing process simply carries forward unchanged for FY 2026-27. The Top 1000 expansion typically brings in more mid-cap entities with less mature ESG data infrastructure than the initial Top 150 cohort, and SEBI's phased clarifications on value-chain scope and the assessment-or-assurance distinction have themselves evolved since the framework was first introduced. Re-reading the current circular each reporting cycle, rather than reusing last year's interpretation memo, is a cheap way to avoid a late-stage scoping surprise.
BRSR Core KPI data architecture
Treat the nine BRSR Core attributes as nine separate data pipelines, each with its own source systems, calculation logic and owner — not as one ESG spreadsheet someone fills in before the filing deadline. GHG emissions data typically originates from energy and fuel consumption records; water and waste data from utility meters and waste-manifest records; wage and gender-diversity data from HR/payroll systems; and customer-fairness data from the complaints-management system. HSE and EHS teams are frequently the de facto owners of the energy, water, waste and emissions pipelines even though the filing itself sits with finance or company secretarial functions, which is exactly why this data architecture needs an explicit owner map rather than an assumed one.
Data owners and system boundaries
| BRSR Core attribute | Likely data owner | Typical evidence source | Reporting frequency |
|---|---|---|---|
| GHG emissions | EHS / sustainability team | Fuel and electricity records, emission-factor workbook | Monthly roll-up, annual disclosure |
| Water consumption | Facilities / EHS | Utility bills, meter logs | Monthly roll-up, annual disclosure |
| Waste generation | EHS / operations | Waste manifests, disposal records | Monthly roll-up, annual disclosure |
| Energy consumption | Facilities / EHS | Utility bills, sub-metering | Monthly roll-up, annual disclosure |
| Gender diversity | HR | HRIS headcount reports | Periodic snapshot, annual disclosure |
| Wages and social security | HR / payroll | Payroll system, statutory filing records | Annual disclosure |
| Inclusive development | CSR / sustainability | CSR spend and beneficiary records | Annual disclosure |
| Customer/complaint fairness | Customer service / legal | Complaints-management system | Periodic roll-up, annual disclosure |
| Openness of business | Company secretarial / finance | Related-party and payment records | Annual disclosure |
Source documents and calculation controls
Every KPI value that reaches the BRSR Core filing should be traceable back to a source document through a documented calculation method — not recalculated from memory each year. For GHG emissions specifically, keep the emission-factor source and version used clearly recorded, since a change in factor source between reporting years without disclosure is a common assurance finding. Build a simple calculation-control note for each KPI: what raw data feeds it, what formula or conversion is applied, who reviews the output before it is submitted, and where the underlying source document is filed. This is the single most effective thing a facility can do to shorten assurance queries, because it answers "how did you get this number" before the assurance provider has to ask.
Where a listed entity operates multiple plants or business units, decide early whether each site maintains its own KPI workbook that rolls up centrally, or whether a single central team pulls raw data directly from each site's systems. The rollup model scales better once you are collecting data from more than a handful of locations, but it only works if every site uses the same calculation method and unit conventions — a plant reporting water consumption in kilolitres while another reports in cubic metres is a data-quality problem that surfaces at the worst possible time, during assurance testing, if it is not standardized upfront.
Value-chain partner data collection
Collecting value-chain KPI data from suppliers and customers is usually the most time-consuming part of BRSR Core readiness, because it depends on partners who are not under your direct operational control and may have no ESG reporting capability of their own. Start the data request cycle early in the financial year rather than at filing time, and keep the requested KPI set to exactly what is required — over-asking suppliers reduces response rates and data quality across the board.
Supplier onboarding and data-quality checks
A workable supplier ESG data-collection process needs: a simple, standardized data-request template mapped to the nine BRSR Core attributes; a defined response deadline with at least one reminder cycle; a basic data-quality check (does reported energy consumption correlate plausibly with reported production volume, for example) before the figure is accepted; and an escalation path for non-responsive or clearly implausible submissions. Where a supplier genuinely cannot provide a KPI, record that as a defined data gap with a stated reason rather than leaving a blank cell — assurance providers treat an explained gap very differently from an unexplained one. Himaya Prevention's responsible sourcing auditing and implementation service and social audit service both run supplier-facing data and evidence collection of exactly this kind, and translate directly into a BRSR value-chain data-request workflow.
Evidence, controls and assurance readiness
Assurance readiness is less about the accuracy of any single KPI and more about whether your organization can demonstrate a controlled, repeatable process for producing that KPI. An assurance provider testing BRSR Core data will typically sample transactions or records behind a reported figure, check the calculation method against the underlying source documents, and test whether the same process was followed consistently across the reporting period.
Exception management and audit trail
Keep an exception log alongside your KPI data: instances where a data source was unavailable, where an estimate was used instead of a metered value, or where a supplier's reported figure looked implausible and had to be followed up. This log, dated and with named reviewers, is often what separates a smooth assurance engagement from a drawn-out one, because it shows the assurance provider that anomalies were caught and handled by your own process rather than only by their sampling. Maintain version control on every KPI workbook so a restated figure from a prior year is traceable to a documented reason, not just a silently changed number.
| Readiness area | What "ready" looks like | Owner |
|---|---|---|
| Data lineage | Every KPI traceable to a source document and calculation note | Sustainability/EHS lead |
| Internal controls | Defined preparer/reviewer roles per KPI, documented sign-off | Function heads (EHS, HR, finance) |
| Exception log | Anomalies and estimates recorded with reasons and follow-up | Sustainability/EHS lead |
| Supplier data completeness | Response rate tracked; gaps explained, not blank | Procurement / sustainability |
| Prior-year comparability | Restatements documented with reasons | Sustainability/EHS lead |
Roles, governance and reporting calendar
BRSR Core reporting works best as a named cross-functional responsibility with board visibility, not as an annual scramble owned informally by whoever filed it last year. A functioning governance model assigns a data owner per KPI (see the table above), a coordinating sustainability or ESG lead who consolidates and quality-checks across all nine attributes, and a defined escalation path to the board or a board committee for material gaps or anomalies discovered during preparation.
Board and management oversight
Board or audit-committee oversight of BRSR Core preparation typically covers: review of the applicability determination each year, sign-off on the KPI data before filing, visibility into any exceptions or data gaps recorded during the year, and confirmation that the assessment-or-assurance engagement (where required) has been scoped and scheduled with enough lead time before the filing deadline. Building this into an existing audit-committee or risk-committee calendar, rather than creating a parallel ESG governance track, keeps accountability where the organization's other assurance-relevant reporting already sits. Himaya Prevention's ESG & sustainability implementation service supports exactly this kind of governance build-out alongside the underlying data-collection work.
A realistic reporting calendar works backward from the filing deadline in distinct phases: applicability confirmation and value-chain scoping early in the financial year; monthly or quarterly KPI roll-ups from each data owner rather than a single year-end push; supplier data-request cycles timed so a second reminder round is still possible before internal deadlines; a dedicated internal review window before the assessment-or-assurance engagement begins; and a buffer between the assurance provider's fieldwork and the actual filing date to resolve any queries raised. Compressing this calendar into the final quarter is the most common reason BRSR Core filings end up with unexplained gaps or last-minute estimates that later need restating.
BRSR implementation checklist
| Checklist item | Status |
|---|---|
| Current-year market-cap ranking confirmed against SEBI's applicability determination | |
| Value-chain coverage requirement confirmed against the current SEBI circular | |
| Data owner assigned for each of the nine BRSR Core attributes | |
| Calculation-control note documented for each KPI (source, formula, reviewer) | |
| Supplier/value-chain data-request template issued with defined deadline | |
| Data-quality checks applied to supplier responses; gaps explained, not blank | |
| Exception log maintained with dated entries and named reviewers | |
| Assessment-or-assurance engagement scoped and scheduled ahead of filing deadline | |
| Board/audit-committee review of KPI data completed before filing |
BRSR Core readiness scorecard
Rate your current status for each readiness area to get a quick priority list.
Supplier response tracker — add a row per value-chain partner to track outstanding data requests (not saved between visits; note it down before closing this page).
| Partner | Status |
|---|
This tool is a screening and workflow aid only, not an assurance opinion or legal advice. Confirm applicability, KPI scope and assurance requirements with a qualified ESG/assurance advisor against the current SEBI circular.
Request a BRSR Core readiness assessment if your scorecard shows several open areas, or request an ESG data-workflow demo to see how the HSEFQ.com ESG metrics, evidence and supplier-assessment modules keep KPI data, calculation notes and supplier responses in one auditable trail instead of a filing-season spreadsheet rebuild.
Frequently asked questions
Which companies fall under BRSR Core in FY 2026-27?
Listed entities ranked in the Top 1000 by market capitalization fall under BRSR Core assessment-or-assurance for FY 2026-27, continuing the phased glide path that started with the Top 150 in FY 2023-24. Confirm your specific ranking against SEBI's applicability determination for the year, since ranking is reassessed annually.
Is value-chain reporting mandatory?
Value-chain disclosure is part of the BRSR Core framework for in-scope listed entities, covering significant upstream and downstream partners for a defined subset of KPIs. Confirm the current coverage threshold and any assessment-versus-assurance distinction for value-chain data against the latest SEBI circular, since this element of the framework has been subject to phased clarification.
What is reasonable assurance?
Assurance is an independent provider's opinion on whether reported data is materially accurate, based on testing samples, calculation methods and internal controls. SEBI's March 2025 circular reframed the BRSR Core compliance mechanism as "assessment or assurance," so confirm which standard applies to your entity and to your value-chain data specifically before committing to an assurance provider's scope of work.
How should ESG source evidence be retained?
Retain the source document, the calculation note, and the reviewer sign-off for every KPI figure, filed in a way that a future assurance provider or auditor can trace the reported number back to its origin without relying on institutional memory. Treat this evidence with the same retention discipline as financial audit evidence, not as informal working files.
Can HSE data feed BRSR Core KPIs?
Yes — energy, water, waste and GHG-emissions data that EHS teams already collect for statutory and management-system reporting is frequently the same underlying data needed for BRSR Core, provided it is captured with the calculation lineage and control discipline the assurance process expects. Aligning EHS data capture with BRSR Core requirements once avoids maintaining two parallel data sets for the same underlying facts.
0 Comments