An Institutional Ethnography Exploring Developers’ Perspectives of the Municipal Development Approvals Process
Bibliographic record
Abstract
Contemporary planning literature describes what should be in municipal plans, but does not describe implementation as fully. Municipal planning authorities create plans to guide development, and also operate approvals processes to regulate it, but a question remained: What might explain any drift between what the plans call for and the final built outcome? In this institutional ethnography, the municipal planning and development processes are explored through the experiences of developers in Calgary, Canada. This research highlights the ways in which 10 key informant developers and/or planning consultants interact with municipal texts, as well as with the public, and workers at City Hall, in order to develop land in the context of the Municipal Development Plan. What is ostensibly a process dominated by technical review is actually heavily influenced by political and financial risks and influences. Developers described struggling with: (1), municipal policy proliferation; (2), policy vagueness and inter-policy misalignment; (3), unwritten-yet-enforced expectations coupled with municipal obsession with minutiae at the cost of the big picture; (4), a lack of municipal leadership to proactively amend plans; (5), the ways in which individual members of the public, and community associations, are engaged, both in policy and in specific development applications; and (6), redundant, expensive, and lengthy processes including (a), paying for plan creation, (b), having to fund infrastructure, (c), going through Growth Management Overlay removal, (d), amending area plans, (e), enduring various pre-applications, and then (f), finally getting to the start of the multi-stage formal approvals processes. Several factors contribute to a drift between the Municipal Development Plan, related policies, and built form outcomes. Ten problems and solutions resulting from the ethnographic analysis of the key informant interviews are presented in the conclusion. Planners, developers, elected officials, and/or members of the public, may find this research helpful in better understanding how the municipal land development approvals process functions from insiders’ experiences.
Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.
How this classification was reachedexpand
Full frame machine prediction
Teacher imitationNot calibrated prevalence, not ground truth. Human validation pending. The Gemma side is a direct model label for every work in the frame, read from the title-only record. The Codex side is a classifier learned from the 10,348 direct Codex labels and calibrated to design-weighted sample rates; fields without enough sample support carry no Codex call. Candidate is the union of the two sides; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels.
Distilled classifier scores by category (both heads)
| Category | Codex | Gemma |
|---|---|---|
| Metaresearch | 0.015 | 0.021 |
| Meta-epidemiology (narrow) | 0.001 | 0.001 |
| Meta-epidemiology (broad) | 0.001 | 0.000 |
| Bibliometrics | 0.003 | 0.003 |
| Science and technology studies | 0.014 | 0.021 |
| Scholarly communication | 0.009 | 0.006 |
| Open science | 0.002 | 0.009 |
| Research integrity | 0.002 | 0.004 |
| Insufficient payload (model declined to judge) | 0.003 | 0.000 |
Machine scores (provisional)
The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.
Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.
score_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from itClassification
machine, unvalidatedMachine predicted; a candidate call from one source (direct Gemma or distilled Codex), not a consensus.
How this classification was reached, model by model and score by score, is at the end of the page under "How this classification was reached".