Skip to content

Principle: To ensure public and private spaces are clearly defined so that conflicts are minimised.

Demarcation between public and private space

All development should front onto and have access from the street or public space. This will create a 'public front' to the development. Dead frontages should be avoided. This includes buildings that present their backs to public space and boundaries between public and private space marked by fences and blank walls. Dead frontages will not only reduce opportunities for overlooking but will also provide opportunities for graffiti and antisocial behaviour.

illustration showing public and private space

Positive aspect: clear distinction between the private and public side of the scheme.

Negative aspect: Blank side walls produce a dead frontage.

Private space should be located to the rear of all types of development and should adjoin onto other private space. Back gardens in particular should back onto other gardens and should avoid adjoining public space, to minimise opportunities for crime.  Rear fencing should be up to 1.8m high to avoid an offender ‘plot hopping’ and escaping along a run of properties.

Dwellings fronting on to the street, Hitchin

A footpath between back gardens creates an enclosed and unappealing space.

Buffer zones/defining defensive space

Ideally dwellings should have front gardens or else a small area to provide a 'stand-off' or buffer zone between the dwelling and the public realm. This buffer zone can be of varying depths and gives a clear indication of where members of the public are welcome and strengthens personal control over private space. A buffer zone can be defined by the use of walls, hedges, railings, fences, etc. This will be particularly important on the edge of developments or where development adjoins open space.

illustration showing buffer zones

Shrubbery provides a subtle distinction between the private and public space.

Railings provide a stronger edge to the buffer zone.

Residential development

Central courtyards, surrounded by buildings, should be clearly defined and designed as private space. This can be achieved by the use of different boundary treatments, entrance/exit gate or barrier system, the use of narrow entrances and/or CCTV. The courtyard should not be a through route for vehicles and pedestrians and should have one entrance and exit.

illustration showing ideal residential development

In the case of flats, communal front and rear entrances to internal communal areas need to be appropriately 'protected', for example with the use of voice and vision CCTV and door access release mechanisms.

Commercial/industrial development

In the case of commercial and nonresidential development there should be a clear distinction between the public front of the building and the private back. Ideally the public front area should cover the main public entrances, visitor parking, etc, while the private back may include staff parking, storage and service yards.

 illustration showing ideal commercial/industrial development

For commercial and non-residential development it may be appropriate to reinforce the distinction between public and private areas through the use of different boundary treatments, surface materials and planting. Open plan designs may therefore not always be suitable.

Checklist

  1. Does the development scheme show a clear and understandable demarcation of public and private space?
  2. Have appropriate boundary treatments/buffer zones been used to distinguish private space and the public realm?
  3. Have back gardens been designed to back onto other private back gardens?
  4. Does all public space serve a purpose and support an appropriate level of legitimate activity?

Rate this page

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.