Invoking the Precautionary Principle: Shell´s approach to protecting the environment: an analysis

With a challenging but realistic ´blueprint for action´ in mind, global companies have strong environment objectives, controls and measures in place in order to make a significant contribution to ´ecosystem resilience´. Through this workshop, Shell invites feedback on its approach to protect the environment and encourages an open dialogue: are we doing enough, when and how much is enough, and how and where to improve performance?

Background
As the search for oil and gas sends Shell to more challenging locations, managing environmental aspects early in any project – such as greenhouse gas emissions, water and land impact – has become increasingly more important. As is improving the way we run our projects and day-to-day operations to use less energy and water, and prevent spills.

Shell has a series of policies, a detailed control framework and an environment strategy that provide guidelines for the company’s plans and actions. The framework requires each area of the company to prioritise environmental improvement activities. By bringing environmental management to the core of business plans and decisions, we aim to run our operations and deliver new projects in line with our business principles, emerging regulatory requirements, environmental challenges and growing stakeholder expectations.

In addition to these internal controls, Shell has formed collaborative partnerships with global environmental organisations to help improve our environment performance and contribute to biodiversity conservation. These partnerships allow us to work with scientific experts and environmentalists to reduce our environmental impact and support biodiversity conservation.

The knowledge café will address the fundamental questions: how much information does Shell need to collect and analyse before proceeding to the next project phase, when and how much is enough, and can it do better? The participants will be invited to express their views and share their knowledge.

Geographical scope:

Rating: 
Average: 5 (1 vote)
Connection could not be established.
Array ( [0] => Array ( [0] => 28000 [SQLSTATE] => 28000 [1] => 18456 [code] => 18456 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. ) [1] => Array ( [0] => 42000 [SQLSTATE] => 42000 [1] => 4060 [code] => 4060 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. ) [2] => Array ( [0] => 28000 [SQLSTATE] => 28000 [1] => 18456 [code] => 18456 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Login failed for user 'drupal'. ) [3] => Array ( [0] => 42000 [SQLSTATE] => 42000 [1] => 4060 [code] => 4060 [2] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. [message] => [Microsoft][SQL Server Native Client 10.0][SQL Server]Cannot open database "aspnetdb" requested by the login. The login failed. ) )