A Minnesota City Has More Room to Rezone Your Whole Neighborhood Than to Deny You One Conditional Use Permit

August 21, 2026 · David J.S. Madgett

Most people assume the deck is stacked the same way in every land use fight: the city holds all the cards, the applicant begs, and a court will not second-guess a local body on local matters. That is half right and half backwards.

Minnesota law sorts zoning decisions into two categories, and the deference a court gives runs opposite to what most applicants expect. When a city rezones — an act of policy affecting the public generally — it gets wide latitude. When the same council rules on a single variance or conditional use permit, it is applying standards it already wrote to one parcel, and the Supreme Court has said in plain terms that the authority “is less circumscribed by judicial oversight when it considers zoning or rezoning than when it considers a special use permit or a variance.” Honn v. City of Coon Rapids, 313 N.W.2d 409, 417 (Minn. 1981).

Three consequences follow, and none of them is obvious:

  • A conditional use permit is not a favor. The use is already declared acceptable in the district; the applicant’s job is to satisfy the ordinance’s standards, and a denial is arbitrary if it does.
  • A variance is the harder ask, not the easier one, even after the Legislature relaxed the standard in 2011.
  • Behind both sits a 60-day clock that turns municipal silence into a grant. The statute does not say the city must act within 60 days. It says failure to deny within 60 days is approval.

Why is a variance harder to get than a conditional use permit?

Because a variance asks the city to excuse compliance with a rule, while a CUP asks it to apply a rule it already wrote.

Honn drew the line: “Our case law distinguishes between zoning matters which are legislative in nature (rezoning) and those which are quasi-judicial (variances and special use permits). Even so, the standard of review is the same for all zoning matters, namely, whether the zoning authority’s action was reasonable.” 313 N.W.2d at 416–17. What changes is not the label but the content of reasonableness:

In legislative zoning, the municipal body is formulating public policy, so the inquiry focuses on whether the proposed use promotes the public welfare. In quasi-judicial zoning, public policy has already been established and the inquiry focuses on whether the proposed use is contrary to the general welfare as already established in the zoning ordinance.

Id. at 417. A rezoning survives if there is any rational basis for it. A CUP denial has to be tethered to the standards in the ordinance itself.

The variance is quasi-judicial too, but the substantive test the applicant must satisfy is stiffer, and the statute puts a hard ceiling on what a variance can ever accomplish.


Did the 2011 “practical difficulties” amendment actually loosen the standard?

It loosened it, but far less than the phrase suggests — and the three elements it substituted are conjunctive.

Before 2011, Minn. Stat. § 462.357, subd. 6, required “undue hardship,” defined to mean the property “cannot be put to a reasonable use if used under conditions allowed by the official controls.” Cities had been reading that through Rowell v. Board of Adjustment of Moorhead, a 1989 Court of Appeals decision treating it as a “reasonable manner” test. In 2010 the Supreme Court threw that out:

We are unable to interpret the statutory language to mean anything other than what the text clearly says — that to obtain a municipal variance, an applicant must establish that “the property in question cannot be put to a reasonable use if used under conditions allowed by the official controls.” … [U]nless and until the legislature takes action to provide a more flexible variance standard for municipalities, we are constrained by the language of the statute to hold that a municipality does not have the authority to grant a variance unless the applicant can show that her property cannot be put to a reasonable use without the variance.

Krummenacher v. City of Minnetonka, 783 N.W.2d 721, 732 (Minn. 2010).

The Legislature took that invitation in under a year. Act of May 5, 2011, ch. 19, §§ 1–2, rewrote both the county statute (§ 394.27, subd. 7, where it struck “hardship” and the old “practical difficulties or particular hardship” framework) and the municipal statute (§ 462.357, subd. 6, where it struck “undue hardship”), substituting a single defined “practical difficulties” standard in each. The act was effective the day following final enactment; it was signed May 5, 2011. That is the current municipal text:

Variances shall only be permitted when they are in harmony with the general purposes and intent of the ordinance and when the variances are consistent with the comprehensive plan. Variances may be granted when the applicant for the variance establishes that there are practical difficulties in complying with the zoning ordinance. “Practical difficulties,” as used in connection with the granting of a variance, means that the property owner proposes to use the property in a reasonable manner not permitted by the zoning ordinance; the plight of the landowner is due to circumstances unique to the property not created by the landowner; and the variance, if granted, will not alter the essential character of the locality. Economic considerations alone do not constitute practical difficulties.

