Your CFO Just Asked 'What's Our Carbon Number?'

Board meeting is Thursday. The CFO wants total Scope 1 and 2 emissions for the current financial year, broken down by state. The sustainability manager opens three spreadsheets, cross-references two incomplete reports, emails two site managers for missing gas data, and spends the next two-and-a-half days assembling a number they're only about 80% confident in.

By the time it reaches the board pack, the data is already six weeks old.

This happens every quarter across thousands of Australian companies right now. And it's about to get a lot worse, because AASB S2 turns climate data into a standing board agenda item - not an annual exercise you can push to the sustainability team and forget about until reporting season.

Climate is now a board-level data problem

AASB S2 paragraph 6 requires entities to disclose how the governance body oversees climate-related risks and opportunities. Specifically, entities must disclose how often climate-related matters are reported to the board, whether the board has the skills and competencies to understand the data, and how climate considerations factor into strategic decisions and target-setting.

That's not a once-a-year disclosure. It describes an ongoing governance rhythm.

The AICD's 2024 Climate Governance Study surveyed 1,057 Australian directors. 80% expressed concern about climate change as a material risk. But 58% said their board doesn't even have a dedicated sustainability committee. And only 26% had undertaken climate governance training - up from 18% in 2021, but still nowhere near where it needs to be.

Here's what we see playing out: boards that genuinely want to exercise climate oversight can't, because the data takes too long to reach them. By the time emissions figures are compiled, validated, formatted into a slide deck, and presented at the next scheduled board meeting, the numbers reflect a period that ended one to three months ago. Directors are making decisions based on a rearview mirror.

Financial data doesn't work this way. Your CFO can pull revenue by division, by month, in minutes. They don't email three department heads and wait two days for someone to reconcile a spreadsheet. But that's exactly how carbon data works in most organisations today.

The real bottleneck isn't calculation - it's assembly

Most sustainability managers we talk to aren't slow at the maths. The emission factor for NSW grid electricity is 0.64 kg CO2-e per kWh. Victoria is 0.78. Multiply consumption by factor, sum it up. The calculation itself takes seconds.

The bottleneck is getting the consumption numbers in one place.

Consider a company with operations across four states - NSW, VIC, QLD, and WA. They've got electricity accounts with different retailers in each state. Gas contracts with two different providers. Fleet fuel cards from three suppliers. Waste collection invoices from a fourth. Each data source arrives in a different format, at a different time, in a different system.

The sustainability manager's job isn't really "carbon accounting." It's data integration. They're a human ETL pipeline - extracting numbers from PDFs, transforming them into consistent units, and loading them into a spreadsheet so they can do the actual calculation.

PwC's 2025 Global Sustainability Reporting Survey found that more than 60% of organisations increased the amount of senior leadership time spent on sustainability reporting in the past year. And a 2025 MIT Sloan study found 66% of companies still use spreadsheets for some part of their Scope 3 tracking. The bottleneck isn't awareness or ambition. It's plumbing.

When the CFO asks "what's our carbon number?", the sustainability manager doesn't need three days to calculate it. They need three days to find it.

What if executives could ask the question directly?

This is the problem we built Carbonly Co-Pilot to solve. Not the annual report generation - we already handle that through our NGER and AASB S2 report modules. Co-Pilot is for the other 364 days of the year. The ad hoc questions. The "can you get me this before lunch?" requests that currently eat up the sustainability team's week.

Carbonly Co-Pilot sits inside the platform and answers questions about your emissions data in plain English. You type a question, and it returns an answer pulled from your live, verified data.

"What were our total Scope 1 emissions last quarter?"

It gives you the number. Broken down however you need it - by project, by site, by state, by source type. In seconds. Not days.

"Compare NSW vs VIC Scope 2 emissions by month for this financial year."

Done. It understands Australian financial years (July to June). It understands "this FY," "last quarter," "YTD." It knows that when you say "Scope 2 by state," you want the state-specific NGA emission factors applied, not a national average.

"Which project had the highest diesel consumption this quarter?"

It queries across your uploaded fuel data, finds the answer, and shows you the numbers. Same data that feeds your compliance reports. Same audit trail. Same source-traced records.

This isn't a chatbot that's been trained on generic climate information. It's querying your actual emissions ledger - the same data your NGER report or AASB S2 disclosure pulls from. Every answer traces back to source documents.

The queries that actually matter for board reporting

We built Co-Pilot because we kept hearing the same pattern. A sustainability manager spends 70% of their time answering questions from executives instead of doing the analytical work that actually moves decarbonisation forward.

Here are the kinds of questions Co-Pilot handles - the ones that used to trigger a two-day data assembly exercise:

Emissions overview: "What's our total Scope 1 and 2 for this FY so far?" or "How do our Q2 emissions compare to Q1?"

Geographic breakdowns: "Show me Scope 2 by state" or "Which site has the highest emissions intensity per dollar of revenue?"

Source-level queries: "How much diesel did we use across all projects in October?" or "What's our natural gas consumption in Victoria YTD?"

Anomaly detection: "Were there any anomalies flagged this month?" or "Which sites showed consumption spikes in the last 90 days?" This connects directly to our anomaly detection module, so you're not just looking at totals - you're catching the outliers that could signal a data error or a genuine operational problem before it shows up in a compliance report.

Target tracking: "How are we tracking against our SBTi target?" or "What's the gap between our current trajectory and our 2030 reduction commitment?"

Scope 3 spend analysis: "Which business unit has the highest Scope 3 procurement spend?" or "What are our top 10 suppliers by estimated emissions?"

Each of these used to be a mini-project. Now it's a sentence.

Why this matters for AASB S2 governance disclosures

Here's the part most companies miss. AASB S2 paragraph 6 doesn't just ask whether your board oversees climate matters. It asks you to disclose how and how often the governance body is informed about climate-related risks. It asks whether the board has appropriate skills and competencies. It asks how climate factors into decisions about major transactions.

If your board gets a climate update once a year - or once a quarter with data that's already two months stale - that's what you're disclosing. And an auditor under ASSA 5010 is going to read that disclosure alongside your actual governance meeting minutes. If your climate data reporting rhythm doesn't match what you've described in your governance disclosure, that's a finding.

The KPMG Australian Sustainability Reporting Trends research found that 76% of ASX100 companies are reporting in line with TCFD recommendations. But reporting in line with TCFD once a year is fundamentally different from demonstrating ongoing board oversight under AASB S2. The standard expects a governance process, not a governance event.

Having a system where any board member (or their direct report) can query live emissions data changes the governance dynamic. Instead of the sustainability team preparing a quarterly climate slide deck that's out of date by the time it's presented, directors can check current numbers before a strategy discussion. The COO can ask about site-level diesel trends before approving a fleet procurement decision. The CFO can pull Scope 2 by state before signing off on a PPA.

That's real governance oversight. Not a PDF attachment nobody reads until the auditor asks about it.

Not replacing your sustainability team - unblocking them

We want to be clear about what Co-Pilot is and isn't. It's not a replacement for sustainability expertise. It doesn't write your transition plan. It doesn't run your materiality assessment. It doesn't decide which Scope 3 categories are material to your business.

What it does is stop your sustainability manager from being a full-time data concierge.

We've heard the same frustration from sustainability teams at companies of every size: they were hired to build decarbonisation strategies, but they spend most of their time pulling numbers for other people. The CFO needs a figure for the board pack. The procurement team wants emissions data for a tender response. The marketing team wants to know if they can claim a year-on-year reduction. The investor relations team needs Scope 1 and 2 for an ESG questionnaire. Each request is reasonable. But they add up to a sustainability manager who's permanently reactive instead of strategic.

Co-Pilot handles the data retrieval so the sustainability team can do the work that actually needs a human - interpreting trends, recommending actions, designing reduction pathways, engaging suppliers on Scope 3.

We're honestly not sure yet whether executives will prefer to query Co-Pilot directly or whether the sustainability team will use it to answer requests faster. Probably both. The point is that the data should be accessible in seconds, not locked behind a three-day assembly process.

The audit trail doesn't change

One concern we hear: "If a board member gets an answer from an AI assistant, how do we know it's accurate? How does that hold up under assurance?"

Fair question. And the answer is that Co-Pilot isn't generating numbers. It's querying the same emissions ledger that produces your compliance reports. Every data point in Carbonly has a source document attached - the utility bill, the fuel receipt, the waste invoice. The emission factor applied is traceable to the NGA Factors workbook or a product-specific EPD. The calculation methodology is documented.

When Co-Pilot tells you "Scope 2 for NSW this FY is 1,247 tonnes CO2-e," that number comes from the same verified dataset your auditor will examine. It's not a separate system. It's not an estimate from a different model. It's your data, queried in plain English instead of through a report export.

The Harvard Business School research published in Nature Climate Change found that 74% of S&P 500 companies have revised their emissions data at least once - and in most cases, revised upward. The root cause wasn't dishonesty. It was fragmented data systems producing inconsistent numbers depending on who queried them and when. A single source of truth queried consistently is one of the simplest ways to avoid restatements.

What this looks like in practice

Imagine it's Wednesday afternoon. The board pack is due tomorrow. The CFO's EA sends a message: "Can you include our FY26 YTD emissions by state, and flag any material changes from last year?"

Old way: sustainability manager opens the master spreadsheet, realises Queensland gas data is missing for November, emails the Brisbane office, waits for a response, manually calculates the delta from last year, formats a table, writes a one-paragraph summary, and sends it at 9pm.

With Co-Pilot: the sustainability manager types "What are our total Scope 1 and 2 emissions by state for FY26 YTD, compared to the same period FY25?" Gets a table in seconds. Checks the anomaly flag - one spike in Queensland gas in November is already explained (planned maintenance shutdown, tagged in the incidents module). Copies the output into the board pack with the source trail intact. Done in five minutes.

The numbers are the same. The audit trail is the same. The difference is time: five minutes versus potentially five hours (or more, if the Brisbane office is slow to reply).

Group 2 entities - this is your problem in 12 months

If you're a Group 2 entity under ASRS, your first reporting period starts for financial years beginning on or after 1 July 2026. That means your governance structures need to be in place before then. Not just documented - actually functioning.

AASB S2 paragraph 6 requires you to disclose how climate-related risks are reported to the board. If the honest answer is "we compile a spreadsheet once a year and include it in the annual report," that's going to look thin compared to companies that demonstrate quarterly or even real-time climate data governance.

You don't need to have every Scope 3 category measured before your board can start exercising oversight. Start with Scope 1 and 2. Get those numbers flowing into a system your board can actually access. Build the governance muscle now, when the data is simpler. Add complexity later.

The companies that are going to struggle with AASB S2 aren't the ones with imperfect data. They're the ones whose data is locked in a spreadsheet that only one person knows how to operate - and that person is on leave when the board meeting happens.

Get your emissions data into a system where anyone authorised can ask a question and get a verified answer. That's the starting point for real climate governance - and it's a more honest disclosure than a polished annual report based on numbers nobody can reproduce.

Related Reading: