Back to top
Last revised January 31, 2018

  1. Step 1: Developer contacts group
  2. Step 2: Group representatives
  3. Step 3: Group and developer meet
  4. Step 4: How to check that your view is supported by your community
  5. Step 5: Group response to developer and suggestions for s106 contributions
  6. Step 6: Remember this is a negotiation
  7. Step 7: Developer response and revised design
  8. Step 8: Record your meetings and discussions
  9. Step 9: Community Involvement Statement (CIS)
  10. Step 10: Keep the Planning Officer and NPN informed
  11. Some points to remember in Pre App CI discussions

Step 1: Developer contacts group

Usually the NPN Administrator will contact your group to let you know that a developer is asking which community group to approach to discuss a development, or that a pre application enquiry has been received by the Planning Authority, who have then notified NPN administrators.

The developer may approach you direct, in which case let the NPN Administrator know at networkadministrator@bristolnpn.net

Sometimes more that one group will be affected by a proposed development and NPN Administrator will arrange that the other groups are given the same opportunity for involvement and suggest which group should be the lead contact for the developer.

Step 2: Group representatives

If your planning group is usually run as an open meeting, or at regular intervals eg monthly, it is better to appoint a small number of your group to meet with the developer as soon as possible and to report back to the group.

Meetings with a small number of people who have knowledge of the site are more effective than large meetings.

Both sides should treat each other with courtesy. Large meetings can become confrontational and are therefore not a good way of working towards an agreement.

If a number of groups are involved, it is a good idea to appoint one of your number to be lead representative for the whole group, to make sure that the discussion is accurately recorded, to liaise with any other groups involved and to chair any subsequent meetings you may have with the developer.

The different groups may have different responses and not agree with each other’s points. Ensure that all the points are recorded.

Step 3: Group and developer meet

At the first meeting you should concentrate on finding out what the developer proposes and agree a timetable for further meetings.

Remind the developer that this group is the sole channel for his Community Involvement responsibilities, and that if there are any other people that he wants to involve they should be invited to the same meetings.

If a number of community groups are involved on a single develop­ment, it is important that they are all at the same meetings to hear the same information and to hear each other’s opinions.

Point out that you would like to sign off the Community Involvement Statement (CIS) before it goes to planning.

It is usually better to avoid expressing opinions directly to the developer at this first meeting be­fore you have had a chance to discuss it within the group and with members of the community most af­fected by the proposed development.

You can ask for drawings from the developer to show the rest of your group.

NPN has a list of professionals (architects and planners) who can assist with understanding of developer proposals and drawing up with response free of charge, if needed.

Step 4: How to check that your view is supported by your community

If the development affects a large number of people, you should consider how the wider community should be informed and their views sought.

You could consider carrying out a survey of local residents and advertising your involvement discussions through your website or local newsletters. Neighbourhood Forums (3 monthly meetings organised by the Neighbourhood Partnership) could be an appropriate vehicle for you to discuss the proposed development, if the timetable permits.

If your group is not composed of those who live immediately around the site, it would be advisable that you check your views with those who do. This might be by circulating a leaflet or letter which lays out your conclusions and asks for their response. However, the view of neighbours may not be the same as that of the group who may be looking at a wider community view. You may need to balance the two views, or tell the developer of the two points of view.

The developer may wish to hold public exhibitions or events. Exhibitions are not usually an effective form of involvement, as they cannot be held at the earliest stage, and therefore cannot be a substitute for the pre application discussion process. However they are a useful way of checking that all the community issues have been identified before the developer makes his Planning Application. It is best to agree the content of the exhibitions and the form of any questions that might be asked beforehand.

At an even earlier stage, before a particular development is being proposed you could draw up a planning statement or spatial plan that sets out the type of development that is acceptable in the neighbourhood, which you get local support for, possibly through a poll, a community organisation with a wide membership base, or through adoption by the Neighbourhood Partnership. This will then be useful for checking your responses to the developer of any site that comes forward in the future.

Step 5: Group response to developer and suggestions for s106 contributions

