Frederick County

Frederick’s Climate Dashboards Show the Work But They Don’t Enforce It

Frederick’s new city and county dashboards make climate work easier to see. Their real test is whether status labels lead to budgets, ordinances, enforceable standards, and public explanations when deadlines slip.

Frederick now has two public dashboards for tracking its shared climate plan: one for the City and one for the County.

Released October 1, the dashboards track the City and County’s implementation of the Community-Wide Climate and Energy Action Plan. The plan calls for greenhouse gas emissions to fall at least 50 percent below 2010 levels by 2030 and reach net zero by 2050.

That is a real transparency improvement -- residents can see which actions each government describes as upcoming, in progress, on track, standardized, or completed, along with selected emissions data.

The thing is, visibility is not enforcement. A dashboard can show that work is underway, but it cannot fund a project, amend a building code, impose a permit condition, or create a consequence when a target is missed. Its value depends on whether the public can follow each status label into an actual decision and a measurable result. Who is responsible for acting? What policy changes will the information support? What happens if the work stalls?

What The Dashboards Track

Both dashboards track work under the shared climate plan, including buildings, power, transportation, waste, natural lands, infrastructure, health, and emergency management. The County also separately identifies agriculture.

As reviewed on October 3:

Measure	Frederick County	City of Frederick
Tracked items	46	40
Status breakdown	9 standardized, 17 in progress, 19 upcoming, and 1 completed	4 pending, 26 on track, 5 in progress, and 5 completed
Overall progress gauge	Not displayed	40 percent
2023 net emissions	2,759,605 metric tons CO₂e	953,098 metric tons CO₂e
Change from 2005	About 47 percent lower	Down from 1,181,357 metric tons CO₂e
Additional target measure	63.7 percent of the way toward the County’s 2030 target	Not displayed in the same format

The dashboards define their status labels as follows.

Frederick County

Standardized: The action has become part of normal County operating procedures.
In progress: The work has started and is expected to be completed or standardized by 2030.
Upcoming: The action is planned or still being explored.

City of Frederick

On track: The action has become part of standard City operating procedure.
Status pending: The dashboard uses this label, while its explanatory legend calls the category “upcoming.”

The emissions figures measure outcomes, while the status labels describe activity. An outreach campaign can be in progress without producing a measurable reduction in emissions. At the same time, regional changes in the electric grid can lower local emissions even when a particular local action is delayed.

That makes the definitions behind the labels and percentages important—and exposes the first problem with comparing the two dashboards.

The Labels Are Not Yet Comparable

A status becomes useful for accountability when the public can connect it to responsibility, timing, funding, and evidence.

But the two dashboards are not aligned. The City’s top-level chart uses “status pending,” while its explanatory legend calls the category “upcoming.” The County does not show the same kind of overall progress gauge that the City does.

The public pages reviewed on October 3 do not plainly explain how the City’s 40 percent overall score is weighted or calculated.

On the City’s building-strategy page, two listed actions have no visible progress or status value. The same page says implementation depends on funding, staff capacity, alignment with other initiatives, and future priorities.

Those may be legitimate constraints. But an accountability tool should make the constraint part of the record.

Until those details are visible, the dashboards show how each government describes its work. They do not yet show whether that work is funded, on schedule, or producing the promised result.

What Is Actually Enforceable

Frederick’s climate plan sets policy direction, but its goals become enforceable only when a separate law, regulation, permit, contract, or budget decision creates a binding duty and a consequence for noncompliance. The question is which commitments have been translated into those requirements—and which remain voluntary or aspirational.

The City and County adopted climate-emergency resolutions in 2020. The City later adopted the Community-Wide Climate and Energy Action Plan through Resolution 26-6 on April 2, 2026. The County dashboard says County Executive Jessica Fitzwater approved the plan on October 28, 2025.

Those actions matter. They establish direction, authorize planning, and create a record against which elected officials can be judged.

The dashboards themselves do not create a fine, permit sanction, or automatic budget consequence for missing Frederick’s overall climate targets.

Maryland law does attach enforceable requirements to parts of the climate plan. The state’s Building Energy Performance Standards, for example, require covered large buildings to report energy use and, beginning in 2030, meet direct-emissions standards or make alternative compliance payments.

Those sector-specific rules are different from a penalty for the City or County missing the CEAP’s community-wide target. The statewide Climate Solutions Now Act requires Maryland to adopt plans and regulations for meeting its emissions goals, but Frederick’s dashboards do not create their own enforcement mechanism.

Enforcement happens when a plan is translated into a legal or administrative lever. Depending on the action, that can mean:

An ordinance or code amendment.
A zoning, permitting, or development standard.
A procurement rule or contract term.
A funded budget or capital project.
A state regulation applied by the responsible agency.
A grant agreement with measurable deliverables.
A departmental procedure with a responsible official and required reporting.

Some plan actions rely on education, rebates, voluntary participation, or cooperation from private actors. Others depend heavily on Maryland policy, especially grid decarbonization and building-performance rules.

The plan itself identifies an important limit: local governments do not have authority to require data center operators to disclose energy use.

It recommends encouraging metering and monitoring. Other proposals—including energy surcharges, renewable-energy requirements, and disclosure of power-purchase agreements—were identified as matters that may require state action.

A public dashboard cannot close an authority gap that local law does not fill.

How The Dashboards Can Affect Policy

The dashboards can still shape decisions if officials and residents use them as more than a communications product.

First, they can expose where adopted goals and funded work diverge. An “upcoming” action that remains unfunded through repeated budget cycles is not merely upcoming. It is a policy choice waiting to be named.

Second, the dashboards can inform annual budgets and capital plans.

If transportation is the City’s largest emissions source, the dashboard should make it easier to connect the climate target to transit service, sidewalk and bikeway investments, fleet replacement, land-use decisions, and vehicle-miles-traveled policy.

Third, they can support code and ordinance work.

A strategy becomes enforceable when the relevant legislative body adopts a rule, assigns an agency to administer it, and provides standards that can be applied consistently.

Fourth, the dashboards can reveal when another policy moves the numbers in the wrong direction.

That is especially important for data centers. The climate plan projects data centers as the County’s largest emissions source under a business-as-usual scenario while acknowledging that actual facility electricity use is not publicly available.

FredCo Paper Trail raised the same accountability test when Maryland announced its data-center dashboard: public reporting needs comparable project-level data, preserved changes, and commitments that can be tested.

A climate dashboard should not become a place where small household programs are counted precisely while the largest emerging load remains an estimate.

What Residents Should Ask For Next

The first version of these dashboards provides a useful map. The next version should provide the receipts.

For each action, the City and County should publish:

The responsible department and named lead.
The original target date and current expected date.
The budgeted amount, funding source, and amount spent.
The specific output delivered.
The outcome metric the action is expected to change.
The evidence supporting the status.
The date of the last update and a visible change history.
The reason for any delay or scope change.
Whether the action is voluntary, administrative, contractual, regulatory, or legislative.
Which level of government has authority to act.

The governments should also reconcile their status terms and explain how progress percentages are calculated.

If the dashboards are meant to be compared, the public should not have to reverse-engineer what “on track,” “standardized,” or 40 percent progress means.

Frederick now has a better window into its climate work. The next test is whether that window becomes a lever.

Accountability begins with seeing the plan. It becomes real when the public can follow each commitment into a budget, a rule, a receipt, and a measurable result.