<body><script type="text/javascript"> function setAttributeOnload(object, attribute, val) { if(window.addEventListener) { window.addEventListener('load', function(){ object[attribute] = val; }, false); } else { window.attachEvent('onload', function(){ object[attribute] = val; }); } } </script> <div id="navbar-iframe-container"></div> <script type="text/javascript" src="https://apis.google.com/js/plusone.js"></script> <script type="text/javascript"> gapi.load("gapi.iframes:gapi.iframes.style.bubble", function() { if (gapi.iframes && gapi.iframes.getContext) { gapi.iframes.getContext().openChild({ url: 'https://www.blogger.com/navbar.g?targetBlogID\x3d23348393\x26blogName\x3dDeveloping+News\x26publishMode\x3dPUBLISH_MODE_BLOGSPOT\x26navbarType\x3dBLACK\x26layoutType\x3dCLASSIC\x26searchRoot\x3dhttps://developingnews.blogspot.com/search\x26blogLocale\x3den_GB\x26v\x3d2\x26homepageUrl\x3dhttp://developingnews.blogspot.com/\x26vt\x3d5750049883697856736', where: document.getElementById("navbar-iframe-container"), id: "navbar-iframe" }); } }); </script>

Note: This blog is no longer active - please visit my new site at HAT Projects where you will find our new blog!

Thursday, August 17, 2006
Obligatory design statements: good or bad?
An interesting point has been raised in relation to the now-compulsory design and access statements for all planning applications. Brian Waters, joint editor of Planning in London, thinks that they will lead to even further 'dumbing-down' of planning staff within LAs.

He reckons that planners are losing the skills to evaluate design quality through a tick-box approach that codifies 'good' quality rather than relying on good judgement. Its a really universal problem: on the one hand 'good judgement' for one person is another person's stupid personal opinion; on the other hand, quality isn't just about ticking certain boxes: it isn't a quantifiable thing.

I have to admit that I thought the design statements were a good thing but clearly, as with all these statements (EIAs, anyone?) a clever person can write a convincing-sounding design statement for a poor scheme. Planners still need to exercise judgement, comparing the written statement with the actual design to see whether the supposed aspirations are evident in the detail. But I can still see his point - when planners are overloaded with case-work, the temptation will be to read the statement and skim over the drawings.


Anonymous Ian said...

I already think that the quantity of supporting material supplied with so many planning applications is completely out of context. When I worked for a planning consultancy I prepared planning statements running to 100s of pages for relatively low key developments...further adding to the overload of planners.

I doubt much of it gets read, as so much of it is superflous to the actual scheme, referencing even the most obscure local policies. A lot of it is included to show the client that he is getting value for money.

Word limits could be one solution - it would lower the amount of reading required, force consultants to really focus their argument, and encourage the public to actually read and comment on the documents.

(Great site by the way)

4:36 am  
Anonymous ben patio said...

The whole planning system is about ticking boxes anyway.

11:39 am  

Post a Comment

<< Home