Custom Dashboards for Sustainability Teams: Why One View of Emissions Data Isn't Enough

A sustainability manager at a multi-site property company told us she spends roughly six hours a week building ad hoc reports for people who all want different things from the same emissions data. The CFO wants cost exposure. The state operations managers each want their facilities only. The board wants a one-page summary showing whether they're on track against targets. And every request means she drops what she's doing, opens a spreadsheet, filters, formats, and emails a PDF.

Six hours a week. That's 312 hours a year — nearly eight working weeks — spent not on improving emissions performance, but on repackaging the same underlying numbers for different audiences.

This isn't a data problem. It's a visibility problem. The data exists. It's just trapped behind a single view that was designed for one type of user.

The "one dashboard for everyone" trap

Most carbon accounting platforms ship with a fixed dashboard. You log in, you see total emissions by scope, maybe a breakdown by facility, a time-series chart, and some summary cards. It looks polished. It tells you almost nothing useful for your specific role.

KPMG's 2024 ESG Assurance Maturity Index surveyed 1,000 senior executives and board members and found that 84% of organisations at early ESG maturity stages still partially rely on spreadsheets for ESG analysis and reporting — even when they have dedicated software. Only 29% of companies surveyed qualified as "Leaders" with mature ESG data management. The gap between having a tool and that tool actually working for everyone in your organisation is enormous.

For Australian companies facing ASRS Group 2 reporting from financial years starting 1 July 2026, this gap matters more than it used to. AASB S2 requires governance disclosures that demonstrate board-level oversight of climate-related risks and opportunities. Directors need to show they have access to emissions data and use it in decision-making. A sustainability team member forwarding a reformatted spreadsheet every quarter doesn't exactly demonstrate embedded governance processes.

The problem isn't that people don't want to engage with emissions data. It's that the default dashboard was built for the sustainability analyst, and everyone else has to ask that analyst to translate.

Four personas, four completely different needs

We've watched this pattern repeat across dozens of conversations with Australian companies preparing for mandatory reporting. Every organisation has at least four distinct user types who need emissions data — and they need fundamentally different views.

The sustainability manager lives inside the data. They need emission source detail: which fuel types, which facilities, which invoices drove this quarter's numbers. They need to spot anomalies — a sudden spike in diesel consumption at one site, a missing month of electricity data, a refrigerant top-up that suggests a leak. They care about data completeness and accuracy at the line-item level, because they're the ones who'll answer the auditor's questions. Their dashboard is dense, granular, and probably has 15 widgets on it.

The CFO doesn't want tonnes of CO2-e. They want dollars. What's our Safeguard Mechanism exposure this financial year? If we exceed our baseline by 10,000 tonnes, what does that cost in ACCUs at current market rates? What's the carbon cost impact on that proposed acquisition? They need emissions data translated into financial language — liabilities, cost projections, compliance penalties. Under AASB S2, the CFO is increasingly the person accountable for climate disclosures being "reasonable assurance ready." A Deloitte survey found that while 77% of executives report progress on sustainability, 57% still cite data quality as a top challenge. The CFO's dashboard should surface the financial implications of emissions, not the raw activity data.

The board needs the highest-level view with the lowest friction. Trend lines. Target progress. Year-on-year comparison. Red/amber/green indicators showing whether the organisation is tracking against its commitments. They should be able to understand the company's climate position in under two minutes, because that's roughly how much time it gets on a board agenda alongside 15 other items. AASB S2 paragraphs 5-8 require disclosure of how the governance body oversees climate-related risks — which means directors need to actually see this data, not just hear about it second-hand.

The facility manager cares about one site. Maybe two. They don't want to see corporate-wide Scope 3 supply chain estimates. They want to know: what were my site's emissions last month compared to the month before? Is my electricity consumption trending up? Did that equipment upgrade actually reduce gas usage? Show them the whole corporate portfolio and they'll either ignore the dashboard entirely or — worse — accidentally act on data from another facility.

