How Neighbouring Municipalities Plan Growth Across a Shared Boundary

How neighbouring municipalities plan growth across a shared boundary

An intermunicipal development plan, usually shortened to IDP, helps neighbouring Alberta municipalities coordinate long-term planning around a shared boundary. Depending on the plan, it may address future land use, road connections, utilities, drainage, environmental matters, application referrals, communication, and dispute resolution.

For landowners and applicants, the essential distinction is between policy direction and property approval. An IDP can influence how a municipality evaluates a later rezoning, subdivision, statutory-plan amendment, or development proposal. It does not, by itself, rezone a parcel, approve a project, assign an infrastructure budget, or complete an annexation.

Its practical effect depends on the current adopted plan, official maps, amendments, referral provisions, and the bylaws governing the municipality where the property is located. This is an Alberta-specific, non-legal guide; similarly named instruments elsewhere may work differently.

What an intermunicipal development plan is

In Alberta municipal practice, an intermunicipal development plan is a high-level statutory plan jointly developed and adopted by two or more neighbouring municipalities. It creates a shared framework for planning matters affecting lands around a common boundary. Alberta municipal summaries consistently identify Section 631 of the Municipal Government Act as the principal legislative reference, although those summaries are not substitutes for the current statute when determining exact requirements or exemptions (Strathcona County’s IDP overview).

A typical two-municipality IDP is approved by both participating councils. A regional plan may involve three or more municipalities and require action by each participating council. Because adoption mechanics and legal requirements are consequential, council approval should be verified through current municipal bylaws rather than inferred from a project webpage or draft document.

The practical need for an IDP arises because a municipal boundary is a legal dividing line, but growth and infrastructure do not necessarily stop there. For example:

• A road on one side may need to connect with a road on the other.
• Development may affect a shared watershed or drainage system.
• New homes or businesses may create demand for transportation, water, wastewater, or emergency access.
• Utility corridors may need to cross the boundary.
• An industrial, commercial, agricultural, or residential use near the boundary may affect properties in both municipalities.
• Environmental features and hazards may extend across municipal jurisdictions.

An IDP gives the municipalities a common framework for anticipating and discussing these issues. It may establish expectations about:

• Where future urban, rural, industrial, commercial, residential, or recreational growth should occur
• How development near the boundary should relate to existing or planned uses across it
• Which transportation and utility corridors should be protected or coordinated
• When one municipality circulates an application or planning proposal to the other
• How municipal administrations and councils communicate
• How disagreements are escalated
• How the plan is monitored, reviewed, amended, or replaced

The plan remains high-level because it generally deals with direction and coordination rather than the design of an individual site. It may identify a preferred growth pattern or future-land-use concept without deciding the locations of individual buildings, lots, local roads, drainage facilities, or permit conditions.

Municipal descriptions of Alberta’s requirements are not identical. Some discuss exemptions or arrangements under which adjoining municipalities do not adopt an IDP. Anyone who needs a definitive answer about whether a plan is legally required, what it must contain, or which exemption applies should consult the current Municipal Government Act, the municipalities’ bylaws, and qualified Alberta advice.

Coordination and conflict reduction are intended purposes of an IDP. They are not guaranteed outcomes. Whether a plan works effectively depends on its wording, the circumstances of individual proposals, and how participating municipalities implement it.

Where an IDP applies and what it usually covers

An IDP does not necessarily cover every parcel in each participating municipality. The municipalities establish a geographic plan area, generally including selected lands on both sides of their shared boundary. Wheatland County explains that the precise area is agreed upon by the municipalities and includes lands along both sides of the boundary (Wheatland County’s IDP resource page).

The width and shape of the area can vary. One plan may cover a relatively narrow fringe beside an urban municipality. Another may include a wider corridor associated with highways, utilities, environmental features, long-term growth, or potential annexation discussions. A plan involving several municipalities may address a broader regional area.

Distance from the boundary is not enough.

Subjects commonly addressed

Although every plan is different, recurring subjects include:

