BRSR evidence file: trace each number to its source
Updated: Oct 20
A Business Responsibility and Sustainability Report (BRSR) evidence file links each reported number to its source records, calculation, reporting boundary and approval. It helps a reviewer reproduce the figure, understand estimates and corrections, and identify the version used in the published report.
Take a draft BRSR with an annual electricity total of 1,080,000 kilowatt-hours (kWh). Operations has a different figure. Finance has the bills, but one month is missing. The spreadsheet contains a replacement number; nobody can tell whether it came from a meter reading or an estimate.
The immediate problem is getting that number right. The recurring problem is being unable to explain how it was produced.
Here is a practical way to build that trail without turning every disclosure into a separate administrative project.
Start with the disclosure and its boundary
Write down exactly what the number represents before asking teams for data. “Electricity consumption” still leaves questions: which legal entities and sites, which dates, which meters, and which sources of electricity?
Record the reporting boundary and the indicator reference from the applicable BRSR format. For energy, that is Section C, Principle 6, Essential Indicator 1 (P6/1E), covering total energy consumption and energy intensity. A standalone report and a consolidated report can cover different operations. A site acquired during the year needs an explicit treatment; copying last year's site list will not resolve it.
For context, the Securities and Exchange Board of India (SEBI) requires BRSR reporting by the top 1,000 listed entities by market capitalisation, subject to applicable rules. BRSR Core is a subset of indicators, and its phased assessment-or-assurance requirement reaches the top 1,000 for FY2026–27. Confirm the entity's position and reporting period rather than treating every Indian business as a mandatory filer. See SEBI's LODR master circular of 30 January 2026, chapter IV-B.
Use the applicable reporting guidance to settle definitions. The Industry Standards Note on BRSR Core, introduced through SEBI's 20 December 2024 circular, provides indicator-specific instructions. For example, its energy section distinguishes components of electricity supply that need appropriate renewable or non-renewable classification. A utility connection alone does not settle that classification.
Build an index that connects records to disclosures
Start with one controlled register and a shared evidence folder. Use the following as a suggested internal structure alongside the prescribed BRSR format. For each indicator, capture:
Definition and coverage: indicator reference, unit, period, entities, sites and exclusions, with reasons
Source records: document or system references, record dates and links that another authorised reviewer can open
Calculation: source values, conversions, formulas, factors and their versions, plus the destination cell in the reporting schedule
Gaps and judgements: missing records, estimates, allocation methods and unresolved questions
Ownership and review: preparer, reviewer, review date and any correction requested
Release status: draft, awaiting evidence or approved, linked to the version used in the report
For energy intensity, also retain the denominator records for revenue from operations, PPP-adjusted revenue and physical output. Record the unit, period and boundary, and the PPP factor's source and year where applicable. A denominator change can alter intensity even when energy use is unchanged.
Keep raw records separate from calculations and preserve both. Replacing a source extract with a cleaned spreadsheet destroys the opportunity to check what changed. A sensible file name includes the site, reporting period and document type; the index provides the connection to the disclosure.
This structure can sit in a spreadsheet while the process is small. Dedicated software becomes useful when site volumes, permissions or review traffic justify it. Either way, decide who controls the master file and how changes are logged.
Download the evidence-index workbook
Use this editable workbook to connect a reporting item with its source record, reporting period, boundary, calculation and responsible role. It includes a clean 100-row evidence register, a 100-row exception log, a separate fictional completed example and a field-by-field guide. Release/version references and point-in-time evidence remain explicit.
Start by entering the reporting entity, dates and basis. Add one row for each evidence item. Keep the source document in your controlled folder, then record a link or reference and a precise page, table or record locator. Record estimation methods and unresolved questions where they arise.
The workbook distinguishes measured or reported values, estimates, reported zero, information not yet collected, information not found in the examined source, and not-applicable items. Its workflow checks identify missing fields, duplicate evidence IDs and incomplete review records. A missing value stays blank. A reported zero needs an explicit numeric zero and a supporting reference. For a narrative item, enter Narrative as the unit marker and the supported statement in the value/statement field; retain its evidence and review records.
The fictional example covers a measured electricity quantity, an estimated water quantity, a training-data gap, an explicitly recorded zero and a boundary-based not-applicable item. All companies, documents, values and reviewers in that example are invented. An additional electricity schedule retains the article’s fictional missing-bill correction example, with guarded formulas that leave missing prerequisites blank.
This is an optional Nitium working aid. It does not replace the prescribed reporting format, determine entity-specific applicability or provide independent assessment or assurance. Confirm indicator references and requirements for the relevant reporting period using the current official sources. The workbook contains no macros or external data connections. Its working data remain in your saved copy.
Workbook prepared 5 October 2026. SEBI LODR Master Circular, 30 January 2026, section IV-B and Annexures 16–17.
BRSR evidence index workbook — editable XLSX, version 2.0.1
A worked example with one missing electricity bill
This is an illustrative example, not a Nitium client case. It covers purchased grid electricity at two hypothetical sites for one financial year. Fuel use and other energy sources sit in separate schedules.
The preparer has:
Factory: 960,000 kWh, supported by records covering all 12 months
Warehouse: 111,000 kWh for 11 months; the March bill is missing
Provisional March estimate: 9,000 kWh, calculated as 300 kWh per operating day × 30 operating days, using records from comparable months
The working total is 1,080,000 kWh. Converting at 0.0036 gigajoules (GJ) per kWh gives 3,888 GJ of purchased grid electricity.
The calculation is straightforward. The warehouse estimate needs more attention. Were the comparison months representative? Did operating hours, occupancy or cooling demand change? Is a utility download, sub-meter log or replacement bill available? Record the answers and the estimate's basis. Keep it provisional while the reporting lead checks its suitability under the applicable methodology and determines any required disclosure.
The register should identify the missing March bill, the warehouse data owner responsible for obtaining it and the date for follow-up. A blank cell must remain visibly incomplete. Entering zero would silently turn an evidence gap into a claim of no consumption.
Suppose the bill arrives before sign-off and shows 9,800 kWh. The corrected annual total becomes 1,080,800 kWh, or 3,890.88 GJ. Preserve the earlier version, record the 800 kWh correction and refresh every dependent calculation. That may include energy totals, intensity ratios and the electricity activity data used for Scope 2 emissions.
This electricity schedule is only one input to the energy disclosure; total energy also needs the other sources and classifications. For Indian grid electricity under the BRSR Core Industry Standards, use the latest applicable CEA-published grid emission factor for Scope 2 and record its year, units and version. A kWh-to-GJ conversion produces an energy quantity, not an emissions figure.
Resolve exceptions before they disappear into the total
An invoice date does not necessarily identify the consumption period. If a bill crosses the financial year-end, document how consumption is assigned to each period and check for overlap with the next bill. Where an allocation is needed, retain its basis.
Shared premises need similar care. A landlord's recharge may combine electricity, maintenance and taxes. Seek consumption data and a supportable allocation method rather than dividing the entire charge by a convenient tariff. Explain the limitation when direct measurement is unavailable.
Where a site receives wheeled power or uses electricity banking, retain supplier and utility settlement statements alongside meter records. Reconcile credited, adjusted and consumed units, explain relevant losses and charges, and support the renewable classification. A banked credit alone does not establish consumption during the reporting period.
For consumption measures, reconcile the schedule with finance records to investigate omissions and duplicates, while recognising that a rupee total alone cannot validate physical units. A credit note, tariff revision or payment delay may explain a financial difference without changing consumption.
SEBI's revised Core framework requires disclosure of changes to the base methodology and industry-specific adjustments or estimates. An internal note helps the team prepare the appropriate disclosure; relevant limitations also need to reach the published report. See SEBI's circular of 28 March 2025, paragraph 3.5.
Give each handover a clear owner
The site data owner supplies the records and explains operational changes. The preparer compiles the schedule and identifies gaps. A reviewer checks the boundary, source coverage and calculation. The reporting lead decides whether unresolved issues require correction, further evidence or disclosure before release.
For a small team, people may hold more than one role. Still arrange a second-person check of significant figures and judgements wherever practicable, and record who performed it.
Collecting records monthly or quarterly can spread the workload, but the cadence should follow the metric and the business. Electricity bills may support a monthly process. Some social indicators need a defined point-in-time population. Give HR and procurement equally clear definitions rather than forcing every indicator into the same template. Keep sensitive employee-level evidence access-controlled; use aggregated schedules for routine review.
Test the file before approving the report
Choose a reported number and ask someone who did not prepare it to reconstruct it. Can they:
Find the source records and confirm coverage of the reporting period?
Reproduce the calculation with the stated units and factors?
Identify estimates, exclusions and changes from the previous year?
Explain significant movements, including any change in the denominator of an intensity ratio?
Find the approval and the exact version used in the final report?
If the answer depends on the preparer's memory, add the missing explanation. Check the final report against the approved schedule, including rounding, units and associated narrative claims.
This is an internal readiness check. External assessment or assurance has its own scope and provider requirements; a well-organised file does not itself supply an independent conclusion. SEBI's framework also addresses provider expertise and conflicts of interest. Agree those arrangements separately from report preparation.
Start with the numbers that are hardest to explain
Choose a few indicators with missing evidence, manual calculations or several data owners. Build the complete trail for those first, resolve the recurring exceptions and then extend the method across the report.
Need help tracing a BRSR figure or resolving a data gap? Nitium Advisory supports BRSR and sustainability reporting, ESG data readiness and carbon-inventory preparation. Discuss a BRSR data-readiness review or explore our BRSR reporting support.
Reviewed 2 October 2026. General reporting guidance; entity-specific applicability and methodology require separate review.
For a defined data-request list, use the data completeness checker to calculate supplied-versus-missing count coverage. It does not validate the evidence or certify reporting compliance.
Comments