Why start with a readiness review instead of the dashboard?

Because in our experience most dashboard problems are data problems. If two sources disagree on last year’s emissions, a chart only makes the disagreement look official. The Data & AI Readiness Review checks the sources first, so your build budget goes to a dashboard people trust rather than one they argue with.

Can the dashboard pull from our existing systems?

Usually. We begin with the exports your team already produces, then connect to source systems directly where their owners approve access. Each connection is scoped up front: which way the data flows, who owns the source and what happens when an import fails, so nobody discovers the gaps on reporting day.

Do you calculate the emissions, or only display them?

Both. Council Fire does greenhouse gas accounting with technical partners, including the Scope 1, 2 and 3 analysis behind the carbon baseline for Luke’s Lobster, and CF Labs builds the view on top. If a platform already produces your numbers, we connect to it instead of recalculating them.

Can you map climate risk across our assets or communities?

Yes. We join public sources such as FEMA’s National Risk Index to your own asset or program records, the way our Climate Risk Lookup does for any U.S. county. The result shows where risk lands and, with social vulnerability data alongside, who is most likely to carry it.

Can we share a dashboard with the public?

Yes, and you decide exactly what shows. Internal views can carry draft figures and working notes, while a public view shows only the fields you approve. Resilient & Ready Anne Arundel, the Resilience Authority’s public portfolio on Aptation, our resilience planning platform, works this way.

Will a dashboard replace our sustainability report?

No. A report is a point-in-time statement with its own review and sign-off, while a dashboard is the working view your team uses between reports. Built well, it makes reporting season easier, because the numbers are already reconciled and owned when the season starts.

What does a dashboard project cost?

Start with the Data & AI Readiness Review at $6,500. If the data is ready, a Tool Sprint builds a working dashboard prototype on it in two to three weeks, for $12,500. For a full build with integrations and public views, our project estimator gives you a first number before we talk.

Climate Data Dashboards for Emissions and Risk

CF Labs

Climate data dashboards your board can decide from.

Start with a Readiness Review

Estimate your build

The problem

The number changes depending on who you ask.

Emissions sit in one workbook, flood risk in a consultant’s PDF, grant spend in the finance system, and the board deck copies from all three by hand. By the time it’s ready, someone has found a different total, and the meeting turns into a debate about the data.

A better chart won’t fix that. The work is upstream: agreeing what each metric means, who owns it and which source wins when two disagree. That’s where we start, before anyone opens a design file.

Every system starts small

0:30

On screen: “Every system starts small,” over roots spreading through soil. Dashboards bloom like ink in water. “You bring the plan,” a seed in an open hand; “It grows toward you”; “Root by root.” CF Labs, software and AI by Council Fire, over a field in flower, then “Plant a plan.” It ends on the Council Fire Labs mark and “Strategy, made operational.”

What we build

6 kinds of build

Dashboards for the questions that come back every quarter

#1
Emissions dashboards
Scope 1, 2 and 3 by facility, supplier or product, with the assumptions behind each figure one click away.
#2
Climate risk and vulnerability maps
Hazards, exposure and social vulnerability across your assets or neighborhoods, from public sources like FEMA’s National Risk Index joined to your own records.
#3
Board and funder reporting
The handful of figures your board, council or funders actually ask about, current and ready to present without a week of copy and paste.
#4
Program and grant tracking
Spend, milestones and outcomes for every program or grant, so a funder report starts as an export instead of a project.
#5
Public dashboards
A public view of what’s funded and why, showing only the fields you choose to publish.
#6
The pipeline underneath
Scheduled imports from your source files and systems, with checks that flag a missing month or a changed definition before it reaches the chart.

A river valley under a wide sky, seen from above

Numbers first

A dashboard is only as good as the numbers under it. We trace each one to its source and date before we design a single chart.

How it works

4 steps, in order

Numbers first, charts second

#1
Name the decision
Which meeting, which question, which people? We design backward from the decision the dashboard has to serve.
#2
Trace every number
We follow each metric to its source, agree its definition and owner, and settle which source wins when two disagree.
#3
Build the pipeline, then the view
Imports and checks come first, so the chart stays current without copy and paste. You see it on your own data every week.
#4
Change it when the rules change
Your team runs the dashboard day to day. A new reporting standard or target ships as its own scoped release.