Actions

Modified on Wed, 14 Oct at 3:58 PM

Turn ideas into reductions. 

Actions represent concrete measures—like efficiency upgrades, fuel switching, or renewable energy sourcing—that change the projected emissions. Add an action to specify its impact and timing, then see how the plan compares with the target.


Actions in Decarbonization Strategy



Tip: Generate AI-suggested actions to speed up planning. These use the organization’s data to propose credible starting points for emission reductions, complete with impact estimates and assumptions. 
Learn more: How AI-suggested actions work


Adding or editing an action

The fields below are the same for actions created manually and for AI-generated suggestions. Each field defines how the action affects the decarbonization plan.



Name: enter a clear, descriptive name so it’s easy to identify and compare later.


Decarbonization lever: select the primary mechanism for reducing emissions. If multiple levers could apply, choose the most relevant one.


Description (optional): add details that explain what the action involves or how it will be carried out.


Start and end year: enter the timeframe when the action will take place. Only years within the scenario’s timeframe can be selected.


Data source: select the scope and category this action affects.


Organizational unit (optional): if the action targets specific org.units, select them here. Leave blank to apply it across all org.units.


Reduction potential: enter the estimated percentage of emissions that can be reduced or avoided through the action, relative to the selected reference year. Determine this by consulting relevant studies or benchmarks that provide reduction potential ranges. If enabled, the AI Analyst can also offer an indicative estimate.


Implementation rate: specify how broadly the action is applied across selected scope/category. For example, if 10% of the vehicle fleet is impacted, enter 10%. When modeling multiple mutually exclusive actions (e.g., switching to electric or biodiesel vehicles), their combined implementation rates must not exceed 100%.


OpEx (optional): enter the yearly change in OpEx. Enter a positive value for an increase in costs, or a negative value to reflect cost savings.


CapEx (optional): enter the total CapEx investment required.


Assumptions (optional): use this field to capture the reasoning behind the action inputs—for example, the source of a reduction potential, expected implementation timing, or any constraints taken into account. Recording assumptions makes it easier for everyone involved to understand, review, and adjust actions later.


Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons
CAPTCHA verification is required.

Feedback sent

We appreciate your effort and will try to fix the article