Standard content for Members only

To continue reading this article, please login to your Utility Week account, Start 14 day trial or Become a member.

If your organisation already has a corporate membership and you haven’t activated it simply follow the register link below. Check here.

Become a member

Start 14 day trial

Login Register

Warning: Trying to access array offset on value of type bool in /var/web/site/public_html/wp-content/themes/fh-master/blocks/content-content.php on line 87 Warning: Attempt to read property "slug" on null in /var/web/site/public_html/wp-content/themes/fh-master/blocks/content-content.php on line 87

A decarbonisation amendment is unlikely to be added to the Energy Bill by the House of Lords, according to Tim Yeo.

Speaking to Utility Week, the chair of the Energy and Climate Change Select Committee, said the Lords “usually take the view they should respect the House of Commons”.

Yeo, whose amendment to get a decarbonisation target for 2030 set by April 2014 was voted down, added while it is uncommon for the Lords to change a bill approved by MPs, “they have the power to do so and it’s not unknown for them to do so.”

However, he said he did not know whether they would “force out an amendment”, but did state there would be a “vigorous debate” by peers.

Looking forward, Yeo made it clear that he remains committed to help bring down the country’s carbon emissions and will not allow the government to renege on its carbon budget pledges.

In relation to next year’s review of the fourth carbon budget, Yeo said: “In the debate on Tuesday (4 June), it was made very clear the House just won’t accept a watering down of the targets.

“That is now non-negotiable.”

Warning: Trying to access array offset on value of type bool in /var/web/site/public_html/wp-content/themes/utility-week/components/component-discovery_zone/component-discovery_zone.php on line 7 Warning: Attempt to read property "term_id" on null in /var/web/site/public_html/wp-content/themes/utility-week/components/component-discovery_zone/component-discovery_zone.php on line 7