Minn. Stat. § 462.357, subd. 6(2). The county version in § 394.27, subd. 7, is worded almost identically.

Read what actually changed. The first element moved from cannot be put to a reasonable use to proposes to use the property in a reasonable manner not permitted by the ordinance — a genuine relaxation, and the one Krummenacher had foreclosed. The second and third elements did not move at all. Uniqueness not created by the landowner and no alteration of the essential character of the locality were in the pre-2011 definition of undue hardship and are in the post-2011 definition of practical difficulties, word for word.

That matters, because in ordinary practice the second element is where variance applications die. A landowner who subdivides a parcel into lots too small to build on, or buys a lot knowing the setback problem, has created the plight. The “reasonable manner” relaxation does nothing for that applicant. And the two threshold conditions in the first sentence — harmony with the ordinance’s purposes, consistency with the comprehensive plan — are independent requirements that sit on top of the three-element test, not inside it.

There are two statutory carve-outs worth knowing. Practical difficulties “include, but are not limited to, inadequate access to direct sunlight for solar energy systems.” And variances “shall be granted for earth sheltered construction as defined in section 216C.06, subdivision 14, when in harmony with the ordinance” — one of the very few places in Minnesota zoning law where a variance is mandatory rather than discretionary.


Can a city grant a variance for a use the ordinance doesn’t allow?

No. This is a flat prohibition, and it is the single most important limit in the subdivision.

The board of appeals and adjustments or the governing body as the case may be, may not permit as a variance any use that is not allowed under the zoning ordinance for property in the zone where the affected person’s land is located.

Minn. Stat. § 462.357, subd. 6(2). The county statute says the same thing: “No variance may be granted that would allow any use that is not allowed in the zoning district in which the subject property is located.” Minn. Stat. § 394.27, subd. 7.

So there is no such thing as a use variance in Minnesota. If the goal is a use the district does not permit, the variance track is closed no matter how compelling the hardship — the paths are a conditional use permit (if the ordinance lists the use as conditional), a rezoning, or an ordinance amendment. Applicants routinely file variance applications that are actually use requests and lose on a ground that had nothing to do with the merits.

One narrow exception appears in the same sentence block: the board or governing body “may permit as a variance the temporary use of a one family dwelling as a two family dwelling.”


What conditions can a city attach — and is “rough proportionality” a real limit?

The 2011 act added a proportionality requirement that did not exist before, and it is easy to miss because it sits at the very end of a long subdivision.

The board “may impose conditions in the granting of variances. A condition must be directly related to and must bear a rough proportionality to the impact created by the variance.” Minn. Stat. § 462.357, subd. 6(2); accord § 394.27, subd. 7. The pre-2011 text had said only that conditions could be imposed “to insure compliance and to protect adjacent properties.” Chapter 19 struck that phrase and replaced it with the nexus-and-proportionality language borrowed from federal exactions doctrine.

That is a live argument. A city that grants a five-foot setback variance and conditions it on a dedication, a cash payment, or an unrelated site improvement now has a statutory standard to answer to, not merely a general reasonableness gloss.

Conditions on a conditional use permit are governed differently. Section 462.3595 does not carry the proportionality sentence; it provides that a CUP “shall remain in effect as long as the conditions agreed upon are observed,” and requires that a certified copy of the permit, including the legal description, be recorded with the county recorder or registrar of titles. Minn. Stat. § 462.3595, subds. 3, 4. The county counterpart is broader still, permitting “such additional restrictions or conditions as [the approval authority] deems necessary to protect the public interest, including but not limited to matters relating to appearance, lighting, hours of operation and performance characteristics.” Minn. Stat. § 394.301, subd. 2.

Note the recording requirement. A CUP that was never recorded still binds the parties, but a later purchaser searching title may never find the conditions that limit the use — a recurring problem in due diligence on income property.


What does a city have to show to deny a conditional use permit?

Two things, in order: a legally sufficient reason, and a factual basis in the record for it.

