DataSolmu blog

ISSB Readiness Needs Evidence Controls, Not Duplicate Reports

How practical ISSB adoption work becomes materiality, governance, evidence, assurance, and claim-control discipline.

ISSB IFRS S1 IFRS S2 ESRS materiality value chain controls evidence assurance disclosure

ISSB readiness becomes useful when it is treated as practical operating work, not just a new reporting label. A company may already be preparing ESRS disclosures, monitoring UK or other jurisdictional adoption, responding to investors, and managing climate or broader sustainability data. The risk is that each workstream becomes a separate document exercise.

The better pattern is evidence control. Reporting teams need to know which disclosure basis applies, which materiality lens is being used, where the information will appear, who owns the judgement, and what evidence supports the claim. That is the layer where ISSB preparation becomes manageable.

Start With One Disclosure Map

IFRS S1 and IFRS S2 are designed around sustainability-related financial risks and opportunities. ESRS reporting has its own structure and can require impact materiality as well as financial materiality. A company that sits across both regimes should not respond by duplicating every disclosure task.

The practical move is to build one disclosure map that separates:

• the reporting basis being addressed;
• the entities, jurisdictions, and reporting periods in scope;
• the disclosure location;
• the materiality lens used for the decision;
• the source data and evidence owner;
• the reviewer responsible for the final judgement.

This map helps the reporting team reuse work without blurring requirements. The same underlying evidence may support more than one disclosure, but the conclusion, wording, location, and sign-off can still differ.

Make ISSB Information Easy To Find

Interoperability only helps if report users can find the relevant information. A company may place ISSB-related information inside a broader sustainability statement, annual report, schedule, or public data book. Whatever format it chooses, the information should be clearly signposted.

That signposting is not just a design choice. It is a control. It tells investors and reviewers which information supports which reporting basis, where the underlying data can be found, and which disclosures are still subject to local scope, timing, or assurance differences.

For DataSolmu, this is a product lesson: disclosure management should preserve both reuse and traceability. A system should let a team reuse evidence across regimes while still showing the exact claim, source data, reviewer, and reporting basis attached to each disclosure.

Treat Materiality As A Governed Process

Materiality is where many reporting projects become inconsistent. A multinational group can have local teams, business units, and jurisdictions that see different sustainability issues as important. Some differences are legitimate. The problem is when those differences are not explained.

A useful materiality process has a group-wide method and room for local evidence. It should involve finance, sustainability, operations, HR, procurement, risk, legal, and commercial teams where relevant. It should also challenge the result against business data, peer practice, risk registers, budgets, investor feedback, and public statements.

The output should not be only a ranked topic list. It should be a decision record:

• which topics were considered;
• which lens was applied;
• who contributed evidence;
• which assumptions were challenged;
• which regional differences were kept;
• which topics were excluded and why.

That record matters because ISSB disclosure work depends on judgement. The reporting team needs a way to show how the judgement was made, not just what the final wording says.

Build Supply-Chain Evidence Gradually

Supply-chain data is often the hardest part of sustainability reporting. Suppliers may be small, global, capacity constrained, or using different methods. The answer is not to pretend the data is perfect. The answer is to make the method and improvement path visible.

A practical supply-chain evidence plan should separate what is known, estimated, requested, unavailable, and improving. It should record data boundaries, methods, assumptions, supplier engagement, and review dates. It should also distinguish investor-useful information from data that would be costly to obtain but not decision-useful.

Collaboration can help, especially where companies share suppliers or industry methods. But collaboration still needs governance. Competition-law boundaries, supplier support, shared methodologies, and technical assistance should be recorded as part of the evidence trail.

Varmennappi-style workflows can support this by turning supplier uncertainty into reviewable tasks: what evidence was requested, what came back, what assumption was used, who approved it, and what must improve before the next reporting cycle.

Put Finance In The Governance Loop

Sustainability reporting cannot sit only with a sustainability team once it becomes connected to financial risks, opportunities, investor information, assurance, and annual reporting. Finance needs to be in the loop because many ISSB concepts are close to financial reporting discipline: materiality, controls, evidence, reporting periods, and review.

That does not mean finance owns every sustainability data point. It means the company needs a central owner, a cross-functional working group, and board-level oversight. Finance, sustainability, risk, legal, procurement, operations, HR, investor relations, and technology teams each bring part of the control environment.

Good governance makes weak claims easier to catch. It also makes scope and evidence gaps visible early enough to fix.

Control Green Claims Before Publication

Sustainability disclosures often need to balance progress, uncertainty, and brand narrative. That balance creates greenwashing risk when claims are vague, selective, unsupported, or too confident.

The control response is direct. Claims should be checked for evidence, methods, assumptions, caveats, dependencies, and consistency with other reporting. The process should also record who reviewed sensitive claims and what changed after review.

Useful checks include:

• does the claim have current supporting evidence;
• does it disclose material limitations or dependencies;
• does it avoid selecting only favorable information;
• does it match internal data and external communications;
• could a reasonable reader interpret it more strongly than intended;
• has legal, finance, sustainability, or leadership review been recorded where needed?

This is where a paper trail becomes practical risk management. If a claim is challenged later, the company needs to show how it was prepared and reviewed.

Prepare For Assurance And Ratings Requests

ISSB reporting may not always require independent assurance by itself, but local regimes can add assurance expectations. Ratings agencies can also request information that goes beyond mandatory disclosure topics. Both pressures reward clean evidence records.

A readiness pilot can help before requirements become mandatory. The company can test whether disclosures have owners, evidence, assumptions, review comments, and version history. It can also identify where ratings questionnaires are creating repeated work that should be answered from controlled public reporting data instead.

Digital reporting will make this more important, not less. If data becomes easier for external users to extract, the company needs stronger confidence that definitions, tags, claims, and source evidence are aligned.

The DataSolmu View

The practical ISSB challenge is not only knowing the standards. It is operating the reporting process across overlapping regimes, uncertain supplier data, materiality judgement, claim review, assurance preparation, and investor information needs.

DataSolmu's view is that this should be managed as an evidence-control system. Each disclosure should connect to a requirement or reporting basis, a materiality decision, an evidence owner, a review trail, and a final claim. That makes interoperability real without losing accountability.

For Varmennappi, the same boundary is useful. The assistant can help teams find missing evidence, unclear assumptions, weak claims, and unresolved review questions. It should not replace the authoritative source or make legal, assurance, or filing conclusions for the company.

Practical Takeaway

ISSB readiness should reduce duplicate reporting work, but only if reuse is controlled. Companies need one disclosure map, governed materiality, supply-chain evidence trails, finance-linked oversight, green-claim controls, and early assurance preparation. That is how practical ISSB implementation moves from policy monitoring into reliable reporting execution.

Source

RPC: Navigating the ISSB's sustainability disclosure standards