These aren't edge cases. These are the four people who always exist. And a fixed dashboard serves maybe one of them adequately.

What configurable actually means in practice

"Configurable dashboard" gets thrown around a lot by software vendors. Usually it means you can change a date filter or toggle between a bar chart and a line chart. That's not configuration. That's cosmetics.

When we built the dashboard system in Carbonly, we started from a different question: can each user build a view that matches their actual job, without needing the sustainability team to set it up for them?

The system works on a grid layout with configurable columns (up to 24 across), rows, and gap spacing. Each widget gets placed at specific x/y coordinates with defined width and height. That sounds technical, but in practice it means you can drag widgets around and resize them until the layout fits your workflow. A sustainability manager might build a dense 6-column grid with small widgets showing emissions by scope, by facility, by category, and by time period all at once. A board member might have a 2-column layout with three large widgets: target progress, year-on-year trend, and top five emission sources.

The visibility system is where it gets genuinely useful for organisations. Dashboards have four visibility levels: private (only you see it), shared (specific people you invite), organisation (everyone in your company), and public. Role-based templates mean you can set up a default "CFO view" or "facility manager view" that gets assigned to new users based on their role. The facility manager logs in and immediately sees their site's data. The CFO sees the financial exposure view. Nobody has to configure anything from scratch unless they want to.

And because the system tracks who views which dashboards, sustainability teams can actually see whether the board is looking at the emissions data they're providing — which matters when your ASRS assurance provider asks about governance processes.

Building the CFO's financial exposure view

Here's a concrete example. Consider a company with three facilities under the Safeguard Mechanism, each with baselines declining at 4.9% per year. The CFO doesn't need to understand emission factor methodologies. They need to know: are we above or below our combined baseline, and what does it cost if we're over?

A financial exposure dashboard might include four widgets. First, a position-vs-baseline chart showing each facility's current reported emissions against its declining baseline for this financial year (July to June — this matters because Safeguard runs on the Australian financial year, not calendar year). Second, a cost projection widget that multiplies any exceedance by the current ACCU price range ($35-82.68, depending on market vs cost containment). Third, a year-on-year operational cost comparison showing what changed. Fourth, a target progress widget tied to any SBTi or internal reduction commitments.

That's the whole view. Four widgets. No Scope 3 category breakdowns, no individual invoice detail, no emission factor references. Just the numbers the CFO needs to make financial decisions about carbon exposure.

Compare that to what the sustainability manager needs on the same platform: a data completeness tracker showing which facilities have submitted all their utility bills for the current quarter, an anomaly detection feed flagging unusual consumption spikes, a scope-by-scope breakdown for NGER reporting categories, and a pending-review queue for documents the AI extraction pipeline has processed but flagged for manual verification.

Same underlying data. Completely different presentations. Both legitimate and necessary.

The facility manager problem is underrated

In our experience, the persona that gets neglected most in carbon accounting platforms is the facility manager. And that's a mistake, because facility managers are often the people closest to the actual emission sources. They know when a boiler is running inefficiently. They notice when the backup generator ran for 48 hours during a grid outage. They see the waste contractor skip a collection.

But if you give a facility manager access to the corporate carbon platform with the default view, they're immediately overwhelmed. Emissions from 40 facilities across five states. Scope 3 procurement data they have no context for. Board-level target charts they don't influence.

What they actually need is dead simple: their facility's Scope 1 and Scope 2 emissions, month-on-month, with the ability to drill into which energy sources drove changes. Maybe an incidents widget if they're tracking environmental events. And the ability to export their facility's data as a CSV or PDF for their own records.

In Carbonly, this works through shared access controls. The sustainability team builds a facility-level template dashboard, sets it as the default for the "facility manager" role, and restricts the data scope to that user's assigned facilities. The facility manager logs in and sees only what's relevant. They can't accidentally access another site's data. They can't misconstrue corporate-wide numbers as their own.

This matters especially for NGER reporting, where facility-level thresholds (25 kt CO2-e or 100 TJ) determine reporting obligations independently from the corporate group. A facility manager who can see their site is approaching the 25,000-tonne threshold can flag it early — instead of the sustainability team discovering it during the October reporting crunch.

What dashboards won't fix

Here's where I need to be honest. Dashboards are only as good as the data behind them.

If your emissions data has gaps — missing utility bills, estimated rather than actual consumption figures, Scope 3 categories populated by spend-based proxies with 30-40% error margins — a beautiful dashboard just makes bad data look authoritative. That's arguably worse than a messy spreadsheet, because at least with the spreadsheet you can see the holes.

We've also learned that too many widgets on a single dashboard actually degrades usefulness. There's a temptation to cram everything onto one screen. But a dashboard with 25 widgets is just a spreadsheet with nicer formatting. We've seen better outcomes from users who build three to four focused dashboards for different contexts (weekly ops review, monthly board pack, quarterly NGER prep) rather than one monster view.

Performance is the other practical consideration. Loading 20 widgets that each query large datasets across multiple financial years takes time. The more widgets, the more database queries, the slower the page load. We're not going to pretend that's a solved problem. Configurable dashboards require some discipline from users — and some honest guidance from us about what's performant and what isn't.

And "real-time" emissions tracking — a term that gets used too loosely in this industry — depends entirely on how frequently data gets ingested. If your electricity data comes from monthly bills processed through AI document extraction, your dashboard updates monthly. That's the reality. Real-time visibility requires real-time data inputs, which most Australian organisations don't have yet (outside of direct SCADA integration for large industrial facilities). Don't let a dashboard label saying "real-time" give you false confidence about data currency.

Why this matters more now than it did two years ago

Before ASRS, sustainability data was largely a voluntary disclosure exercise. The sustainability team owned it end to end. They produced an annual sustainability report, maybe a CDP submission, and the board glanced at it once a year.

That world is gone. Under AASB S2, Group 2 entities reporting from FY2026-27 need to demonstrate governance processes for climate risk oversight. Directors need to show they monitor emissions performance and factor it into strategic decisions. CFOs need emissions data integrated with financial reporting. Risk committees need to understand exposure to carbon pricing and physical climate risks.

This means emissions data needs to flow to five or six different functions within the organisation — each with different context, different expertise, and different questions. A single fixed dashboard, or worse, a sustainability manager manually building reports for each stakeholder, doesn't scale.

The companies that are handling ASRS compliance well aren't the ones with the most data. They're the ones where the right data reaches the right people in a format those people can actually use. That's what configurable dashboards are for. Not prettier charts — but the right chart, for the right person, at the right time.

Export matters here too. The board member wants a PDF they can review on a flight. The CFO wants Excel data they can pull into their financial model. The sustainability manager wants a CSV to reconcile against NGER submission files. Being able to export from any dashboard widget in the format each stakeholder needs — CSV, Excel, or PDF — sounds unglamorous, but it's the feature people actually use every week.

Start with three views, not thirty

If you're building out dashboard views for your organisation, don't try to build everything at once. Start with three.

First, the board view: total emissions trend, target progress, and top five sources. Keep it to four widgets maximum. Make it the default for anyone with a "Director" or "Board Observer" role.

Second, the operations view: facility-level breakdown with month-on-month comparison. This is what your sustainability team and ops managers will use daily. It can be denser — eight to ten widgets — because these users live in the data.

Third, the NGER/compliance view: emissions organised by NGER reporting categories, facility-level thresholds, and data completeness tracking. This is the view you'll pull up when your October 31 deadline is three weeks away and you need to know what's missing.

Everything else — CFO financial exposure, Safeguard position tracking, incident correlation views — can come later, once you've confirmed the underlying data is clean enough to trust. Because the gap between a spreadsheet and software isn't just automation. It's giving people who aren't sustainability specialists a reason to engage with emissions data on their own terms.

Related Reading: