


Ask the community...
Thanks for posting this question! I've been wondering about the same thing with a potential settlement from a workplace accident (not workers comp related). Good to know these types of settlements generally don't affect unemployment benefits.
I went through something similar last year with a personal injury settlement from a slip and fall. Washington ESD didn't reduce my benefits at all since it wasn't work-related income. The key is being upfront about it when you file your weekly claim. I reported it under "other income" with a brief explanation that it was a personal injury settlement unrelated to employment. They reviewed it for about 10 days and then confirmed it wouldn't affect my benefits. Just make sure you keep all your settlement paperwork in case they ask for documentation later. The transparency really helps avoid any issues down the road.
This is super reassuring! The 10-day review period seems pretty reasonable compared to some of the horror stories I've heard about Washington ESD taking weeks or months to make decisions. Did they send you any kind of written confirmation that the settlement wouldn't affect your benefits, or was it just reflected in your continued payments?
This is such a helpful thread! I'm bookmarking this for future reference. One thing I'd add for anyone still struggling - if you're using Safari on Mac, try switching to Chrome or Firefox. Safari has some weird compatibility issues with the ESD site that cause similar login loops. Also, make sure your browser is updated to the latest version. I spent hours troubleshooting only to find out my Chrome was like 6 months out of date and that was causing the redirects to fail. The whole SAW integration is honestly a mess, but at least there are workarounds!
Thanks for mentioning the Safari issue! I've been helping my mom with her unemployment claim and she's been using Safari on her iPad - that might explain why she keeps having problems. I'll have her try Chrome instead. It's ridiculous that in 2025 we still have to play browser roulette just to access basic government services. The fact that this thread exists and has so many different solutions shows how broken the system really is.
Just wanted to add another potential fix that worked for me when I had the same issue last year - if you're still getting stuck in loops even after following all the great advice here, try logging into SAW from an incognito/private browser window. Sometimes cached session data from previous login attempts can interfere with the authentication process. Also, I noticed that if you have multiple Washington state services linked to your SAW account (like licensing, voting registration, etc.), it can sometimes cause conflicts. In my case, I had to temporarily remove my business license service from SAW, add the unemployment insurance service, complete the setup, and then re-add the business license later. It's a pain but it worked when nothing else did!
When I had my standby issue I couldn't get through to ESD on the phone for nearly a week... every morning I'd call right when they opened and still couldn't get through. If you're having trouble, try that Claimyr service I mentioned - it saved me so much frustration and time. What I learned is that it's super important to deal with these issues fast before they turn into bigger problems with your claim!
Thank you everyone for all the helpful advice! I was able to get through to ESD this morning (after many attempts) and explained the situation. They were actually understanding about the confusion. I have to retroactively submit job search activities for the past weeks, but they're giving me time to do it. And I've started the proper standby request process now. Lesson learned - always verify everything in the ESD system and don't just take your employer's word for it!
That's great news! Glad you got it sorted out. Make sure to document everything going forward - save confirmation numbers, take screenshots, and keep records of who you spoke with. It'll make things much easier if any questions come up later.
So glad you were able to get it resolved! This is such a common issue - employers often think they've handled the paperwork when they haven't actually submitted it properly to ESD. Your experience is a perfect example of why it's so important to double-check your own account status rather than assuming everything was done correctly. Hopefully your standby request gets approved quickly so you won't have to keep doing the job searches while you're waiting to return to your landscaping job!
MAKE SURE you keep doing your job search activities even while waiting for everything to update!!! I know someone who thought winning their appeal meant they didn't have to do job search for a while (no idea why they thought that) and they got disqualified all over again for a completely different reason. Don't give ESD any excuse!
I went through something similar last year! The system lag is frustrating but totally normal. One thing I'd add to the great advice already given - if you haven't already, I'd recommend requesting a copy of the written appeal decision for your records. Sometimes it takes a few weeks to arrive by mail, but having that official document can be really helpful if any questions come up later about your eligibility. You can usually request it by calling the appeals office directly (they're easier to reach than the main ESD line). Congrats on winning your appeal!
Freya Larsen
Last resort option - you can actually file your weekly claim over the phone if you absolutely can't get into the website. The automated phone system for weekly claims is separate from the regular customer service line. The number should be on your paperwork from when you first filed your claim.
0 coins
Freya Larsen
•Yeah it's not as convenient as online but at least you won't miss your deadline. Just have your Social Security number and claim information ready.
0 coins
Miguel Herrera
•Good point about the phone filing option. Not everyone knows about that backup method.
0 coins
Omar Hassan
UPDATE: I tried the incognito browser suggestion and it worked! I was able to log in immediately. Thanks everyone for all the help. Turns out it was some kind of browser cache issue after all.
0 coins
Zainab Ali
•Glad you got it sorted without needing to call. Always try the free fixes first, but good to know there are options like Claimyr if you really get stuck.
0 coins
Leo McDonald
•Wait, I think there might be some confusion here - the UPDATE post was from Omar Hassan, but the original post was from Sofia Rodriguez. Are you Sofia posting from a different account, or did Omar have the same issue? Just want to make sure we're all on the same page here.
0 coins