The Supreme Court set out the framework in RDNT, LLC v. City of Bloomington, 861 N.W.2d 71 (Minn. 2015): “There are two steps in determining whether a city’s denial was unreasonable, arbitrary, or capricious. First, we must determine if the reasons given by the city were legally sufficient. Second, if the reasons given are legally sufficient, we must determine if the reasons had a factual basis in the record.” Id. at 75–76 (citing C.R. Invs., Inc. v. Village of Shoreview, 304 N.W.2d 320, 325 (Minn. 1981)).

The burden sits with the applicant, and it sits there because of the statute. Section 462.3595, subd. 1, provides that conditional uses “may be approved by the governing body or other designated authority by a showing by the applicant that the standards and criteria stated in the ordinance will be satisfied.” RDNT read that as dispositive: “Thus, the burden was on RDNT to show that it could satisfy the standards specified by ordinance.” 861 N.W.2d at 78.

But carrying that burden is supposed to end the inquiry:

If a conditional use permit applicant demonstrates to the governing body that imposing a reasonable condition would eliminate any conflict with the ordinance’s standards and criteria, it follows that the governing body’s subsequent denial would be arbitrary.

Id. (citing Zylka v. City of Crystal, 283 Minn. 192, 196, 167 N.W.2d 45, 49 (1969), for the proposition that “[a] denial would be arbitrary … if it was established that all of the standards specified by the ordinance as a condition to granting the permit have been met”).

Where applicants lose is on the evidence. RDNT itself is a cautionary case: the city denied a senior-housing expansion on traffic grounds even though its own engineer conceded the streets were not at capacity, and the Supreme Court affirmed. Reviewing courts do not weigh conflicting expert evidence — the function is “not to weigh the evidence, but to review the record to determine whether there was legal evidence to support the zoning authority’s decision.” Id. at 76 (quoting Barton Contracting Co. v. City of Afton, 268 N.W.2d 712, 718 (Minn. 1978)). The city had traffic studies, engineer testimony, and specific neighbor accounts of speeding and crosswalk violations. That was enough. As the opinion put it, “[t]he fact that a street could physically handle more traffic does not determine whether the neighborhood or the public could handle more traffic.” Id. at 77.

The lesson for an applicant is that the fight is won at the hearing, not on appeal. Generalized neighborhood opposition will not sustain a denial; specific neighborhood testimony, corroborated by a study, will.


Does a vague ordinance standard help the city or hurt it?

It hurts the city. This is the most counterintuitive rule in Minnesota CUP law, and cities regularly get it backwards.

An ordinance clause like “the proposed use will not be injurious to the surrounding neighborhood or otherwise harm the public health, safety and welfare” is legally sufficient — a city may deny on that ground. But RDNT then quoted a rule from 1973 that cuts the other way: “the ‘absence of more express standards makes denial of a special-use permit more, not less, vulnerable to a finding of arbitrariness.’” 861 N.W.2d at 76 (quoting Hay v. Township of Grow, 296 Minn. 1, 6, 206 N.W.2d 19, 22–23 (1973)). The court’s own conclusion followed directly: the ordinance was legally sufficient, “but [we] will examine the factual basis for the City’s findings more closely than we would under a less subjective standard.” Id.

So a council that leans on a catch-all welfare clause has bought itself heightened factual scrutiny. A council that identifies the specific ordinance criterion the application fails is on much safer ground.


Do the reasons have to be written down at the time?

Yes, and this is where local bodies lose cases they should win.

Honn’s fifth procedural directive: “The municipal body need not necessarily prepare formal findings of fact, but it must, at a minimum, have the reasons for its decision recorded or reduced to writing and in more than just a conclusory fashion. By failing to do so, it runs the risk of not having its decision sustained.” 313 N.W.2d at 416. The court had already quoted Zylka for the sharper version: “the failure of the council to record any legally sufficient basis for its determination at the time it acted made a prima facie showing of arbitrariness inevitable.” Id. (quoting Zylka, 283 Minn. at 198, 167 N.W.2d at 50).

