South Kesteven Design Code Draft

Ends on 27 April 2026 (42 days remaining)

Chapter 4. Movement Comment

Movement is how we get around within and between our towns and villages. Just like buildings, new streets should reflect the character of their area and feel like extensions to existing places. This character will be different depending on where the street sits in the street hierarchy and its context and location.

The majority of the public realm within our towns and villages is formed by streets. Their design therefore has a significant impact on new places’ quality and character.

MUST
M1: Lincolnshire County Council guidance on parking, highways and street design must be followed, but this section provides additional detail and principles which focus on the design of places.

As set out in the Local Plan, polict DE1, 'All major development (as defined in the Glossary) must demonstrate compliance with: h. Manual for Streets guidance and relevant Lincolnshire County Council guidance' but this section provides additional detail and principles which focus on the design of places.

South Kesteven is in a privileged position compared to many other authorities. Lincolnshire County Council is an exceptional Highways Authority dedicated to Manual for Streets principles and with low or no commuted sums for many elements.

This means that we have high expectations for exceptional street design and expect to see these elements included in schemes:

  • Street trees;
  • Swales;
  • Raised crossings and Copenhagen crossings;
  • Permeable and block paving;
  • Tight corner radii;
  • Edge lanes; and
  • Shared surface streets.

4.1 Street network

The street network is how our streets are laid out and interconnect. It is important because it can help or hinder how people travel around. In most cases, the street network will outlive the buildings it originally served. A well-connected street network provides a variety of routes for moving around.

MUST
M2: Developments must create a connected and permeable street network and respond to pedestrian desire lines to key destinations, where opportunities exist, by a) knitting in to the existing street network; b) providing more than one point of access to sites; c) avoiding traditional cul-de-sacs (e.g. without modal filters for pedestrians and cyclists);
SHOULD

4.1.0.02

Key foot and cycle paths (such as to existing village or town centres) should be in place before first occupation to ensure the development is accessible for all ages and abilities.
SHOULD

4.1.0.03

Provision should be made to create streets linking potential future neighbouring developments. Futureproofing connectivity opportunities will prevent developments becoming isolated and impermeable.
Fig 4.1: New developments should link into existing streets and design in opportunities for connectivity with future developments.
Fig 4.1: New developments should link into existing streets and design in opportunities for connectivity with future developments.
SHOULD

4.1.0.04

Access streets should not be located at the entrance to sites (parallel to existing streets). Instead, existing streets should be fronted by homes, with parking either as driveways directly accessible from the existing street or with some form of rear parking (courtyard or mews). Existing hedges and trees should be retained where possible and shared driveways serving 2-3 dwellings could help retain frontage landscape.
Fig 4.2: Permitted and unpermitted site entrance designs
Fig 4.2: Permitted and unpermitted site entrance designs

4.2 Street hierarchy

Streets must be designed according to the following hierarchy of users. This Design Code is aimed at achieving this aim with the explicit aim of creating places which put people first.

4.3	Hierarchy of users	A diagram illustrating the hierarchy of users, showing different user groups arranged from highest to lowest creating places which put people first.
Fig 4.3: Hierarchy of users
Fig 4.4: Diagram of street hierarchy showing a primary street (dotted), secondary streets (dashed) and a large network of tertiary streets.
Fig 4.4: Diagram of street hierarchy showing a primary street (dotted), secondary streets (dashed) and a large network of tertiary streets.
MUST
M3: A clear street hierarchy must be created and all streets within the hierarchy must be designed to be different from one another, be characterful, have a clear 'place' funtion and prioratise pedestrians first. Standardised and overly engineered streets with only a 'movement' function must be avoided (for example 5.5m carriageway with 2m pavements each side, standard turning head, concrete kerbs and tarmac surfacing throughout with no additonal features).

4.2.1 Street Typologies

SHOULD

4.2.1.01

The primary street will usually be the primary access route into a development. It should feature:

  • Roadside swales
  • Trees on both sides of the street
  • No front parking to preserve the building line
  • Strong front boundary treatments such as railings and walls
  • Integrated on street visitor parking where possible
SHOULD

4.2.1.02

Shared surface streets are encouraged where the following conditions are met:

  • Where traffic levels will be low
  • Design speeds are 10mph
  • Carriageway width 5m or below
  • Trees, planting or SuDS in build-outs
  • Block, clay or stone paver surface
  • Integrated on street visitor parking where possible
Fig 4.5: Examples of an appropriate and inappropriate shared surface street
Fig 4.5: Examples of an appropriate and inappropriate shared surface street

