A Day in the Life of an Australian Sustainability...

Picture the ASIC surveillance letter. It goes to the entity, but the questions in it land on the Sustainability Manager, not the CFO, the Chair or the assurance partner, because they signed off the Basis of Preparation, chose the emission factors, approved the supplier data, and told the CFO the numbers were ready for the audit committee.

ASRS Group 2 went live on 1 July 2026. NGER reporters that lodge financial reports under Chapter 2M were pulled in through the registration pathway. Every entity clearing two of three thresholds ($200M+ revenue, $500M+ gross assets, 250+ employees) is now in. Q1 of the first reporting year is closed. Q2 is being finalised. Q3 is the middle of the fight, which is why we are picking Q3 for this walk-through.

What follows is a realistic Q3 Wednesday for the Sustainability Manager at a hypothetical mid-market Australian construction and infrastructure business. Around 900 people, twelve active projects, NGER Group A facility reporter, subject to AASB S2 in year one, ASSA 5010 limited assurance on Scope 1 and 2. Around 40 recurring suppliers issue emission-relevant documents every month: Ampol, BP Australia, AGL, Origin, Boral, Holcim, InfraBuild, Cleanaway, Veolia, Toll and a long tail.

7:30 AM. Overnight extraction queue check

The Sustainability Manager opens the extraction queue from their phone before leaving the house. Overnight, the AI Document Engine has processed 63 documents that landed in the per-project ingestion inbox between 6 PM and 6 AM. Every project has its own dedicated email address, plus a folder synced from OneDrive that site engineers use when the internet is patchy on a highway job.

Of the 63 documents, 58 matched with high confidence. Five sit in the review queue as low-confidence matches. The Sustainability Manager works through that five-item list.

The overnight anomaly checks have flagged a diesel volume that jumped 34% week-on-week for one project, and the Data Health Agent has flagged a supplier record with missing fields. Each flag links back to the source document. The Sustainability Manager triages: the diesel jump is real (a new civil crew mobilised on-site), and the incomplete record belongs to a new subcontractor no one told them about. Ten minutes of work. In a spreadsheet workflow, that new subcontractor might not have surfaced until the auditor asked.

8:15 AM. Site manager forwards yesterday's Ampol fuel dockets from a truck cab

At 8:14 AM the phone buzzes. A site manager on a Newcastle highway upgrade has forwarded 22 photos of Ampol fuel dockets from yesterday's shift. Some are creased. Two have coffee on them. One is a photo of a photo. All are addressed to the project's dedicated ingestion inbox, so they land straight in the right project workspace.

The dockets are read for litres, fuel grade, docket number, date and site code. Twenty of the 22 clear the confidence threshold. Two are legible enough to extract but the docket number is partially obscured, so they go to review. The manager confirms the number from the sequence of the other 20. A few minutes of review for a stack that would have taken an afternoon to key in. One stack, one shift, one project. That is the everyday shape of construction data entry, and it repeats across every site on the books.

9:00 AM. The electricity invoice with a new layout

In this scenario, the company's electricity retailer has changed the layout of its commercial invoice. Four fields have moved: the meter number is now in a header block instead of a footer, the daily average kWh is a new field, the emission factor reference has disappeared, and the billing period date format has switched from DD/MM/YYYY to DD Mon YYYY.

The new invoices go through extraction like any other. Values that come back low-confidence go to the review queue, and the manager checks those against the PDFs. When the manager corrects a match, the line text is saved as an alias for the organisation, so later documents with the same wording match through it (how that works).

In year zero this would have been a spreadsheet rebuild. Someone rewriting a VLOOKUP against the new column position. Someone else discovering the change three weeks later when their pivot table returned zeros.

10:30 AM. CFO asks "how are we tracking against last year"

Slack notification. The CFO wants a comparison of Q1 FY26 vs Q1 FY25 emissions by scope, by project, in the next 40 minutes, for a private conversation with the Chair. In the old workflow this was a two-day exercise involving a re-baseline from a spreadsheet extract, a manual grid factor lookup for the previous financial year, and a lot of prayer that the pivot tables would agree with the source data.

