Before signing off on a disclosure, a reviewer needs to confirm more than whether the figures and wording appear correct. The review should also establish that the information reflects the current reporting version, agrees with supporting data, meets applicable reporting requirements, presents an accurate narrative, has relevant evidence, and has passed the necessary review and approval controls.
Financial and sustainability disclosures often bring together information from multiple sources, contributors and reporting stages. A change made during one stage can affect content that has already been reviewed elsewhere.
A structured disclosure review checklist helps reviewers focus on the information, evidence, changes and decisions that matter before approving the latest version.
1. Is the Disclosure Based on the Latest Version?
Version control is one of the first considerations in a disclosure review.
When multiple contributors work across documents, shared drives and email, reviewers may be looking at different versions of the same disclosure. Comments might relate to an earlier draft, while subsequent changes have already been incorporated elsewhere.
Before proceeding, reviewers should be able to identify:
- The current disclosure version.
- The changes made since the previous review.
- The status of the disclosure within the review workflow.
- Whether the version being reviewed is the one intended for approval.
Controlled versions, assigned ownership and visible review statuses help maintain clarity throughout the reporting process.
For further context, see 7 Signs Your Disclosure Management Process Is Creating Unnecessary Work.
2. Do the Reported Figures Agree with the Supporting Information?
The same financial or sustainability metric may appear in several reporting locations, including financial statements, supporting notes, management commentary and sustainability disclosures.
A revised figure in one location can affect calculations, percentages, tables and accompanying explanations elsewhere.
During disclosure review, attention should be given to whether:
- Reported values agree with the relevant source information.
- Figures used across related disclosures remain consistent.
- Supporting calculations reflect the latest information.
- Totals, percentages and comparative values are accurate across reporting locations.
Required reconciliation and validation procedures remain essential. The objective is to distinguish these necessary controls from additional comparisons caused by duplicated or disconnected information.
3. Is the Narrative Accurate and Consistent with the Quantitative Information?
A disclosure may contain correct figures and still present a misleading picture if the surrounding commentary does not reflect those figures. Narrative accuracy requires more than checking grammar or readability; it requires checking whether explanations, trends and conclusions are supported by the latest reported information.
For example, a statement describing a decrease in costs should not remain unchanged after a final adjustment shows an increase. The same principle applies to sustainability metrics, year-on-year comparisons and performance explanations.
Before sign-off, reviewers should verify that:
- Descriptions of increases, decreases and trends agree with the final figures and comparisons.
- Narrative references to percentages, units, baselines and reporting periods are accurate.
- Explanations of significant movements, assumptions and performance drivers are supported by the underlying information.
- Management commentary, financial notes, sustainability narratives and summary sections do not contradict the related quantitative disclosures.
A change to a number may require a corresponding change to the explanation. Reviewing the two together helps avoid disclosures that are numerically correct but narratively inconsistent.
4. Is the Disclosure Complete Under the Applicable Regulatory Requirements?
A disclosure can be internally consistent and supported by evidence but still be incomplete if an applicable reporting requirement has been missed. Regulatory completeness is therefore a distinct checkpoint, not simply another data-validation exercise.
Because requirements differ by jurisdiction, entity type, reporting period and reporting framework, reviewers should assess completeness against the obligations that actually apply to the organization.
The review should establish whether:
- Applicable disclosure requirements have been identified and mapped to the relevant sections of the report.
- Required statements, notes, qualitative explanations, metrics and comparative information have been included where applicable.
- Any reporting boundaries, periods, prescribed formats and filing-related requirements have been addressed.
- Omissions, exemptions or transitional reliefs have been assessed, documented and approved where appropriate.
- Open regulatory interpretation or compliance questions have been resolved by the responsible specialists before sign-off.
The objective is not to apply every possible requirement. It is to demonstrate that all requirements relevant to the particular disclosure have been considered and that any decision not to report an item has a documented basis.
5. Have Validation Issues and Missing Information Been Addressed?
Disclosure review also involves resolving data-quality, consistency and validation issues that could affect the reliability of the reported information.
Validation activities can help identify missing reporting data, incomplete disclosures, inconsistent units or reporting periods, missing documentation and unresolved issues.
Before approval, reviewers should consider whether identified exceptions have been assessed and whether the relevant reporting information has been corrected or appropriately resolved.
Automated validation can support this process by highlighting issues for investigation. It does not replace professional judgment, required reporting controls or authorized review.
6. Is the Supporting Evidence Available and Relevant?
Supporting evidence for a disclosure may include calculations, working papers, source extracts, methodology notes and management explanations.
The existence of supporting documentation is important, but reviewers also need to establish its relationship to the disclosure being examined.
Relevant review considerations include:
- Whether supporting records can be traced to the reported information.
- Whether the evidence relates to the appropriate reporting period.
- Whether the documentation reflects the current disclosure version.
- Whether significant calculations and explanations are accessible for review.
Maintaining the relationship between disclosures and their supporting evidence helps reviewers examine the basis of reported information without repeatedly reconstructing reporting history.
7. Have Review Comments and Outstanding Issues Been Resolved?
Disclosure reviews often involve several contributors across finance, sustainability, compliance, legal and management functions.
Review comments may lead to changes in data, wording, calculations or supporting explanations. As disclosure progresses, it becomes important to preserve the context of these decisions.
Before sign-off, reviewers should be able to determine:
- What changes were made during the review process.
- Why significant revisions were introduced.
- Whether earlier comments have been addressed.
- Whether outstanding issues have clear owners and recorded resolutions.
Keeping comments, explanations and decisions associated with the relevant disclosure helps maintain continuity between review stages.
8. Have Later Changes Affected Earlier Reviews or Approvals?
A disclosure can be reviewed correctly and still require reconsideration if its underlying information changes afterward.
For example, an adjustment to a reported figure may affect a related calculation, narrative explanation or supporting document that was previously reviewed.
The important question is whether the earlier review remains applicable to the latest information.
A controlled change-management process should help identify affected disclosures, assess the significance of revisions and determine whether further review or approval is required.
Different changes call for different responses. The appropriate action depends on the nature of the change, organizational policies, materiality considerations and applicable reporting controls.
For a closer look at this challenge, read The Hidden Cost of Disconnected SEC Reporting Workflows.
9. Are the Required Reviews and Approvals Complete?
Disclosure management involves responsibilities across preparation, validation, review and approval.
Clear ownership, defined review stages and appropriate authorization help teams understand which activities have been completed and which decisions remain outstanding.
Before final sign-off, the answers to these questions should be clear:
- Who is responsible for the disclosure?
- Which review activities have been completed?
- Do any issues or approval dependencies remain open?
- Have changes affected previously completed approvals?
- Are the required approvals recorded, and do they remain applicable?
The purpose of a connected disclosure management process is not to remove formal reviews or approvals. It is to preserve reporting controls while making the status, evidence and history of each disclosure easier to follow.
Disclosure Review Checklist: A Quick Reference
The following nine-point checklist brings together the review considerations discussed above.
| Review area | Question to verify |
|---|---|
| Version control | Is the latest disclosure version clearly identified? |
| Data consistency | Do reported figures agree with source information and related disclosures? |
| Narrative accuracy | Does the narrative accurately explain the latest figures, trends and comparisons? |
| Regulatory completeness | Have all applicable disclosure requirements been addressed or appropriately documented? |
| Validation | Have missing information, inconsistencies and identified exceptions been addressed? |
| Supporting evidence | Is the evidence current, relevant and traceable to the disclosure? |
| Review comments | Have outstanding comments and issues been appropriately resolved? |
| Change management | Have subsequent changes been assessed for their effect on earlier reviews and approvals? |
| Approval status | Are the required reviews and approvals complete and applicable to the current version? |
This is a practical review reference. It does not replace an organization’s prescribed approval procedures, internal controls or applicable reporting requirements.
How EcoActive Supports Controlled Disclosure Reviews
EcoActive brings financial and sustainability reporting data, disclosure narratives, supporting evidence and responsibilities into a connected, governed reporting environment.
Its disclosure management capabilities include automated validation, controlled review and approval workflows, role-based permissions, version histories, evidence traceability and audit trails.
By keeping reporting information, changes, comments and approvals connected, EcoActive helps teams maintain visibility across the disclosure lifecycle while preserving human responsibility for reporting judgments and final authorization.
Learn more about EcoActive’s Financial Disclosure Management Software.
Frequently Asked Questions
What should a disclosure reviewer check before approval?
A disclosure reviewer should examine the current version, supporting figures, narrative accuracy, applicable regulatory requirements, validation issues, evidence, review comments, subsequent changes and approval status. The specific review requirements depend on the organization’s established controls and reporting responsibilities.
Can a disclosure require another review after it has already been approved?
Yes. If the underlying reporting information changes, an earlier approval may need to be reconsidered. Whether further review or formal reapproval is required depends on the significance of the change and the applicable approval procedures.
How can reviewers check narrative accuracy against reported figures?
Reviewers should compare descriptions of trends, changes, percentages and performance drivers with the final quantitative data. They should also confirm that related sections of the report use consistent explanations, periods and assumptions.
What does regulatory completeness mean in disclosure review?
Regulatory completeness means confirming that all disclosure requirements applicable to the reporting entity, period and framework have been considered, required information has been included, and any omissions or permitted reliefs have an appropriate documented basis.
Can automated validation replace manual disclosure review?
No. Automated validation can identify potential inconsistencies, missing information and other exceptions. Professional judgment, required controls and authorized approvals remain necessary.
Why is evidence traceability important in disclosure review?
Evidence traceability helps reviewers connect reported information to supporting data, calculations, documentation and relevant reporting decisions. This makes it easier to verify the basis of a disclosure and understand its review history.
Final Thoughts
A disclosure review is not limited to checking the final wording or figures. It also involves verifying applicable reporting requirements, confirming that narrative statements are supported by quantitative information, and understanding the evidence, changes and decisions behind approval.
Keeping versions, reported information, narrative explanations, regulatory checks, evidence, review comments and approvals connected gives reviewers the context they need to evaluate disclosures while maintaining the controls required throughout the reporting process.
