Part I of II: This post is the first part of a review of the development application process, and common myths and misconceptions surrounding the process. Part II can be found here.
With the advent of our new blog, I will occasionally be sharing my perspective on various current issues as they relate to city planning—an area in which I am very active as Chair of the Planning Committee. Planning has long been my wheelhouse, and I have a mix of history and personal perspective to share on many matters, after 20 years in office.
credit: Ambro |
With the advent of our new blog, I will occasionally be sharing my perspective on various current issues as they relate to city planning—an area in which I am very active as Chair of the Planning Committee. Planning has long been my wheelhouse, and I have a mix of history and personal perspective to share on many matters, after 20 years in office.
THE DEVELOPMENT APPROVAL
PROCESS
Lately, I’ve received
a lot of questions about the approval process for new development proposals,
and the role that our on-staff urban planners play in these procedures. I fear
there is a fair amount of confusion about the process for development plan
approvals, and the role of city staff in the process. Let’s take a tour of the
process.
1. A property owner has an idea.
The
first step: the owner has an idea of how they’d like
to develop their property.
2. The property owner seeks
pre-consultation.
At this
stage, city staff will listen to the landowner’s initial ideas and will share
with him a list of the steps he needs to take before filing his formal
application. Steps may include traffic studies, sun shade studies, or other
neighbourhood info. Some landowners may also consult community associations or
other concerned parties.
3. The property owner files a
formal application, which is reviewed by the planner.
The
formal application becomes publicly available for review. The city’s urban
planner begins the process of reviewing the application package, seeking to
develop her recommendation of approval or rejection for the proposed
development. When she has reviewed all the provided package, studies, and
information, she renders her recommendation to either approve or reject the
project.
4. The property owner makes a
choice.
If the
urban planner rejected the landowner’s proposed plan, he can choose to go one
of two ways: he may forge ahead, without the approval of the planner, in the
hopes of appealing to the Planning Committee...or, he may rethink his plan and
decide to either change his proposal. He may also drop the project altogether.
5. Planning Committee reviews and
votes.
At this
stage, Planning Committee hears from the planner, the property owner, and
sometimes other parties like community associations who may have a vested
interest in the matter. After hearing the presented information and reviewing
the application package, the committee votes on the plan, and the proposal is
either approved or rejected.
Now, what doesn’t happen at the pre-consultation stage is any sort
of approval or rejection by the city staff. At this point, the staff’s role is
simply to provide the landowner with a checklist of all the studies, appeals,
and procedures he will need to provide to be sure his formal application will
be considered ready for review. It seems there is an urban myth
circulating that city staff are able to give approval at this early stage of
the process; this is simply untrue. Staff’s job at this level is to provide the
landowner with the information he needs for application, but not to offer a
favourable or unfavourable recommendation.
credit: Salvatore Vuono |
The stages of application are in place to ensure that all potential developers have their 'ducks in a row', and are prepared with solid research to back their proposals. It's is a step-by-step process, with each stage dependent on the results of the last.
So what happens with the many proposals that are declined at an earlier stage? Why is the public not directly informed of all of these discarded plans? And why is there sometimes a wary attitude towards the procedures and the staff who follow them? Read Part II to learn more.
-Peter
Thanks for this Peter. Whatever disagreements we have about where you or the planning department draw the lines, it's worse when we can't even agree on which lines we're discussing - or who's holding the pen at any given time.
ReplyDeleteSo bravo. The outline above is really helpful for those of us who find our way here to read it - and I'll do my bit to Tweet about it.
But a few suggestions to help those who aren't likely to get here:
1) Develop a standard chart / infographic showing these steps and where a given proposal is in the process. This could be at every consultation as a handout, art board, or a Powerpoint slide.
2) Develop a short "Planning process 101" video: Again, this could be shown at the beginning of a public meeting - particularly one that is likely to be contentious. I think the Carling Bayview CPD meeting we both attended this week was much more productive because the video answered a lot of questions and made its case in a clear and professional package.
3) Facilitation: I think it would be useful to have at least one trained, bilingual facilitator to manage public meetings for the Planning department. This person's job could include the "process education" function, but more importantly to act as an impartial chair to ensure a consistent, structured approach to consultations.
Last night's meeting on the Somerset / Breezehill Claridge proposal was *very* unpleasant for people on both sides of the issue - not only because there were a lot of misinformed questions, but also because the meeting wasn't intelligently planned. It was chaired by one of the developer's hired planners, who was hampered by a) a split focus on making her case professionally and controlling the flow of the meeting, b) the perception that she was "playing for one of the teams" - i.e. that she had a vested interest in the outcome and therefore couldn't be fair, and c) unilingualism.
That's just a few for starters. I'd gladly volunteer a couple hours of professional time if you wanted to host a brainstorming session to develop "planning education" tools.
Thanks again for starting the conversation.
Thanks for the suggestions, Dennis. Some of this is very doable; the infographic or chart idea is something I'll be looking into for sure. -Peter
DeleteThe outline is good. It's more accessible than the one on the City's site: http://ottawa.ca/en/city_hall/planningprojectsreports/planning/dev_review_process/
ReplyDeleteI'm left wondering how I can get my hands on the responses to development applications. I found the search form for the developments themselves (http://app01.ottawa.ca/postingplans/home.jsf?lang=en), but I can't seem to find the planners' responses.
Hi Evan,
DeleteGlad you found the post helpful and clear. In regards to the responses to development applications: if the planner reviewing the application finds that he will not be able to recommend approval, he informs the applicant in a meeting or email. If the applicant continues to carry onward with his application despite the news, only then does the planner write a formal report. Otherwise, the applicant has a chance to revise his application or drop it entirely--in either of these cases, there would be no formal letter from the planner at that point.
Of course, all emails, correspondence, etc between a city staff and an applicant, in relation to a public process, are available by request via MFIPPA.
Hope this helps.
Peter, good blog posts. Re: City Planning I & II. If I may,
ReplyDeleteI would like to mention that the city provides Primer courses that focus on such matters to City Planning, Master Transportation, the OMB and other valuable subjects. It’s two plus years to achieve your certificate, but its free and very well instructed by competent city staff.
Thanks for the reminder, Perry. We love when people take advantage of learning opportunities such as this!
ReplyDelete