Disclosure methods and examples
Updated: Oct 7
Use a source-linked example to decide what context to preserve beside a disclosure. This collection contains 127 original Nitium analyses covering disclosures from 30 Indian issuers. An analysis explains a method, boundary, unit, missing-state or version issue. It is not an additional company-reported measurement or a template to copy into another company’s report.
Edition: 0.6.0-sample1661. Hub review: 6 October 2026. The examples retain their own period strings, including exact ranges, fiscal-year labels and paired-year context. Across the release they concern selected FY2022–23 through FY2025–26 disclosures. Release source retrieval and selected-row checking took place on 5–6 October 2026; row timestamps remain in the files. Original report-publication dates were not established. This is a fixed historical, source-screened sample, not a live feed, representative sample, complete issuer inventory or latest-year coverage claim.
What an analysis record contains
Each record has a stable example_id, company and period context, a subject, an original_summary, why_useful, boundary_or_limitations, and an exact source reference. Read those fields as a bundle. The source observation and Nitium’s interpretation are different layers of evidence; neither a short title nor an isolated numeric cell carries the full explanation.
The six examples below are selected deliberately to illustrate six reading questions across four issuers. This is not a prevalence study, a representative subset or a ranking of reporting quality. The six examples remain unchanged from the frozen 99-record 0.5.0-sample1040 collection and are retained in the expanded 127-record collection. Showing it here creates no new analysis or numeric-record credit.
Six worked reading questions
1. Standalone boundary excludes subsidiary consolidation
Issuer and period: Cochin Shipyard Limited; 2024-04-01/2025-03-31.
Source observation: The report explicitly uses a standalone boundary and separately lists two subsidiaries.
Nitium’s interpretation: A list of subsidiaries in a report does not establish that their environmental or workforce figures are included. The boundary field must control the dataset.
Limit: No consolidated or subsidiary figures are inferred.
Source edition: Cochin Shipyard Limited Business Responsibility and Sustainability Report FY2024-25. Printed/PDF p1, Q13; Printed/PDF p3, Q23.
Stable example ID: EX-CO-COCHINSHIP-20250331-ENTITY_BOUNDARY.
2. An energy heading changes the scale of every absolute cell
Issuer and period: Vardhman Textiles Limited; FY2024-25 (source label).
Source observation: The energy table explicitly uses Million GJ, while several intensity labels mention per rupee and their accompanying units use crore-scale denominators.
Nitium’s interpretation: Preserve the absolute heading scale and keep denominator ambiguities out of numeric comparison; a unit conversion is a separate calculation, not a new reported observation.
Limit: Only absolute quantities are extracted here. Intensity rows remain held rather than repaired from financial revenue.
Source edition: Vardhman Textiles Limited Business Responsibility and Sustainability Report 2024-25. Printed/PDF p30, energy heading; Printed/PDF p31, water intensity; Printed/PDF p32, GHG intensity; Printed/PDF p34, waste intensity.
Stable example ID: EX-CO-VARDHMAN-20250331-UNIT_SCALE.
3. Scope 2 label does not establish its accounting method
Issuer and period: Cochin Shipyard Limited; 2024-04-01/2025-03-31.
Source observation: The GHG table supplies a Scope 2 total but the examined table does not identify location-based or market-based accounting.
Nitium’s interpretation: Keep an unspecified-method category until a source identifies the method. Do not mix those observations with a method-specific peer comparison.
Limit: This is absence in an examined table, not proof that the method is undisclosed everywhere or that the issuer is non-compliant.
Source edition: Cochin Shipyard Limited Business Responsibility and Sustainability Report FY2024-25. Printed/PDF p26, GHG table.
Stable example ID: EX-CO-COCHINSHIP-20250331-SCOPE2_UNSPECIFIED.
4. Water-source total includes internally produced treated water
Issuer and period: Rashtriya Chemicals and Fertilizers Limited; 2024-04-01/2025-03-31.
Source observation: The Others category includes water from in-house sewage-treatment plants and notes that some is shared with BPCL.
Nitium’s interpretation: A withdrawal dataset needs the issuer-specific category definition and destination context before it is interpreted as freshwater input or exclusive consumption.
Limit: The examined tables do not establish a full reconciled water balance.
Source edition: Rashtriya Chemicals and Fertilizers Limited Business Responsibility & Sustainability Report FY2024-25. Printed p95 / PDF p29, water-source note.
Stable example ID: EX-CO-RCF-20250331-RECLAIMED_WATER.
5. Current detailed waste categories do not reconstruct a prior breakdown
Issuer and period: Vardhman Textiles Limited; FY2024-25 (source label).
Source observation: The current-year nonhazardous list separately identifies fly ash and other materials, while the prior year provides an aggregate.
Nitium’s interpretation: Retain the level of disaggregation actually reported in each year. A detailed current category is not evidence of the same unreported prior category or of its absence.
Limit: No cause of the total change is inferred and no historical fly-ash amount is estimated. Small displayed-component/subtotal residuals remain explicit.
Source edition: Vardhman Textiles Limited Business Responsibility and Sustainability Report 2024-25. Printed/PDF p33, waste categories; Printed/PDF p34, continuation.
Stable example ID: EX-CO-VARDHMAN-20250331-WASTE_GRANULARITY.
6. Safety rate basis can be explicit while values remain dashed
Issuer and period: Sandhar Technologies Limited; 2024-04-01/2025-03-31.
Source observation: The safety table identifies a per-million-person-hours LTIFR basis and includes contract workforce, yet displays dashes in its current and prior safety cells.
Nitium’s interpretation: Preserve the available denominator definition separately from the unavailable rate and underlying worked-hours count. A rendered dash must not become an inferred zero.
Limit: P3 safety population includes contract workforce. This note does not infer absence of injuries or fatalities and does not extend that population definition to Q20 headcounts.
Source edition: Sandhar Technologies Limited Business Responsibility and Sustainability Report 2024-25. Printed p110 / PDF p23, safety table and footnote.
Stable example ID: EX-CO-SANDHAR-20250331-SAFETY_DASHES.
Turn an example into a review step
State the question in your own reporting boundary. For example: does a source mention subsidiaries without including their metrics?
Open the exact report edition and every cited page. Read the table title, column years, units and footnotes together.
Separate what the source states from your interpretation and from anything still unknown. Keep raw dashes, unresolved definitions and source-specific limits.
If two source versions differ, preserve both and explain which version your selected observation uses. Do not infer the cause of a change just because the digits reconcile.
Document what additional evidence would resolve the question. An example helps frame that request; it cannot determine another entity’s accounting treatment.
Download and use the collection
The 0.6.0-sample1661 complete edition ZIP contains D008-disclosure-examples.csv and D008-disclosure-examples.json, each with the same 127 original analyses. Extract the format you prefer. The page provides selected teaching cards; it does not provide an on-page search or filtering tool. CSV and JSON are two formats of the same records.
Use the source, coverage, metric, period, history and qualification files inside this ZIP for the expanded collection. Retain mandatory-qualifications, record-qualifications and source-provenance-availability with any subset; shorter source-scope summaries do not replace the full conditions.
Previous-edition example support: the seven links below remain bound to 0.5.0-sample1040, which supports the unchanged teaching examples. Use the current-edition ZIP above for the expanded collection and its supporting files.
Open D008-disclosure-examples.csv in a spreadsheet with UTF-8 import. Filter company_id, period and subject, or use text search in the downloaded original_summary field. Keep example_id with each selected analysis.
Read original_summary, why_useful and boundary_or_limitations together. The example title alone may omit an important condition.
Use source_id, source_url and precise_locator to reopen the original report. A locator can name more than one source page or report year; do not assume the first link covers the whole analysis.
The period field is text because some analyses span source versions. Do not turn every fiscal-year label into an exact quoted date range. Metric dictionaries and source-history files support the wider numeric release; D008 does not pretend that each analysis has an observation-history join.
Attribution, missing information and maintenance
The analysis summaries are Nitium’s interpretations of public issuer disclosures, not statements authored or endorsed by those issuers. They identify where a question arises; they do not establish a prevalence rate, allegation, legal conclusion or overall sustainability rating. Each stable example ID counts once. A related observation, repeated citation, alternate file format or teaching card adds no analysis record.
AI-assisted preparation and separate internal source checks support transcription and interpretation. They do not independently verify company measurements, provide professional assurance or establish compliance. The issuers are not identified as Nitium clients or endorsers. No report PDFs, report graphics or third-party assurance materials are distributed. The release does not grant a blanket licence over source reports; retain attribution, exact units, locations and source-specific limits when making a subset.
This frozen edition changes only through versioned corrections or a reviewed successor. Source amendments, broken links, altered reuse conditions and material method changes trigger a review. New company reports are not incorporated automatically. The method file preserves source-specific access limits, including City Union Bank’s direct-PDF availability caveat.
Prepare your own evidence trail
Use the public ESG report directory to locate reporting boundaries and editions. For a related metric collection, see reported greenhouse-gas data. The downloaded files provide historical examples; your own reporting needs its own period, scope and source records.
For help with evidence preparation for an independent review, review Nitium’s services or discuss the reporting question and evidence gaps.
Comments