Skip to content

The following section outlines the Hertfordshire design review process, in line with Design Council CABE good practice guidance, and details how to prepare for a review, a typical review programme, and the final reporting stage.

Schemes can be referred for design review by the local planning authority, or a member of the project team. Depending on the type of review (design review panel or desktop review) the design review team requires between 2 and 4 weeks to arrange a review.

Prepare

Inception

Early discussion with the design review team is required to determine whether design review is appropriate, and what type of review would be most suitable.

  • Design Review Panel is a formal process where the project team presents their scheme to the panel, followed by a question and answers session. It gives the project team and the local planning authority the opportunity to engage in discussion and hear the panel’s views directly. 
  • Desktop review involves a smaller meeting between a Chair, a second panel member, and a representative of the design review team. Desktop review may be suitable for schemes that have previously been for review and have been amended, or where schemes are already in the planning system and subject to tight timescales for determination.

Once the review approach has been agreed, a design review pro forma should be submitted to the design review team by the project team or representatives of the client, and copied to the relevant Local Planning Authority.

The pro forma should provide background information and a description of the proposed development, and highlight the key design issues. The information provided will be used to help inform the assembly of an appropriately skilled and experienced panel, and identify any additional stakeholders that should be in attendance at the review, for example landowners, the highways authority, community groups or expert bodies with specialist interests.

A week before the design review, the project team must submit an electronic package of plans and documents, and a copy of the PowerPoint presentation, to the design review team. These materials will be forwarded to the panel members and other attendees alongside an agenda.

For more information about materials requirements, please refer to the project team briefing note and checklist.

Review

Attendees

The review is facilitated by the design review team, in addition to the panel representatives of the project team and the Local Planning Authority should be attendance, as well as other key stakeholders where appropriate.

The size of the panel can vary according to the scale and nature of the scheme and the range of skills and experience required, however typically includes a Chair alongside 2-3 panel members.

Observers, who are not directly engaged in the design review, but will benefit from an overview of the process, may also be invited to attend where appropriate. 

Agenda

Depending on the quantity, location, scale and nature of the scheme(s) submitted, the panel can review between 1 and 3 schemes in a day. In general, a small to medium scale development is likely to take half a day, and a large scale development is likely to take a whole day.

An outline of the review programme is given below:

  1. Welcome & Introductions
  2. Site visit
  3. Project Team Presentation
  4. The Local Planning Authority’s View
  5. Q&A session
  6. Conclusion & Summary
  7. Closed Panel Discussion

For more information about the review programme, please refer to the project team briefing note and checklist.

Report

After the review a panel report is issued to the project team and copied to the Local Planning Authority, within 10 working days. The report contains a brief overview of the review and a summary of the panel’s observations and recommendations for the next steps.

The report will state whether the panel feels:

  • This is a good project that they support as it stands.
  • This is a project that they could support provided improvements are made.
  • A fundamental re-think is required.

If a scheme is at the pre-application stage, the report is deemed confidential. If a scheme is at the full application stage, the report is considered a public document and is published on the Building Futures website.

For more information about the report and the legal issues surrounding its publication, please refer to legal issues.

 

 

 

 


 

Cookies

Like many other websites, we place small information files called 'cookies' on your computer.

Why do we use cookies?

To remember your settings, for example your language and location. This means you don’t have to keep entering these details when you visit a new page.

To find out how you use the site to help us update and improve it.

How do I change my cookie settings?

You can change the settings of your web browser so that it won’t accept cookies. For more information visit AboutCookies.org.

But, doing this may stop you from using some of the online features and services on this website. 

Cookies we use

Cookies do a lot of different jobs, and we use 2 types of cookies:

Required functionality cookies – these cookies are essential for the website to work.

Performance and feature cookies – these cookies help to improve the performance and feel of this website, for example providing you with personalised services.


Take a look at a list of cookies we use on our website:

NameTypeHow we use itHow long we use the information for

ASP.Net_Sessions

 

Required functionality

An automatic cookie set by our software. 

Just for the time you are on our website.

ServerID

 

Required functionality

An automatic cookie set by our software. 

Just for the time you are on our website.

_ga

Required functionality

To track the effectiveness of our website using Google Analytics. 

2 years

saved-pages

Performance and feature

To save the pages that you visit by clicking the heart at the top of the page. 

1 month

geoPostcode

Performance and feature

This stores your postcode (or partial postcode) when we ask you for your location.

Just for the time you are on our website or 30 days (you choose this).

geoCoordinates

Performance and feature

This stores your location as a pair of latitude / longitude coordinates.

Just for the time you are on our website or 30 days (you choose this).

reckonerName-history

Performance and feature

This keeps a history of all answers submitted to the ready reckoner.

This is set in the control for each ready reckoner. If you haven't interacted with the ready reckoner for the set amount of days, the cookies are deleted.

reckonerName-content

Performance and feature

This keeps a history of what content cards are clicked on when using the ready reckoner.

This is set in the control for each ready reckoner. If you haven't interacted with the ready reckoner for the set amount of days, the cookies are deleted.

SQ_SYSTEM_SESSION

Required functionality

This used to track user sessions on forms hosted on eservices.hertfordshire.gov.uk

Just for the time you are on our website.


Third party cookies

There are links and content from other sites and services on our website. These sites and services set their own cookies.

Below are a list of cookies that the other sites and services use:

Service namePurposeMore information

Google analytics (_utma/b/c/z)

These are used to compile reports for us on how people use this site.

Cookies of the same names are also used for the same purpose by other websites such as Building FuturesCountryside Management Service and Hertfordshire LIS.

Visit the Google Analytics website for more information about the cookies they use.

You can prevent data from being collected and used by Google Analytics by installing Google's Opt-out Browser Add-on.

Google Translation - googtrans

This cookie is used to remember which language to translate each page into if you have chosen to do so.

It expires at the end of your browser session.

Bing

We use a Bing cookie to track the success of our marketing campaigns and make them more efficient.

Visit Bing to find out more about their cookies.

Google

We use a Google cookie to track the success of our marketing campaigns and make them more efficient.

Visit Google to find out more about their cookies.

Facebook

We have a number of presences on Facebook, which we may link to. Facebook may set some of its own cookies if you follow these links.

Visit Facebook to find out more about their cookies.

Twitter

We have a number of presences and feeds on Twitter, which you may wish to follow or read from this website. Twitter may set some of its own cookies.

Visit Twitter to find out more about their cookies.

YouTube

We have a YouTube channel, which we may link to. YouTube may set some of its own cookies if you follow those links.

Visit YouTube to find out more about their cookies.

Netloan

This ASP.NET_Sessionid cookie is essential for the Netloan secure online payments website to work, and is set when you arrive to the site. This cookie is deleted when you close your browser.

 

HotJar

This session cookie is set to let Hotjar know whether that visitor is included in the sample which is used to generate funnels.

Visit HotJar to find out more about their cookies.

Siteimprove

These cookies are set to help us report on how people are using the site so we can improve it.

Visit Siteimprove to learn more about their cookies.