BRSR Plantation Evidence in India: What Principle 6 Reviewers Actually Look For

SEBI's Business Responsibility and Sustainability Report (BRSR) puts environmental performance on the board agenda. For companies that fund tree plantation through CSR or operations greening, Principle 6 is where plantation claims meet assurance. The weak pattern is familiar: a headline tree count in the annual report, thin backup in the working papers, and a scramble when the assurance provider asks where those trees are and whether they still live.

This guide is for sustainability, ESG, and CSR leads at Indian corporates — and for the agencies that deliver their plantation days. It explains what BRSR plantation evidence usually means in practice, how to structure Plant → Track → Report without over-claiming carbon credits, and how to keep a clean trail for internal audit and external assurance.

Principle 6 is about performance, not ceremony

BRSR Principle 6 covers how an entity manages environmental impacts. Plantation programmes show up as:

• Hectares or trees planted under CSR Schedule VII activities
• Operational green belts (factories, mines, campuses, corridors)
• Supplier or community programmes that the company funds and discloses

Assurance providers do not need a romantic planting-day story. They need traceable claims: what was planted, where, by whom, under which programme code, and what follow-up happened. A photo album and a vendor invoice are not enough when numbers appear in the BRSR annexures.

The evidence stack that survives review

Treat plantation disclosure like any other quantitative ESG claim. Build a stack:

1. Registry — each tree, plot, or belt segment has an ID, GPS, species, date, and project tag
2. Source documents — work orders, NGO / agency MoUs, nursery invoices linked to the same project ID
3. Survival / condition — timed field checks (for example 3 / 6 / 12 months) with status and photo when status changes
4. Spatial context — mapped polygons for belts and community blocks so counts can be reconciled to area
5. Export pack — a repeatable PDF / XLSX that matches how your assurance team wants Principle 6 working papers

Optional satellite NDVI or SAR integrity layers help programme managers prioritise field visits. They guide evidence collection; they do not replace ground truth for BRSR working papers.

What usually fails BRSR plantation claims

Failure	Why it hurts assurance
Aggregate "trees planted" with no locations	Cannot sample or verify
Duplicate or missing GPS	Inflated or untestable counts
No survival after monsoon	Year-2 disclosure contradicts year-1 optimism
Carbon tonnes stated as "credits"	Over-claim; registries and methodologies are separate
Vendor Excel only on one laptop	Not an entity-controlled record

CAG-style audits of public plantation programmes have shown the same pattern for years: planting is easy to announce; survival and location are hard to prove. Listed companies face a different regulator, but the evidence logic is the same.

A planting count and a modeled tonne are not the Green Credits leadership indicator. What that line asks, and which file stays separate, is in Green Credits and BRSR Principle 6.

Mapping plantation data to BRSR language

You do not need to invent a new language for auditors. Map fields once:

• Activity description → CSR project name / EC green-belt condition / campus greening code
• Quantitative indicator → trees registered, hectares mapped, survival % at last survey
• Methodology note → how GPS accuracy, mortality, and replacements are defined
• Limitations → sites not yet resurveyed; modeled CO₂e labeled as estimate only

Keep facts and estimates in separate columns. Facts: geo-tags, photos, survival counts, maintenance visits. Estimates: modeled biomass or CO₂e. If you mention VM0047, ISO 14064-2, or similar frameworks, state clearly that your stack is audit preparation / structured evidence, not registry issuance or legal certification.

A 90-day BRSR plantation readiness pilot

Corporates that are starting from photo-only programmes do not need a multi-year overhaul before the next filing. A focused pilot works:

Days 1–15 — Scope
Pick 1–2 live plantation projects (one CSR event block, one operational green belt). Agree the Principle 6 lines you will support this year.

Days 16–45 — Register
Map polygons, register trees or plots with GPS + photos, tag species and programme, freeze a baseline export.

Days 46–75 — First survival pass
Run a structured check; record alive / stressed / dead / replaced; attach photos on status change.

Days 76–90 — Assurance pack
Export the working paper your assurance provider asked for. Document definitions and known gaps. Decide the cadence for the next financial year.

This is the same Plant → Track → Report loop mining and CSR teams use for operational greening — applied to disclosure discipline.

Roles: who owns what

• ESG / sustainability — disclosure language, assurance liaison, methodology notes
• CSR / plant ops — field vendors, agencies, nursery quality
• NGO / event agency — day-of capture; should not be the only copy of the registry
• Internal audit / assurance — sample selection, evidence completeness

Put registry ownership in the MoU. Corporates should keep read access and export rights even when partners capture field data.

How Aranyix fits (without over-claiming)

Aranyix is a plantation MRV platform: geo-tagged registration, survival tracking, satellite health fusion, and structured exports for programmes including BRSR-oriented packs. It helps teams assemble audit-prep evidence. It does not issue Verra, Gold Standard, or other registry credits, and it is not a certification body. Final BRSR assurance remains with your company and appointed provider.