• Existing and future land use
• Long-term growth patterns
• Compatibility between uses near the boundary
• Transportation routes and road connections
• Water, wastewater, stormwater, and other servicing
• Drainage and watershed management
• Environmental features and constraints
• Municipal interfaces and transition areas
• Application and statutory-plan referrals
• Communication between municipal administrations
• Intermunicipal committees or oversight arrangements
• Dispute-resolution procedures
• Implementation responsibilities
• Monitoring, review, amendment, repeal, and replacement

Some IDPs are concise and primarily procedural. Others contain detailed future-land-use maps, growth staging, infrastructure concepts, environmental policies, or specific referral triggers.

Rocky View County describes its IDPs as addressing current and future land uses, servicing infrastructure, shared transportation corridors, municipal interfaces, and intermunicipal processes. It also uses a 20-year vision to describe its plans, but that is a local description—not a universal duration for every Alberta IDP (Rocky View County’s explanation of IDPs).

Plan Areas and Notification Areas are not always the same

Some documents distinguish between an area governed by substantive planning policies and a broader area used for notifications or information sharing. This structure should not be assumed to exist in every IDP.

The draft Canmore–Municipal District of Bighorn IDP illustrates the distinction. It identifies an IDP Area, where mutually relevant development policies would apply, and a Notification Area, where specified planning documents and redistricting matters would be shared. It also addresses watershed protection, wildlife considerations, transportation, utilities, and steep-creek hazards as examples of issues that may cross or affect both sides of a boundary (draft Canmore–M.D. of Bighorn IDP).

That document must be treated strictly as a draft example. Its council-adoption fields are blank, and the file is identified as a draft prepared for an open house. It illustrates possible plan content but has not been established here as an adopted and operative plan.

For a particular property, check every relevant map and definition. A parcel could be close to the boundary but outside the adopted Plan Area. A broader referral or Notification Area could also apply to proposals outside the core policy area.

What an IDP does—and what it does not do

An IDP establishes policy direction and coordination processes. Municipal planners and councils may refer to it when evaluating land-use changes, preparing recommendations, or considering whether a proposal fits the municipalities’ long-term plans.

That influence can be significant, but it should not be confused with direct project approval.

Matter	What an IDP can do	What requires another decision or agreement
Future land use	Identify preferred uses, growth areas, transition areas, or compatibility expectations	A rezoning, statutory-plan amendment, subdivision approval, or development permit
Existing zoning	Provide policy relevant to future applications	An amendment to the applicable land-use bylaw
Individual development	Guide municipal review and identify cross-boundary considerations	Approval by the authority responsible for the application
Subdivision	Establish servicing, access, compatibility, environmental, or referral policies	A subdivision decision under the applicable municipal and provincial framework
Roads and utilities	Identify corridors, connections, constraints, or coordination needs	Engineering, capital approval, land acquisition, construction authorization, and operating arrangements
Project funding	Identify matters that may require future cooperation	A budget decision, financing approval, or separate funding agreement
Detailed site planning	Set high-level direction	An area plan, concept plan, site plan, engineering package, or other detailed approval
Cost sharing	Recognize a need for shared infrastructure or services	A servicing, revenue-sharing, cost-sharing, or other intermunicipal agreement
Annexation	Discuss long-term growth or establish a framework for future discussions	A separate annexation process and the applicable government decisions
Referrals	Identify proposals to be sent to the neighbouring municipality for comment	A decision by the municipality or authority with jurisdiction
Disputes	Establish communication and escalation procedures	Further action under the adopted plan, applicable law, or another agreement

It does not ordinarily rezone property

An IDP ordinarily does not itself change a parcel’s land-use district or the uses currently permitted by the local land-use bylaw.

The IDP can nevertheless influence a later rezoning. If an owner applies to change land from agricultural to industrial use, for example, planners may compare the proposal with the IDP’s future-land-use map and compatibility policies.

The County of Grande Prairie describes this distinction directly: an IDP establishes a long-term land-use concept without changing currently permitted uses, but that concept may be considered when a rezoning is proposed. It also states that local development permits, subdivisions, and rezonings remain subject to County decision-making and the County’s land-use bylaw (County of Grande Prairie’s IDP guidance).

An IDP should therefore be reviewed alongside—not instead of—the current zoning and land-use rules.

It does not approve or budget a project

