The 400-Hour NGER Report: Where the Time Actually Goes

Last October, a sustainability manager at a construction company told us she'd blocked out six weeks in her calendar just for NGER reporting. Six full weeks. She still didn't make it without weekend work.

That tracks with what we hear across NGER-reporting companies every year. The 31 October deadline consumes entire teams for months. But when you ask people how many hours it actually takes, you get vague answers. "A lot." "Months." "Too many." Nobody sits down and adds it up, probably because the answer is depressing.

So we did. Based on what practitioners - sustainability managers, environmental consultants, operations teams - consistently describe across mid-size companies with 5 to 10 NGER-registered facilities, the total is roughly 400 hours per reporting year. That's 10 full working weeks. For a sustainability manager earning $130,000 to $150,000 loaded (salary plus super plus overheads), those 400 hours represent around $50,000 in labour cost. And that's before you account for the opportunity cost of what that person isn't doing - like actually reducing emissions.

Here's where those hours go. Not in theory. In practice.

Data collection: ~200 hours

Half the entire effort. Gone before anyone touches an emission factor.

Data collection means chasing utility bills from property managers who respond on their own schedule. It means downloading fuel card statements from three different portal logins, then reconciling them against delivery dockets that may or may not match. It means emailing site managers who don't respond, then following up, then following up again. It means requesting missing invoices from suppliers who've changed their billing format since last year.

For a construction company with 8 active sites, a fleet of 200+ vehicles, and a mix of electricity, gas, diesel, and water accounts, you're looking at 800 to 1,200 documents per reporting year. Each one needs to be located, downloaded or scanned, filed, and confirmed as the right period for the right facility.

The documents arrive as PDFs, scanned images, Excel exports, email attachments, and occasionally paper. Some come from a shared drive that three people have access to. Others are in someone's email inbox. A few are still in a filing cabinet at a regional office. And every year, at least a handful simply don't exist - the bill was never received, the meter wasn't read, the account was under the wrong entity name.

This is the part that burns people out. It's not intellectually difficult. It's just relentless.

Data processing: ~60 hours

Once you have the documents, you need to get the numbers out of them and into a format you can calculate from. That means opening each PDF, finding the consumption figure, the billing period, the meter or account number, and typing it into a spreadsheet. Or copying it. Or squinting at a scanned image where the font is 8-point and slightly crooked.

Then comes unit conversion. Gas bills arrive in megajoules or cubic metres. Electricity in kilowatt-hours. Diesel in litres. But your calculation workbook might need gigajoules, or tonnes, or kilowatt-hours everywhere. So you convert. And you double-check the conversion, because a decimal point in the wrong place turns 1,400 GJ into 14,000 GJ, and nobody catches that until the Clean Energy Regulator asks why your facility emissions tripled.

After that, you match each line to an emission factor. NGA Factors are updated annually by DCCEEW, and they differ by state - Victoria's grid factor is 0.78 kg CO2-e/kWh while Tasmania's is 0.20. You need the right factor for the right fuel type, the right state, and the right scope. Getting this wrong doesn't just produce a bad number. Under the NGER Act, it can trigger a compliance action. The ANAO found that 72% of 545 NGER reports it examined contained errors, with 17% including significant ones. Many of those errors started right here, in data processing.

Consultants who prepare NGER reports for clients face exactly the same bottleneck. The documents still need to be collected, still need to be processed, and the hours still get billed - often at $180 to $350 per hour depending on the firm. The cost difference between consultant-led and software-assisted reporting is worth understanding before you lock into either approach.

Quality assurance: ~50 hours

You've got your data in the spreadsheet. Now you need to trust it.

Quality assurance means checking for duplicates - it's surprisingly common for the same bill to be entered twice when multiple people contribute to the same workbook. It means comparing this year's figures to last year, facility by facility, and investigating anything that's moved more than 10 to 15 percent. That investigation is its own time sink: is the increase real (higher production) or an error (wrong meter, wrong period, double-counted)?

It means reconciling fuel card data against purchase orders and delivery dockets. Fuel cards capture litres at the pump, but delivery dockets capture bulk fuel deliveries to a site tank. These are different data sources for the same thing, and they rarely match perfectly. The gap between them is where errors hide.

For companies with fleet vehicles - and most construction and mining companies have hundreds - fuel reconciliation alone can eat 15 to 20 hours. That's before you look at electricity, gas, or water.

This phase is where the ANAO error statistics come from. Not from bad maths. From bad data entering the system unchecked.

Calculation: ~30 hours

This is what people think NGER reporting is. Applying emission factors, calculating per-gas breakdowns (CO2, CH4, N2O), converting energy content, and aggregating across facilities.

It's important work. The NGA Factors workbook has specific factors for every fuel type, combustion method, and state grid. Scope 1 calculations require you to break emissions into individual greenhouse gases and apply the correct global warming potentials - NGER uses AR5 values, which is a technical difference from AASB S2 that requires AR6. Scope 2 requires the right state-based grid factor and a decision about location-based versus market-based methodology.

But here's the thing: calculation is only 30 of the 400 hours. Less than 8% of the total effort. The actual carbon accounting - the part that requires domain expertise - is a small fraction of what consumes reporting season. Most of the time goes to finding documents and typing numbers.

Report generation: ~30 hours

Once the calculations are done, you need to produce the actual NGER report. That means populating the report template through the Clean Energy Regulator's EERS portal (which replaced the OSCAR system), cross-checking that facility-level totals aggregate correctly to the corporate group level, and generating supporting schedules.

