The Compliance Calendar Nobody Follows (Until the...

Picture a sustainability manager at a mid-cap construction company. Ask her how she tracks carbon compliance deadlines and she'll show you a personal Google Calendar with colour-coded entries. Red for NGER. Blue for AASB S2. Green for CDP. Yellow for the board pack.

When she goes on leave, nobody else knows what's due when. When she's sick for a week in September, data collection doesn't happen. The entire compliance position of a company with $400 million in revenue lives inside one person's calendar app.

This scenario plays out at nearly every company we talk to.

Australian companies now face at least six distinct carbon reporting obligations, each with different deadlines, different data requirements, and different consequences for getting it wrong. NGER due 31 October. AASB S2 sustainability reports lodged with ASIC within three months of financial year-end. Safeguard Mechanism reconciliation by 31 March. CDP submission window closing mid-September. Climate Active renewal dates tied to your certification anniversary. SBTi progress reporting annually, with a mandatory five-year target review that can land at any time.

Nobody has all of this in one place. And that's how compliance failures actually happen. Not because people don't care, but because nobody triggered the data collection early enough.

Six deadlines, one data problem

Here's what makes this genuinely difficult. It isn't just that the deadlines overlap. It's that each framework needs the same underlying emissions data presented differently, validated differently, and submitted through different portals on different timelines.

Take a company with a 30 June financial year that reports under NGER, is caught by AASB S2 as a Group 2 entity from 1 July 2026, has a Safeguard facility, holds Climate Active certification, and discloses to CDP. That company faces this in a single twelve-month period:

Deadline	Framework	What's required	Consequence of missing it
31 March	Safeguard Mechanism	Surrender ACCUs/SMCs for prior year exceedance	Excess emissions penalty of $330/tonne plus $33,000/day
June-September	CDP	Full climate questionnaire (13 modules)	Score of F (failure to disclose), investor scrutiny
30 September	AASB S2 (disclosing entities)	Sustainability report lodged with ASIC	Up to $198,000 ASIC infringement per event
31 October	NGER	Emissions and energy report via EERS	Civil penalty of 100 penalty units ($33,000) per day late
Rolling	Climate Active	Annual public disclosure statement	Certification lapsed, ACCC greenwashing risk if you keep using the mark
Rolling	SBTi	Annual progress disclosure, 5-year target review	Target status downgraded or removed from dashboard

That's six compliance touchpoints using overlapping but not identical datasets. And here's the part that actually breaks things: the data collection lead time is longer than most people assume.

If you need electricity consumption data from a utility retailer for a billing period that ended in June, you won't get the final bill until mid-July at the earliest. Some retailers take three to four weeks. If your NGER data collection doesn't start until August, you're already behind before you've opened a spreadsheet.

For AASB S2 disclosures, the challenge is worse. You need Scope 1 and 2 emissions plus whatever Scope 3 categories you've determined are material, and all of it needs to be at a quality level that survives assurance. Limited assurance for the first few years, but assurance nonetheless. Your auditor isn't going to accept "we're still waiting on the gas bills" as an explanation.

Why the calendar in someone's head doesn't work

That sustainability manager with the colour-coded phone calendar is extremely competent. The problem isn't her. It's the single-point-of-failure design.

Here's what we've seen go wrong repeatedly. A company's NGER report is due 31 October. The sustainability manager knows she needs to start data collection in July. But she's also preparing the company's first AASB S2 disclosure, which has consumed most of her bandwidth since April. CDP submission closed in September, so she spent August on that. By the time she turns to NGER, it's mid-September.

She requests missing utility bills from three retailers. Two respond within a week. The third takes 22 days. It's now 8 October. She still needs to reconcile the data, calculate emissions using current NGA Factors, run internal QA, get sign-off from the CFO, and submit through the EERS portal.

She makes it. Barely. But the numbers were rushed, the QA was superficial, and nobody's confident the figures would survive a CER compliance review. The Clean Energy Regulator can audit NGER reports for up to five years after submission. A rushed October report becomes a liability that sits on the books until 2031.

This isn't a skills problem. It's a workflow problem. When compliance deadlines and data dependencies live in one person's head, every absence, every competing priority, every slow utility retailer becomes a systemic risk.

Working backwards from deadlines changes everything

The fix is embarrassingly simple in concept but almost nobody does it. You work backwards from each deadline to map when data collection must start, when validation must be complete, and when sign-off must happen. Then you put all of those trigger dates in a shared system that alerts the right people at the right time.

For the 31 October NGER deadline, working backwards looks something like this. Submission and final QA needs the last two weeks of October. CFO sign-off needs a week, so the draft report must be ready by mid-October. Data reconciliation and emissions calculations take two weeks with a clean dataset. That means all activity data must be collected and validated by late September. Utility bill requests to retailers need three to four weeks of lead time. So the first data requests need to go out by late August at the latest.

Late August. Not October. Not September. August.

For AASB S2, the maths is even more aggressive. A disclosing entity with a 30 June year-end must lodge by 30 September. That's only three months. And unlike NGER, which is a standalone submission to the Clean Energy Regulator, AASB S2 sits inside your annual report alongside your financial statements. Your auditor needs time with it. Your board needs to approve it. Your legal team needs to review the transition plan disclosures and scenario analysis.

Realistically, the sustainability report needs to be in near-final form by early September. Which means emissions data must be locked by mid-August. Which means data collection for the full financial year needs to wrap up in July, within weeks of the year ending.

We're not sure most Group 2 entities have mapped this out yet. Many are still focused on understanding what AASB S2 requires, let alone building a backwards timeline to actually deliver it on time.

The data overlap nobody exploits

Here's something that should make this easier but usually makes it worse. About 80% of the underlying data is common across all these frameworks.

Your Scope 1 emissions from natural gas combustion are the same number whether you're putting it in an NGER report, an AASB S2 disclosure, a CDP questionnaire, or a Climate Active submission. The activity data (gigajoules consumed), the emission factor (from the NGA Factors workbook), and the calculation method don't change between frameworks.

What changes is the presentation. NGER wants facility-level data broken out by greenhouse gas type using AR5 Global Warming Potentials. AASB S2 requires AR6 GWPs from the most recent IPCC assessment. CDP wants it sliced by Scope and business activity. Climate Active needs it reconciled against your offsets.

But most companies don't have a single source of truth for this data. They have the NGER spreadsheet over here, the AASB S2 working papers over there, the CDP response in a separate portal, and the Climate Active submission in yet another. When one number changes, the others don't update. By October, the Scope 2 figure in your NGER report has drifted from the one in your CDP response, and your auditor is asking questions you can't easily answer.

A proper multi-framework reporting setup calculates once and formats many times. Same data, same calculation engine, different output templates. That's how you keep six frameworks consistent without maintaining six separate datasets.

What a real compliance calendar looks like

We built compliance calendar functionality into Carbonly because we watched this problem repeat across every company we talked to during our years in enterprise data at mining and energy companies. The pattern is always the same. Competent people. Bad systems. Missed triggers.

A functional compliance calendar isn't a list of dates. It's a dependency-aware workflow that connects deadlines to data readiness. It should tell you three things at any point in time.

First, what's due in the next 90 days and what's the completion status. Not just "NGER due 31 October" but "NGER 78% data complete, 3 facilities missing June electricity bills, estimated gap-close date 15 September."

Second, what data collection actions need to happen this week to keep every framework on track. If a utility bill request takes three weeks and your NGER deadline is ten weeks away, the calendar should flag that request now, not in six weeks when it's too late.

Third, who needs to be notified. The CFO doesn't need weekly updates on data collection status. But they do need to know, four weeks before the AASB S2 lodgement deadline, that the sustainability report draft is ready for review. The facility manager needs to know that their site's energy data hasn't been submitted yet and the NGER deadline is eight weeks away.

This isn't complicated technology. But it does require that all your emissions data, across all frameworks, lives in one system with visibility into what's complete and what's missing. If your data is spread across five spreadsheets and three email threads, no calendar tool can tell you whether you're on track.

The hidden risk: framework interactions

There's a subtlety that catches people out. These frameworks don't just share data. They reference each other.

AASB S2 paragraph 29(a) requires disclosure of Scope 1 and Scope 2 greenhouse gas emissions. If you're also an NGER reporter, ASIC expects those numbers to be consistent with what you reported to the Clean Energy Regulator. Different GWP values (AR5 for NGER, AR6 for AASB S2) mean the numbers won't be identical, but they need to be reconcilable. An auditor who sees your AASB S2 Scope 1 figure diverge from your NGER figure by more than the GWP adjustment can explain will ask uncomfortable questions.

Safeguard Mechanism compliance depends directly on your NGER data. Your reported emissions determine your exceedance position. If your NGER figures are wrong, your Safeguard position is wrong, which means you might surrender too many or too few ACCUs.

CDP asks whether you report under any mandatory schemes and what figures you reported. If your CDP response says your Scope 1 emissions are 45,000 tonnes but your NGER report says 47,200 tonnes, that inconsistency is visible to any investor who checks both.

Climate Active requires you to demonstrate carbon neutrality against your total emissions footprint. If your footprint calculation uses different activity data than your NGER report, you've got a consistency problem that the ACCC could characterise as misleading.

All of these interactions mean that getting one framework wrong can cascade into problems across all the others. And the only way to catch these inconsistencies before they become audit findings is to manage all frameworks from the same data, on the same timeline, with the same review process.

Start with what's due next

If you don't have a compliance calendar today, don't try to build the perfect system before your next deadline. Start with two things.

Map every carbon reporting obligation your company has, with exact due dates, and put them somewhere every relevant person can see. Not a personal calendar. A shared system. Include the data collection trigger dates, not just the submission dates. For most frameworks, the trigger date is 8 to 12 weeks before the deadline.

Then look at your data. Right now. How much of your FY2025-26 activity data is already collected and validated? If you're reading this in April and your NGER deadline is October, you should have July through March data locked down. If you don't, that's your first action item.

If you want to see how Carbonly handles multi-framework compliance tracking with automated deadline management and data gap alerts, reach out to us at hello@carbonly.ai. Per-project pricing, no lock-in contracts, and we'll show you exactly where your data gaps are before you commit to anything.

Related reading: