The Board Asked Why Emissions Moved. Here Is Who...

Group Scope 1 emissions moved 8% quarter-on-quarter. The audit committee chair looks up from the pack and asks the obvious question. Why.

The sustainability lead's answer, in the meeting: "We're still investigating." The answer three weeks later, in an email attachment: a 14-slide PowerPoint that lands two days after the next board meeting.

That is the actual rhythm of variance analysis in most Australian ASX200 finance functions right now. Three-week turnarounds on a question a director asked in a 20-minute agenda slot. And the workaround is not "hire more analysts". The workaround is that the analysis has to already exist by the time the question gets asked.

That is what the Variance Explanation Agent is for.

The three-week PowerPoint problem

Variance analysis on the emission ledger is not conceptually hard. It is decomposition. You take the current period total, you take the comparison period total, and you break the difference into named contributors. Rate effect. Volume effect. Mix effect. New sources. Removed sources. Methodology shifts.

What makes it hard in practice is that the data lives everywhere. Fuel logs in a fleet management system. Invoice batches in accounts payable. Site manager notes in an operations Teams channel. The NGA Factors workbook in someone's downloads folder. The sustainability team pieces the story together by hand, over three weeks, into a deck that describes what already happened.

By the time the board sees it, two things are true. The number is a snapshot from six weeks ago. And the driver commentary is a narrative reconstruction, not a query against live data.

For a monthly board rhythm, that timeline does not work. For an AASB S2 governance disclosure that has to describe how directors are actually informed about climate matters, it barely works either. Paragraph 6(a)(iii) asks how and how often the governance body is informed. "In a slide deck that arrived after the meeting" is not a good answer.

What the Variance Explanation Agent actually does

The agent runs the decomposition against the live emission ledger, on demand, for any two periods. Current quarter vs prior quarter. Current year vs prior year. Any custom pair. The output is a ranked list of named drivers per facility, per material, per scope, with the underlying source records attached to each one.

The decomposition is deterministic. For every material at every business unit, the agent splits the emission delta into an activity effect (quantity difference at the prior-period factor), a factor effect (factor change at the prior-period quantity), and flags any methodology shifts where the scope classification changed. New emission sources that only appear in the current period get their own contributor line. Sources that disappeared get another. Each contributor carries the tonnes CO2e impact and the percentage of total variance it explains.

That is the maths. What the CFO sees is a ranked list.

Three worked examples of what a driver row looks like in practice.

Perth mine site diesel up 18%, contributing 340 tCO2e to group variance. The agent surfaces the activity effect against the prior-period factor, then links through to the source fuel dockets. Operational context, in this case, is that a night shift started in May and two additional haul trucks are contributing roughly 340 extra litres per shift. The sustainability lead does not have to construct that story from scratch; the agent surfaces the ranked variance driver and the underlying records, and the operational narrative gets added by the site manager who already knows the answer.

Melbourne distribution centre refrigerant down 12%. On the surface, a positive story. The agent flags something different: R-410a service dockets are running 40% behind the prior-year pace at this stage of the reporting cycle, and the pending service window in Q4 may reverse the movement entirely. The driver row shows the current activity data alongside the expected shape of the ledger by year-end. That is the kind of context a board briefing needs, because "refrigerant emissions down" without the pending service window is a story that will unwind at the next board meeting.

Group Scope 2 up 3% despite consumption flat. The agent surfaces this as a factor effect, not an activity effect. The NGA 2025 Factors updated mid-year for Victoria from 0.76 to 0.78 kg CO2-e per kWh. Same kilowatt hours, different factor, different tonnes. The driver row makes the methodology origin explicit so the board understands the movement is a calculation artefact, not an operational deterioration. This is the class of driver that most spreadsheet analyses miss entirely, because factor version drift does not show up if the analyst is using the same lookup table across both periods.

Every driver row in every example above carries the same audit metadata: facility, material, magnitude in tCO2e, direction, and a link through to the underlying source records. That is the difference between a variance narrative and a variance narrative that survives assurance.

Why the agent's answer beats the spreadsheet

Three reasons, and none of them are "AI".

The decomposition is deterministic. Rate effect versus volume effect versus factor effect is standard variance analysis maths. The agent applies it consistently across every material at every business unit, which is where the spreadsheet version breaks down. A human analyst has time to decompose ten drivers by hand. The ledger has three hundred. The agent does all three hundred, ranks them, and hands back the top ones.

The source records are one click away. Every contributor line links back to the underlying source documents that generated the emission records. That matters at board level because directors ask follow-up questions. "Show me the actual invoice" is a reasonable request. In the PowerPoint workflow, the answer is "I'll get back to you". In the agent workflow, the answer is a link.

The narrative is grounded in the live ledger, not a snapshot. Three weeks after the analysis started, new invoices have arrived, service dockets have been reconciled, and the underlying data has moved on. A snapshot analysis is out of date by the time it lands. The agent's answer reflects the state of the ledger at the moment the CFO asks the question.

And every explanation carries the audit trail. Factor versions are pinned to each emission record. If the Victoria grid factor updated on 15 May 2026 from 0.76 to 0.78, the emission records before that date carry the old factor and the ones after carry the new one. When the agent surfaces the 3% Scope 2 factor effect above, it is not inferring a factor change; it is reading the pinned factor version on each record and computing the delta directly. That property is what makes the output defensible under ASSA 5010 assurance.

The Proactive Report Agent puts variance in front of the CFO

The Variance Explanation Agent does not sit and wait for someone to click a button. It feeds the Proactive Report Agent, which auto-generates a quarterly draft board pack for the CFO and sustainability lead in the week before the board meeting. The variance analysis is inline in that draft. Top three drivers by magnitude, with the source records attached, with the forecast implication surfaced next to each one.

