Minnesota code timeline · Structural · 2003

Stucco and EIFS Moisture Barriers in Minnesota Homes Before 2003

Minnesota amended its moisture-barrier requirements after widespread stucco failures in the Twin Cities. Exterior cladding installed before that change was often built without a drainage plane behind it.

By Karl Espilseth, Founder, Tarn · Updated

What it is

EIFS — exterior insulation and finish system, often called synthetic stucco — is a layered exterior wall assembly of foam insulation, mesh and a thin finish coat. The critical detail is not the surface but what sits behind it. A drainage plane gives any water that gets past the finish somewhere to go and a way back out. Early installations were often applied as a sealed barrier system with no drainage path, on the theory that keeping water out entirely was enough.

Why it matters

In Minnesota's climate, water gets in. It gets in at windows, at penetrations, at transitions, and through freeze-thaw cycling that opens small gaps. When it gets behind a sealed system with nowhere to drain, it stays against the sheathing, and the damage develops out of sight — sometimes for years before anything is visible from inside or outside. The failures in Woodbury and elsewhere in the early 2000s are what drove Minnesota's amendments, and they are also why some insurers now ask specific questions about stucco on homes of this vintage.

What's worth doing next

This is the factor on this list where a specialist inspection is most worth the money, because visual inspection genuinely will not tell you. Moisture testing — probe readings taken at the vulnerable points around windows and penetrations — is the standard approach and is a distinct service from a general home inspection. If the home has stucco or EIFS applied before 2003, it is worth doing before the inspection contingency expires rather than after.

I built Tarn as a homeowner, not a code official. Everything on this page is sourced to published Minnesota law and linked so you can check it yourself.

Minnesota uses a single statewide building code, so these requirements are state law rather than city ordinance — they apply the same way across every Minnesota city Tarn covers, except where noted. Code changes are also prospective: they apply to work done after the change, not retroactively to homes already standing. A home that predates a standard isn't out of compliance with anything. It just predates it, and that's worth knowing before you buy.

Check this against a specific address

Tarn runs the full Minnesota code timeline automatically when you search an address with a year built in any of these cities.

Search an address

Other Minnesota code-era factors

See the full Minnesota code timeline