twimco.Let’s talk ↗︎
Menu
Field notes / Operations

Michigan's MiUI launch may send late notices that aren't really late. Every system cutover should plan for that

Michigan switched its unemployment system to MiUI on November 9 and moved claimants from certifying every two weeks to every week. The agency is already warning that some people will get late-certification notices they don't deserve. That honest warning holds a lesson for anyone changing a system and a rule at once.

Editorial engraving of a bright state benefits office where a staffer shows a worried claimant a weekly schedule on a tablet beside a wall calendar.

Michigan's Unemployment Insurance Agency fully launched MiUI on November 9, 2026, retiring MiWAM and the MARVIN phone line and moving claimants from biweekly to weekly certification and payment. UIA says some workers may get late-certification notices because of the prior week's downtime or the schedule change; it asks them to certify for available weeks, answer any fact-finding questionnaire promptly, and says it will review each case and in most cases find the certification wasn't late or the downtime was good cause.

What changed in Michigan on November 9

Michigan's Unemployment Insurance Agency fully launched MiUI on November 9. It replaces MiWAM, the online system people have used for 14 years, which is now permanently offline. The MARVIN phone line, where claimants certified by calling at a set day and time, is gone too.

Existing claims and history moved across, so nobody with an open claim has to file again. You still sign in with a MiLogin account, and you still have to register in person with Michigan Works!. Payment methods didn't change.

The rule changed alongside the system. In MiUI, claimants certify every week instead of every two weeks, and they're paid weekly as well. That's simpler in the long run. In the first weeks, it creates a predictable problem.

Employers are moving too. MiUI is also where businesses now report wages and pay unemployment taxes, and UIA lists a separate line for them through the Office of Employer Ombudsman. If you run payroll or HR for a Michigan employer, expect questions from former staff this month, and point them to the agency's own channels rather than guessing at the new rules.

Sequence of work

Michigan's MiUI week, as announced

  1. Week of Nov 2

    Downtime Period while claims move from MiWAM to MiUI.

  2. Mon Nov 9

    MiUI fully live. MiWAM and the MARVIN phone system permanently offline. Weekly certification begins.

  3. Wed Nov 11

    Veterans Day. Offices closed; payments may arrive later.

  4. Through Dec 8

    Daily claimant coaching webinars on applying and weekly certification.

Dates from Michigan LEO's November 9, 2026 release.

The notice the agency is already warning about

The release is unusually candid. It says some unemployed workers may receive a notice about a late certification, either because of the previous week's system Downtime Period or because of the switch from biweekly to weekly. In plain terms, someone following the old two-week rhythm, or someone who couldn't certify while the system was down, may be flagged.

What UIA asks claimants to do:

  • Certify for any available weeks in MiUI now.
  • Answer any fact-finding questionnaire promptly if one arrives.
  • Don't panic about the notice. UIA says it will review each situation individually, and in most cases will find the certification wasn't late or that the downtime was good cause.

Help is unusually available this week. There are daily coaching webinars on applying and weekly certification through December 8, a how-to video series, a MiUI University site, 12 local offices and Michigan Works! staff trained on the new system. The agency also notes that offices are closed on Veterans Day and that payments may arrive later.

When the system and the rule change in the same week, the old rule keeps showing up as errors in the new system.

Why this happens in almost every cutover

Michigan isn't unusual here. It's just saying it out loud.

When an organization moves to a new system, it often takes the chance to fix a rule at the same time. Weekly instead of biweekly. A new form instead of a phone call. A clearer deadline. Each change is sensible. Together, they mean the first cycle in the new system is judged against a rule people haven't learned yet, after a downtime they couldn't avoid.

When the system and the rule change in the same week, the old rule keeps showing up as errors in the new system.

The system does exactly what it was configured to do. A deadline passes, a notice goes out. Nobody did anything wrong, and yet a lot of people receive a letter that sounds as if they did. Staff then spend weeks reviewing cases whose outcome everyone could have predicted on day one.

We've written before about what gets lost when a portal switch closes open tasks, in what happens to task history when the portal changes, and about splitting a state service across two systems in Michigan Treasury's e-services cutover. False exceptions are the other side of the same coin: not lost work, but extra work the switch itself creates.

What to plan before your own go-live

If you run a public program, a benefits process, a licensing system or even a customer portal with deadlines, Michigan's week is a cheap lesson. Before go-live, ask five questions.

Which notices will fire in the first two cycles that wouldn't have under the old rules? Run last month's activity through the new rules and count. Those are your expected false exceptions.

Should those notices go out at all? Some can be held for a cycle, reworded to explain the change, or routed to a review queue first. A letter that says "our schedule changed, please certify for these weeks" lands very differently from "you are late".

What's the written rule for staff? UIA's "in most cases" outcome suggests a default. Write it down, so a reviewer can close an expected case in minutes and spend time on the ones that are genuinely different.

Who answers the phone in week one? Expected exceptions turn into calls. Michigan staffed the line every day, holiday included. Plan the people, the script and the hours before the letters go out, not after the queue builds.

What will you count? The number of late notices sent tells you little. The number that turned out to be real tells you whether the system and the rule are working, and when the transition is actually over.

Decision guide

Planning for false exceptions before go-live

ConsiderationCommon defaultBetter plan
NoticesSystem sends the standard late notice as soon as a deadline passesNotices for the first cycles are held, softened or reviewed before sending
StaffEvery case handled from scratch by whoever picks it upA written rule for the expected cases, so most close quickly and consistently
MessageExplanation published after complaints startThe warning goes out with the launch, in plain words
MeasureCount of late notices sentCount of late notices that turned out to be real
Decision framework for any cutover that changes a rule as well as a system; illustrative, not Michigan's internal process.

The part Michigan got right

It's easy to read a release like this as a problem. It's better read as good practice. UIA said what would go wrong before most people noticed, told claimants exactly what to do, kept the phones open on a holiday and put a date on the extra help. Many cutovers manage none of that.

The step most organizations can add is the one before the warning: catching the predictable exceptions in testing, so fewer people ever get the letter. That takes a few days of running real past cases through the new rules, and a decision about which outcomes should wait for a person.

It also helps to separate the two changes where you can. If the rule can change a cycle after the system does, people learn one new thing at a time, and the exceptions you see in each cycle point clearly at one cause. Where that isn't possible, because the law, the budget or the vendor contract sets the date, the planning above matters even more.

We help public agencies and the vendors who serve them plan cutovers like this, from rule changes to the notices people actually receive. See our government and public sector work or talk to us.

Related work: Sutton|Place

FAQ

What changed when Michigan launched MiUI?

Michigan's Unemployment Insurance Agency fully launched MiUI on November 9, 2026, retiring MiWAM and the MARVIN phone line. Existing claims and history moved across, sign-in is still through MiLogin, and payment methods didn't change. Claimants now certify every week instead of every two weeks, and they're paid weekly as well.

I got a late-certification notice after the MiUI switch. What does it mean?

UIA says some workers may receive a late-certification notice because of the prior week's downtime or the switch from biweekly to weekly certification. It asks claimants to certify for any available weeks in MiUI, answer any fact-finding questionnaire promptly, and not panic: the agency says it will review each situation and in most cases will find the certification wasn't late or that the downtime was good cause.

Do I have to file a new unemployment claim in MiUI?

No. Existing claims and history moved across, so nobody with an open claim has to file again.

Where can I get help with weekly certification in MiUI?

UIA pointed to daily coaching webinars on applying and weekly certification through December 8, a how-to video series, a MiUI University site, 12 local offices, and Michigan Works! staff trained on the new system. Offices were closed on Veterans Day, and the agency noted that payments may arrive later.

twimco.

We build alongside the people doing the work.
Bring us the problem you’re thinking about.

Related work

Sutton Place ↗︎