An IDP is not a development permit for a business, housing project, industrial site, subdivision, road, or utility. It also does not assign a construction budget simply because it identifies infrastructure that may be desirable.

A policy supporting a future road connection may allow municipalities to preserve and coordinate around the concept. Delivering the road may still depend on engineering, land acquisition, capital approval, procurement, construction authorization, and a separate agreement about costs or operations. The City of St. Albert similarly describes IDPs as high-level instruments that do not approve or assign budgets to individual development projects (City of St. Albert’s IDP overview).

It does not replace detailed planning or cost-sharing agreements

A broad future-land-use map does not settle the precise locations of buildings, lots, local roads, parks, drainage facilities, or utility lines. Those details may require an area structure plan, concept plan, subdivision design, site plan, engineering study, or development permit.

Likewise, coordination does not automatically allocate costs. If two municipalities agree that a utility connection or road is desirable, they may still need a separate agreement covering design, construction, ownership, operation, maintenance, financing, or revenue.

It does not complete annexation

Annexation changes a municipal boundary. An IDP may discuss long-term urban growth, identify an area of municipal interest, or establish expectations for future annexation discussions. It does not itself transfer land between municipalities.

Landowners should distinguish among:

1. Land shown as a possible long-term growth area
2. Land identified for possible annexation discussions
3. An active annexation proposal
4. A completed and effective boundary change

These stages are not equivalent.

It is also inaccurate to describe every IDP as “merely advisory” or as enforceable in exactly the same way for every issue. Its practical and legal effect depends on the adopted wording, applicable legislation, related bylaws, and the particular decision under consideration.

How an IDP can affect a property or development application

An IDP is most likely to matter when a property falls within one of its mapped areas and a proposal engages a subject addressed by the plan.

Proximity to the boundary alone does not establish coverage. Begin by confirming that the parcel is inside the current adopted Plan Area or another mapped area to which referral or notification provisions apply.

How planners may use the plan

When reviewing a proposal, planning staff may consider questions such as:

• Does the proposal match the IDP’s future-land-use direction?
• Could it conflict with an existing or planned use across the boundary?
• Does its access fit a planned regional road network?
• Could servicing interfere with long-term infrastructure plans?
• Could drainage or stormwater affect land in the neighbouring municipality?
• Are there environmental, watershed, habitat, flood, erosion, or hazard concerns?
• Must the application be circulated to the neighbouring municipality?
• Does the proposal also require an amendment to another plan or the land-use bylaw?

The municipality with jurisdiction over the property remains responsible for its local development, subdivision, and rezoning decisions under the applicable framework. The neighbouring municipality may provide comments through a referral process. The precise weight, procedure, and consequences of those comments must be determined from the adopted IDP and governing documents.

A hypothetical boundary subdivision

Suppose a landowner applies to subdivide property beside a shared municipal boundary.

The IDP might require the application to be sent to the neighbouring municipality. Its planners could comment that:

• An internal road should align with a future cross-boundary connection.
• Stormwater should not be discharged onto adjoining land.
• Private servicing could interfere with a future utility corridor.
• Residential lots should be separated from an existing industrial use.
• A drainage study or traffic analysis is needed.
• The design should preserve access to a planned regional route.

Staff in the municipality where the property is located would consider those comments with the land-use bylaw, municipal development plan, applicable area plans, technical information, and other requirements. The referral might lead to revised plans, requests for further information, or an intermunicipal disagreement. The actual decision-making authority and available procedures must be confirmed from the controlling documents.

Referral periods are plan-specific

The unadopted Canmore–M.D. of Bighorn draft illustrates a proposed circulation system for certain planning documents, redistricting applications, and subdivisions. It gives the receiving municipality an ordinary 21-day response period unless more time is requested. That proposed period belongs to the draft and is not an Alberta-wide deadline (draft Canmore–M.D. of Bighorn IDP).

Another plan may establish a different period, distinguish among application types, allow extensions on different terms, or use different geographic triggers. Do not calculate a project schedule from another municipality’s plan.

Property-review checklist

Before buying, designing, financing, or applying:

1. Confirm the plan’s status. Determine whether it is adopted, proposed, under review, paused, amended, repealed, or replaced.
2. Find the adopting bylaws. Do not treat an unsigned PDF or project page as proof of adoption.
3. Locate the parcel on the official map. Check its legal description and parcel boundaries against the map legend.
4. Identify every applicable mapped area. Plan, policy, referral, and Notification Areas may have different functions.
5. Read the related policies. Do not rely on map colours or labels alone.
6. Review referral provisions. Identify which applications are circulated and what response period applies.
7. Check amendments. A later bylaw may have changed the map, designation, wording, or process.
8. Review the land-use bylaw. Confirm current zoning, permitted and discretionary uses, and development standards.
9. Add other applicable plans. Check the municipal development plan and any area or site-specific plan.
10. Ask the responsible planning department to confirm your interpretation.

This guide is general information, not legal, planning, development, or property-specific advice. Professional advice may be appropriate where rights, deadlines, substantial investment, or conflicts between documents are involved.

How an IDP moves from proposal to adopted plan

The details vary among municipalities, but a practical IDP lifecycle may include:

1. Research and issue identification The municipalities collect information about land use, growth, transportation, servicing, environmental conditions, and relevant plans.

2. Intermunicipal work Councils, administrations, planners, committees, or consultants identify shared interests and possible disagreements.

3. Draft preparation A draft is developed with maps, policies, referral provisions, dispute procedures, and implementation clauses.

4. Public and stakeholder engagement Municipalities provide the participation opportunities established for the project.

5. Revision The draft may be revised in response to technical work and public or stakeholder input.

6. Public hearing Alberta municipal sources describe public involvement before adoption, and the supplied finalized example included a formal public hearing. The exact requirements should be verified against current legislation and the municipalities’ procedures.

7. Approval by participating councils Each participating municipality takes the required council action.

8. Implementation Staff begin applying the adopted policies, maps, referrals, and communication procedures.

9. Monitoring and review The municipalities assess whether the plan remains suitable as conditions change.

10. Possible amendment, repeal, or replacement The required procedure should be checked in the legislation, adopting bylaws, and administration provisions of the plan.

Historical Wembley example

The Town of Wembley and County of Grande Prairie process illustrates engagement during draft preparation. A 2023 notice described a second open house and invited plan-area landowners, ratepayers, residents, and interested groups to learn about the proposal, ask questions, and comment (Town of Wembley’s historical IDP page).

That notice is historical, not a current invitation or evidence of adoption. The County of Grande Prairie’s later IDP page reported the Wembley project as on hold. Anyone investigating its present status should check the latest records from both municipalities.

Finalized Tri-Area example

The Tri-Area IDP involving the City of Medicine Hat, Cypress County, and the Town of Redcliff is a finalized multi-municipality example. The reported 2024–2025 update included research, two rounds of community and stakeholder engagement, analysis, a joint public hearing on February 12, 2025, and approval by the participating councils. The final 2025 plan was then made available (Medicine Hat’s Tri-Area project page).

This is one documented process, not a mandatory sequence or timetable for every Alberta IDP.

Red Deer example

The City of Red Deer reports that its IDP with Red Deer County was adopted by both councils in 2025, covers land immediately adjacent to the city, and is discussed jointly each year (City of Red Deer’s IDP page).

Annual joint discussion is a feature of that arrangement, not a universal statutory review interval. Another IDP may establish a different schedule or identify events that prompt a review.

Status labels matter

Before relying on an IDP webpage or PDF, distinguish among:

• Draft: Working text that has not received final approval
• Proposed: Presented for consideration but not yet adopted
• Under development: Research, drafting, or engagement is continuing
• Paused or on hold: Work has stopped temporarily or indefinitely
• Adopted: Approved through the applicable municipal process
• Amended: Changed through one or more later instruments
• Consolidated: Updated to incorporate amendments in one document
• Under review: Being reconsidered but not necessarily replaced
• Repealed or replaced: No longer the controlling plan
• Exempt arrangement: The municipalities rely on an applicable exemption or alternative arrangement described in current law

A document can remain online after its status changes. A file called “final” may be a final draft rather than an adopted plan. Verify adopting bylaws, council records, amendments, and the latest official status page.

How an IDP relates to other planning documents and agreements

