DataSolmu blog
IFRS Sustainability Disclosure Examples Need Controls
How illustrative IFRS S1 and IFRS S2 disclosures become evidence, judgement, governance, and review workflows.
Illustrative sustainability disclosures are useful when they help a reporting team ask better implementation questions. They become risky when they are treated as wording to copy.
PwC's VALUE Plc example is built around a fictional group applying IFRS S1 and IFRS S2. That makes it useful as a practical prompt: it shows the kinds of reporting choices, boundaries, judgements, controls, metrics, and cross-functional ownership that a company may need to organize before public disclosure. The lesson is not that every company should follow the same structure. The lesson is that disclosure quality depends on the operating records underneath the structure.
For DataSolmu, the strongest use is to convert example disclosures into reviewable work: what decision was made, who owns it, what evidence supports it, what assumptions remain, and how the final claim is checked.
Treat Examples As Prompts, Not Templates
An illustrative report can make an abstract standard feel concrete. It can show how a company might connect general requirements, climate disclosures, governance, strategy, risk management, metrics, and targets in one reporting package.
But examples are not company-specific evidence. A real company still needs to decide which risks and opportunities are material, which entities and activities are in scope, which value-chain assumptions matter, which transition reliefs are used, and which disclosures are unsupported or not yet ready.
A practical review starts with a simple control question: if this example suggests a disclosure pattern, what evidence would our company need before using a similar pattern?
That keeps the team away from cosmetic reporting. It also prevents a disclosure example from becoming stronger than the underlying process.
Start With Basis, Boundary, And Judgement
The basis of preparation is not administrative text. It is where the reporting team records the reporting period, reporting entity, presentation choices, connectivity with financial statements, and the boundary of sustainability-related financial information.
Those choices should be controlled before drafting begins. A good evidence record separates:
- the reporting entity and group boundary;
- the reporting period and publication timing;
- the reporting basis being applied;
- the value-chain information included or excluded;
- transition reliefs or first-year assumptions;
- significant judgements and measurement uncertainties;
- links to financial reporting, risk, strategy, and operational records.
Materiality should sit in the same control layer. The team should be able to show which sustainability-related risks and opportunities were considered, how the financial materiality judgement was made, who reviewed it, and why excluded topics were left out.
For Varmennappi-style review, this is a natural intake workflow. The assistant can help identify missing assumptions, unclear ownership, and weak evidence records before the wording becomes a public claim.
Make Governance Operational
Governance disclosures often look like descriptions of committees, board oversight, management roles, remuneration policies, and risk processes. The implementation work is more concrete.
The reporting team needs evidence that oversight actually receives useful information, management responsibilities are assigned, risk processes include sustainability topics, and metrics or targets are reviewed by accountable owners. If remuneration or incentive structures refer to sustainability performance, the underlying metric definitions and review process should be visible.
This is where disclosure governance becomes operational discipline. A company should not only say who oversees sustainability-related risks and opportunities. It should preserve the route from issue identification to management review, board visibility, approval, and final disclosure.
DataSolmu's view is that governance is strongest when it is connected to evidence flow. The same platform layer should show the owner, source data, judgement, review status, and final claim.
Turn Climate Examples Into Evidence Routes
Climate disclosures can cover physical risk, transition risk, resilience, scenario assumptions, policies, controls, non-GHG metrics, and greenhouse gas emissions. An example can show how these parts may fit together. The real work is making each part testable.
A climate evidence route should answer:
- which risk or opportunity is being assessed;
- which business activities, locations, suppliers, or assets are affected;
- which time horizon is used;
- which assumptions support the assessment;
- what source data supports the metric or narrative;
- who reviewed the method and result;
- what uncertainty remains.
GHG emissions need particular care. Scope boundaries, calculation methods, source systems, estimates, restatements, and target progress should not be buried in disconnected spreadsheets. They should be versioned and reviewable.
This matters because climate disclosure combines narrative and numbers. If the climate story and the evidence model drift apart, the report becomes harder to defend.
Apply The Same Discipline To Social And Governance Topics
Illustrative disclosure examples can also help teams see that non-climate topics need the same control logic. Workforce diversity, fair wage commitments, supplier payment practices, and similar topics can look softer than climate metrics, but they still depend on definitions, boundaries, data quality, policies, controls, and review.
For social disclosures, the reporting team should check whether workforce categories are defined consistently, whether regional differences are explained, whether policies apply to the right populations, and whether metrics can be traced to source systems.
For governance-related disclosures, supplier payment practices are a useful example. Payment terms, late payments, disputed invoices, supplier segmentation, and remediation actions can all depend on finance, procurement, legal, and operational data. A public metric should connect back to a controlled process, not just an exported number.
The common thread is evidence ownership. Every disclosure topic needs someone who can explain the definition, method, evidence, review, limitation, and improvement plan.
Build A Review Loop Before Publication
Examples are most valuable when they help the reporting team design a review loop. The loop should start before writing and continue through final publication.
A practical loop includes:
- an intake record for each risk or opportunity;
- a boundary and materiality decision;
- assigned evidence owners;
- method and data-quality checks;
- review comments and approval status;
- final wording tied to the evidence record;
- unresolved assumptions carried into the next reporting cycle.
This also prepares the company for assurance, board review, investor questions, and later digital tagging work. The clearer the evidence route, the easier it is to find weak claims before they are published.
The DataSolmu View
The useful lesson from illustrative IFRS sustainability disclosures is not presentation style. It is control design.
A company needs a way to move from standard requirements and examples into its own evidence, boundaries, judgements, owners, metrics, and claims. That operating layer should be visible enough for reviewers to challenge it and practical enough for teams to maintain it during the reporting cycle.
For Varmennappi, that means the assistant can help teams review inputs, surface gaps, test assumptions, and prepare better reviewer questions. It should not replace the authoritative standards, copy example wording into a company report, or make legal, assurance, or filing conclusions.
Practical Takeaway
Use illustrative disclosures as implementation prompts. For every example pattern, ask what basis, boundary, materiality decision, governance route, evidence owner, metric definition, and review record would make the same idea defensible for the company. That is how example disclosures become controlled reporting work instead of borrowed narrative.