Build a 90-day action plan + a 12–36 month roadmap you can actually execute (not a slide-deck fantasy)
By using this kit, you will produce real artifacts:
90-day plan
Owners, due dates, deliverables
12–36 month portfolio roadmap
Sequenced initiatives with dependencies
Portfolio initiative backlog
Impact + feasibility scoring
Governance cadence
Steering, monthly close, decision gates
Measurement plan
What you'll prove and how
Leadership teams
Who need a roadmap that survives execution
Sustainability teams
Who own targets and reporting
Finance teams
Who control capital planning and approvals
Ops/Facilities teams
Who execute projects and live with outcomes
Use this when:
You can start without perfection, but you need:
Pick your first 10–20 sites (or top 20% by spend/size) and do:
A roadmap is not a list of projects.
A roadmap is:
sequencing
dependencies
owners
decision gates
measurement
funding path
Beginner rule: If your roadmap doesn't say "who does what by when," it's not a roadmap.
Pick 1–2 primary goals: reduce operating cost volatility, reduce outage/comfort risk, reduce emissions and reporting risk, meet commitments, increase tenant readiness. Write it in one sentence: "We will reduce energy and emissions while improving comfort and reliability, with proof and repeatable workflows."
Decide which assets are in scope (owned/operated/managed/leased), what 'coverage' means (by area, by spend, by energy), what counts as 'measured vs allocated vs proxy', and what you will NOT do this cycle (to protect focus).
Build a table that enables prioritization: size/asset type, lease/control reality, energy/fuel presence, major system age/EOL, pain indicators (comfort complaints, repeat failures), and feasibility constraints.
Common initiative families: operations & controls, retro-commissioning, targeted upgrades (VFDs, sensors), equipment replacement, electrification (heat pumps), metering & data, renewable procurement, tenant engagement. This is your backlog.
Use a 2-axis score: Impact potential (cost, reliability, emissions) and Feasibility (data availability, access, constraints, timing, funding). Add 2 modifiers: Strategic alignment and Learning value.
Foundation (0–90 days): data, governance, pilot selection. Quick wins (3–6 mo): controls/RCx, metering. Capex cycle (6–24 mo): major replacements, electrification. Scale (12–36 mo): standardization, repeatable delivery.
You need: a monthly close for energy/carbon data, a quarterly steering for roadmap adjustments, and a capex decision gate process (approve / defer / kill).
Every roadmap line item must say: what you'll measure, where the data comes from, what 'success' looks like, and who owns measurement.
| Site/Asset | Size | Control/lease reality | Utilities paid by | Data holder | Scope 1 sources present? | Major systems EOL soon? | Pain score (1–5) | Feasibility (H/M/L) | Notes | |---|---:|---|---|---|---|---|---:|---|---|
| Initiative | Category | Applies to (which sites) | Impact (1–5) | Feasibility (1–5) | Cost level ($/$$/$$$) | Dependencies | Owner | Next step | Target start | |---|---|---|---:|---:|---|---|---|---|---|
Impact score (1–5): - 5: major cost/reliability/emissions benefit - 3: moderate benefit - 1: minor benefit Feasibility score (1–5): - 5: data + access available; can start in 30–60 days - 3: needs some prerequisites - 1: blocked (access, capacity, unclear scope) Priority: - Do first: Impact 4–5 AND Feasibility 4–5 - Pilot: Impact 4–5 AND Feasibility 2–3 - Defer: Impact 1–3 OR Feasibility 1
90-Day Plan Week 1–2 - Confirm scope boundaries and success metrics - Build portfolio baseline table (v1) Owner: Due: Week 3–4 - Select pilot sites (1–3) - Define measurement plan (M&V) Owner: Due: Week 5–8 - Launch 1–2 pilots (controls/RCx, metering, data pipeline) - Start renewable procurement discovery (if applicable) Owner: Due: Week 9–12 - Pilot readout: what worked, what failed, what scales - Publish 12–36 month roadmap v1 Owner: Due:
| Time window | Initiative | Sites | Dependencies | Funding path | Owner | Proof metric | |---|---|---|---|---|---|---| | 0–3 mo | Data governance + pipelines | Portfolio | None | OpEx | | % coverage | | 3–6 mo | Controls/RCx program | Top sites | Baseline data | OpEx | | kWh change | | 6–18 mo | Capex bundles | Target sites | Engineering + access | CapEx | | measured savings | | 12–36 mo | Scale electrification where feasible | Subset | capacity + capex | CapEx | | fuel reduction |
Roadmap Steering (Quarterly) Agenda: 1) Progress against 90-day / quarterly deliverables 2) Data coverage and quality (measured vs allocated vs proxy) 3) Pilot learnings and scale recommendations 4) Capex decisions (approve/defer/kill) 5) Risks and constraints 6) Next quarter priorities Outputs: - Updated roadmap (v++) - Decisions logged - Owners and due dates assigned
Portfolio Decarbonization Roadmap (Executive Summary) Objective: Scope: Current baseline reality (honest): - Coverage: - Data quality: - Key gaps: Roadmap approach: - Screen → focus → improve - Foundation → quick wins → capex cycle → scale Top priorities (next 90 days): 1) 2) 3) 12–36 month themes: - Controls + commissioning - Targeted retrofits and replacements - Electrification where feasible - Renewable procurement (if applicable) - Tenant/customer engagement (if applicable) Governance: - Monthly close - Quarterly steering Measurement: - Proof metrics and M&V approach Decisions needed: - Budget for pilots - Owner assignments - Timeline approvals
% portfolio with usable energy data
+ evidence links
# of pilots launched and completed
Execution proof
% initiatives with assigned owners
And proof metrics
kWh/fuel reductions measured
vs baseline (for completed projects)
Reduction in "unknowns"
Over time
v1.0 (2026-01): Latest release