An IDP is one component of a broader planning framework. A property may also be affected by a regional plan, municipal development plan, area plan, land-use bylaw, and application-specific decisions.

The supplied municipal sources do not establish a universal order of legal precedence for every possible conflict. If documents appear inconsistent, consult the current legislation, adopting bylaws, interpretation provisions, and responsible municipality.

Instrument	Primary role	What it does not replace
Intermunicipal development plan	Coordinates high-level planning and procedures around a shared boundary	Local zoning, individual approvals, detailed site plans, annexation decisions, or cost-sharing agreements
Municipal development plan	Sets broad growth and development direction for one municipality	Parcel-specific zoning or individual development approval
Land-use bylaw	Establishes districts, permitted and discretionary uses, development standards, and approval rules	Broader intermunicipal planning
Detailed or site-specific plan	Provides more detailed land-use, road, servicing, open-space, or design direction	Required rezoning, subdivision, engineering, or development approvals
Annexation process	Considers and authorizes a municipal boundary change	Ordinary land-use planning or development approval
Servicing or cost-sharing agreement	Assigns operational, financial, construction, or maintenance responsibilities	High-level land-use coordination
Intermunicipal Collaboration Framework	Provides a separate form of intermunicipal collaboration referenced alongside IDPs by some municipalities	The IDP’s shared-boundary land-use policies

Municipal development plans

An IDP has an intermunicipal focus, coordinating matters affecting an agreed boundary area or other cross-boundary geography.

Both may matter to an application. For example, an IDP might identify an area for coordinated industrial growth while the municipal development plan sets the municipality’s broader industrial strategy. Applicable regional and area plans may also need to be considered.

Land-use bylaws

An IDP does not automatically rewrite those rules.

The practical distinction is:

• The land-use bylaw addresses what uses and standards currently apply.
• The IDP may indicate whether a different long-term use is supported or how a proposed change should be coordinated.

A parcel can therefore retain its current zoning while an IDP identifies a different future direction. That direction may become important when the owner applies for rezoning, subdivision, or development.

Detailed plans and site planning

An IDP may show a broad residential, industrial, agricultural, commercial, or environmental area. It generally does not determine the exact locations of lots, buildings, local roads, parks, drainage facilities, or utilities.

Those details may require an area structure plan, concept plan, site plan, engineering work, subdivision application, or development permit.

Annexation documents

An IDP can address possible annexation or long-term urban expansion without authorizing a boundary change. An annexation agreement, application, recommendation, or final decision has a different function.

A future-growth designation should not be described as completed annexation. Nor should annexation itself be treated as automatic zoning or development approval.

Servicing and cost-sharing agreements

An IDP may identify where roads, water, wastewater, emergency access, drainage works, or other infrastructure should be coordinated. It need not determine who designs, builds, owns, operates, maintains, or pays for that infrastructure.

Those questions may require separate servicing, funding, revenue-sharing, or cost-sharing agreements.

Intermunicipal Collaboration Frameworks

Some Alberta municipalities discuss IDPs and Intermunicipal Collaboration Frameworks, or ICFs, together. They are separate intermunicipal instruments, although their subject matter may be related.

For example, Parkland County refers to establishing both IDPs and ICFs with neighbouring former members of the Edmonton Metropolitan Region Board after the board’s disbandment on March 31, 2025 (Parkland County’s intermunicipal planning page). That local context does not establish a precise province-wide division of responsibilities between every IDP and ICF.

Where documents overlap or appear inconsistent, review their current wording and obtain municipal or legal interpretation rather than assuming that one always controls the other.

Referrals, disagreements, and ongoing implementation

Adoption is not the end of an IDP’s role. The plan becomes relevant when applications, policy amendments, infrastructure proposals, or new information engage the shared interests identified by participating municipalities.

Application referrals

A common IDP function is to identify when one municipality circulates material to another. Depending on the plan, referrals may involve:

• Municipal development plan amendments
• Area structure plans or other statutory plans
• Land-use bylaw amendments and rezonings
• Subdivision applications
• Development permit applications
• Transportation or infrastructure proposals
• Proposals affecting environmental or hazard areas