Edge Lanes are effective in enhancing connectivity within development sites, making it easier to travel around and move through sites and reducing the number of private drives and cul-de-sacs. This can substantially reduce walking distances for pedestrians and also create less need for vehicles (such as refuse collection) to turn into the street.

SHOULD

4.2.1.03

Edge lanes, rather than private drives, should be the default street type on the edge of Suburban and Village Area Type developments.
Fig 4.6: Edge lanes at a new development in Oxfordshire (left) and in a development in Market Deeping (right)
Fig 4.6: Edge lanes at a new development in Oxfordshire (left) and in a development in Market Deeping (right)

Home Zones (or play streets) can be successfully designed in to quieter streets within connected layouts. These are designed primarily to meet the needs of pedestrians, cyclists, children and residents.

CAN

4.2.1.04

Large developments of 50 homes or more could include at least one Home Zone (play street), though more are encouraged.
CAN

4.2.1.05

On new developments, traffic-free play streets or corridors can be created on routes towards schools or other key community facilities.

Fig 4.7: A Home Zone, or play street, at Marmalade Lane in Cambridge
Fig 4.7: A Home Zone, or play street, at Marmalade Lane in Cambridge

4.3 Street design

4.3.1 Raised tables

SHOULD

4.3.1.01

Where raised tables are used, it should be as infrequent long stretches in key locations for placemaking purposes and to benefit pedestrians. Short raised tables which act as speed humps must not be used.

4.3.2 Crossings

SHOULD

4.3.2.01

Raised crossings

  • All pedestrian crossings across primary streets with high pedestrian traffic should be raised crossings.
  • Raised crossings should be constructed with contrasting paving materials or colours to enhance visibility.
  • All junctions between a primary street and lower-order street type should be a raised or Copenhagen crossing, where the pavement is extended across the junction.
Fig 4.8: An example of a standard crossing and a Copenhagen crossing, where the pavement height and materials are extended across the junction, thereby prioritising pedestrians.
Fig 4.8: An example of a standard crossing and a Copenhagen crossing, where the pavement height and materials are extended across the junction, thereby prioritising pedestrians.
4.9	An example of a raised crossing	An image showing a raised pedestrian crossing, with the roadway lifted to pavement level to slow vehicles and improve accessibility.
Fig 4.9: An example of a raised crossing

4.3.3 Turning heads

While layouts should avoid cul-de-sacs as far as is possible, it is recognised that this is not always possible and that turning heads may be required. For example, on small and medium-sized infill sites where it is not possible to create more than one site entrance or any additional active travel routes.

This doesn't mean that conventional turning heads, with wide expanses of tarmac, are necessary or acceptable. Other approaches are possible that integrate good street design and placemaking principles.
Where turning heads are unavoidable, they are to be designed to the following requirement:

SHOULD

4.3.3.01

Conventional turning head patterns (hammerhead etc.) should not be used. They must be hidden and form part of squares or courtyards that have a place function too.

Characteristics to be avoided include:

  • Large expanses of tarmac
  • Leftover space and verges
  • A shape that is unrelated to the building line
SHOULD

4.3.3.02

The turning area should be kept free of parked vehicles. This can be achieved by providing clearly demarcated parking areas.
CAN

4.3.3.03

In line with turning heads being designed as public spaces, they should incorporate the following:

  • Greenery
  • Street trees
  • SuDS
  • Materials other than tarmac (some tarmac is permissible)
Fig 4.10: Turning heads should have a place function in addition to a movement role
Fig 4.10: Turning heads should have a place function in addition to a movement role
Fig 4.11: An example of a turning head which has a stone paved border and functions as a public space in addition to being a turning head.
Fig 4.11: An example of a turning head which has a stone paved border and functions as a public space in addition to being a turning head.

4.4 Walking, wheeling and cycling

Walking and cycling routes offer a healthy and sustainable mode of travel for commuting, leisure or getting to school.

4.4.1 Cycle Infrastructure

Facilities for cyclists need to be comprehensively thought out and continuous, both within the site and in connecting on to key destinations elsewhere.

Key factors to consider:

  • Think of different types of cyclists: commuters (exiting the neighbourhood on a longer journey), leisure cyclists (road bikes, families on wider cycle trip), practical trips (to the shop, school, train station, town centre), children (cycling around the neighbourhood or to school or park);
  • Easy to use: avoid 90 degree bends, missing sections, demarcate crossings over other streets, potential on-street parking conflicts;
  • Design to be attractive to use and encourage all types of people to cycle: ‘would this cycle route design encourage me to cycle?’
