Hand over an ESG evidence folder an independent reviewer can use

Prepare the handover around the reviewer's agreed requests and the exact disclosure version under review. Provide an index that connects each request to a record, calculation, explanation and owner. Test access before the handover, and make later changes visible through a controlled revision record.

This guide is for reporting teams preparing records for an independent assessment, assurance or other agreed review. It addresses the practical transfer of evidence after scope has been established. Our BRSR Core readiness guide covers scoping and responsibilities; the evidence-file guide covers construction of the source trail.

Confirm what the recipient needs

Obtain the agreed request list, criteria, reporting period, entity boundary, required formats, authorised recipients and transfer method. Ask which source systems the reviewer needs to inspect and which records can be supplied as extracts. A generic folder checklist cannot override an engagement-specific request.

Keep the preparation role distinct from the independent provider's role. SEBI's BRSR Core framework addresses provider expertise and conflicts of interest; appointing a readiness adviser does not settle provider eligibility. Source: SEBI master circular, chapter IV-B, paragraphs 4.1–4.2; BRSR Core FAQs, section V.

Use a small number of clearly identified sections

The following is a suggested organisation, not a mandatory assurance format:

• Read first: scope, reporting dates, entity/site list, contact owners and known limitations

• Disclosure under review: the exact draft, with its version and preparation date

• Request index: request ID, indicator, source locator, calculation reference, owner and status

• Calculations and methods: editable schedules where agreed, units, factor references, assumptions and reconciliations

• Source evidence: authorised records or controlled links, organised so references remain stable

• Decisions and queries: open questions, responses, approvals and outstanding actions

• Release history: what changed, why, who approved it and which files were superseded

A useful index entry identifies a specific sheet, cell, page, table or system extract. “See energy folder” is not a precise locator. If a document supports several requests, reference the same controlled record rather than creating several copies that may diverge.

Separate the working area from the handover version

Keep the working files available to the preparers. Label the review set with a version or release date and record the versions it contains. This need not require special software: the critical point is that recipients can tell which set they are examining.

Use the Source document and approval register to record each source version, its controlled location, access checks and approval scope. The editable workbook keeps purpose-specific review decisions alongside the source record, helping the handover team identify which version was approved for the stated use.

Do not treat a PDF export as interchangeable with its calculation workbook. The export may display the result while the workbook carries formulas, methods and links. Supply the formats agreed with the reviewer and identify any limitations such as unavailable source-system access or missing historical extracts.

A hypothetical version mismatch

Fictional example, not a Nitium client case. A team prepares handover set R2. The disclosure PDF was exported from workbook version 3, but the calculation folder contains version 4 after a late correction. Both files are named “final”. A reviewer could examine valid source evidence and still compare it with the wrong disclosure.

Before transfer, the coordinator checks the release index and finds the mismatch. The team confirms which correction management approved, regenerates the disclosure from the approved workbook, and records both filenames and versions in R2. Version 3 remains in the history with a superseded label.

If version 4 has not yet been approved, the coordinator records that status and resolves it through the reporting owner instead of presenting it as settled. If a change occurs after handover, the team issues a revision note through the agreed channel, identifying affected requests, results and replacement files. It does not silently swap a document behind the same link.

Test access with the intended permissions

Check that authorised recipients can open the required records and that links do not depend on a preparer's personal login. Use the minimum necessary access and the agreed sharing arrangements. Do not make a folder public to solve an access problem.

Where evidence contains employee details, commercially restricted information or third-party material, agree a controlled route, relevant extract or appropriate redaction with the responsible owner and reviewer. A public handover index should not expose private source links or personal records. Do not alter substantive evidence under the guise of tidying it.

Run a handover rehearsal

1. Choose an agreed request and locate the corresponding disclosure version.

2. Follow its index to the calculation and precise source evidence.

3. Confirm the unit, period, boundary and important assumptions.

4. Locate the preparer, review record and known limitations.

5. Check whether later changes are visible and linked to affected requests.

6. Record access failures or missing explanations and resolve them before transfer.

This rehearsal tests usability of selected records. It does not establish that every disclosure is correct or replace procedures the independent provider considers necessary.

After handover, maintain one query record with the request, response owner, answer, supporting evidence and next action. Acknowledgement of receipt is different from acceptance of evidence; let the reviewer determine whether a response addresses the request.

Nitium's ESG assurance-readiness service supports evidence organisation and data-trail preparation. Discuss an evidence handover or email contact@nitium.in with the review scope and current state of the records. Share only a non-confidential outline initially.

Sources checked 5 October 2026. Nitium's services described here do not include independent assessment or assurance opinions. This folder workflow does not establish compliance, authenticate documents or guarantee an independent review outcome.