Back to Washington Unemployment

Keisha Williams

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

Just checked my ESD account and I'm totally confused. My claim status changed to 'processing' which seems good, but there's no determination letter in my inbox. The weird part is that my decision status says 'Fired - Inability/mandatory retirement' which makes NO sense. I wasn't fired for inability - I was let go because my department was outsourced! I'm 34 years old so definitely not retirement age. Is this some kind of coding error? Has anyone else seen this status before? I'm worried they're going to deny my benefits for something that's completely untrue. Should I be calling ESD about this or just wait for the determination letter to arrive?

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.

0 coins

Thanks for explaining! That's what I was afraid of. I've been trying to call ESD for the past 2 days but can't get through - just endless hold then disconnection. Do I have any other options to reach them?

0 coins

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!!!

0 coins

3 weeks?? I can't wait that long without benefits. How did you finally get it fixed?

0 coins

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.

0 coins

Thank you for this detailed explanation! I'll try uploading my layoff letter which clearly states it was a department elimination. Still going to try calling too but at least this gives me something I can do while waiting.

0 coins

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!!!

0 coins

While employers do sometimes misrepresent separation reasons, in this case it sounds more like a coding error than deliberate misrepresentation. The "processing" status suggests this is still in initial stages and can be corrected. Let's not jump to conclusions without more information.

0 coins

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.

0 coins

I've never heard of this service before. Did it actually work? Right now I'm desperate enough to try anything that might help me talk to a real person at ESD.

0 coins

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.

0 coins

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

0 coins

Just to clarify - tardiness can be classified as misconduct in some cases. That's different from OP's situation where the code doesn't match the actual separation reason at all. But you're right that adjudication can take several weeks, which is why it's better to correct the record before it reaches that stage.

0 coins

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!

0 coins

thats awesome!!! so glad u got it fixed!!!

0 coins

Great news! This is exactly why it's so important to check your claim status regularly and address any discrepancies immediately. For anyone else reading this thread, always verify the separation reason shown on your claim matches your understanding of why you're not employed. Correcting errors early can save months of headaches and delayed benefits.

0 coins

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!

0 coins

Washington Unemployment AI

Expert Assistant
Secure

Powered by Claimyr AI

T
I
+
43,783 users helped today