Minnesota PTO Laws: What Employers Must Know (2026)

Minnesota's Earned Sick and Safe Time law is recent, broad, and carries one design choice that separates it from almost every comparable statute: an 80-hour carryover ceiling.

Most state sick-leave laws reset roughly annually. Minnesota lets balances accumulate to twice the annual entitlement. Over two or three years, a stable workforce builds up meaningful banked time — and employers who modelled this as a 48-hour annual cost tend to be surprised by year three.

This is general information rather than legal advice — confirm current requirements with the Minnesota Department of Labor and Industry or an employment attorney before finalizing a policy.

Earned Sick and Safe Time

Accrual is one hour per 30 hours worked, up to at least 48 hours per year.

Every employer with one or more employees is covered. No size threshold at all.

Use begins as hours accrue — Minnesota does not impose the 90-day gate most states use.

Carryover is permitted up to a total balance of 80 hours. You may cap use at 48 hours in a year while the balance continues building toward 80.

Front-loading is an alternative: grant 48 hours at the start of the year and you avoid carryover entirely, or grant 80 and avoid the question altogether.

Documentation may be required only for absences of more than three consecutive scheduled days.

Covered reasons are wide, including the employee's own illness, care for family under a broad definition, closure of the workplace or a child's school due to weather or public emergency, and safe-time absences.

The 80-hour ceiling changes the economics

Compare the steady-state liability against a typical annual-reset state:

For a 20-person team, the difference at steady state is roughly 640 hours of banked time — about 80 working days sitting on the books.

That is not a payout liability, since Minnesota does not require sick time to be paid out. It is a coverage liability: time your team is entitled to take, potentially in concentrated periods, that your staffing model needs to absorb.

Front-loading 48 hours annually is the standard way to bound it, at the cost of granting time some employees would never have accrued.

Minneapolis and St. Paul

Both cities had ordinances before the state law arrived, and both remain in force. They differ from the state rule in places — accrual caps, covered employers, and how hours worked within city limits are counted for employees who are only sometimes there.

Where a local rule is more generous, it governs. For an employer with staff moving between sites, the practical answer is usually to apply the most generous applicable rule across the board rather than tracking hours by geography.

This is the same shape of problem as Illinois, where Chicago stacks its own entitlement on the state floor — and the opposite of New Jersey, which preempted every local ordinance in favour of one uniform rule.

Vacation: your policy governs

Minnesota has no statute converting accrued vacation into wages. Use-it-or-lose-it is generally permissible for vacation with a clear written policy, and payout at separation is required only where you promised it.

As always, the exposure is your own wording. PTO payout laws compares the states, and use-it-or-lose-it PTO covers designing an expiry clause that is fair as well as lawful.

Can one PTO bank cover it?

A combined bank can satisfy ESST if it meets the accrual rate, the covered reasons, carryover to 80 hours, the absence of a waiting period, and the documentation limits.

The no-waiting-period rule is the one that trips existing policies. Many PTO policies impose a 30- or 90-day probationary hold on all time off. For the bucket satisfying ESST, that hold is not permitted.

A Minnesota handbook audit

1. Does it allow use from day one, with no probationary hold on the ESST bucket?
2. Does it carry balances to 80 hours rather than resetting at 48?
3. Does it mention weather and public-emergency closures as covered reasons?
4. Does it cover safe time explicitly, not just illness?
5. Does it account for Minneapolis or St. Paul staff?
6. Does it limit documentation to more than three consecutive days?

How to write a PTO policy covers structure, and the PTO policy generator will draft one.

Tracking

The 80-hour ceiling is what makes Minnesota awkward to run by hand. A rule that accumulates across years cannot be verified by looking at the current year's sheet — you need continuity of balance across resets, which is precisely what a spreadsheet rebuilt each January destroys.

The sick leave accrual calculator will convert hours worked into earned time, and the PTO accrual calculator covers vacation. If your tracking currently starts fresh each year, why spreadsheets break for PTO describes the failure directly: multi-year carryover is the case hand-built trackers almost never survive.