The Sustainability Manager pulls Q1 FY26 against Q1 FY25 from the ledger and works through a variance analysis. Within the hour they have a decomposition: total emissions up 9.2%. Of that, 6.1 percentage points is activity growth (four new projects mobilised). Two points is a factor version change (NGA 2025 factors are used for FY26; NGA 2024 was used for FY25, and Victoria's grid factor rose from 0.77 to 0.78 kg CO2-e/kWh). One point is a category mix shift toward higher-intensity diesel plant. The remaining 0.1 points is boundary consolidation from a small acquisition.

Factor versioning matters here. Because every FY25 record stores the NGA 2024 factor version it was calculated under, the year-on-year comparison is like-for-like at the activity layer and separately quantified at the factor layer. The Chair gets a chart, three bullet points and a source-document link.

11:30 AM. A concrete supplier's docket layout has changed

Three concrete dockets from the North Sydney project have come back as low-confidence matches. In this scenario the supplier has moved the delivery ticket number to a new footer position and added a QR code that partially overlaps the volume field. Two of the three dockets have partial volume reads.

The manager confirms the m³ values against the site diary and records them, and notes the supplier for a conversation through the supplier portal if the new layout keeps producing unclear reads. A supplier issuing that many dockets is worth a conversation.

12:30 PM. Working lunch: the waste invoice does not add up

The waste contractor's invoice for the Melbourne project shows a tonnage figure of 47.6 tonnes and a bin-lift count of 84, which looks high against the usual pattern for that site, so the manager pulls it for a closer look.

The Sustainability Manager pulls up the invoice source document. There is a line item they missed on the first pass: a one-off skip bin hire that inflated the tonnage without a corresponding lift count. The manager splits the record (skip tonnage carried on a different waste category). The typed audit event captures who changed the record and when, retained for seven years under Carbonly's internal policy.

1:30 PM. Auditor sample request: five records to walk-through

The ASSA 5010 assurance provider is midway through their limited assurance procedures. They email five records they want to walk-through end-to-end for Scope 1 fuel and Scope 2 electricity: source document, extraction, factor version, calculation rule, approver, and any restatement history.

The manager produces the evidence pack for the five sample records: the source documents, the verbatim line text, the factor version used (NGA 2025 for FY26), and the typed audit events showing who approved and changed each record. The manager attaches it to the auditor's ticket and moves on. This is one of three questions an assurance provider asks that a spreadsheet cannot answer.

In a spreadsheet workflow, "walk me through five records" can be a five-person full-day exercise. Sometimes three days.

3:00 PM. Scope 3 supplier engagement: 12 of 20 have responded

Twelve of the 20 top-spend suppliers have responded to the Scope 3 data request that went out via the Supplier Portal three weeks ago. The Data Chase Agent has been sending scheduled reminders. Of the 12 responses, nine came in through the portal directly (structured, immediately usable), two came in as PDFs uploaded to the portal, and one came in as an email attachment routed via the per-project ingestion address.

The eight suppliers who have not responded get a personal follow-up. Not a system-generated one. Category 1 purchased goods is where limited assurance is heading in year two under ASSA 5010, so this is the right hour to invest.

4:00 PM. Board pack question: why did Q2 refrigerant emissions spike

The board pack goes out on Friday. The Chair has asked for a note on why Q2 refrigerant emissions were 41% higher than Q1. The manager decomposes it from the ledger: two large split-system replacements at the head office fit-out released roughly 4.2 kg of R-410A (GWP 1924 under AR5, GWP 2256 under AR6). Under AR5 that is around 8.1 tonnes CO2-e. Under AR6 it is around 9.5 tonnes.

Because NGER uses AR5 for the FY26 report but AASB S2 disclosure applies AR6, both numbers need to appear in the board pack. Carbonly records the AR5 figure. The manager calculates the AR6 figure separately, links the HVAC contractor's invoice as the source, and cites both GWP values in the board pack draft.

5:15 PM. Evening handover to the on-call reviewer

A part-time reviewer takes overnight and weekend document review coverage. The Sustainability Manager writes a two-line handover note in the platform. The on-call reviewer picks up the records still sitting in the review queue across all 12 projects. The manager closes the laptop at 5:30 PM.

What the manager did NOT have to do

The list of things that never entered the Sustainability Manager's day is longer than the list of things that did. They did not look up NGA Factor editions (each record stores its factor version). They did not convert litres to kilolitres or kWh to MJ (unit normalisation did that). They did not maintain a per-supplier column mapping spreadsheet. They did not chase source documents through email folders (every record links back to its source document, retained for seven years). They did not rebuild a VLOOKUP after the retailer's layout change.

None of this is glamorous. All of it is the difference between a Sustainability Manager who can look the auditor in the eye and one who cannot.

How this day looked before the platform: the 12-hour version

Before the AI Document Engine, this Wednesday plays out very differently. 7:30 AM is triage of a shared inbox with 63 unread emails. 8:15 AM is hand-keying 22 Ampol dockets into Excel. 9:00 AM is a call from finance because their pivot table zeroed out on the electricity invoices after the layout change.

The CFO comparison slips to Friday and uses FY25 factors for both years because rebasing is too painful. The waste invoice anomaly is discovered by the auditor in October. The audit sample request takes three days. The refrigerant question quotes the wrong GWP. The day ends at 8:30 PM. Turning that manual day into a supervised one is the actual return on this category of software.

FAQ

What does a Sustainability Manager do in year one of AASB S2?

In year one of AASB S2, the Sustainability Manager owns operational execution of the ASRS Group 2 program: data collection from every project and supplier, factor version pinning, Scope 1 and 2 calculation under limited assurance, Scope 3 engagement across top-spend suppliers, the Basis of Preparation document, response to ASSA 5010 auditor sample requests, variance explanation for the board, and reconciliation between the NGER submission (AR5 GWPs) and the AASB S2 disclosure (AR6 GWPs).

How much time does a Sustainability Manager spend on data entry?

A manual spreadsheet workflow at a mid-market construction reporter can consume most of a Sustainability Manager's week during peak reporting months. Most of that time goes on keying supplier documents one at a time, because that is how the quantities get out of the paperwork and into the ledger. With an AI Document Engine handling extraction and factor matching, the workload shifts toward reviewing flagged items.

Who is responsible for AASB S2 sign-off in an ASRS Group 2 entity?

Directors are legally responsible for the sustainability report under the Corporations Act, and s 180 duties of care and diligence apply. The CFO typically signs the Basis of Preparation. The Sustainability Manager owns the underlying data, factor choices and methodology. The ASSA 5010 assurance provider expresses an opinion (limited assurance in year one for Scope 1 and 2). ASIC surveils the disclosure once it lands.

What software does a Sustainability Manager actually use during the day?

On a well-instrumented day the Sustainability Manager works from one carbon accounting platform: emissions ledger, extraction, factor versioning, evidence pack and Supplier Portal. It is fed by per-project email ingestion and OneDrive or SharePoint folder sync. The Sustainability Manager should not be running a spreadsheet as their primary system of record in year one of AASB S2. If they are, the assurance provider will find it.

How does the Sustainability Manager work with the assurance provider?

The Sustainability Manager is the primary counterparty during ASSA 5010 fieldwork. Practical hygiene: agree the sample selection method up front, publish the Basis of Preparation before fieldwork, link every source document to its ledger record, record the factor version on every calculation, and keep an evidence pack ready so "walk me through five records" is a quick answer, not a three-day scramble.

What this costs

Carbonly is priced per project with a $100/month workspace minimum. Want the walk-through against a real Boral docket, AGL invoice and Ampol fuel receipt from your own portfolio? Email hello@carbonly.ai.

A Day in the Life of an Australian Sustainability Manager in Year One of AASB S2