HOA landscaping review works differently in a Whitefish resort community than it does in a typical Kalispell neighborhood, and treating the two towns as interchangeable is a common way homeowners get caught off guard. The difference isn't just paperwork, it's which body has authority over your yard in the first place.
Whitefish: Resort and Planned Communities Lead the Way
Detached single-family homes and duplexes in Whitefish are exempt from the city's Architectural Review Standards, which mainly apply to commercial, industrial, and multi-family projects (City of Whitefish: Architectural Review). That surprises a lot of homeowners who assume the city itself reviews every yard change. In practice, the review layer that actually governs most residential landscaping in Whitefish comes from private HOAs, not the city.
The Design Review Board Model
In HOA communities like Whitefish Mountain Resort, anything that affects the exterior appearance of a home or yard, including landscaping, deck or patio changes, and exterior lighting, goes through a Design Review Board before work starts (Whitefish Mountain Resort: Design Review Board). That's a genuinely different process than a city permit review. It's evaluating fit with the community's design standards, not just code compliance, which means two technically code-compliant landscaping plans can get different answers from the same board depending on how well each fits the neighborhood's established look.
Kalispell: A City-Wide Ordinance, Not a Patchwork of HOAs
Kalispell takes a different approach. Its landscape ordinance, on the books since January 2011, applies city-wide, so a qualifying project needs plan sign-off through the same municipal process whether or not the property happens to sit inside a private community (Kalispell Landscape Ordinance). That's the opposite structure from Whitefish's exemption-plus-private-review model. In Kalispell, the baseline landscaping requirement comes from the city itself, and an HOA layer, where one exists, sits on top of that baseline rather than being the main source of the rule.
Why This Distinction Matters for Homeowners
A homeowner moving from a Kalispell neighborhood to a Whitefish resort community, or the other way around, can reasonably assume the rules work the same way. They don't. In Kalispell, skipping the city's landscape ordinance review on a qualifying project is a city compliance issue from the start. In a Whitefish resort community, a homeowner might be fully exempt from city architectural review and still need HOA design review approval before touching the exterior, because the resort's private governance, not the city, is doing the reviewing.
What Both Systems Actually Look At
Despite the structural difference, the substance of what gets reviewed overlaps more than the process suggests. Site plans showing drainage and grading, plant material and hardscape choices, and how a project fits its surroundings come up in both a Kalispell landscape ordinance review and a Whitefish HOA design review. The main difference is who's asking and what standard they're applying, a city ordinance evaluates code compliance, while an HOA design review board is also weighing aesthetic fit with the rest of the community.
HOA Timelines Run Separately From City Timelines
Because Whitefish's residential HOA review and Kalispell's city ordinance review are structurally different processes, they also don't run on the same clock. A Whitefish HOA design review board typically meets on its own schedule, which can add weeks beyond what a straightforward city permit process would take on a comparable project in Kalispell. Building that HOA-specific timeline into a project schedule, rather than assuming HOA review moves at the same pace as a city department, avoids a scheduling surprise partway through planning.
Properties Without Either Layer
Not every property in either town has an HOA, and not every project in Kalispell qualifies for landscape ordinance review under the ordinance's thresholds. A homeowner outside both frameworks still has to meet base zoning and building code requirements, but skips the additional layer entirely. Confirming whether your specific property carries HOA covenants, and whether your specific project meets Kalispell's ordinance thresholds, is worth doing directly rather than assuming based on the neighborhood.
The Practical Takeaway
Whitefish and Kalispell approach landscaping oversight from close to opposite directions: one exempts most residential work from city review and pushes it to private HOAs where they exist, the other applies a city ordinance city-wide and layers HOA review on top where applicable. Knowing which model applies to your property before you start designing saves a redesign later, since a plan built around Kalispell's ordinance requirements doesn't automatically satisfy a Whitefish HOA's aesthetic standards, and vice versa.
Checking Covenants Before You Buy or Design
HOA covenants and design guidelines are typically recorded documents available through the county or the HOA management company itself, and reviewing them before finalizing a landscaping design, rather than after a plan is already drawn up, avoids designing something that has to be reworked to satisfy a review board. This matters most for homeowners newer to a specific community who haven't yet gone through a design review cycle and don't have a feel for how strictly a given board interprets its own guidelines in practice.
What Iron Peak Does
We check which review layer, city ordinance, HOA design review, or both, applies to a project before we finalize a design, so plans don't need reworking mid-process. Our complete landscape renovations page covers how we handle larger projects that typically trigger review, and our rock & mulch installs page covers material choices that fit both city and HOA aesthetic standards. For the broader permitting picture across both towns, see our permits and HOA guide. We build across Whitefish and Kalispell.
Not sure which review process applies to your property? Get an estimate and we'll help you figure out what your project needs.
