DataSolmu blog

IFRS S1 Basis for Conclusions Makes Evidence Work Visible

How IFRS S1 implementation becomes scope, materiality, core-content, judgement, and transition evidence discipline.

ISSB IFRS S1 disclosure materiality value chain controls evidence readiness implementation
Illustration of IFRS S1 evidence readiness moving through objective, materiality, core content, judgement, and transition controls.

IFRS S1 implementation is easier to manage when the reporting team treats it as an evidence system, not as a writing project. The IFRS Foundation's Basis for Conclusions is useful because it shows the reasoning behind the standard: why sustainability-related financial information needs a clear objective, why judgement matters, and why reporting discipline has to connect sustainability work with financial reporting habits.

The practical question for a company is not only "what does the standard say?" It is "what operating records would show that our sustainability disclosure process is controlled, explainable, and reviewable?"

That is where IFRS S1 readiness becomes DataSolmu work: scope decisions, materiality records, connected information, evidence owners, judgement trails, and transition controls.

Start With The Reporting Question

IFRS S1 is built around information that helps users of general purpose financial reports understand sustainability-related risks and opportunities. For a reporting team, that objective should become a practical intake question before drafting begins.

Useful intake records include:

This prevents the team from jumping straight into narrative. A disclosure should be the result of a controlled decision, not the first place where the decision is made.

Make Materiality Reviewable

Materiality is not just a topic filter. It is a judgement about whether information could influence users' decisions. That judgement becomes fragile when it is kept in meeting notes, spreadsheets, or memory.

A stronger process records the facts and assumptions behind the decision. The team should be able to show which risks and opportunities were considered, what evidence was used, which business units or functions contributed, what was excluded, and why the conclusion still holds for the reporting period.

The same discipline applies to connected information. Sustainability disclosures often depend on strategy, financial planning, risk management, procurement, operations, workforce data, and value-chain assumptions. If those links are not visible, the report can look coherent while the evidence remains scattered.

For Varmennappi-style review, this is a natural checkpoint. The workflow can ask whether a materiality conclusion has an owner, evidence, challenge record, scope boundary, and unresolved assumptions before the claim moves into public reporting.

Turn Core Content Into Owned Workflows

Governance, strategy, risk management, and metrics and targets are often discussed as disclosure headings. In implementation, they are better treated as workflow routes.

Governance needs evidence of who oversees sustainability-related risks and opportunities, what information they receive, and how decisions are escalated. Strategy needs a link between sustainability topics, business model, financial planning, resilience, and dependencies. Risk management needs process evidence: identification, assessment, prioritisation, monitoring, and integration with wider risk systems. Metrics and targets need definitions, boundaries, source systems, assumptions, and review history.

Those routes should not live in separate reporting silos. A climate metric may depend on operations data, supplier estimates, finance review, internal controls, and target governance. A risk disclosure may need strategy input, risk-owner approval, and evidence that the topic was considered over the right horizon.

DataSolmu's view is that core content becomes reliable when every public claim can be traced back to an owner, method, evidence record, and review point.

Control Where The Information Lives

IFRS S1 readiness also requires discipline around where sustainability-related financial information appears and how it connects with the rest of the reporting package. Companies may use annual reports, sustainability statements, management commentary, or other report locations depending on local requirements.

That placement choice should be controlled. The reporting team should know which document contains the information, which reporting basis it supports, when it is published, whether comparative information is needed, and how consistency with other public statements is checked.

This matters because reuse can create risk. The same evidence may support several disclosures, but the reporting basis, materiality lens, wording, timing, and sign-off may differ. A controlled source-to-claim workflow lets teams reuse work without flattening those differences.

Track Judgement And Uncertainty

Sustainability reporting involves judgement: whether information is material, which assumptions are reasonable, how uncertain estimates should be described, and when prior information needs correction. These are not side issues. They are part of the control environment.

A practical evidence record should capture:

This is especially important where data is new, supplier information is incomplete, methods are developing, or financial effects are difficult to estimate. The goal is not to remove uncertainty. The goal is to make uncertainty visible enough to review.

Treat Transition As A Managed State

Transition reliefs and effective dates can help companies start, but they should not become informal shortcuts. A company needs a clear record of which reliefs were used, why they were available, which disclosures are affected, and what must improve in later periods.

A simple transition register can separate work into current-period disclosures, deferred items, data-quality improvements, owner assignments, system changes, assurance preparation, and open judgement questions. That register helps leadership see whether first-year reporting is a controlled stage in a readiness plan or just a deadline response.

It also helps with future review. When a relief expires or local rules change, the team can see which evidence gaps were known, who owned them, and what changed since the previous reporting cycle.

The DataSolmu View

The strongest lesson from IFRS S1 implementation is that disclosure quality depends on the operating layer below the report. The company needs a way to connect sustainability topics to reporting scope, materiality, evidence, owners, review, uncertainty, and final wording.

That is the layer DataSolmu cares about. Reporting software should preserve the route from question to judgement to evidence to claim. It should also make weak spots visible before publication: unclear ownership, unsupported assumptions, inconsistent source data, missing review, or overconfident language.

For Varmennappi, the boundary is practical. It can help teams review inputs, find evidence gaps, challenge assumptions, and prepare cleaner reviewer questions. It should not replace the authoritative standard, make legal or assurance conclusions, or generate a filing-ready report.

Practical Takeaway

IFRS S1 readiness should be managed as evidence readiness. Start with the reporting objective, make materiality and connected information reviewable, turn core content into owned workflows, control report placement and reuse, document judgement and uncertainty, and keep transition decisions visible. That is how sustainability-related financial disclosure becomes more than a narrative exercise.

Source

IFRS Foundation: IFRS S1 Basis for Conclusions