Carbon Reporting Automation: Tier 1 Case Study

The $15 Million Spreadsheet Problem

When this client's National Sustainability team first contacted us, their carbon reporting process was, to put it bluntly, a mess.

This is not a small operation. As one of Australia's leading Tier 1 infrastructure contractors, a subsidiary of the world's largest construction company (a French multinational with €70+ billion in annual revenue), they deliver major projects across transport, utilities, and defence sectors. Projects worth hundreds of millions of dollars. Projects where sustainability credentials are increasingly a competitive differentiator.

Yet their ESG data collection looked like this: random Excel templates (each project manager had their own version), data arriving via email attachments, SharePoint folders with no consistent structure, and a sustainability team spending weeks each quarter manually consolidating numbers that should have taken hours.

Meanwhile, their internal IT department was investing heavily in enterprise ERP systems. SAP-like platforms with seven-figure implementation costs. But those systems were not solving the sustainability reporting problem. They were designed for financial data, not emissions tracking.

The Real Cost of Chaos Based on research from Deloitte's State of Digital Adoption in Construction, construction professionals waste approximately 10.5 hours weekly searching for information across fragmented systems. For a senior sustainability manager billing at $150/hour, that represents $82,000 annually in lost productivity.

This is the story of how we fixed it with standardised Excel templates, SharePoint, and PowerBI, for a fraction of what an ERP implementation would have cost. And how that solution is still running strong more than three years later. It is also a prime example of how our process automation approach focuses on practical outcomes over technology for technology's sake.

Why This Matters Now: Australia's Mandatory Climate Reporting

Before diving into the solution, it is worth understanding the regulatory pressure that made this project urgent.

From 1 January 2025, Australia's mandatory climate reporting requirements came into effect under the Treasury Laws Amendment (Financial Market Infrastructure and Other Measures) Act 2024. Large companies must now disclose:

• Scope 1 emissions (direct emissions from owned sources)
• Scope 2 emissions (indirect emissions from purchased electricity)
• Scope 3 emissions (value chain emissions, from the second reporting year)
• Climate-related risks and financial impacts

For construction companies, this is particularly challenging. The Australian construction industry contributes approximately 10% of national carbon emissions, with embodied carbon from materials representing a significant portion.

Penalties for non-compliance are severe: up to $15 million or 10% of annual turnover for misleading statements. Directors face personal liability.

For a company of this scale, operating across multiple states with dozens of concurrent projects, accurate carbon reporting is not optional. It is a board-level compliance requirement.

The Before: What Data Chaos Actually Looks Like

When we conducted our initial assessment, here is what we found:

The Template Problem

Project A: Uses "SW_Carbon_Template_v3.xlsx"
Project B: Uses "Emissions_Tracker_v2_Final_FINAL.xlsx"
Project C: Uses a custom spreadsheet built by the project engineer
Project D: Submits PDF reports with no raw data
Project E: Emails monthly totals in the body of an email

Every project had developed its own approach. Some tracked Scope 1 and Scope 2 emissions separately. Others combined them. Some included water usage. Others did not. Units varied between kilograms and tonnes. Date formats were inconsistent.

The Collection Problem

Data submission worked like this:

1. Project teams were asked to submit monthly sustainability data
2. Data arrived via email to various team members
3. Someone saved attachments to SharePoint (sometimes)
4. Quarterly, the sustainability team manually hunted for missing data
5. Chase emails went out. Phone calls were made.
6. Eventually, enough data arrived to compile a report

The Reporting Problem

Quarterly sustainability reports took three to four weeks to produce. The process:

1. Download all available data from SharePoint
2. Manually consolidate into a master spreadsheet
3. Convert units and fix formatting inconsistencies
4. Identify missing data and chase project teams
5. Re-consolidate after late submissions
6. Build PowerPoint slides with charts
7. Present to leadership with caveats about data quality

The sustainability team was spending 80% of their time on data wrangling and 20% on actual sustainability work. That ratio needed to flip.

The Solution: Right-Sized Tools for the Actual Problem

Here is what we did not do: we did not recommend an enterprise ESG platform with a six-figure price tag and an 18-month implementation timeline.

Here is what we did: we built a solution using tools the organisation already had, in a way that matched how project teams actually work.

Component 1: Standardised Excel Templates

We designed a single, standardised Excel template for all project data collection. The key design principles:

Simplicity over comprehensiveness. Project engineers are not sustainability specialists. The template asks for exactly what is needed, nothing more.