It is good practice to send the developer a written response within 14 days of the first meeting; remember, tell him what you like about his proposals as well as what you don’t like. The aim should be to work towards a mutually agreeable proposal, and to show the developer that community involvement is useful to him, not just another hurdle.

You can express your opinions about anything that you feel is important but remember that the Planning Authority can only take account of issues that are relevant to Town Planning and in particular the current planning policies and any official town plans that cover the site.

At this stage, you should start to consider if the development might have an impact on the wider area around the site and that will make changes in the locality.

You should also consider the order of priority for changes to be made. For example, dealing with additional traffic on the local road system or requiring more community facilities.

It may be possible to make these changes by asking the Planning Au­thority to get the developer to make a financial contribution to improving local facili­ties or to carry out additional works beyond the site, through a “Section 106” Legal Agreement (See Planning Obligations Supplementary Planning Document on the council web­site for the type of developer contributions that are normally considered)

Step 6: Remember this is a negotiation

Remember and remind the developer, that this is a process of negotiation and that you would welcome further meetings, once he has considered your initial response and that his Community Involvement Statement (CIS) should be signed off by your group representative as an accurate account of the process and what was said.

Step 7: Developer response and revised design

Ask the developer for a further meeting, when he can give you his reply to the group’s initial response.

This meeting should include a discussion of how each of the points in the response will be handled.

Invite the same people to this (and subsequent meetings if they occur) as have already been in­volved in the first response to make sure there is continuity and that each meeting does not have to go over the same ground.

The outcome should be that you have an understanding of what can be changed to accommodate the group’s response and what cannot. This should all be recorded.

Step 8: Record your meetings and discussions

This record can also be offered to the developer to use as the Community Involvement Statement (CIS) to attach to his Planning Application.

If there are any minutes of meetings between you and the developer, make sure that they are accurate since the group or developer may use these minutes as evidence in the CIS.

Step 9: Community Involvement Statement (CIS)

: submitted by the developer with the Planning Application

The developer should draw up his own Community Involvement Statement (CIS) setting out the meetings he has had with the group and send it to the group for them to agree. If the group wishes, it can ask him to him to amend the record before signing it.

If the group or groups can agree the statement, then the lead representative should sign it as a true record.

Note that countersigning the CIS does not mean that you support the proposals; your signature shows that the CIS is a true record of the dates of meetings, who was involved, and what main issues were raised, and if possible, how the design has been changed to respond to those issues.

If you do not agree with the developer’s final CIS, tell the Planning Case Officer at the Council. You can send your own Statement, which can be supported by your record form, telling the Planning Officer about the involvement process and the developer’s response to your views.

The Planning Officer will use this information in his report to the Planning Committee when it considers and decides upon the Planning Application.

Step 10: Keep the Planning Officer and NPN informed

Copy in all your responses to the Planning Officer and NPN Administrator.

If the planning officer is aware of the community’s views at the earliest stage he can use them to guide him in his responses to developer enquiries.

The NPN will monitor Community Involvement cases in order to improve the process.

Some points to remember in Pre App CI discussions

Points to remember

  1. Pre-Application Community Involvement (Pre App CI) is a negotiation. Work with the developer to achieve the best result for the community.
  2. Respect the other party and their point of view. Confrontation is not effective.
  3. Prepare for the meeting by finding out as much as you can about the proposed development site. Contact the Planning Officer and ask to see his Pre-App enquiry response.
  4. Meetings with fewer people, who have done some preparation, will be more effective than meetings with large numbers of people.
  5. If more than one community group is involved in the discussions arrange to work together.
  6. Agree at the beginning of the meeting who are the main contacts and who is recording the discussion.
  7. Be clear at the beginning of the meeting who you represent and how you are going to feedback to the rest of the community, you or the developer should agree who is going to ensure that the near neighbours are kept informed.
  8. Agree the timetable for feedback of responses, future discussions and for the programme up to the proposed Planning Application.
  9. If other Community Involvement techniques, for instance exhibitions and questionnaires, are to be used you should ask to be involved in the content and the format of these events and to see the responses.
  10. Keep the Planning Officer and the NPN Administrator informed of the discussions. You could invite the Planning Officer to your meetings.