SHOULD

4.4.1.01

These elements should be included with cycle infrastructure:

  • Continuous routes where possible
  • Segregated along high traffic streets and primary and secondary streets
  • Minimal conflicts with side streets and driveways
  • Link key destinations such as schools, parks and local centres

4.4.2 Route design

SHOULD

4.4.2.01

Safe walking and cycling routes should connect key amenities within the site and lead to primary routes outside the site boundary.
SHOULD

4.4.2.02

Understanding where pedestrians need and want to cross the street is important in ensuring that amenities can be reached easily and safely. Safe crossings should be created at direct and high traffic crossing points.
SHOULD

4.4.2.03

Frequent places to stop, rest or chat should be provided. Benches should be provided at least every 200m along routes which are expected to be popular.
SHOULD

4.4.2.04

Where blocks are 150m or longer, a well-overlooked walking/cycling route should be introduced through the block to maintain permeability and convenient walking routes.
SHOULD

4.4.2.05

Pavements should be at least 3m wide at key locations such as high streets and outside schools and shops to prevent crowding and overspill onto the carriageway.
CAN

4.4.2.06

Walking and cycling routes can form an independent network, for example by cutting through green spaces.

4.5 Parking

It is a priority for the council that parking be designed well and attractively, balancing parking needs with efficient use of space, high quality placemaking and adherence to the local context.

Parking requirements must be considered at the outset of the design. Insufficient and poorly designed parking can have negative impacts on how streets function, can create cluttered and chaotic environments and can create unnecessary neighbour and community conflicts and divisions.

4.5.1 Car parking principles

SHOULD

4.5.1.01

Standard parking spaces should be the following sizes:
Standard parking space: 5m x 2.4m
On-street parking space: 6m x 2m
MUST
M4: In a driveway, it must be possible to get a wheelie bin of 0.6 metres width past a parked car. It must also be possible for passengers to get in or out of both sides of the car whilst it is parked on the driveway. Single driveway parking spaces between two walls (or other vertical obstructions) must be a minimum of 3.3m wide and double driveways between two walls (or other vertical obstructions) must be a minimum of 6.4m wide and include a buffer strip in a different material or colour of 0.8m between driveways. A plan must be submitted to illustrate this.

Given the approximate width of a car (including mirrors) is around 2.1m, in practice this means the total space required for driveways adjacent to a house will be about 3.3m. For double driveways, it is about 6.4m.

Fig 4.12: An example of border planting between a driveway and house (left) and between driveways (right)
Fig 4.12: An example of border planting between a driveway and house (left) and between driveways (right)
SHOULD

4.5.1.03

Courtyard and mews parking should be sufficiently lit between midnight 6am, though lighting should not enter habitable rooms.
CAN

4.5.1.04

Parking can be peripheral with parking spaces up to 100m from the front door. This can be seen as an opportunity to design homes accessed from pedestrian lanes or footpaths. Such peripheral parking can still be well-enclosed by walls and/or hedges.

4.5.2 Garages and carports

SHOULD

4.5.2.01

Internal garage dimensions should be a minimum of:

  • 3m wide and 6m deep (single)
  • 5m wide and 6m deep (double)
SHOULD

4.5.2.02

Whether integral or detached, garages and carports should be set back by at least one metre from the front elevation of a house. Space should be provided in front of garages and car ports for cars to be parked without overhanging the pavement.
SHOULD

4.5.2.03

In line with Lincolnshire County Council guidance, garages should only be considered as parking provision when they are of a size that will accommodate general storage (such as lawn mowers, hedge trimmers, ladders, bicycles etc) and be wide enough to accommodate modern cars.

Additional codes related to the design and materials of garages and carports is found in Chapter 7. Identity.

4.5.3 Materials

SHOULD

4.5.3.01

At least 50% of the area of driveways, if soil conditions allow, should use permeable surfaces as part of a site’s sustainable drainage strategy. Options include grass between driving strips, block paving, gravel, grasscrete, permeable stone slabs, permeable resin-bound gravel or a combination of these.
CAN

4.5.3.02

Tarmac can be used for driving or walking strips in courtyard or peripheral parking areas.

4.5.4 Parking patterns

This section includes the various permitted parking options in South Kesteven. A well-designed layout will need to use multiple types of parking.

Fig 4.13: A village street which achieves a high-quality layout design due to its balance of a variety of parking patterns.
Fig 4.13: A village street which achieves a high-quality layout design due to its balance of a variety of parking patterns.
Fig 4.14: Examples of flats over garages (FOGS) in Bourne (left) and a small rear courtyard at Cecil Square in Stamford (right)
Fig 4.14: Examples of flats over garages (FOGS) in Bourne (left) and a small rear courtyard at Cecil Square in Stamford (right)

