How can we recognise an employee’s energy-saving idea?

Thank the idea, the evidence gathered and the steps taken to test it. If a result was measured, state the period and scope accurately. A useful suggestion can be acknowledged before a saving has been established.

Should we reward the team with the lowest energy use?

Raw totals may reflect different equipment, hours or responsibilities. Recognise thoughtful actions and appropriate comparisons rather than ranking unlike teams by a single number.

Can we mention carbon savings in the thank-you?

Only with an appropriate calculation and clear assumptions. Otherwise describe the energy-related action directly. Recognition does not need an invented environmental figure to be meaningful.

Recognition messages

Recognising Energy-Saving Work: 10 Thank-You Messages

Thank the action and the evidence, keeping environmental claims within what was measured.

Recognise a useful action before making a big claim

An employee may notice faulty controls, gather meter readings or ask the evening team whether a proposed schedule will work. Those contributions deserve specific thanks even before anyone can calculate a saving. The fictional examples below focus on observable work rather than assumed environmental outcomes.

Keep operational needs in view. Equipment may need to remain on, some spaces have particular requirements and different shifts use a building differently. Thank the person who checks those constraints as well as the person who proposes a change.

Describe the evidence at its actual scale

A quieter week does not by itself prove that a new setting reduced energy use. Where there is a measured result, describe the period and comparison accurately. Where there is only an estimate, say so.

For a broader process improvement, use the process-improvement messages. Environmental recognition works best when the wording is as careful as the work: a clear action, an honest result and credit for the people who made it possible.

10 messages you can send

Thank you for checking which equipment needed to stay on overnight. We now have a shutdown list that respects the operational requirements.
For a practical check
Credits a specific process without guessing savings.
I appreciated the meter readings alongside your proposal. The team could discuss the pattern using evidence instead of assumptions.
For measurement
Recognises the quality of the information.
Thanks for reporting the heating fault with the times and rooms affected. Facilities had enough detail to investigate the issue.
For a useful fault report
Names information that enabled follow-up.
You tested the lighting schedule with the evening team before changing it. Thank you for considering the people who use the building later.
For checking with users
Balances energy use with working conditions.
Thank you for documenting the new equipment settings and who can change them. The next shift has a clear reference.
For an operational handover
Credits continuity and ownership.
I appreciated that your report separated measured use from estimated savings. It made the uncertainty easy to understand.
For honest reporting
Rewards a clear distinction between data and estimates.
Thanks for arranging the maintenance check rather than asking people to work around the faulty controls. We have a proper route to fix the cause.
For addressing a cause
Recognises action through the responsible team.
Thank you for comparing similar operating periods before drawing a conclusion. The quieter week alone would have given us a misleading result.
For a fair comparison
Credits attention to a confounding factor.
You checked the proposed change against the storage requirements before the trial. Thank you for keeping the operational constraints visible.
For protecting requirements
Avoids celebrating a shortcut that could compromise the work.
Thanks for sharing the result of the trial, including the part that did not work. That gives the next team something useful to build on.
For sharing a trial result
Recognises learning without overstating success.

What makes one land

Name a measured result only when you have the data and permission to share it.
Avoid turning energy use into a competition that ignores different roles or operating needs.
Thank maintenance, measurement and consultation as well as the visible change.
Do not convert an action into carbon savings or tree equivalents without a suitable basis.

Questions people ask

How can we recognise an employee’s energy-saving idea?: Thank the idea, the evidence gathered and the steps taken to test it. If a result was measured, state the period and scope accurately. A useful suggestion can be acknowledged before a saving has been established.
Should we reward the team with the lowest energy use?: Raw totals may reflect different equipment, hours or responsibilities. Recognise thoughtful actions and appropriate comparisons rather than ranking unlike teams by a single number.
Can we mention carbon savings in the thank-you?: Only with an appropriate calculation and clear assumptions. Otherwise describe the energy-related action directly. Recognition does not need an invented environmental figure to be meaningful.