Error message

  • Warning: Illegal string offset 'field_name' in node_reference_preprocess_node() (line 862 of /Applications/MAMP/htdocs/sites/all/modules/references/node_reference/node_reference.module).
  • Warning: Illegal string offset 'field_name' in node_reference_preprocess_node() (line 864 of /Applications/MAMP/htdocs/sites/all/modules/references/node_reference/node_reference.module).
  • Warning: Illegal string offset 'field_name' in node_reference_preprocess_node() (line 862 of /Applications/MAMP/htdocs/sites/all/modules/references/node_reference/node_reference.module).
  • Warning: Illegal string offset 'field_name' in node_reference_preprocess_node() (line 864 of /Applications/MAMP/htdocs/sites/all/modules/references/node_reference/node_reference.module).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
  • Warning: Illegal string offset 'field' in DatabaseCondition->__clone() (line 1817 of /Applications/MAMP/htdocs/includes/database/query.inc).
Tim Lesiuk
Tim Lesiuk
Executive Director of Business Development and Chief Negotiator
British Columbia Climate Action Secretariat

Tim Lesiuk is Executive Director of Business Development and Chief Negotiator in the Climate Action Secretariat, the agency responsible for meeting the province’s greenhouse gas (GHG) reduction targets. Tim leads British Columbia’s negotiations with the Western Climate Initiative (WCI). He is the Canadian Co-chair of the WCI and is also Chair of the Offsets Committee. Tim leads the development of the Cap and Trade system in British Columbia and the establishment of the Pacific Carbon Trust. Prior to joining the Climate Action Secretariat, Tim was responsible for climate change management in BC Hydro.

New Ground: New Protocol Types and Offset Supply

Although regulated entities in California will be able to use carbon offsets to meet only eight percent of their compliance obligation under cap-and-trade, many observers are concerned that offsets will be in short supply, especially after 2014. Amid these concerns, there is much speculation around possible domestic project types that California and WCI may add to their programs to boost supply. This session will examine the prospects for including additional offset types in the California and WCI programs and their potential for addressing supply concerns.

1:30pm
3:00pm
Program Path Text: 
Path 2: Offsets and Other Mitigation

Plenary Session - Full Steam Ahead: WCI Update

WCI is reaching a watershed moment with plans for Québec and California to link their cap-and-trade programs later this year. WCI Partners will provide an update on program development, followed by an interactive forum for questions and answers.

11:00am
12:00pm