A conclusory record is not curable after the fact. In Earthburners, Inc. v. County of Carlton, 513 N.W.2d 460 (Minn. 1994), a county board denied a CUP with a single stated reason — “public testimony presented in opposition.” The Supreme Court held the record wholly inadequate and directed that on remand “the board must articulate the reasons for its ultimate decision, with specific reference to relevant provisions of its zoning ordinance,” and if it denies, “must articulate the board’s specific basis for the denial, i.e., an explanation of the applicant’s failure to satisfy the ordinance criteria.” Id. at 463. The court also warned that it has “been reluctant to allow local boards an opportunity after the fact to substantiate or justify earlier decisions.” Id.

The statute now codifies part of this for cities. Under Minn. Stat. § 15.99, subd. 2(c), a multimember governing body that denies a request “must state the reasons for denial on the record and provide the applicant in writing a statement of the reasons for the denial,” adopted no later than the next meeting and in any event “before the expiration of the time allowed for making a decision,” and it “must be consistent with the reasons stated in the record at the time of the denial.”


What happens if the city just says nothing?

The request is approved. Not “deemed submitted,” not “subject to further action” — approved.

Minn. Stat. § 15.99, subd. 2(a):

[A]n agency must approve or deny within 60 days a written request relating to zoning, septic systems, watershed district review, soil and water conservation district review, or expansion of the metropolitan urban service area for a permit, license, or other governmental approval of an action. Failure of an agency to deny a request within 60 days is approval of the request. If an agency denies the request, it must state in writing the reasons for the denial at the time that it denies the request.

Three features of the section deserve attention.

“Relating to zoning” is broad. In 500, LLC v. City of Minneapolis, 837 N.W.2d 287 (Minn. 2013), the Supreme Court held that an application to a heritage preservation commission for a certificate of appropriateness qualified. The phrase “a written request relating to zoning” is unambiguous and “refers to a written request that has a connection, association, or logical relationship to the regulation of building development or the uses of property.” Id. at 291. The court rejected the city’s attempt to limit the section to requests “explicitly authorized by an applicable zoning ordinance or statute,” because that would add words to an unambiguous statute. Id. Applicants and cities alike underestimate how many approvals this reaches.

A failed vote is a denial only if the “no” votes explain themselves. Section 15.99, subd. 2(b): “When a vote on a resolution or properly made motion to approve a request fails for any reason, the failure shall constitute a denial of the request provided that those voting against the motion state on the record the reasons why they oppose the request.” A 3–3 tie in silence is not a denial. If the 60 days run out behind it, the request is approved by operation of law. The same paragraph adds that a denial by failed motion “does not preclude an immediate submission of a same or similar request.”

The extension must be taken before the clock runs out. Subdivision 3(f) allows the agency to extend “before the end of the initial 60-day period by providing written notice of the extension to the applicant,” and the notice “must state the reasons for the extension and its anticipated length, which may not exceed 60 days unless approved by the applicant.” An extension announced on day 62 is not an extension. The applicant may also request an extension in writing under subdivision 3(g).

Two more mechanics matter in practice. The 60 days start on receipt of “a written request containing all information required by law or by a previously adopted rule, ordinance, or policy of the agency, including the applicable application fee,” and if the submission is incomplete, “the 60-day limit starts over only if the agency sends written notice within 15 business days of receipt of the request telling the requester what information is missing.” Minn. Stat. § 15.99, subd. 3(a). And an approval with conditions counts as a timely response: subdivision 3(c) provides that the agency meets the deadline if it can document that the response was sent within 60 days, and failure to satisfy conditions “may be a basis to revoke or rescind the approval … and will not give rise to a claim that the 60-day limit was not met.”

Section 15.99 also carries its own carve-outs. Subdivision 2(a) begins “[e]xcept as otherwise provided in this section, section 462.358, subdivision 3b, or 473.175, or chapter 505” — so subdivision review, Metropolitan Council review, and plats operate on their own timelines. Subdivision 3(d) and (e) extend the deadline where another statute, federal law, or court order requires a prior process, or where prior approval from a state or federal agency is required.


Where do you file — district court or the Court of Appeals?

This is the trap, and the answer turns on who said no, not on what they said.

