When Your Tier 1 Asks for Your Project Emissions: A...

The email lands at 4pm on a Friday. It is from the head contractor's sustainability coordinator. There is a spreadsheet attached. The deadline is 14 days. The columns ask for diesel litres by month, by project, by plant item. Electricity kWh on site offices and crib huts. Concrete cubic metres with strength class. Asphalt tonnes, mix design, supplier. Transport kilometres for materials in and spoil out. Plant hire diesel, separated from your own fleet. EPDs where you have them.

You forward it to the project engineer, who forwards it to the site supervisor, who tells you he has a shoebox of fuel dockets in the ute and the refueller statements are on the office accountant's desk.

This is now a normal week for HSEQ managers, environmental advisors and operations managers at small and mid-sized Australian civil and trade contractors. The Tier 1s, Laing O'Rourke, John Holland, CPB, Acciona, Fulton Hogan, BMD, Bielby, Lendlease, have been pulled into mandatory climate reporting under AASB S2, and they are pushing the data request down the supply chain. Major Road Projects Victoria, TfNSW, Cross River Rail and Snowy 2.0 all flow these requirements through their head contractors and into your subcontract.

We have watched this go badly enough times to want to write down how it should actually work.

What the head contractor is genuinely asking for

The spreadsheet column headers can be misleading. What the Tier 1 actually needs, to satisfy their AASB S2 Scope 3 Category 1 disclosure or their Infrastructure Sustainability Council (ISCA) IS rating, is the underlying physical activity. Not your invoice total. Not your spend. Litres. Kilowatt-hours. Cubic metres. Tonnes. Kilometres. Hours.

The reason matters. Spend-based factors carry error bands of 30 percent or worse. A Tier 1 reporting under AASB S2 cannot defend a Scope 3 number built on spend-based factors when the head contractor's auditor walks in. That is why the request specifies quantities, and why it gets bounced back when a subbie returns a single number that says "diesel spend for the project: $487,000".

A typical request, for one project, over one quarter, looks like this:

Scope 1: diesel litres for owned plant and fleet, by month, by item where possible. Refrigerant top-ups on site coolrooms. AdBlue consumption.
Scope 2: electricity kWh for site sheds, crib huts, lighting towers if mains-connected. State of supply, because the NGA Factors 2025 workbook gives VIC 0.78 kg CO2-e/kWh and TAS 0.20.
Scope 3: concrete cubic metres by strength class, with supplier. Asphalt tonnes by mix design. Steel reinforcement tonnes. Plant hire diesel by hour. Subcontractor sub-subcontractor data where you sub-let. Transport kilometres for major material movements.

Climate Active certification used to be the umbrella some contractors aimed for. We are not recommending it now. The Federal Government's review left Climate Active without standing as a defensible standalone disclosure for AASB S2 purposes. The Tier 1 wants raw activity data, not a Climate Active certificate.

Why most subbies hand back something that gets bounced

The pattern we see, and we see it almost every week, runs like this. The HSEQ manager has 14 days. They open the spreadsheet, build a tab per project, and start emailing site supervisors. The supervisors send back a mix of: fuel docket photos on WhatsApp, a Word doc someone typed from memory, an Excel sheet that has plant hours but not litres, and a comment that says "concrete invoices are with accounts, ask Karen".

The HSEQ manager spends six days reconciling, three days chasing the half that did not respond, and submits on day 13. The head contractor's sustainability team reviews the file and bounces it back because:

Diesel litres are at the entity level, not the project level.
Concrete is shown as a single line "concrete: $312,000" instead of m³ by strength.
Plant hire is missing entirely because the subbie thought plant hire was the hire company's problem.
There is no source document trail. The Tier 1's auditor needs to see the underlying docket or invoice for any line above their materiality threshold.

You then have another 5 days, in the middle of a job, to fix it. The site supervisors are now actively avoiding your calls. We have seen this cycle eat 80 to 120 hours of an HSEQ manager's quarter, on top of the actual safety and environment work.