4.5.5 On-plot parking patterns

Parking on plot is usually the most appropriate type of parking in the Suburban and Village Area Types.

4.5.6 Side parking patterns

A flexible configuration suitable for detached, semi-detached or end-of-terrace homes.

A diagram showing different side parking layouts, such as parking aligned with building line, angled
Fig 4.15: Side parking patterns

4.5.7 Front parking patterns

Space efficient and practical configuration which nonetheless makes it more difficult to create a high-quality, well-enclosed streetscape.

MUST

M5: Front parking requirements

  • For detached and semi-detached dwellings, must be screened by a wall, railings or hedge front boundary treatment
     
  • For detached and semi-detached dwellings, must be screened by a wall, railings or hedge front boundary treatment
     
  • For detached and semi-detached dwellings and terraced units where possible, must not occupy entirety of plot width, with the remainder allocated for a front garden;
     
  • End terraces must have parking at the sides if space is needed at the front for landscaping to soften the parking and for paths to access front doors.
     
  • There must be no more than 4 spaces in a row without being broken up by landscaping.
CAN

4.5.7.02

On larger plots, it can be in the form of a front courtyard with a separate entrance and exit.

Fig 4.16: Examples of acceptable front parking, where the driveways do not occupy the entire width of the plot
Fig 4.16: Examples of acceptable front parking, where the driveways do not occupy the entire width of the plot
A diagram showing different front parking layouts, illustrating how vehicles are arranged directly in front of plots with garages set back from front elevation.
Fig 4.17: Front parking patterns
Fig 4.18: Acceptable and unacceptable front parking for a terrace
Fig 4.18: Acceptable and unacceptable front parking for a terrace

4.5.8 Corner house parking patterns

Corner parking is a practical option for corner plots.

MUST

M6: Corner parking requirements:

  • A house, not the driveway or a garage/carport, must be adjacent to the junction
  • Screened by a wall, railings, picket fence or hedge
  • More than one driveway must not be adjacent to each other
Fig 4.19: Permitted and unpermitted types of corner driveways
Fig 4.19: Permitted and unpermitted types of corner driveways

4.5.9 Courtyard parking patterns

Courtyard parking will primarily be in the middle of a block or to the rear of back gardens, though occasionally could be as a small front courtyard area.

SHOULD

4.5.9.01

Courtyard parking should only be used if there are clear placemaking benefits such as creating beautiful streets or spaces not dominated by parking.
MUST

M7: All of the courtyard parking requirements below must be met:

  • Must not include more than 18 parking spaces
  • Must be overlooked by adjacent homes and at least one home (or flat-over garage/FOG) fronting onto the courtyard or at least two if the courtyard includes 12 or more parking spaces
  • Must include street trees, other planting and/or border planting
  • Must provide access to the rear gardens or rear entrances of properties.
  • Entrances must be screened either by homes or walls/hedges
  • Must include a combination of parking spaces, garages, carports and mews houses
  • Boundary treatment must be limestone or brick walls or hedges, not fences, following the materials codes in 7. Identity
CAN

4.5.9.03

The courtyard entrance can be accessed through a gateway or overcroft.

A view of a small rear courtyard with room for parking and planting.
Fig 4.20: A small rear courtyard
Fig 4.21: An example of a small front courtyard serving a group of semi-detached and detached houses
Fig 4.21: An example of a small front courtyard serving a group of semi-detached and detached houses

4.5.10 Mews parking patterns

Mews streets containing homes and rear parking interlinked with the street network can be very effective, creating overlooked streets and ‘places’ rather than simply just parking areas.

MUST

M8: All of the mews parking requirements below must be met:

  • If mews provides parking for adjacent homes, access must be provided to the rear gardens or rear entrances of properties
     
  • Must include small homes, flats over garages/FOGs, carports and/or garages with at least some ground floor windows
     
  • Must include street trees, border planting or other planting, with sufficient space given for trees to mature
     
  • In the Village Area Type, mews must have an informal, rural character with more planting and a curved or meandering street design
SHOULD

4.5.10.02

Mews should:

  • Have at least two entrances
  • Mews longer than 50 metres should include additional pedestrian permeability.
Fig 4.22: An example of an informal mews suitable for a Suburban or Village location
Fig 4.22: An example of an informal mews suitable for a Suburban or Village location

4.5.11 Peripheral parking patterns