Validation built in. Data validation rules prevent common errors. Dropdown lists for categories. Numeric fields that reject text. Date pickers that enforce consistent formatting.

Clear instructions on every tab. No separate user manual to lose. Instructions live in the template itself.

The template captures:

• Scope 1 emissions (diesel, petrol, LPG, natural gas)
• Scope 2 emissions (electricity consumption)
• Water usage
• Environmental incidents
• Project metadata (name, phase, reporting period)

Component 2: SharePoint Folder Structure

We created a template folder structure in SharePoint that gets replicated for each project:

/Sustainability/
    /[Project Name]/
        /Raw Data/
            2024-01_Emissions.xlsx
            2024-02_Emissions.xlsx
            ...
        /Supporting Documents/
            Fuel invoices
            Electricity bills
        /Archive/

When a new project starts, the project coordinator creates a folder using the template. The structure is identical across all projects. The sustainability team knows exactly where to find data for any project.

Component 3: Overnight ETL Process

Here is where the automation happens. Every night at 2 AM:

1. A scheduled task scans all project folders in SharePoint
2. Extracts data from standardised templates
3. Validates against business rules
4. Consolidates into a central data warehouse
5. Calculates emissions using Australian Government NGER factors
6. Logs any errors for morning review

The ETL process handles:

• Unit conversions (litres to CO2-equivalent)
• Missing data flagging
• Duplicate detection
• Historical data preservation

Component 4: PowerBI Dashboard

The PowerBI dashboard provides multiple views of the same underlying data:

Corporate Overview:

• Total emissions by scope (1, 2, and combined)
• Progress against reduction targets
• Month-over-month and year-over-year trends
• Carbon intensity (emissions per dollar of revenue)

Regional Breakdown:

• Emissions by state/region
• Comparison of regional performance
• Regional targets vs actuals

Project Level:

• Individual project emissions
• Project phase analysis
• Fuel type breakdown

Data Quality:

• Missing data by project (highlighted in red)
• Late submissions
• Data completeness percentage

The Missing Data Alert Feature This was a specific request from the sustainability team. The dashboard highlights which projects have not submitted data for the current period. Instead of chasing project teams manually, the missing data is visible to regional managers in their weekly dashboard review. Peer pressure drives compliance far more effectively than email reminders.

Implementation Timeline

Week 1: Discovery and Assessment

• Interviewed sustainability team on current process
• Documented data requirements for regulatory compliance
• Reviewed existing templates and identified inconsistencies
• Mapped data flows and identified gaps

Week 2: Template and SharePoint Design

• Designed standardised Excel template with validation
• Built SharePoint folder structure template
• Created setup documentation
• Piloted with two volunteer projects

Week 3: ETL Build and Testing

• Developed extraction routines for Excel templates
• Built transformation logic including NGER factors
• Set up SQL database for central storage
• Tested with historical data from three projects

Week 4: Dashboard and Training

• Built PowerBI dashboard with all required views
• Connected to central data warehouse
• Trained sustainability team on dashboard use
• Trained regional coordinators on project setup
• Documented handover procedures

Total elapsed time: four weeks. Total implementation cost: significantly less than a single month's license fee for most enterprise ESG platforms.

The Results: Three Years and Counting

Here is what the implementation delivered:

Quantified Improvements

Qualitative Outcomes

Board reporting improved. Leadership now receives accurate, timely sustainability metrics. The quarterly sustainability report is no longer qualified with "data may be incomplete" disclaimers.

Project teams adopted the process. Because we designed the template around how project engineers actually work (minimal effort, clear instructions), adoption was high. The template takes five minutes to complete each month.

The sustainability team does sustainability work. With 75% less time spent on data wrangling, the team focuses on emissions reduction initiatives, regulatory preparation, and sustainability strategy.

Audit readiness. When external auditors review sustainability data, there is a clear audit trail from source documents through to reported figures.

Still Running After 3+ Years

This is the metric that matters most. The solution we built in 2022 is still in daily use. The sustainability team has trained new staff on the process. They have added new projects without our involvement. The PowerBI dashboard has been refined and extended.

That longevity comes from two deliberate design choices:

1. We used tools they already knew. Excel and PowerBI are standard corporate tools. No specialist skills required for maintenance.

2. We documented everything. Support documentation, user manuals, and technical specifications. When questions arise, answers are available.

The Honest Comparison: Simple Tools vs Enterprise ERP

Let us address the elephant in the room. This client's IT department was investing heavily in enterprise systems. Why did we use Excel and PowerBI instead of recommending a proper ESG platform?

