Talk:Philip Dilley

This article must adhere to the biographies of living persons (BLP) policy, even if it is not a biography, because it contains material about living persons. Contentious material about living persons that is unsourced or poorly sourced must be removed immediately from the article and its talk page, especially if potentially libellous. If such material is repeatedly inserted, or if you have other concerns, please report the issue to this noticeboard.

If you are a subject of this article, or acting on behalf of one, and you need help, please see this help page.

This article is rated Stub-class on Wikipedia's content assessment scale.
It is of interest to the following WikiProjects:

Biography

	Biography portal This article is within the scope of WikiProject Biography, a collaborative effort to create, develop and organize Wikipedia's articles about people. All interested editors are invited to join the project and contribute to the discussion. For instructions on how to use this banner, please refer to the documentation.BiographyWikipedia:WikiProject BiographyTemplate:WikiProject Biographybiography articles
	This article has been automatically rated by a bot or other tool as Stub-class because it uses a stub template. Please ensure the assessment is correct before removing the `\|auto=` parameter.

Experience

Prior to being appointed Chairman of the UK Environment Agency, what experience did Philip Dilley have in managing matters relating to the UK environment? It would be useful to have this information added to the article.--Observer6 (talk) 23:11, 11 January 2016 (UTC)[reply]

This is a really good question. He is a civil engineer and hence is probably familiar with flood defences and coastal erosion. What I'd also like to know was what his duties were in terms of educating the public and HMG to understand the risks of flooding. Quite a lot can be simulated using Hydrographs but it appears storm frequency is changing and there is more building on flood plains. JRPG (talk) 19:11, 19 January 2016 (UTC)[reply]