Peripheral parking are parking areas on the edge of a block or on the edge of developments. allowing for pedestrian-priority areas at the cost of a longer walk to the front door.

SHOULD

4.5.11.01

Peripheral parking requirements:

  • Well landscaped with street trees and/or other planting
  • Buildings or high quality walls (per the codes in Identity) should provide a strong built form edge to the parking area.
A diagram illustrating a peripheral parking layout, showing well landscaped parking requirements with trees or planting.
Fig 4.23: Peripheral parking diagram

4.5.12 Visitor on-street parking patterns

The use of on-street parking can allow for more urban streets, or act as an overflow to prevent dense developments becoming too dominated by driveways.

SHOULD

4.5.12.01

On-street, unallocated parking can help create orderly streets and design-out problematic pavement parking. Space for on-street parking varies depending on other parking arrangments and design components of the street. Street should be designed with the aim of providing some on-street parking. The requirements below should be met:

  • A footpath should be present on the outside of the parking space to facilitate easy access to both sides of the vehicle.
     
  • On-street parking should be broken up by street trees every 3 spaces or fewer.
     
  • In the Village Area Type only, on-street parking should be informal, appearing as a widening of the street.
     
  • If at a 45 degree angle, parking should only be on one side of the street
Fig 4.24: Formal on-street visitor parking (left) and informal Village Area Type visitor on-street parking (right)
Fig 4.24: Formal on-street visitor parking (left) and informal Village Area Type visitor on-street parking (right)
Fig 4.25: An example of acceptable on-street visitor parking
Fig 4.25: An example of acceptable on-street visitor parking

4.5.13 Parking for blocks of flats

Creating larger parking areas for blocks of flats is key to doing "gentle density" well, especially in Town Centre, Local Centre and Urban Neighbourhood Area Types.

MUST

M9: All of the parking requirements for blocks of flats below must be met:

  • Car parks serving blocks of flats must be screened by buildings
  • Must include street trees and border planting
  • Walls that complement the building that the car park serves
Fig 4.26: Examples of acceptable parking to serve blocks of flats
Fig 4.26: Examples of acceptable parking to serve blocks of flats
Fig 4.27: An appropriate courtyard parking serving flats in Stamford
Fig 4.27: An appropriate courtyard parking serving flats in Stamford

4.5.14 Cycle parking

Provision of adequate cycle parking is a key driver in encouraging active travel plans will have to be submitted to detail cycle storage areas and paths.

SHOULD

4.5.14.01

A plan should be provided to illustrate convenient and appropriate cycle storage locations for all dwellings
SHOULD

4.5.14.02

Secure cycle parking should be as easily accessible as car parking, ensuring that it is Easy, Accessible, Sociable and Timely (EAST). This means it must be accessible without the need to move multiple bikes or squeeze past cars.
SHOULD

4.5.14.03

Developments should provide cycle storage in front gardens, garages, back garden sheds, side entrances (where appropriate), garages or protected communal areas such as in apartment blocks.
SHOULD

4.5.14.04

Public bike parking should be located prominently as close to amenities as possible, be well overlooked and ensure that a clear 2m minimum pavement width is maintained.

4.5.15 Electric Vehicle (EV) charging

This code acknowledges that EV charging technology will continue to develop. This guidance applies to all new build (residential and commercial) development. The retrofitting of EV chargers or provision in the adopted highway should be discussed with officers on a case-by-case basis. Further guidance is available from Lincolnshire County Council: https://www.lincolnshire.gov.uk/roads-transport/electric-vehicles

SHOULD

4.5.15.01

Electric vehicle (EV) charging points should not obstruct pedestrian walkways or intrude on pedestrian or cycling space.
SHOULD

4.5.15.02

For new housing developments with garages and off-street parking, each dwelling should have an on-plot charge point or be futureproofed to include one. This should typically be wall mounted.

4.6 Public transport

Access to public transport is key to providing people with choice for everyday journeys beyond their immediate neighbourhood, especially for those not able to drive. Good access to public transport helps reduce reliance on the private car.

SHOULD

4.6.0.01

Shared mobility should be considered early in the design. These may be particularly appropriate in rural areas with low ridership where traditional bus services may not be practical.
SHOULD

4.6.0.02

Streets that will accommodate bus routes should be fairly direct without too many frequent turns and allow buses to remain in forward gear (for example, a looped route within a new area of housing).
SHOULD

4.60.03

Cycle parking and stands should be provided at bus stops in key locations, as this can enlarge the catchment area of a bus stop.
For instructions on how to use the system and make comments, please see our help guide.
back to top back to top