When Enterprise ESG Platforms Make Sense

• Organisations with 1,000+ employees across multiple countries
• Complex value chain emissions requiring supplier integration
• Requirements for real-time IoT sensor data
• Need for blockchain-verified carbon credits
• Multiple regulatory frameworks (EU Taxonomy, TCFD, GRI, SASB)

When Right-Sized Tools Make Sense

• Organisations that need compliant reporting without 18-month implementations
• Teams that need solutions this quarter, not next year
• Budgets that prioritise outcomes over features
• Staff who need to use the system, not become system administrators

For this Tier 1 contractor, the right-sized approach delivered:

• Implementation in weeks, not months
• Cost at 10% of enterprise alternatives
• A solution their team could maintain themselves
• Full compliance with Australian reporting requirements

The enterprise ERP project continued in parallel. But the sustainability team was not going to wait 18 months for carbon reporting when regulations were landing now.

The Handover: Building for Longevity

We designed this engagement to end. Not because we did not want ongoing work, but because a properly built solution should not require permanent external support.

Documentation Delivered

• User Manual: Step-by-step guide for project coordinators
• Template Guide: Detailed instructions for completing the Excel template
• Technical Documentation: ETL logic, database schema, PowerBI data model
• Troubleshooting Guide: Common issues and solutions
• Training Materials: Slide deck for onboarding new staff

Knowledge Transfer

Over the final week, we:

• Trained the sustainability team on dashboard administration
• Walked IT through the ETL process and monitoring
• Ran through common modification scenarios
• Conducted a simulated "system down" troubleshooting exercise

Support Transition

We provided 30 days of post-implementation support, then transitioned to their internal IT. They have not needed to call us since.

Key Lessons for Your Organisation

If you are facing a similar ESG data collection challenge, here is what we learned:

Start with the Process, Not the Technology

We spent more time in Week 1 understanding how project teams actually work than we spent writing code. The best technology cannot fix a broken process.

Design for Adoption, Not Completeness

We could have built a template that captured 50 data points. We captured 12. Why? Because a template that takes 5 minutes gets completed. A template that takes 30 minutes gets ignored.

Make Missing Data Visible

The dashboard's "missing data" view changed behaviour faster than any amount of email reminders. When regional managers see their projects highlighted in red during a leadership meeting, data appears quickly.

Build for Handover from Day One

We documented as we built, not after. Every design decision was recorded. Every configuration was explained. The result: a system the client can maintain without us.

What This Means for Australian Construction

The construction industry faces mounting pressure on sustainability credentials. The Infrastructure Sustainability Council reports that "Excellent" ratings are increasingly a requirement for major government contracts. This client targets ISC ratings on all major projects.

But sustainability reporting does not require enterprise-scale investment. What it requires is:

1. Standardised data collection - One template, consistently applied
2. Automated consolidation - Overnight ETL, not manual copy-paste
3. Actionable visibility - Dashboards that highlight problems
4. Audit-ready documentation - Clear trail from source to report

These capabilities are within reach of any construction company with SharePoint and Microsoft 365.

Ready to Fix Your Carbon Reporting?

If your sustainability data collection looks like this client's did three years ago (random templates, email attachments, quarterly fire drills), there is a better way.

The same approach applies across construction, manufacturing, and logistics companies throughout Australia. The pattern is consistent: right-sized tools, practical processes, and solutions that actually get used.

Your action plan this week:

1. Audit your current ESG data collection process (count the template variations)
2. Map where data gets stuck (usually between project sites and corporate)
3. Calculate how many hours your team spends on manual consolidation

Book a free 30-minute consultation and we will show you exactly how we would approach your situation, no enterprise platform sales pitch required.

Related Resources:

• Automated Compliance Reporting: The Complete Guide for Australian Businesses
• AI for Construction: Automating Project Documentation and Compliance
• Automate Report Generation with Python and AI
• Construction Industry AI Solutions - How we help Tier 1 contractors with automation
• Process Automation Services - Our end-to-end automation implementation approach

Sources: Research synthesised from BDO Australia Mandatory Sustainability Reporting guidance (2024), Deloitte State of Digital Adoption in Construction (2025), Australian Treasury Laws Amendment Act (2024), Clean Energy Regulator NGER Scheme documentation, Infrastructure Sustainability Council ratings framework, and direct implementation experience with a Tier 1 infrastructure contractor's National Sustainability team 2022-present.