Prepare management sign-off with clear decisions and release conditions
Give management a defined disclosure version, a short account of the checks performed and the unresolved decisions that could change the report. Record what is approved, any conditions still to be met, who confirms those conditions and which version may be released.
This guide is for reporting leads preparing management review of ESG disclosures. It is a suggested internal workflow, not a prescribed approval form. Follow the organisation's actual governance, legal and reporting requirements for who must review, approve, sign or file the report.
Define the decision before the meeting
Separate approval of source inputs, acceptance of a calculation method, approval of disclosure wording and authority to release the report. A data owner's confirmation does not automatically approve the public narrative or settle a legal interpretation.
BRSR includes governance and oversight disclosures, including the responsible director's statement, relevant authorities and review arrangements. Those actual arrangements should inform the review process. Source: SEBI master circular, Annexure 16, section B, questions 7–10. The decision pack below is Nitium's suggested preparation aid.
Bring a compact decision pack
Report identity: entity, period, boundary, purpose, audience and exact draft version
Coverage: what has been collected and which sites, metrics or records remain incomplete
Review performed: checks completed, who performed them and important limits such as sampling
Decisions needed: the issue, evidence, reporting consequence, proposed treatment and responsible owner
Changes: significant revisions since the last review and affected comparisons or public claims
Release dependencies: corrections, external engagement steps or other conditions still required
Keep detailed schedules available through precise references. Management should be able to understand a decision without searching a folder, while a reviewer should be able to trace it beyond the summary.
Use a decision record rather than a completion score
For each open issue, record the disclosure affected, what is supported, what remains uncertain, the possible effect, decision owner, agreed action and closure evidence. Avoid treating every issue as equally important merely because it occupies one checklist row.
An internal status can be:
Ready for release: the specified checks and required approvals for that version are complete.
Conditions outstanding: named actions still need evidence and confirmation; the affected material is not yet released.
Decision required: the responsible owner must resolve treatment or obtain specialist input before release.
These labels describe workflow, not regulatory compliance or assurance. Recording acceptance of an issue does not make an unsupported statement accurate. Do not publish a known materially wrong figure or claim because the pack has received a signature.
A hypothetical review with three different outcomes
Fictional example, not a Nitium client case. A reporting manager presents draft R4 and its supporting schedules. Three items remain:
Missing site coverage. The energy narrative says all 12 sites are included, but the schedule contains 11. The manager records a release-blocking coverage question, names the facilities owner and requests the missing evidence and a refreshed review. The wording is not approved as complete.
Unsupported claim. A paragraph describes an internal data check as independent assurance. The team corrects the description to match the work actually performed and sends the changed wording for approval.
Rounding mismatch. A chart displays a different rounded total from the approved schedule. The preparer corrects it and the checker verifies the final export. This does not require inventing a new source value.
The decision record identifies R4 as reviewed with conditions outstanding. After the required work, R5 is presented with the closure evidence. The release approval names R5 and its associated schedules, rather than saying “the ESG folder is approved”.
Make the last check about the released file
Before handing the report to the person authorised to release it, compare the exported document with the approved schedules. Check units, rounded values, scope descriptions, dates, source references and any caveats that could have been lost in editing.
If a material input changes after approval, route the affected calculation and disclosure back through the required review. Keep the earlier version and decision history. Do not assume that approval of yesterday's workbook covers today's amended report.
Sign-off readiness checklist
The decision and required approvers are clear
The report version and supporting schedules match
Missing coverage, estimates and limitations are visible
Material claims have supporting evidence
Conditions have an owner and a verifiable closure test
Independent-provider conclusions are described accurately and separately
The final release file and approval record are retained
Our readiness guide explains preparation and independent-provider roles. Nitium's BRSR reporting support helps teams prepare drafts and identify information gaps. Discuss a reporting-review pack or email contact@nitium.in with a non-confidential outline.
Sources checked 5 October 2026. This aid does not replace required governance approvals, legal advice or an independent assessment or assurance engagement. No checklist score certifies the report.
Comments