Thursday, 9:15 AM. Unit 5's increase is going out for January 1, and you check the one thing you always check: how much notice does Minnesota require. One month, says the statute. You count back to December 1, draft the letter, and move on to the next twelve.
The number was right. The document it came from was the wrong one. Minnesota has a second rule sitting next to the first, and it says a landlord may not give a notice of a rent increase shorter than the period the lease requires of the tenant when they want to leave. It cannot be waived. So if your lease template asks residents for 60 days' notice to vacate, the state has quietly handed you a 60-day rent increase notice, in every unit that template governs, for as long as it governs them. Nobody sends you that memo. You wrote it.
This is a strange category of operating rule, and it is worth naming: a legal obligation you authored yourself, in a document you drafted for an entirely different reason. The 60-day move-out clause exists because someone wanted more runway to re-lease. That was a good instinct. It also set the floor on every future rent conversation in the portfolio, and the person who wrote it almost certainly did not know that, because the two facts live in different places: one in a lease template, one in a statute nobody reads on a Thursday morning.
The cost of that gap is unusual because it is invisible until it is expensive. A notice that is short does not arrive slightly late. It fails, and the increase slides a full rental period while the old rent keeps running, on every unit you served the same way on the same day. And the exposure scales with exactly the thing you have been trying to build, which is consistency: one template, applied uniformly, means one misread clause applied uniformly too. The portfolios that standardized hardest have the most units pointed at the same wrong number.
Then there is the version of the problem that has no lease clause behind it at all, which is the advice. Search how much notice Minnesota requires and you will be told, confidently and repeatedly, that increases under 10 percent take 30 days and increases of 10 percent or more take 60. There is no such statute. It is another state's rule, restated often enough to look settled, and it is now being repeated back to operators by the tools they ask. Something can be wrong in public for years without anyone correcting it, because the only people positioned to notice are the ones who read the chapter, and they are not writing blog posts.
The clause you drafted to protect your leasing calendar is now the rule your rent increases run on.
Here is the line that moves when this runs as a system instead of a memory. The question stops being "what does Minnesota require" and becomes "what does this lease require," asked per lease, at the moment it matters, rather than once in general and then assumed forever. The uniform template stops being a uniform liability, because the answer is read off the document that governs the unit rather than off the one everyone remembers signing. A rent increase becomes a pricing decision with a date attached, and the date is not a guess.
That is how Scaalr runs a Minnesota increase: each schedule is validated against the resolved market when you set it and again before anything serves, the statutory minimum holds as a hard floor, the lead above it is yours to set for exactly this reason, and the notice is composed, signed, and recorded as served rather than remembered as sent. A St. Paul address resolves to the stabilized rules by default, and the exempt regime is one you select, because your certificate of occupancy date is a fact you hold and we do not. The full rulebook, every rule tied to its official source, is here: Minnesota Rent Increases: No State Cap, St. Paul's 3 Percent.
For the complete guide to the state rules, the notice clocks, and the St. Paul ordinance, see: Minnesota Rent Increases: No State Cap, St. Paul's 3 Percent.
Put one building on it first. $99 covers your first 50 units, Alex included. Cancel anytime.