For a city or town, Minn. Stat. § 462.361, subd. 1, provides that any person aggrieved by an ordinance, rule, decision, or order of a governing body or board of adjustments and appeals “may have such ordinance, rule, regulation, decision or order, reviewed by an appropriate remedy in the district court.” Honn worked through what “appropriate remedy” means: declaratory judgment for a rezoning (certiorari is not appropriate for legislative acts), with mandamus and, for a narrow quasi-judicial legal question, certiorari available in the right case. 313 N.W.2d at 414, 416.

For a county board of adjustment, Minn. Stat. § 394.27, subd. 9, is explicit and carries a deadline that the municipal statute does not: decisions on variances and administrative appeals “shall be final except that any aggrieved person or persons … shall have the right to appeal within 30 days, after receipt of notice of the decision, to the district court in the county in which the land is located on questions of law and fact.”

For a county board of commissioners deciding a conditional use permit, the answer is different again — certiorari to the Court of Appeals. The Supreme Court explained why in a footnote that is worth reading twice:

The general rule adopted by this court in Honn is that even quasi-judicial zoning actions should be reviewed in district court, not by certiorari review in the court of appeals. This case falls, however, within a narrow exception to that general rule for decisions by county boards. This exception exists because the legislature has not provided for judicial review of zoning decisions of county boards in the district court as it has for zoning decisions of cities, towns and even county boards of adjustment.

Interstate Power Co. v. Nobles County Board of Commissioners, 617 N.W.2d 566, 574 n.5 (Minn. 2000). The footnote compares § 462.361, subd. 1, and § 462.352, subd. 11 (defining “governing body” as only a city council or town board), and § 394.27, subd. 9, with § 394.301, which authorizes county CUP proceedings but provides no district court review — and corrects an earlier statement in In re Livingood as “overly broad.”

Certiorari is unforgiving. Minn. Stat. § 606.01: “No writ of certiorari shall be issued, to correct any proceeding, unless such writ shall be issued within 60 days after the party applying for such writ shall have received due notice of the proceeding sought to be reviewed thereby. The party shall apply to the court of appeals for the writ.” Miss that window on a county CUP denial and there is no district court fallback, because “[d]istrict courts do not have subject-matter jurisdiction over claims that must be resolved in a certiorari appeal.” Zweber v. Credit River Township, 882 N.W.2d 605, 609 (Minn. 2016).

Two refinements from Zweber are worth carrying. Legislative decisions — those with broad applicability that “affect the rights of the public generally” — can be reviewed by filing a summons and complaint in district court. Id. And derivative constitutional claims are not automatically swallowed by the certiorari rule: “certiorari review is exclusive when a claim requires an inquiry into the validity of a quasi-judicial decision,” but claims that do not require the district court to examine the validity of the decision — a takings claim seeking only damages, an equal protection claim spanning years of conduct — may proceed in district court. Id. at 611. The Court of Appeals on certiorari “cannot weigh evidence as a trier of fact.” Id. at 612.

A claim that the agency blew the 60-day deadline goes to district court regardless. The Supreme Court explained that a § 15.99 claim “is not a challenge to a decision — quasi-judicial or otherwise. Rather, it is a challenge to a city’s failure to render a decision, which necessarily provides no decision for the court of appeals to review by writ of certiorari.” 500, LLC, 837 N.W.2d at 289 n.2.

One defense to plan around: § 462.361, subd. 2, lets a municipality raise failure to exhaust local procedures, and if the court so finds “it shall require the complaining party to pursue those remedies unless it finds that the use of such remedies would serve no useful purpose under the circumstances of the case.”


What is the standard of review, and what do you get if you win?

The formulation courts actually apply is a four-part one:

[W]hether the municipality “was within its jurisdiction, was not mistaken as to the applicable law, and did not act arbitrarily, oppressively, or unreasonably, and to determine whether the evidence could reasonably support or justify the determination.”

Krummenacher, 783 N.W.2d at 727 (quoting In re Stadsvold, 754 N.W.2d 323, 332 (Minn. 2008)). Municipalities have “broad discretionary power” in considering whether to grant or deny a variance. Id. (citing VanLandschoot v. City of Mendota Heights, 336 N.W.2d 503, 508 (Minn. 1983)).

The remedy is where expectations most often break. Winning does not always mean getting the permit:

In cases where a variance has been denied, the general rule is that “[i]f the zoning authority’s decision is arbitrary and capricious, the standard remedy is that the court orders the permit to be issued.” But there is an exception to this general rule “when the zoning authority’s decision is premature and not necessarily arbitrary.”

Id. at 732–33 (quoting Stadsvold, 754 N.W.2d at 332, 333). Where the board applied the wrong legal standard, the usual disposition is a remand for reconsideration under the correct one — which is exactly what happened in Krummenacher, in Stadsvold, and in Earthburners. An applicant who wins on “you used the wrong test” typically wins a second hearing, not a permit. An applicant who wins on “you had no factual basis” is in much better position to get the permit ordered.


How much of this changes for counties?

Less than the separate chapter suggests, with three real differences.

The substantive variance standard is now identical. The 2011 act rewrote § 394.27, subd. 7, in parallel with § 462.357, subd. 6, replacing the old “practical difficulties or particular hardship” framework — the one the Supreme Court had parsed in Stadsvold, distinguishing a less rigorous “practical difficulties” test for area variances from a more rigorous “particular hardship” test for use variances — with the same three-element practical-difficulties definition that now governs cities. The county board of adjustment has “the exclusive power to order the issuance of variances,” § 394.27, subd. 7, and the same rough-proportionality limit on conditions.

The procedural rules are tighter on paper. Section 394.27, subd. 6, requires that “[t]he reasons for the board’s decision shall be stated in writing,” and provides that an appeal from an administrative official’s determination “stays all proceedings in furtherance of the action appealed from” unless the board certifies imminent peril to life or property. Subdivision 8 requires that a certified copy of any board order — on an appeal or a variance — be recorded with the county recorder or registrar of titles, with the legal description.

The forum and deadline differ, as set out above: a 30-day district court appeal from a board of adjustment under subdivision 9, but certiorari to the Court of Appeals within 60 days under § 606.01 for a county board’s CUP decision.

If you are counting days, count them from the right trigger, under the right statute, for the right body. In this corner of the law the wrong forum is fatal in a way the wrong argument usually is not.


For neighbors on the other side of the table, the same rules run in reverse: a variance granted on a record that never addresses uniqueness, or a CUP approved without findings tied to the ordinance criteria, is vulnerable. Related issues come up in easement and access disputes, in special assessment appeals under chapter 429 when a municipal improvement follows the approval, in property tax appeals under chapter 278 when a use restriction affects value, and in claims against a city where notice and immunity rules apply.


Madgett Law, LLC represents Minnesota property owners, applicants, and neighboring landowners in variance and conditional use permit proceedings before city councils, boards of appeals and adjustment, planning commissions, and county boards, and in the judicial review that follows — declaratory judgment actions under Minn. Stat. § 462.361, district court appeals under § 394.27, subd. 9, certiorari petitions in the Minnesota Court of Appeals, and claims under the 60-day rule of Minn. Stat. § 15.99. We build the hearing record with the appeal in mind, because in land use practice the record made at the council table is usually the only record there will ever be. Call 612-470-6529 or send us a message.

