ESG Reporting for Business Functions

Purpose

Give the minimum regulatory and market context so participants understand why requests continue and where their role enters the process.

Key concepts

What changed under the Omnibus and what did not; the three reporting lanes (directly in scope, affected through the value chain, voluntary); how CSRD, ESRS and the Voluntary Standard fit together at a high level; the end-to-end reporting lifecycle and where functions plug in; the boundary between what the course covers and what stays with the reporting lead, legal counsel and assurance provider; the blueprint readiness rubric is introduced here as the target.

Activity

Classify three short company scenarios into lanes and mark where your function enters.

Case link

Determine NordCore's reporting lane and each role pack's responsibilities.

Output

A personal function-impact map (why I am involved, what I may own, who depends on my input), which becomes the cover of the blueprint.

Core deliverable

1, the workstream charter.

Purpose

Turn a technical disclosure request into a bounded assignment inside the participant's function.

Key concepts

Navigating an ESRS request without reading the standards line by line; breaking a request into narrative, policy, action, target, metric and evidence; the four ownership roles (data production, review, approval, disclosure); workstream boundaries, dependencies, decision rights and the participant's own place in the RACI; milestones, review points and a defined escalation route.

Activity

Decode a deliberately ambiguous request and list what must be clarified before work begins.

Case link

Each NordCore role converts a different request into a scoped assignment.

Output

A one-page workstream charter (scope, owner, inputs, outputs, timeline, dependencies, escalation).

Core deliverable

1, the workstream charter.

Purpose

Enable contributors to add useful evidence to double materiality and the impact, risk and opportunity assessment without leading the methodology.

Key concepts

Impact and financial materiality in plain language, and why the two blur in practice, so prioritisation must reflect both impact severity and financial exposure; what functions know that the reporting team does not; evidence versus opinion versus stakeholder input; how a functional input actually changes a materiality decision; documenting assumptions, uncertainty and disagreement; avoiding broad data collection disconnected from material topics.

Activity

Assess a small set of candidate topics from your function's angle and justify what evidence is relevant.

Case link

NordCore teams weigh climate, workforce, supplier labour, operational safety and business-conduct issues.

Output

A functional IRO and evidence map (issue, relevance, source, owner, unresolved question).

Core deliverable

2, the evidence map.

Purpose

Show that credible reporting is a coherent chain from intent to proof, not a set of isolated KPIs.

Key concepts

How policies, actions, targets and metrics connect, and who owns each link; distinguishing a commitment, an implemented action and a measured result; baselines, target periods, methodologies and ownership; finding gaps between policy language and operational reality; recognising unsupported or overstated claims (introduced here, exercised in full in Module 7).

Activity

A claim-and-evidence autopsy on a weak disclosure, rebuilt using only the evidence available.

Case link

Each NordCore role tests whether its policy-to-action-to-target-to-metric chain is internally consistent.

Output

A policy, action, target and metric evidence map plus a list of disclosure gaps to correct or escalate.

Core deliverable

2, the evidence map.

Purpose

Prepare data that is consistent, explainable and usable for reporting and review.

Key concepts

Clear metric definitions, reporting boundaries and source systems; data lineage at contributor level (where the number came from, who changed it); methodologies, estimates, proxies and limitations; period and boundary consistency; value-chain and Scope 3 inputs, including the value-chain cap (partners with 1,000 or fewer employees may decline anything beyond the Voluntary Standard, and the requester must indicate which items exceed the cap and state that right; it applies only to CSRD reporting) and how to request supplier information proportionately; coverage percentages, and separating a refusal from a non-response; issue logs and version control. Deep lineage and consolidation are routed to the finance and data role packs rather than the whole cohort.

Activity

Review a flawed submission (inconsistent boundaries, unsupported estimates, duplicate figures, missing evidence) and write the specification and issue log that would have prevented the defects.

Case link

NordCore's finance, HR, procurement and operations packs each contain a different data-quality failure.

Output

A data-specification sheet, quality checklist and issue log for one functional metric.

Core deliverable

3, the data-specification sheet.

Purpose

Move participants from sending the number to producing information that survives management challenge and limited assurance.

Key concepts

What limited assurance means for a contributor; preventive and detective controls; evidence standards, retention and traceability; review, approval and sign-off; managing corrections, late changes and exceptions; the one-line test that separates reliable evidence from unsupported narrative; the few assurance findings contributors cause. Held at contributor level: participants learn what a reviewer will ask and what evidence answers it, not audit methodology.

Activity

Design proportionate controls for one metric and stress-test whether the retained evidence would support a reviewer's challenge.

Case link

NordCore receives assurance questions on workforce, emissions and supplier information.

Output

A control-and-evidence matrix (risk, control, owner, reviewer, frequency, retained evidence).

Core deliverable

4, the control-and-evidence matrix.

Purpose

Build the coordination and judgement needed when reporting crosses functions, systems and deadlines.

Key concepts

Running effective data-owner and issue-resolution conversations; escalating missing data, changed methodologies and disputed ownership; working with sustainability, finance, legal, communications, internal audit and assurance; challenging public claims not supported by the reporting record; documenting decisions so the rationale is visible later. All claim-and-escalation work is consolidated in this module.

Activity

A live simulation with late data, a methodology change, conflicting owners and an unsupported external claim; participants decide what can be reported, what must be qualified and what must be escalated, then justify each decision.

Case link

NordCore must resolve the same conflicts across roles.

Output

An escalation map and a claim-challenge checklist.

Core deliverable

5, the operating plan with 90-day actions.

Purpose

Integrate the course into a practical operating model participants can take back to work.

Key concepts

Workstream readiness and maturity against the shared rubric; prioritising gaps by reporting risk and business impact; the minimum viable process for the next cycle, including the reporting calendar and governance rhythm; resource, system and capability needs; peer challenge focused on your contribution and its defensibility; continuous improvement after the cycle.

Activity

A five-minute defence of your blueprint against structured peer challenge, where peers probe evidence and defensibility rather than enterprise-level decisions.

Case link

Each NordCore role completes its workstream and the class tests whether the combined process is coherent.

Output

A role-specific reporting workstream blueprint and a 90-day action plan.

Core deliverable

Assembles all five into the blueprint, and completes 5, the operating plan and 90-day plan.