ESD claim shows 'Fired - Inability/mandatory retirement' status - what does this mean?

That status typically means ESD is processing your claim under the classification that you were terminated due to performance/ability issues or a mandatory retirement policy. Since you said you were let go due to outsourcing (which would be lack of work), this sounds like a misclassification. You absolutely need to contact ESD immediately to correct this before a formal determination is issued, as this type of separation reason often results in disqualification.

omg this hapened to me 2!! my status said somethin about misconduct but i was laid off. took 3 weeks to get fixed and i almost lost my benefits. defintely call them asap!!!

I've seen this a few times with clients I help. Here's what's happening: When your employer responded to ESD's request for separation information, they either 1) checked the wrong box on the form, or 2) gave information that ESD misinterpreted. The good news is that "processing" means no final determination has been made yet. The "Fired - Inability" code is just an initial classification that will be reviewed during adjudication. You have three options: 1. Call ESD immediately to clarify (recommended but difficult to reach them) 2. Upload documentation to your account showing the real reason was outsourcing (org chart changes, layoff notice, etc.) 3. Wait for the determination letter and appeal if it's incorrect (risky, could delay benefits by months) Don't panic yet, but definitely take action this week.

the whole system is RIGGED against us!!! i bet your employer is lying to avoid their unemployment insurance rates going up. companies do this ALL THE TIME to screw workers. they'll claim performance issues even when it's totally false. DOCUMENT EVERYTHING and fight back!!!

I had something similar happen last month - different category but wrong reason. I tried calling for days but couldn't get through. I finally used Claimyr (claimyr.com) and got connected to an ESD agent in about 20 minutes. They have a video showing how it works: https://youtu.be/7DieNd3C7zQ?si=26TzE_zGms-DODN3. The agent was able to see notes on my account and corrected the classification issue right away. Saved me from having to go through a lengthy appeal process.

Yes, it worked for me! The ESD agent I spoke with said these classification errors are pretty common, especially when multiple layoffs happen at once or when employers use third-party services to respond to ESD inquiries. The important thing is getting it corrected before they issue the formal determination letter.

this happend to my cousin he got fired for being late but hes claim said misconduct which is different i think??? anyway he had to do the adjudication thing where they interviewed him and his boss but it took like 6 weeks and he didnt get paid that whole time it was super rough

UPDATE: I managed to get through to ESD this morning! The agent confirmed it was a coding error. Apparently my employer correctly stated I was laid off due to outsourcing, but someone at ESD selected the wrong category when entering it into their system. The agent corrected it on the spot and my status now shows "Lack of work - Business reorganization." She said my benefits should process normally now. What a relief!

So glad to hear you got this resolved! Your experience is a perfect example of why it's crucial to act quickly when you see incorrect information on your claim. For anyone else dealing with similar issues, here are a few key takeaways from this thread: 1. "Processing" status with wrong separation reason doesn't mean you're doomed - it's often fixable before final determination 2. Keep trying to call ESD even if it's frustrating - sometimes persistence pays off 3. Have your layoff documentation ready (termination letters, emails about department closures, etc.) 4. Check your claim status regularly so you catch errors early Thanks for sharing the update - it gives hope to others who might be dealing with similar coding mistakes!

Wow, what a rollercoaster! I'm so relieved you got this sorted out, Keisha. Your story really highlights how these coding errors can happen to anyone - it sounds like it was just human error on ESD's end when they were processing your employer's response. For anyone else who might encounter this, I'd also suggest taking screenshots of your claim status at different stages. Sometimes these systems can be glitchy and having visual proof of what you're seeing can be helpful when talking to agents. Also, if you do get disconnected while on hold (which happens way too often), try calling right back - sometimes you get lucky and get through faster on the second attempt. Thanks for sharing your resolution - it's going to help so many people who find themselves in similar situations!