|
For community members and developers alike, meeting the minimum requirements may not be enough. Developers know that there are instances when they must notify the public about their plans. (See page 16 for a list of these times.) Community members can also “get by,” attending public hearings on large proposals while paying little heed to numerous other development initiatives that affect them. This too, may be insufficient. Getting those “ducks in a row” requires more than the minimum. To really get the parties talking, it is often best to do more than the minimum. This guide strongly recommends thatfor many types of projectsall parties invest maximum effort in consultation. Development projects and the community will both benefit. WHEN TO CONSULT Consulting often proves beneficial in these situations:
|
When it seems scary to go public because it will make the process harder, that is exactly the time to do it. To try and slide anythingby will only takelonger in the end. Ben Henderson, community member |
||||||||||||||||||||||||||||||||||||
|
WHY CONSULT? Reaps invaluable benefitsEffective consultation almost always:
Prevent potential problemsEffective consultation:
ALL PLAYERS BENEFIT Making the extra effort to consult has high potential to address each player’s day-to-day concerns. Consider some of the various perspectives to understand why.
STANDARD CITY NOTICE AND CONSULTATION PRACTICES The standard notification and consultation practices followed by the City of Edmonton appear in the following chart. Special circumstances and developments may require additional notice or consultation. |
|||||||||||||||||||||||||||||||||||||
|
|||||||||||||||||||||||||||||||||||||