City ESST: most-favorable rule across three jurisdictions.
Minneapolis, St. Paul, and Bloomington each run their own Earned Sick and Safe Time ordinances on top of the state law. Coverage applies to workers performing 80+ hours per year inside city boundaries — the same threshold as state coverage. Employers must follow the requirements most favorable to the employee. The 2025 amendments (Saint Paul Nov 16, 2025; Minneapolis Dec 31, 2025) aligned the cities more closely with the state framework, but residual differences persist — most notably St. Paul's harassment-related leave accommodation, broader than state.
City ESST Most-Favorable Routing
Tracks worker hours in Minneapolis, St. Paul, and Bloomington against city coverage thresholds. Applies most-favorable rule per worker. Routes harassment-related leave per St. Paul's broader scope.
What those rules do at city threshold crossings.
The hero card configuration: Flag on coverage threshold, Critical on city-specific scope.
When a worker accumulates 80+ hours of work in Minneapolis, St. Paul, or Bloomington in any benefit year, the worker is covered by that city's ESST ordinance. The threshold tracks state coverage threshold (80 hours/year) with city-specific geographic boundaries.
St. Paul's ESST ordinance accommodates leave requests related to harassment, even where state law would not require ESST coverage. Workers in St. Paul can use ESST for harassment-related circumstances; in Minneapolis or under state law, the same circumstance might not be covered.
Deploy Minnesota city ESST coordination in your Teambridge.
Tell us about your Minnesota workforce. We'll spin up Minneapolis/St. Paul/Bloomington coverage tracking, most-favorable rule application, harassment-leave routing, and 21 other Minnesota policies in a sandbox tenant.
Three city ordinances, state law on top — most-favorable rule decides.
The three cities share a common 80-hour coverage threshold and a 1-per-30 accrual rate. Differences come from use cases, documentation thresholds, and increment-of-use rules.
80-hour coverage threshold
All three city ordinances cover workers performing at least 80 hours of work in city boundaries during any benefit year. The threshold mirrors the state ESST coverage threshold (80 hours/year). A worker who hits 80 hours in Minneapolis is covered by Minneapolis ESST in addition to state ESST. A worker hitting 80 hours in St. Paul is covered by St. Paul ESST. The thresholds are independent — a worker can be covered by all three ordinances if they hit 80 hours in each city.
Most-favorable rule
Where the city ordinance and state law differ, the employer must apply the requirements most favorable to the worker. In practice: if a city ordinance provides more generous accrual, broader use cases, longer documentation thresholds, or shorter increments-of-use, the city rule applies. Employers cannot 'cherry-pick' provisions; they apply the city ordinance in full where the city is more favorable.
Teambridge tracks city coverage and applies the most-favorable rule.
The post-2025 alignment narrowed the gap between state and city rules; the residual differences (especially St. Paul harassment) still require per-jurisdiction handling.
Cumulative hours per benefit year.
Each worker's hours are tracked separately against Minneapolis, St. Paul, and Bloomington boundaries. Crossing 80 hours in any city triggers ESST coverage by that city ordinance.
City vs state requirements compared.
For workers covered by a city ordinance, requirements are compared against state law. Most-favorable rule applied per requirement (accrual, use cases, documentation, increments).
Broader use case enabled in St. Paul only.
Workers in St. Paul who request ESST for harassment-related circumstances are accommodated. The same request from a worker in Minneapolis or outside city boundaries is evaluated against state-law use cases (which may not cover harassment specifically).
City coverage indicated.
Each worker's pay statement indicates which ESST regime governs (state, Minneapolis, St. Paul, Bloomington, or multiple). Balance and usage tracked accordingly.
Still evaluating? Get a free Minnesota compliance audit.
Send us your existing Minnesota scheduling and pay configuration. Our compliance team returns a written audit within 5 business days — every Minnesota-specific exposure ranked by risk and back-pay liability.