That means the sustainability lead walks into the pre-board meeting with an existing draft, not a blank page. The conversation is about which drivers to lead with and what operational commentary to add, not about assembling the variance decomposition from raw invoices. This is the workflow described in the Carbon Data at the Board Meeting post, and it changes the CFO's relationship with sustainability data. The number becomes a live artefact instead of a lagging report.

The forecast reads the same driver list

There is a second reason the driver decomposition matters, and it is not about the past. It is about the year-end projection.

The emissions forecasting engine uses the same driver decomposition to project where the ledger lands by year-end. When the agent surfaces "Perth site night shift diesel" as the top Q2 variance driver, the forecast reflects that driver rolled forward. If the shift pattern continues, the projected Scope 1 for the year moves accordingly. If the driver is expected to reverse (as in the Melbourne refrigerant example), the forecast reflects the reversal.

That linkage matters at board level for one specific reason. Safeguard Mechanism baselines decline 4.9% per year. A facility that is 340 tonnes into a Q2 variance is not just answering "why did this move"; it is answering "are we going to breach". The driver-forecast link means the same variance analysis that explains the past becomes the input to the exposure projection for the year. One decomposition, two uses.

The Data Health Agent separates real movement from data quality

Not every variance is a real operational movement. Some variances are the ledger changing shape because the data quality changed.

A supplier who normally emails monthly invoices skipped a month. A factor version updated mid-quarter and only re-flowed through half the records. A duplicate fuel docket inflated the diesel total by 30,000 litres. These look like operational movements in an aggregate. They are actually data quality events.

The Data Health Agent runs alongside the Variance Explanation Agent and tags any driver row whose root cause is data quality. On the board briefing output, those drivers get a separate category. That way, when the sustainability lead is walking the audit committee through the top variances, the answer to "is this a real change or a data issue" is already labelled on the row. The CFO does not have to ask.

The board-pack quality checklist

Every variance the agent surfaces carries, at minimum:

Facility (which business unit generated the variance)
Material or driver (which activity or factor moved)
Magnitude in tCO2e and percent of total variance
Driver category (operational, seasonal, methodology, data-quality)
Source-document links for the underlying records
Forecast implication (how the driver rolls into year-end projection)

That is the metadata set that lets a board briefing pass audit review. Assurance providers under ASSA 5010 will ask for the audit trail behind each material variance. If the variance narrative in the board pack has no traceability to underlying records, the answer to the auditor is "let us reconstruct it". The agent skips that step by attaching the source records to every driver row at the moment the driver is surfaced.

The MCP integration puts variance analysis on the CFO's own AI stack

The Variance Explanation Agent is exposed through the Carbonly MCP server via the ask_copilot tool. That means a CFO who already uses ChatGPT or Claude Desktop for other finance queries can connect that AI assistant directly to the live carbon ledger and ask the variance question in plain English.

"Why did group Scope 1 move this quarter" gets the same ranked driver list the sustainability team sees, in the CFO's own tool. The source records surface as links. The AASB S2 governance disclosure improves as a byproduct, because now the CFO is genuinely engaging with the underlying data, not with a slide deck someone else prepared.

We should be honest about what this changes. It is not that the CFO becomes a carbon accountant. It is that the CFO can ask the variance question at 6pm on a Thursday and get a real answer before the Friday board packet gets finalised. That is a different governance rhythm than the three-week PowerPoint one.

The consultant angle

Sustainability consultants who run quarterly variance analysis across five or ten client portfolios face the compounding version of this problem. Five clients, three-week turnarounds each, and none of it is scalable.

The consultants who use Carbonly under a multi-tenant configuration run the Variance Explanation Agent across each client's ledger and compress a per-client variance analysis from days to minutes. The consultant still owns the operational commentary, the strategic framing, the recommendation on which drivers to flag to the board. The agent does the decomposition and the source-record attachment. That is the split of labour that lets a consulting practice scale, and it is why we treat consultants as buyers, not competitors.

What the agent is not

One important boundary. The Variance Explanation Agent is variance analysis on the realised emission ledger. It is decomposition of movements that already happened.

It is not scenario analysis under AASB S2 paragraph 22. Scenario analysis projects emissions or climate impacts under hypothetical climate pathways (a 1.5 degree pathway, a 2.5 degree pathway, a policy shock). That is a different question, requiring different inputs, different assumptions, and different tooling. Do not conflate the two. Variance analysis explains what moved. Scenario analysis explores what could move under a specified future.

Both matter for AASB S2 disclosure, and both belong in a well-run climate governance function. But asking the variance agent to run scenario analysis is a category error.

Practical starting point

Pick one facility with meaningful recent variance. A construction site where fuel consumption moved more than 10% quarter-on-quarter is a good candidate. A distribution centre where the electricity bill jumped. A Safeguard-covered facility where the year-to-date exposure has shifted.

If the workspace has an MCP integration configured, ask ask_copilot via ChatGPT or Claude Desktop: "why did Perth diesel move this quarter". Or open the emissions trend chart in the workspace and click "Explain this change" on the movement itself. Same agent, same answer, different surface.

The ranked driver list will surface the top contributors with source records attached. Walk the top three drivers with the site manager. That conversation is what makes the number defensible at board level. The agent does the arithmetic; the operational context comes from the people who know the operation.

Carbonly is per-project pricing with a $100/month workspace minimum. For a demonstration of variance analysis against a real ledger, or to discuss the Group 2 AASB S2 board reporting workflow, contact hello@carbonly.ai.

The Board Asked Why Emissions Moved. Here Is Who Actually Answers That Question