The problem is not the people. The problem is that the data collection is happening after the fact, every time, instead of being captured the moment the docket arrives.

The workflow change that actually fixes it

The shift is small to describe and large in practice. Stop trying to collect the data when the head contractor asks. Start capturing it the moment the supplier emails the docket. The data already exists at that moment, in a PDF or JPG attachment, sitting in someone's inbox.

The mechanic that makes this work is a project-specific email address. Every project you set up gets its own ingestion address. The refueller sends their weekly statement to that address. The concrete supplier sends the delivery dockets to it. The plant hire company sends their off-hire reports to it. The site supervisor forwards anything they get on their phone to it. The asphalt supplier CCs it on every load ticket. We cover the broader mechanics in email-based carbon data ingestion, but the project-specific part is what makes it work for subcontractors juggling four or five jobs.

Each document that arrives gets read by the document AI engine, turned into a typed record (date, supplier, quantity, unit, material), matched to an emission factor through five-tier material matching, and tagged to the project it arrived under. PDF, CSV, Excel, Word, scanned image, all of it. The source document stays attached to the record for the 7-year audit trail the head contractor's auditor will want to see.

By the time the Tier 1's request lands, the data is already there. The HSEQ manager's job becomes filtering the project ledger for the requested date range and exporting it, rather than rebuilding it from scratch. We have written about this transformation at length for contractors with 200+ project sites, and it works at the small end too.

The supplier portal pattern for your own subbies

If you are a Tier 2 or Tier 3 contractor, you have your own sub-subcontractors. Plant hire companies, traffic management, line marking, the rock guys. They are sitting in the position you are sitting in with the Tier 1. They get asked, they panic, they email you a spreadsheet that you cannot trust.

The pattern that works here is a supplier portal. Your sub-subcontractors get a login, a separate role from your internal team, and they submit their data through a form or by emailing dockets to a project address. They cannot see your internal ledger or your other suppliers' submissions. The data they submit gets reviewed by your project team, then accepted into your ledger. We use a six-role permission model (Owner, Admin, Manager, Contributor, Auditor, Viewer, plus a separate Supplier role) precisely because subcontractor data needs a different trust level from your own field data. More on this in our scope 3 supplier engagement guide.

This matters more than it sounds. The reason subbies hate the head contractor's request is that they have nowhere to put the data their own subcontractors send them. So they paste it into the same spreadsheet, lose track of which line came from where, and the audit trail breaks. A supplier portal with a separate role keeps your sub-subcontractor data ringfenced and traceable, without ever giving them visibility into your own commercial information.

The end-of-month docket reconciliation that actually finishes

Anyone who has done it knows the rhythm. The refueller statement arrives on the 5th. You match it against the delivery dockets the site supervisor has, hopefully, sent through. The plant hire off-hire report arrives on the 8th and has hours that do not quite line up with what the site daily diaries said. The concrete statement comes through with quantities but the strength class is on the individual delivery dockets, which are in the site office.

When the dockets and statements are arriving at the project email address as they are issued, this reconciliation stops being a month-end fire drill. The refueller statement total can be cross-checked against the sum of individual dockets already in the ledger. Anomalies, like a docket that says 450 L when the truck only holds 380, get flagged automatically and surfaced to whoever is on review. That is what we mean by anomaly detection on emissions data; it is not magic, it is comparing today's record against the pattern of the last 90 days.

The other quiet win: when something is missing, you know about it in real time. If the asphalt supplier has not CC'd the project address for two weeks, that is a question you can ask now, not a hole you discover in week 13 of the quarter.

What you keep after the data goes upstream

This is the part most subcontractors do not think about until later, and then wish they had.

Once you have built a project ledger that captures fuel, electricity, materials and plant hour data at the line level, with source documents attached, you have not built a one-off response to a Tier 1 request. You have built the foundation of:

Your own NGER inventory, if you cross the corporate threshold of 50 ktCO2-e or 200 TJ of energy. Mid-sized civil contractors with a sizeable plant fleet are closer to this than they think. Our NGER thresholds 2026 piece walks the maths.
Your AASB S2 Group 3 disclosure, which lands for financial years starting on or after 1 July 2027. Group 3 includes any company meeting two of: 100+ employees, $25M+ revenue, $12.5M+ assets. A lot of subcontractors who do not think of themselves as "big" are in Group 3. We cover the timeline in our ASRS Group 3 reporting requirements and the 12-month preparation guide.
The next head contractor request, which will be easier than this one because the ledger already exists for the next project.
Tender responses where the Tier 1 asks for your carbon credentials as part of pre-qualification. Increasingly common on MRPV, TfNSW and Snowy 2.0 supply chain work.

The data does not disappear when the upstream request is filed. The ledger keeps building. We have written more on what this looks like from the head contractor's perspective and from the subcontractor scope 3 view, and they are two sides of the same problem.

Talking to your data without exporting it

One thing we get asked about a lot: can the HSEQ manager just ask a question and get an answer, rather than building a pivot table? Yes. The project ledger is queryable in natural language through Carbonly Co-Pilot. "How much diesel did we burn on the Kingsford Smith Drive job last quarter?" returns the number with the underlying records linked. "Which concrete supplier had the highest GWP per cubic metre on Project X?" returns the breakdown.

For teams that already live in ChatGPT or Claude, the same project ledger is reachable from those assistants directly, so you can ask your usual AI tool about your project emissions without copying data out. Useful when the project engineer wants a quick number for a progress claim meeting and does not want to log into another system.

The AR5/AR6 GWP toggle is worth flagging too. NGER still requires AR5 GWP values for methane and other gases. AASB S2 wants AR6. The ledger holds both, switchable at the report level, so you can give the head contractor what their auditor needs without recalculating. Background in our AR5 vs AR6 GWP piece.

What we still do not solve

A few things to be honest about, because nobody fixes everything.

Plant hire diesel where the hire company refuses to break out fuel by hour remains hard. The best we can do is estimate from plant hours and a published consumption rate, and flag the estimate as lower-confidence. If your hire company will not give you the data, no software changes that, although we have seen the request itself prompt them to start.

Concrete EPDs are still patchy. The big suppliers have them, the smaller regional batchers often do not. For now you get product-specific data where it exists and supplier-average factors where it does not.

Subcontractor data quality varies wildly. The supplier portal helps because it forces structure on what they submit, but a sub-subbie who genuinely has not been tracking their fuel will guess, and a guess is a guess regardless of what system catches it.

A note on consultants

A lot of small contractors get their first Tier 1 request and reach for a sustainability consultant. That is sensible. A good consultant will set up your project chart of accounts properly, walk you through the head contractor's specific request language, and review the first quarter's data before it goes upstream. We do not see consultants as competitors; Carbonly is designed to sit as the data layer underneath the advice a consultant gives their clients, so the same platform serves both the contractor and the practice supporting them. Per-project pricing means a contractor with one Tier 1 project does not pay enterprise rates.

Where to start, this week

Pick one project. The current one with the loudest Tier 1 request, or the next one starting.

Set up a project-specific email address for it. Tell the refueller, the concrete supplier, the plant hire company and the site supervisors to send dockets and statements to that address from now on, in addition to wherever they already send them. Sync the project's OneDrive or SharePoint folder if the head contractor is dropping files there. Forward the next 30 days of supplier emails to the address so the ledger has a starting point.

Then wait, and watch the ledger fill. By the time the next data request lands, the work is mostly already done.

Reach out at hello@carbonly.ai if you want a hand setting up a single project for an upcoming Tier 1 submission. We have seen most variations of this request by now, and the setup for one project is not a big lift.