Referral triggers may depend on geography, application type, proposed use, distance from the boundary, or potential intermunicipal effect. A plan may also identify the information to be sent and the time available for a response.

The receiving municipality might support the proposal, raise concerns, request information, recommend revisions, or use the plan’s dispute process. The effect of silence, late comments, or unresolved objections should never be assumed; it must be checked in the controlling plan and applicable procedures.

A neutral disagreement model

Dispute-resolution provisions recur in municipal descriptions of Alberta IDPs, but there is no basis for assuming every plan uses an identical formula. A general process might involve:

1. Planning staff identifying a potential inconsistency or cross-boundary concern
2. Staff from both municipalities exchanging information
3. Senior administrators or an intermunicipal committee discussing unresolved issues
4. Escalation under the specific IDP’s dispute-resolution provisions
5. Any further action authorized by the adopted plan, applicable legislation, or another agreement

This is a process model, not a statement of mandatory statutory steps. Review the controlling IDP for actual referral periods, notice requirements, committee roles, decision procedures, and escalation provisions.

The Canmore–M.D. of Bighorn draft illustrates one proposed arrangement: an Intermunicipal Collaboration Committee made up of councillors from both municipalities would oversee implementation and monitoring, while each municipality would retain decision-making autonomy within its jurisdiction. Because that document is an unadopted draft, the arrangement cannot be assumed to be operative or representative of other plans.

Monitoring and review

Conditions can change after an IDP is adopted. Monitoring may identify a need to reconsider policies because of:

• Revised growth forecasts
• Major development proposals
• New road or utility plans
• Updated environmental or hazard information
• Changes to municipal or regional plans
• Annexation
• Legislative or policy changes
• Repeated referral disagreements
• Amendment requests from a participating municipality

These are possible reasons for review, not universal amendment triggers. The plan itself should be checked for monitoring responsibilities, review schedules, and amendment procedures.

An IDP is intended to improve coordination and reduce the potential for conflict. It would go too far to claim that adoption necessarily prevents disputes or accelerates approvals. A referral can identify issues earlier, but it may also require additional analysis and discussion.

How to find and verify the IDP that matters to you

The safest approach is to verify the plan through both municipalities sharing the boundary. Do not rely solely on a search result, third-party map, real-estate listing, or one municipal summary.

Step 1: Identify the municipalities

Determine:

• Which municipality contains the parcel
• Which municipality is across the relevant boundary
• Whether more than two municipalities participate
• Which municipality will receive the proposed application

Use the legal description and official municipal mapping where possible. A mailing address or community name may not make jurisdiction clear.

Step 2: Search both official websites

Look for pages titled:

• Intermunicipal Development Plan
• Statutory Plans
• Long-Range Planning
• Planning Policies
• Plans and Bylaws
• Regional Planning
• Current Planning Projects

One municipality may provide the newest project-status page while another hosts the adopting bylaw or consolidated plan.

Step 3: Collect the controlling documents

Look for:

• Adopting bylaws from every participating municipality
• The complete IDP
• Maps and schedules
• Amendment bylaws
• A consolidated copy, if available
• Repeal or replacement bylaws
• The current project-status page
• Council records where status remains unclear

A webpage listing municipal partners does not prove that a particular parcel is covered. It may also omit amendments or replacement documents.

Step 4: Verify status

Check dates, signatures, adoption fields, bylaw numbers, amendment records, and current project notices. In particular, distinguish among draft, proposed, adopted, amended, consolidated, paused, under review, repealed, and replaced documents.

The examples in this guide show why status matters:

• The Tri-Area IDP involving Medicine Hat, Cypress County, and Redcliff was reported as finalized and approved in 2025.
• The Red Deer–Red Deer County IDP was reported as adopted by both councils in 2025.
• The Wembley–County of Grande Prairie material records a historical draft and engagement process; a later County page reported the project as on hold.
• The Canmore–M.D. of Bighorn document used here is an unverified draft with blank adoption fields.

Status should still be rechecked immediately before relying on any of these examples.

Step 5: Locate the parcel on every relevant map

Compare the parcel with:

• The Plan Area
• Any Notification Area
• Future-land-use designations
• Referral areas
• Transportation corridors
• Servicing areas
• Environmental or hazard overlays
• Long-term growth or annexation-interest areas

Read the legend, scale, notes, definitions, and accompanying policies. A map colour rarely provides the whole answer.

Step 6: Read the connected policies

Focus on:

• Current and future land-use compatibility
• Growth sequencing
• Transportation and access
• Water, wastewater, and stormwater
• Drainage and environmental constraints
• Technical-study requirements
• Referral triggers
• Response periods
• Dispute procedures
• Amendment provisions

For a potential purchase, consider both current use rights and policies that could affect a future change.

Step 7: Check related municipal documents

Add the following to the review:

• Municipal development plan
• Applicable area structure or redevelopment plan
• Other local or concept plans
• Land-use bylaw and zoning map
• Transportation and servicing plans where relevant
• Current annexation or planning-project pages

Do not assume a universal hierarchy. Identify what each document says about the parcel and ask the municipality how they are interpreted together.

Step 8: Determine what applies if there is no IDP

The absence of an IDP does not necessarily mean there is no boundary-planning policy. Another local framework may apply.

For example, the County of Grande Prairie says that areas adjoining municipalities without an IDP are addressed through rural-urban fringe policies in its municipal development plan. That is a local approach, not a general rule for every Alberta municipality.

Step 9: Ask the responsible planning department

Useful questions include:

• Is this the current consolidated plan?
• Has it been adopted by every participating council?
• Is my parcel inside the Plan Area or only a Notification Area?
• What future-land-use designation applies?
• Which applications must be referred?
• What response period applies?
• Have amendments changed the map or policy?
• Which municipal development plan, area plan, and land-use bylaw provisions also apply?
• Would the proposal require one or more plan or bylaw amendments?

Frequently asked questions

Does an intermunicipal development plan change my property’s zoning?

Ordinarily, no. Municipal guidance describes an IDP as setting long-term direction without itself changing a parcel’s current land-use district or permitted uses. A zoning change is handled through the applicable municipal bylaw process.

The IDP can still affect a later application. If you seek rezoning, subdivision, development approval, or a statutory-plan amendment, planners may compare the proposal with the IDP’s future-land-use and compatibility policies. Confirm current rights through the land-use bylaw as well as the adopted IDP.

Can an IDP identify land for possible annexation without annexing it?

Yes. An IDP may discuss future growth, identify an area of interest, or establish a framework for possible annexation discussions. It does not itself change the municipal boundary.

A future-growth designation, an annexation-interest area, an active proposal, and a completed annexation are different stages. The applicable annexation process and current government records must be reviewed separately.

Who approves an intermunicipal development plan?

Municipal sources describe a two-municipality IDP as being adopted by both participating councils. A plan involving more municipalities requires the corresponding council action from its participants.

Verify approval through adopting bylaws and current municipal records. A polished PDF, unsigned adoption page, or the word “final” in a file name is not enough.

How can residents and landowners participate before an IDP is adopted?

Participation opportunities may include open houses, surveys, information sessions, stakeholder meetings, written comments, and a public hearing. The exact opportunities and deadlines are project-specific.

Municipal sources describe public involvement before adoption, and St. Albert’s overview states that its IDPs will include a formal public hearing before finalization. Check both municipalities’ current notices, engagement pages, council agendas, and hearing information rather than relying on historical announcements.

How do I know whether an IDP applies to my property?

Confirm the parcel against the maps in the current adopted plan and all applicable amendments. Do not rely only on proximity to the boundary.

Check the Plan Area, any Notification or referral area, the future-land-use designation, related policies, and the land-use bylaw. Then ask the municipality responsible for the property to confirm the interpretation for your parcel and proposed application.

The practical takeaway

An intermunicipal development plan is best understood as a cross-boundary decision framework, not an individual project approval or an automatic change to property rights. Its practical effect comes from the current adopted text, official maps, amendments, referral procedures, and related municipal bylaws.

For a property or proposal, follow a simple sequence: identify the participating municipalities, verify the plan’s current status, locate the parcel on official maps, read the applicable land-use and referral policies, review the other governing plans and bylaws, and confirm your interpretation with the municipality responsible for the application.