For companies that also report under the Safeguard Mechanism, there's an additional layer - you need to reconcile your reported emissions against your baseline, and if you're above it, you need ACCUs or Safeguard Mechanism Credits to cover the excess. Getting the numbers wrong here has direct financial consequences: $330 per tonne above baseline plus $33,000 per day while in excess.

Formatting doesn't sound like it should take 30 hours. But when you're pulling numbers from multiple worksheets, checking that Scope 1 plus Scope 2 match what you're submitting, making sure facility boundaries are consistent with prior years, and generating the energy production and consumption schedules - it adds up fast.

Review and validation: ~30 hours

The report exists. Now it needs to survive scrutiny.

Internal review typically involves the CFO or finance director, the operations team (who need to confirm the activity data reflects reality), and sometimes legal. Each reviewer asks questions. Each question triggers a check. Each check occasionally reveals a number that doesn't look right, which sends you back to quality assurance.

If the company has engaged an external auditor for voluntary assurance - and the CER strongly encourages it - the auditor will request source documents for a sample of data points. They'll want to trace a specific electricity figure from the NGER submission back through the calculation workbook, back to the actual utility bill. If you can't produce that chain of evidence, you've got a problem. The CER's compliance priorities for 2025-26 explicitly flag data traceability as a focus area.

Sign-off itself is straightforward. Getting to the point where everyone is comfortable signing off is not.

The uncomfortable total

Add it up:

Phase	Hours	% of Total
Data collection	~200	50%
Data processing	~60	15%
Quality assurance	~50	12.5%
Calculation	~30	7.5%
Report generation	~30	7.5%
Review and validation	~30	7.5%
Total	~400	100%

Two hundred and sixty of those 400 hours - data collection plus data processing - are document handling problems. Not carbon accounting problems. They require no emissions expertise. They require finding a PDF, reading a PDF, and typing what the PDF says into a spreadsheet.

That's 65% of the total NGER reporting effort spent on work that a well-built system should handle automatically.

And then AASB S2 makes it worse

Here's what keeps us up at night. Everything above is just NGER. AASB S2 mandatory climate disclosures are rolling out in parallel, with Group 2 entities - which includes all NGER-registrable corporations - reporting from financial years starting 1 July 2026.

AASB S2 demands everything NGER demands, plus Scope 3 emissions (from your second reporting period), plus climate scenario analysis, plus transition plans, plus governance disclosures. The Treasury's Policy Impact Analysis estimated total compliance costs of $1.0 to $1.3 million per entity per year during transition.

So that 400-hour NGER report? It's now the foundation for a much larger disclosure obligation. And if your NGER data is unreliable - built on manually transcribed bills with no audit trail - then your AASB S2 disclosure inherits every error and every gap. The penalties for AASB S2 non-compliance go up to $15 million or 10% of annual turnover. Directors are personally liable.

The 400-hour NGER report isn't just expensive on its own. It's the floor, not the ceiling.

What actually shrinks the hours

We're not going to pretend this goes to zero. It doesn't. But the 400-hour breakdown makes clear where automation hits hardest and where humans still matter.

The 260 hours in data collection and processing are almost entirely a document handling problem. If a system can pull documents from email inboxes and shared drives, read them in any format - PDF, scanned image, Excel, CSV - extract the right numbers (consumption, period, meter ID, account number), and match materials to emission factors automatically, those 260 hours collapse. Not to zero, because edge cases exist. But to 30 to 40 hours of exception handling: documents the system flags as uncertain, accounts that don't match a known facility, new suppliers with unfamiliar invoice formats.

Quality assurance drops from 50 hours to around 10 when anomaly detection runs continuously instead of relying on a human to eyeball a spreadsheet looking for outliers. Year-on-year comparisons, duplicate detection, and reasonableness checks can happen the moment data enters the system, not weeks later during a crunch.

Calculation drops from 30 to roughly 5 when NGA emission factors are mapped automatically - correct state, correct fuel type, correct scope, correct reporting year. No manual lookup. No wrong-column mistakes.

Report generation drops from 30 to about 5 when the submission template auto-populates from verified data, and supporting schedules generate alongside it.

Review drops from 30 to around 15. It doesn't halve because review is inherently a human activity - someone needs to exercise judgement, ask "does this make sense," and take accountability for what gets submitted. But when every data point has a full audit trail showing exactly which document it came from, which factor was applied, and why, the reviewer isn't reconstructing evidence. They're confirming it.

The realistic outcome: 400 hours down to 80 to 100. That's an honest estimate. We're not claiming zero human involvement - that would be irresponsible for a regulatory submission that carries penalties up to $660,000 for failure to report accurately under section 19 of the NGER Act. Humans still review, approve, and investigate the edge cases that any system will flag.

But 300 hours saved is 300 hours a sustainability manager can spend on emissions reduction strategy, Safeguard Mechanism compliance planning, or preparing for the AASB S2 disclosures that are coming whether you're ready or not.

We're not entirely sure what the right split is for every company - a mining operation with 15 facilities and complex fugitive emissions will look different from a property portfolio with 40 buildings and straightforward electricity bills. The 400-hour figure is a mid-range estimate, not a universal constant. But the proportions hold: the majority of time goes to documents, not to accounting.

We built Carbonly specifically around this insight. Not as a calculation engine with a data entry screen bolted on. As a document processing system that happens to understand emissions accounting. Because the bottleneck was never the maths. It was always the paperwork.

That's 400 hours your team will never get back. Unless you stop treating NGER reporting as a manual project and start treating it as a data pipeline.

Related reading: