


Ask the community...
Just wanted to follow up and say THANK YOU to everyone who helped, especially @Evelyn Martinez for the specific breakdown and @Freya Nielsen for connecting the dots about my short-term job! I uploaded documentation from both construction companies last night - W2s, paystubs from my main employer, the few paystubs I still had from that 3-week job, and my layoff letter, all clearly labeled. Woke up this morning and the "missing employment information" alert is GONE! My claim status changed to "processing" and I actually got a timeline estimate of 3-5 business days. After almost a month of stress, I can't believe it was that simple once I knew what they actually needed. This community is a lifesaver - the ESD website and phone system are absolutely useless but you all provided clearer guidance than I ever got from official sources. Hopefully this thread helps other people in the same boat!
This is amazing news and such a relief to hear! I'm so glad you got it sorted out. Your experience really shows how important this community is - it's crazy that we have to rely on each other for basic information that ESD should be providing clearly from the start. I'm saving this whole thread for future reference in case I run into similar issues. Congrats on getting your claim moving and thanks for following up to let us know what worked!
This is such a perfect example of how broken the ESD system is! I'm so frustrated reading this because I went through almost the exact same thing 6 months ago. The "missing employment information" alert is completely useless - it tells you nothing about what they actually need. Like others have said, you definitely need to upload documentation for ALL employment during your base year, including that 3-week construction job. I made the same mistake of forgetting about a short temp job and it held up my claim for weeks. The fact that we have to crowdsource basic information that should be clearly explained on their website is absolutely ridiculous. ESD really needs to overhaul how they communicate document requirements because this confusion happens to literally everyone. Really glad @Evelyn Martinez was able to provide the official breakdown - that kind of clarity should be available upfront, not something you have to hunt down in forums!
Absolutely agree! It's infuriating that ESD makes such basic information so hard to find. I just went through this exact situation myself and ended up in the same documentation hunt. What really gets me is that they have all this technology for their portal but can't be bothered to create clear, specific guidance about what documents they need for different scenarios. Instead we're all left guessing and stressing about losing our homes while they sit on claims for weeks. Thank goodness for people like @Evelyn Martinez sharing insider knowledge, but it shouldn t'take an ESD employee randomly commenting in a community forum for us to get answers that should be standard information!
Bottom line: severance can affect unemployment but it doesn't have to if it's structured right. Get clarification from Washington ESD, be completely honest when filing your claim, and keep good records. You'll get through this!
Good luck with everything! And seriously, if you need to reach Washington ESD, that Claimyr service really does make the phone situation much more manageable.
I went through something similar last year when my tech company did layoffs. The $8,000 severance amount is pretty typical, and the good news is that Washington state is generally more worker-friendly than some other states when it comes to severance and UI benefits. Here's what I learned: if your severance agreement doesn't specifically mention covering a certain number of weeks or acting as "pay in lieu of notice," you're probably in the clear to start collecting right away. The fact that yours just says it's "in appreciation of service" sounds promising. One tip I wish someone had told me - when you file your UI claim online, there's a section where you can upload documents. Include your severance agreement there from the start, even if they don't explicitly ask for it. It saved me from having to deal with follow-up requests later. Also, start your claim as soon as possible after your last day of work, regardless of the severance situation. Washington ESD can always adjust things retroactively if needed, but you don't want to lose out on potential benefit weeks while you're figuring everything out.
This is really comprehensive advice, thank you! I especially appreciate the tip about uploading the severance agreement right from the start. Did you end up having any issues with the timing of your benefits, or did everything go smoothly once you provided the documentation?
That's exactly the kind of practical advice I was hoping to find! I'm feeling much more confident about this whole process now. The tip about uploading documents proactively is gold - I can see how that would prevent a lot of back-and-forth delays. Quick question though: when you say start the claim "as soon as possible after your last day," do you mean literally the next day, or is there a specific window I should be aiming for? I want to make sure I don't miss any important timing requirements.
As someone who just started receiving benefits last month, this is really helpful information! I had no idea about this change and was wondering why the job search section disappeared from my weekly claim. I've been keeping my own informal notes but clearly need to switch to the official form. Does anyone know if there's a grace period for people who are new to the system and didn't know about this requirement? I'm worried I might have already messed up my first few weeks by not using the proper documentation format.
@Amara Adeyemi - I wouldn t'worry too much about the first few weeks if you were genuinely doing job search activities and just keeping informal notes! The key is that you were actually doing the work. If you do get audited later, you can explain that you were new to the system and didn t'know about the official form requirement initially. ESD usually looks at whether you made a good faith effort to comply. I d'recommend downloading the official form now and starting to use it going forward, and maybe try to recreate your previous activities on the proper form if you can remember the details. The important thing is showing you re'making the effort to follow the requirements once you know about them!
I'm in the exact same boat as you! Just discovered this change when I filed my claim this week and was totally blindsided. I've been scrambling to figure out what I'm supposed to do differently now. The lack of clear communication from ESD about this change is really frustrating - they should have sent out notices or at least put up some kind of announcement on the website explaining the new process. I'm going to download that official form everyone's mentioning and start tracking everything properly from now on. Thanks for posting about this because I was starting to think something was wrong with just my account!
Bottom line for OP - you're good, your employer is handling all unemployment tax obligations and you won't see any deductions on your paystub for unemployment insurance in Washington state.
Perfect, thank you everyone! This thread has been super helpful. Now I understand how the system works and can stop worrying about my paystub.
Just wanted to add that if you're coming from a state that does deduct unemployment taxes from employee paychecks, Washington's approach can definitely feel weird at first! I moved here from Pennsylvania where they take out both state and federal unemployment taxes from your pay. Here in Washington, you'll only see the federal taxes that go to Social Security and Medicare, plus federal income tax. The state unemployment system is completely invisible to you as an employee, which is honestly kind of nice - one less line item to worry about on your paystub.
Sophia Russo
Another thing to keep in mind is that Washington ESD considers your field of expertise when determining suitable work. Since you were a warehouse supervisor with management responsibilities, they understand that's a specialized skill set that commands higher wages. A regular warehouse worker position isn't just a pay cut - it's also a significant step down in responsibility level. You're absolutely within your rights to decline this offer and continue searching for supervisory roles that match your experience and previous salary range. Just make sure to keep detailed records of your job search efforts and any offers you receive or decline.
0 coins
Javier Morales
•This is exactly what I needed to hear! The responsibility level difference is huge - going from managing people and processes back to just basic warehouse tasks feels like it would be a real career setback. I'm definitely going to keep looking for supervisor positions that actually use my management experience. Thanks for pointing out that specialized skills matter in these decisions!
0 coins
Fatima Al-Qasimi
•Exactly right about the specialized skills aspect! I went through something similar when I was laid off from my logistics coordinator position. Washington ESD recognized that my experience in supply chain management and vendor relations wasn't something I should have to abandon for just any warehouse job. The key is being able to articulate how your supervisory experience - the team management, safety compliance, inventory oversight - represents legitimate career advancement that you shouldn't be expected to give up after just 6 weeks of unemployment. Document not just the wage difference but also the scope of responsibilities in your previous role versus what's being offered. That complete picture really strengthens your case for declining unsuitable work.
0 coins
Alexis Burroughs
My husband has been outta work since last week of July, with one phone interview and one in person. We’re about to go to 13 weeks of benefits. He might have to take a job that pays 60% less than what he was earning, as nothing in tech industry employment is panning out - 29 yrs software development. We’re concerned if he doesn’t take this and nothing in the next 13 weeks…we’re homeless! So we figure better to be able to pay mortgage and food on table, and to declare bankruptcy coz we cant pay our bills!
0 coins
Norah Quay
•I can't imagine how stressful this must be for your family. 29 years in software development represents incredibly valuable expertise that companies desperately need. Before accepting such a drastic pay cut, have you explored all the tech networking opportunities? LinkedIn, local tech meetups, former colleagues who might know of openings? Sometimes the best opportunities come through professional networks rather than job boards. Also, consider that many companies are struggling to find experienced developers right now - your husband's skills are in demand, it's just a matter of connecting with the right opportunity. If you do end up needing to take temporary lower-paying work to keep afloat, remember it doesn't have to be permanent, and you can often continue receiving partial UI benefits while working. Hang in there - 29 years of experience doesn't just disappear, and the right opportunity will recognize that value.
0 coins
Isabella Tucker
•I'm really sorry to hear about your husband's situation - being in tech for 29 years and facing this kind of uncertainty must be devastating. One thing that might help is looking into whether Washington state offers any extended benefits or additional programs for long-term tech workers who've been displaced. Given the widespread tech layoffs, there may be specific resources available. Also, has he considered reaching out to his professional network from those 29 years? Sometimes former colleagues, managers, or even people he mentored might know of opportunities that aren't publicly posted yet. The 60% pay cut is really severe - I'd definitely recommend calling Washington ESD to discuss whether that would truly be considered "suitable work" for someone with his experience level, even at the 13-week mark. Don't give up hope yet - your husband's decades of experience are incredibly valuable, and the right opportunity could still come along.
0 coins