Sources: Minn. Stat. § 462.357, subd. 6(2) (municipal variances — threshold requirements of harmony with the ordinance and consistency with the comprehensive plan; three-element “practical difficulties” definition; “[e]conomic considerations alone”; solar-access inclusion; mandatory earth-sheltered variance; prohibition on use variances; temporary two-family use; conditions must be “directly related to and must bear a rough proportionality to the impact created by the variance”); § 462.352, subd. 11 (definition of “governing body”); § 462.3595, subd. 1 (applicant’s burden to show ordinance standards satisfied), subd. 3 (duration), subd. 4 (recording of CUP with legal description); § 462.361, subd. 1 (district court review by appropriate remedy), subd. 2 (exhaustion defense); § 394.27, subd. 5 (board of adjustment authority), subd. 6 (written reasons; stay on appeal), subd. 7 (county variances; exclusive power; identical practical-difficulties definition; rough proportionality), subd. 8 (recording of orders), subd. 9 (30-day appeal to district court on questions of law and fact); § 394.301, subds. 1–2, 4 (county CUPs; applicant’s showing; conditions; recording); § 15.99, subd. 1(b)–(d) (definitions of agency, request, applicant), subd. 2(a) (60-day deadline; failure to deny is approval; written reasons at time of denial), subd. 2(b) (failed motion as denial only with reasons stated on the record), subd. 2(c) (multimember body’s written statement of reasons), subd. 3(a) (start of the clock; application fee; 15-business-day incompleteness notice), subd. 3(c) (approval with conditions; documented timely response), subd. 3(d)–(e) (extensions for required prior processes and approvals), subd. 3(f)–(g) (agency extension before the end of the initial 60 days, capped at 60 days absent applicant approval; applicant-requested extension); § 606.01 (60-day certiorari deadline; application to the Court of Appeals), all at revisor.mn.gov. Act of May 5, 2011, ch. 19, §§ 1–2 (H.F. 52), 2011 Minn. Laws (amending Minn. Stat. 2010, §§ 394.27, subd. 7, and 462.357, subd. 6; deleting “undue hardship” and “hardship,” inserting “practical difficulties,” and replacing the prior conditions language with the rough-proportionality sentence; effective the day following final enactment; signed May 5, 2011), at revisor.mn.gov/laws/2011/0/19. Honn v. City of Coon Rapids, 313 N.W.2d 409, 414, 416–17 (Minn. 1981) (remedies for review under § 462.361; requirement that reasons be recorded in more than conclusory fashion; quoting Zylka v. City of Crystal, 283 Minn. 192, 198, 167 N.W.2d 45, 50 (1969), on prima facie arbitrariness; legislative versus quasi-judicial review; zoning authority “less circumscribed” on variances and special use permits than on rezoning). Krummenacher v. City of Minnetonka, 783 N.W.2d 721, 727, 732–33 (Minn. 2010) (standard of review, quoting In re Stadsvold, 754 N.W.2d 323, 332 (Minn. 2008); “broad discretionary power,” citing VanLandschoot v. City of Mendota Heights, 336 N.W.2d 503, 508 (Minn. 1983); rejection of the Rowell “reasonable manner” standard under the pre-2011 statute; remedy and remand). RDNT, LLC v. City of Bloomington, 861 N.W.2d 71, 75–78 (Minn. 2015) (two-step CUP review, citing C.R. Investments, Inc. v. Village of Shoreview, 304 N.W.2d 320, 325 (Minn. 1981); vaguer standards make denial “more, not less, vulnerable,” quoting Hay v. Township of Grow, 296 Minn. 1, 6, 206 N.W.2d 19, 22–23 (1973); courts do not weigh the evidence, quoting Barton Contracting Co. v. City of Afton, 268 N.W.2d 712, 718 (Minn. 1978); capacity versus livability; applicant’s burden under § 462.3595 and Zylka on arbitrary denial). Earthburners, Inc. v. County of Carlton, 513 N.W.2d 460, 463 (Minn. 1994) (inadequate record; remand requiring reasons with specific reference to ordinance provisions; reluctance to permit after-the-fact justification). Interstate Power Co. v. Nobles County Board of Commissioners, 617 N.W.2d 566, 574 & n.5 (Minn. 2000) (legislative versus quasi-judicial acts; county board CUP decisions reviewable only by certiorari because no statute provides district court review). 500, LLC v. City of Minneapolis, 837 N.W.2d 287, 289 n.2, 291 (Minn. 2013) (“relating to zoning” construed broadly; § 15.99 claims belong in district court). Zweber v. Credit River Township, 882 N.W.2d 605, 609, 611–12 (Minn. 2016) (certiorari exclusive where a claim requires inquiry into the validity of a quasi-judicial decision; legislative decisions reviewable by summons and complaint; appellate court cannot weigh evidence). Case texts read at static.case.law (Caselaw Access Project). This article is general legal information about Minnesota law. It is not legal advice, it does not create an attorney–client relationship, and no particular outcome is promised or implied.

Get new guides by email

Plain-English guides to Minnesota law, sent when a new one is written. No schedule, nothing for sale.

Used only to send these guides. Unsubscribe from any email. This is attorney advertising — subscribing does not create an attorney–client relationship.

← All news & articles