


Ask the community...
Something else to be aware of: if your separation is marked as "lack of work" (which a layoff due to project completion would be), ESD usually processes these claims faster with fewer questions. But they do need verification that it truly was lack of work. If you can't get documentation quickly, another option is to ask your former employer to respond directly to ESD's request for information that they should have received. Some employers are slow to respond to these, which is often what causes the delay in claim processing.
That's great news that your supervisor is getting you that letter! Just a heads up - when you submit it, make sure it includes your full name and the dates of your employment along with the layoff reason. ESD is pretty specific about what they need on these documents. Also, if you do run into any delays after submitting it, don't panic. Sometimes it takes them a few business days to review and update your claim status. Keep checking your eServices account for any updates or additional requests. Good luck!
Thanks for the additional tips! I'll make sure the letter includes all those details. It's reassuring to know that a few days processing time is normal - I was worried that any delay would mean something was wrong. I've been checking my eServices account obsessively, so I'll try to be more patient once I submit the documentation.
I had a backdating appeal hearing about 6 months ago with a very similar situation - I was laid off and spent weeks job searching without realizing I should have filed for unemployment immediately. The key thing that helped me win was framing it as a genuine misunderstanding about eligibility rather than avoidance of the system. During my hearing, I emphasized three main points: 1) I truly believed unemployment benefits were only for people who had stopped job searching, 2) I was actively doing everything I thought was required (job searching), and 3) I had no prior experience with unemployment so I relied on incorrect assumptions. The judge asked me directly why I didn't call ESD or research online, and I explained that I was focused entirely on finding work and operating under the misconception that filing for benefits would somehow conflict with active job searching. I think being honest about the confusion rather than defensive made a big difference. Your extensive job search documentation is actually a huge asset - it proves you weren't just sitting around doing nothing. Make sure to present it as evidence that you were fulfilling what you believed were your obligations during unemployment. Good luck with your hearing!
This is so encouraging to hear! Your situation sounds almost identical to mine. I was definitely in that same mindset of thinking I had to choose between job searching OR filing for unemployment, not realizing I could and should do both. Did you have any other supporting documentation besides your job search records? I'm trying to gather everything I can before Thursday's hearing.
@Serene Snow I also had my termination letter that showed my last day of work, which helped establish the timeline. Additionally, I brought printouts of a few job applications with timestamps to show I started searching immediately after being laid off. The judge seemed to appreciate that I had a clear paper trail showing my activities during the disputed period. One thing I wish I had done was bring documentation of any conversations with friends or family about my job search - even text messages can help show your state of mind at the time. Since your hearing is Thursday, maybe gather any texts or emails you sent during those 8 weeks mentioning your job search efforts?
I'm going through a backdating appeal myself right now and wanted to share what I've learned from talking to other claimants who've been through this process. The judges definitely vary in how they interpret the "good cause" standard, but several people have told me that having extensive job search documentation like yours actually strengthens your case significantly. One thing that might help - if you have any emails or texts you sent to friends/family during those 8 weeks mentioning your job search or expressing confusion about unemployment benefits, bring those as evidence. They can help demonstrate your genuine state of mind at the time. Also, practice explaining your timeline clearly and concisely. The judges appreciate when you can walk through exactly what happened week by week without getting too emotional or defensive. Focus on the facts: when you were laid off, what you understood about the process, what actions you took, and when you realized you should have filed earlier. The $4,200 you're owed shows this is definitely worth fighting for. Even if the odds aren't perfect, you've got a legitimate case with the misunderstanding angle and strong job search evidence. Wishing you the best of luck with your hearing next week!
I'm dealing with this exact same issue right now and this thread has been incredibly helpful! Made the same mistake yesterday on my weekly cert and have been stressed about it ever since. It's really reassuring to see how many people have successfully gotten this resolved, whether through the early morning calling strategy or using Claimyr. The fact that this happens "multiple times per day" according to the agents really highlights how much PFML needs to add an edit button - it's such a basic feature that would save everyone so much time and stress! I'm going to try calling right at 8 AM tomorrow with all my documentation ready, and if that doesn't work out I'll definitely give Claimyr a shot based on all the positive experiences shared here. Thank you to everyone who took the time to share their solutions and success stories - this community support makes dealing with these government systems so much more manageable!
Ethan, you're absolutely not alone in this! I just made the exact same mistake two days ago and found this thread while desperately searching for solutions. It's honestly both frustrating and comforting to see how incredibly common this issue is - like you said, if agents are dealing with this multiple times daily, PFML really needs to prioritize adding that edit button! I ended up trying the Claimyr service yesterday after reading all the positive experiences here, and I have to say it worked exactly as advertised - got connected to an agent in about 18 minutes who fixed the issue immediately. The agent was super understanding and said it's one of the most common calls they get. Your backup plan of calling at 8 AM is smart too based on Anastasia's success with that approach. Either way, don't stress too much - from everything I've seen in this thread, it's a really quick fix once you get through to someone. Good luck and definitely update us on how it goes!
I'm going through this exact same situation right now! Just made the mistake on my weekly cert this morning and immediately started panicking when I couldn't find an edit button anywhere. This thread has been such a lifesaver - it's amazing (and frustrating) to see how many people deal with this exact issue. The fact that PFML agents handle this "multiple times per day" but there's still no simple edit feature is honestly ridiculous, especially when people are already stressed about medical leave and finances. Based on all the success stories here, I'm definitely going to try the Claimyr service that Brady, Skylar, and others have recommended - the 15-20 minute wait times sound so much better than the 2+ hour horror stories with the regular phone line. It's such a relief to know this is actually a quick fix for the agents once you get through. Thanks to everyone who shared their experiences and solutions - you've turned what felt like a complete disaster into a manageable problem with a clear path forward!
I went through this same confusion when I first filed! The one-week waiting period in Washington is mandatory for all regular unemployment benefits. Here's what I learned the hard way: even though you won't get paid for that first week, you absolutely MUST file your weekly claim for it. I made the mistake of thinking I could skip filing that first week since I wouldn't get paid anyway, and it caused a delay in my entire claim process. The waiting period starts from the Sunday of the week you file your initial claim, regardless of what day you actually submitted it. So if you filed last week, your waiting period is already running. Make sure to file your weekly claims on time every week, including that unpaid waiting week - it's crucial for keeping your claim active and getting your payments started from week 2 onward.
Thanks for sharing your experience! This is exactly the kind of real-world insight that's so valuable. I almost made the same mistake of thinking I could skip that first week since there's no payment. It's frustrating that the system isn't more intuitive about this - like why not just automatically file that waiting week claim when you submit your initial application? Seems like a lot of people get tripped up by this same issue. Did you have to call Washington ESD to fix the delay, or were you able to resolve it online?
Oh wow, I'm so glad I read this before making the same mistake! I was literally about to skip filing for that first week thinking it would save me some hassle. Thank you for the warning - sounds like it would have just created more problems down the road. This whole process is already stressful enough without adding delays on top of it. I really appreciate everyone sharing their experiences here, it's way more helpful than trying to decode the official Washington ESD website.
I went through this exact same situation a few months ago and can confirm what others have said - it's a mandatory one-week waiting period for all regular unemployment benefits in Washington. The key thing that saved me a lot of stress was understanding that this waiting period is built into the system, not a sign that something is wrong with your claim. I'd recommend checking your eServices account regularly to make sure your weekly claims are being processed correctly. Also, if you're like me and need to talk to someone at Washington ESD about your specific situation, don't waste time trying to call during peak hours (Monday mornings are the worst). I found early mornings or late afternoons work better, though even then it can take multiple attempts. The waiting period definitely stings when you're already dealing with job loss, but at least you know exactly what to expect timeline-wise. Hang in there!
This is really reassuring to hear from someone who's been through it recently! I was starting to worry that maybe I'd done something wrong since I haven't gotten paid yet, but it sounds like this is just how the system works. Your tip about checking eServices regularly is great - I'll make sure to stay on top of that. And thanks for the heads up about calling times, I was planning to try calling Monday morning but I'll definitely avoid that now. It's frustrating that we have to jump through all these hoops when we're already stressed about being unemployed, but at least knowing what to expect helps a lot.
Reina Salazar
Thanks everyone for the detailed explanations! I think I finally understand - Washington ESD takes your two highest quarters from your base period, adds them together, then divides by 52 weeks. So if I had $15,000 and $13,500 in my two best quarters, that would be $28,500 ÷ 52 = about $548 per week. Much clearer than trying to figure it out from the confusing info I found online. Now I just need to gather all my pay stubs to calculate the exact quarters and see if I meet the minimum requirements.
0 coins
Dyllan Nantx
•Just wanted to add that when you're calculating your quarters, make sure you're using the calendar quarters (Jan-Mar, Apr-Jun, Jul-Sep, Oct-Dec) and not pay periods or any other time frame. I made that mistake initially and got confused about which wages belonged to which quarter. Also, if you had multiple jobs during the same quarter, you add all the wages from all employers together for that quarter. The Washington ESD system automatically does this when they process your claim, but it's good to know for your own calculations.
0 coins
Zara Shah
•That calculation looks spot on! One thing I'd add is to keep copies of all your documentation when you file. Washington ESD sometimes asks for wage verification later, especially if there are discrepancies between what employers reported and what you claim. Having your pay stubs organized by quarter will save you a headache if they need additional proof. Also, don't forget that even if your calculation shows you qualify, Washington ESD still needs to verify you're unemployed through no fault of your own - so make sure you understand the reason for your job separation before filing.
0 coins
Isaac Wright
I went through this same confusion when I filed my Washington ESD claim last year. The key thing that helped me was realizing that Washington uses a pretty straightforward formula compared to other states. Take your two highest earning quarters from your base period, add them together, then divide by 52. So if your best quarters were $20,000 and $18,000, that's $38,000 ÷ 52 = $731 per week (subject to the $999 maximum). The tricky part is making sure you're looking at the right base period timeframe - it's the first four of the last five completed quarters before you file. I'd recommend calling early in the morning around 8 AM if you need to speak with someone at Washington ESD, as that's when I had the most luck getting through without waiting hours on hold.
0 coins
Anastasia Sokolov
•Thanks for the tip about calling at 8 AM! I've been trying to get through to Washington ESD for days with no luck. Your calculation example is really helpful too - it's reassuring to see that the formula is consistent across different people's experiences. One question though: when you say "first four of the last five completed quarters," does that mean if I file today in late May 2025, my base period would be Q1 2024 through Q4 2024? Or would it include Q1 2025 since that quarter is completed? I want to make sure I'm looking at the right timeframe when I gather my wage documents.
0 coins