Reading reporting boundaries in two shipbuilder BRSRs

Before comparing two ESG figures, record the activities, people and dates each figure covers. A report-wide standalone boundary gives you the entity starting point. The notes beside individual metrics can still change how you should interpret the data.

This small Nitium study examines that preparation problem using the FY2024–25 Business Responsibility and Sustainability Reports of Cochin Shipyard Limited (CSL) and Mazagon Dock Shipbuilders Limited (MDL). It is intended for finance, sustainability and operational teams building a source-linked reporting file.

Our question and sample

We asked: what extra information do metric-level notes provide when both reports describe their entity boundary as standalone? Both reports make that choice in Section A, question 13. CSL BRSR, page 1; MDL BRSR, page 2.

The sample contains two companies in one industry, shipbuilding and ship repair, for the reporting period 1 April 2024 to 31 March 2025. The date range is explicit in CSL's BRSR and in MDL's issuer-authored annual report. Some metric rows also contain FY2023–24 comparatives. Those comparatives do not create additional report-directory entries. MDL Annual Report, printed page 4 / PDF page 6.

We selected these official, digitally readable reports to test a small, traceable dataset after reviewing source-use conditions. This is a purposive calibration sample. It does not estimate how common these disclosure features are across Indian companies, private businesses or other industries.

An entity boundary does not settle activity coverage

MDL's Scope 1 note excludes off-road vehicles because distance-travelled data are unavailable and the company wanted to avoid mixed methodologies. Its limited Scope 3 disclosure covers business travel, assumes one-way flights and states that the prior year was not quantified. MDL BRSR, page 39; page 43.

For a data-preparation team, the useful finding is the need for a second coverage field below the entity boundary. Record which activities are included, which are excluded, why a source is missing and what evidence would resolve the gap. Preserve a partial inventory as partial. An unquantified earlier period cannot support a numerical change calculation.

A practical follow-up question is: “Can the activity owner supply a complete activity record for the excluded source, and who will decide the calculation method?” That is a request for evidence and a documented technical decision. It is not a reason to invent an emissions estimate.

Workforce coverage belongs with the safety measure

CSL's safety table expressly includes contract workforce. That note accompanies incident measures and lost-time injury frequency rates. CSL BRSR, page 18.

Carry that population definition into the data row and the review file. A reviewer needs to know whether the numerator and hours-worked denominator cover the same people. The word “workers” alone is not enough to establish that two issuers, two tables or two periods use equivalent populations. This study does not calculate a new safety rate or compare the companies' safety performance.

A footnote can determine the correct snapshot

CSL's Board table shows a sanctioned strength of 12. Its footnote specifies an actual Board of six directors at 31 March 2025. The sanctioned figure refers to a different basis. CSL BRSR, page 3.

For an actual-membership field, our record retains six and the reporting-date note. A useful review instruction is to read the table heading, footnote and as-of date together before choosing a cell. Store authorised positions separately only if the project needs that different measure. Do not substitute a later website list for a historical snapshot.

Keep method evidence separate from the boundary label

The examined Scope 2 tables do not explicitly label the figures location-based or market-based. MDL does identify a CEA factor-source version in its footnote. We retain that factor provenance while leaving the accounting-method label unspecified. CSL BRSR, page 26; MDL BRSR, page 39, note 18.

This is an evidence-handling choice: “not identified in the examined table” should remain visible. It is not a finding that a method is absent everywhere, or a conclusion about compliance. Before making a method-specific comparison, locate the inventory-method note or obtain the relevant explanation through the reporting team's authorised process.

A boundary register you can use

For each material metric, record:

1. Entity and sites. Identify the reporting entity and any site-specific scope that the source actually establishes.

2. Activity or population. State the equipment, emissions categories, employees, workers or other population covered.

3. Time basis. Record the reporting period, the snapshot date where relevant and any partial-year coverage.

4. Method and denominator. Keep accounting method, factor provenance, units and intensity or rate denominators in separate fields.

5. Exclusions and unresolved questions. Give each gap an owner and evidence request. Preserve missingness until it is resolved.

6. Source and version. Link the exact page, table and footnote. Record whether a comparative has been revised before calculating a trend.

Use an explicit review outcome: ready for the intended comparison, usable only with a named limitation, or held pending an answer. The decision should concern a particular use of the data. A row suitable for illustrating a disclosure method may still be unsuitable for a peer-performance comparison.

Method and limits

This study uses accepted records from Nitium dataset edition 0.4.3-pilot100-mdl-provenance: two report-directory records, 88 reported metric observations and 10 original disclosure analyses. These are 100 linked records, not 100 companies or datasets. All 100 received a separate internal source-checking pass. The research examples above are linked to the exact company disclosures; original values, units, coverage notes and identified anomalies remain in the underlying edition.

The review checks transcription and interpretation against published reports. It does not verify the companies' underlying measurements, provide assurance, rank sustainability performance or establish legal compliance. Neither company is presented as a Nitium client or endorser. The sample excludes rights-held sources, unreviewed issuer batches, superseded extraction versions, derived conversions and missing values from numeric counts. Restricted third-party assurance text and source-report graphics are not reproduced.

No peer ranking, water-balance reconstruction or emissions-change calculation is used in this article. Two issuers in one sector cannot establish national patterns. Further research should add industries and ownership types through the same source, rights and row-checking controls.

Data editions: This article’s analysis remains tied to the original 100-record calibration edition 0.4.3. The broader edition 0.5.0-sample1040 download contains 1,040 records across 19 issuers, with its own coverage and limitations. It does not enlarge this article’s two-shipbuilder research sample retrospectively. The report directory describes the broader collection. The separate edition 0.6.0 download contains 1,661 selected records across 30 issuers; it does not expand this article’s original 100-record, two-shipbuilder research sample.

Next step: If you are preparing a reporting boundary or evidence handover, bring the entity list, reporting dates and unresolved metric questions to the discussion. Read our BRSR evidence-file guide or contact Nitium Advisory about your reporting requirement.

Prepared with AI-assisted research. Source review date: 5 October 2026. This is a historical methods-calibration study; it is not a claim to contain the companies' latest available disclosures.