What Minnesota courts have said about design discretion

The most useful recent Minnesota decision on architectural control is Warner v. Pines of North Oaks Home Owners' Association, No. A25-1129, decided by the Court of Appeals on 17 February 2026.³ It is nonprecedential — under Minn. R. Civ. App. P. 136.01, subd. 1(c), persuasive authority only, not binding.

The Warners bought the last undeveloped lot in a 99-lot North Oaks subdivision and submitted a design the board rejected three times as inconsistent with the neighbourhood's one-storey villa character. They argued the board could apply only the written architectural standards in the rules.

The court disagreed. Where the covenants make the written standards a floor — the association “shall establish the criteria for approval, which shall include and require, at a minimum” — and state a purpose of a “homogenous residential community,” a board may deny a design for incompatibility with existing homes even though the written standards are silent on the feature. The court pointed out that the standards omitted two of the four criteria the covenants required, which proved they could not be the whole test, and observed that on the owners' reading a “day-glo orange” house would have to be approved.

The limit the court added matters as much as the holding: “The board does not have unfettered discretion and nothing in our opinion should be interpreted as granting the board such powers.” A footnote restates that an association is not a state actor and so is not subject to the Due Process Clause, citing Windcliff Ass'n v. Breyfogle, 988 N.W.2d 911, 920 (Minn. 2023).

How the case and the statute fit together

Warner says written guidelines are often a minimum rather than a ceiling, and that discretionary compatibility standards in the covenants can be applied. Chapter 82 now requires that the procedure be written, that the decision be written, that it be reasonable, and that it arrive within 90 days.

Those are complementary, not contradictory. Minnesota associations retain substantive discretion over design where their covenants confer it. What they lose is the ability to exercise it slowly, informally, or without saying why.

The practical consequence is that the written decision becomes the document that carries the association's reasoning. Where a board denies on a compatibility ground not spelled out in the guidelines — exactly the Warner situation — the denial letter is where the covenant language and the reasoning have to appear.

The completeness question decides the deadline

Because the 90 days runs from an application containing all required information, the definition of “required” is doing the load-bearing work, and it is the association that writes it — in the procedure the statute now requires.

Two failure modes are foreseeable. A procedure that lists required materials vaguely lets the board keep an application perpetually incomplete, which is the abuse the section exists to stop and is hard to square with a “fair, reasonable, and expeditious procedure.” A procedure that lists nothing at all means every application is complete on submission, and the clock starts immediately.

The workable answer is a specific, closed list of submission requirements, plus a commitment to state completeness (or what is missing) within a short, defined period of receipt. The statute does not require that acknowledgement step, but it is what makes the 90 days administrable.

The declaration can still set a different period

The deadline applies “[u]nless the declaration, bylaws, or rules and regulations provide for a different period.” That is an unusually wide override — it reaches down to rules, which the board itself adopts.

It is not unlimited: the overall procedure must still be “fair, reasonable, and expeditious,” and the decision must still be reasonable. A rule setting a 12-month review period would be difficult to defend against that language. But an association with genuine seasonal constraints has room to say so in its procedure rather than fail the statutory default.

What to do before January

Adopt the procedure in 2026. The statute requires the procedure to be made “by rule or regulation,” and from 1 January 2027 rules require 21 days' notice and comment before adoption. Doing this in the fourth quarter avoids running the first compliance rulemaking under the new regime.

Decide who decides. The section permits the board or an appointed committee. A committee that reviews and a board that ratifies is a common structure and is compatible — but the 90 days covers the whole path to decision, not just the committee stage.

Write a denial template with a reasons field. The same discipline Chapter 82 imposes on fine resolutions applies here in substance: a written, reasonable decision made under the director standard of care.

What to watch next

Nothing is pending. Chapter 82 leaves architectural standards untouched — S.F. 3418, which would have voided covenants on minimum home size, building materials, architectural style and fencing outright, was never heard and died with the biennium.⁴ Minimum-size, materials and fencing covenants remain enforceable in Minnesota.

This describes the statute and a nonprecedential decision. It does not predict the outcome of any particular application.