


Ask the community...
I'm in a very similar situation - my hours just got reduced from 38 to 25 per week and I wasn't sure if I qualified for anything. Reading through all these responses has been incredibly helpful! I had no idea about the Shared Work program or that there were alternatives to just applying for jobs to meet the search requirements. One question I have after reading everything: If I file my initial claim now but my hours reduction doesn't start for another two weeks, do I still need to file weekly claims during those two weeks when I'm still working full time? Or do I wait until my hours actually get cut to start the weekly filing process? Also, has anyone had experience with how long the adjudication process typically takes for partial unemployment claims? I'm trying to plan my budget around when I might actually start receiving benefits.
Great questions! From what I understand based on the other responses here, you should file your initial claim right away even before your hours get cut - that establishes your claim effective date. But for the weekly claims, you'd wait until you actually start working the reduced hours to begin filing those, since you report your actual hours worked and wages earned each week. As for adjudication timing, it seems like it varies a lot based on what others have shared. @Diego Castillo mentioned 3 weeks total from filing to first payment, while @Elijah O Reilly'said 6 weeks due to adjudication delays. @Natalie Adams also mentioned it being a long process. It might depend on how straightforward your case is - voluntary hours reduction by employer should be pretty clear-cut compared to more complex situations. I d definitely'recommend asking your employer about that Shared Work program @Amara Torres mentioned since it sounds like it eliminates the job search requirements and might process faster. Worth a shot!
I went through partial unemployment when my hours were reduced from 40 to 24 per week about 6 months ago. A few tips that might help: First, definitely file your initial claim as soon as you know about the reduction - don't wait until it actually happens. The effective date matters for when benefits can start. Second, the weekly benefit calculation can be tricky to estimate beforehand. I was making about $18/hour and thought I wouldn't qualify for much, but between the partial benefit and the new $25 weekly supplement, I was getting around $180/week which really helped cover my rent shortfall. Third, keep really good records of everything - your old schedule, new schedule, pay stubs, any documentation from your employer about the hours reduction being involuntary. ESD may ask for proof that this wasn't your choice. The job search requirement was annoying but manageable. I mostly did online workshops and updated my resume/LinkedIn rather than actually applying places since I wanted to keep my current job. Just document everything properly. One last thing - if you have any issues with your claim getting stuck, don't waste weeks trying to call ESD. Use one of those callback services or try contacting your local WorkSource office for help navigating the system. The sooner you get it resolved, the better.
This is really comprehensive advice, thank you! The $180/week example at $18/hour is super helpful - I make about $16/hour so this gives me a good ballpark of what to expect. I'm definitely going to start documenting everything now before my hours actually get reduced. Your point about the callback services is interesting - I saw @Sophia Russo mention something similar earlier about Claimyr. Good to know there are alternatives to sitting on hold for hours if issues come up. I m'hoping my case will be straightforward since it s'a clear employer-initiated hours reduction, but it s'good to know about backup options. One quick follow-up question: When you were doing the online workshops for job search requirements, did you find them through WorkSource specifically, or were there other sources that ESD accepted? I want to make sure I m'doing activities that definitely count toward the requirement.
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!
This is such a helpful summary! I'm bookmarking this thread because it shows exactly how to handle these situations. One thing I'd add - if you can't get through by phone, don't forget about the secure messaging option in your ESD account. It's slower than calling but at least creates a paper trail of your attempts to correct the error. Also, screenshot everything in case the status changes again!
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!
This is such great advice about taking screenshots! I wish I had thought of that when I was dealing with my issue. It's so stressful when you're seeing something confusing on your claim and then worrying it might disappear or change before you can get help. The tip about calling back immediately after getting disconnected is gold too - I probably gave up too easily the first few times I tried calling. This whole thread has been incredibly helpful for understanding how these coding errors work and what to do about them. Thanks everyone for sharing your experiences!
Great to hear it worked out! This is really helpful info for others in similar situations. BECU does seem to be pretty reliable with government deposits - I've had good experiences with them too. It's always nerve-wracking when you're counting on that money for bills, but at least now you know the typical timeline for future payments. Glad you made it through the adjudication process and are finally getting your benefits!
This whole thread is super helpful! I'm new to UI benefits and had no idea about the timing differences between banks. Good to know BECU is reliable - I might switch from my current bank if I run into deposit delays. The adjudication wait sounds brutal, glad you finally got through it @Camila Castillo!
Just wanted to add my experience for anyone else who might be wondering about timing - I've been getting UI benefits for about 8 months now and the pattern is pretty consistent. When ESD shows "paid" on Saturday, the money hits my account (Wells Fargo) on Monday around 3-4am. When it shows "paid" on Friday, it usually arrives the same Monday. The only time I've had delays was during a federal holiday when banks were closed an extra day. One tip: if you're stressed about timing like the OP was, you can usually see pending deposits in your online banking on Sunday evening, even though they won't officially post until Monday morning. That at least gives you peace of mind that it's coming!
That's really useful info about being able to see pending deposits on Sunday! I wish I had known that earlier this week - would have saved me a lot of anxiety. The federal holiday delay is something I hadn't thought about either. Thanks for sharing your experience over 8 months, it's reassuring to hear there's a consistent pattern once you know what to expect.
I'm going through this same situation right now and wanted to share what I learned from speaking with a Washington Apple Health representative. Your UI benefits of $600/week ($31,200 annually) would put you over the standard Apple Health income limit, but you may still qualify for Apple Health coverage with a small premium or subsidized marketplace coverage. The rep told me that many people on unemployment end up in what's called the "coverage gap" - too much income for free medicaid but still qualifying for significant help with marketplace premiums. I'd definitely recommend using the income calculator on wahbexchange.org that someone mentioned earlier, and don't forget that your UI benefits won't last forever, so your eligibility could change again when they end. The most important thing is to report the income change promptly so there are no issues later.
This is exactly the kind of detailed info I was hoping to find! @Fatima Al-Maktoum, when you spoke with the Apple Health rep, did they give you any guidance on the timeline for reporting income changes? I want to make sure I handle this correctly and avoid any potential issues with overpayments or coverage gaps. Also, did they mention whether there's a specific form I need to fill out when reporting UI benefits, or can I just update my information online through the Washington Healthplanfinder portal?
@Fatima Al-Maktoum This is incredibly helpful information, thank you! I m'the original poster and your explanation about the coverage "gap really" clarifies my situation. When you mentioned that many people on unemployment still qualify for subsidized marketplace coverage, do you know approximately what income range qualifies for the most help with premiums? I m'trying to figure out if my $31,200 UI income would still get significant assistance or if I d'be looking at much higher monthly costs than my current free Apple Health coverage. Also, did the rep mention anything about prescription drug coverage differences between Apple Health and marketplace plans?
I've been following this thread closely since I'm in almost the exact same situation - receiving about $580/week in UI benefits and worried about my Apple Health coverage. After reading everyone's experiences, I decided to be proactive and called the Washington Apple Health line this morning right at 8am (thanks @Brianna Schmidt for that tip!). I actually got through after about 20 minutes on hold. The representative confirmed that my UI benefits would put me over the standard Apple Health income limit, but she walked me through the online portal to update my income information and check my options. What I learned is that even though I won't qualify for free Apple Health anymore, I'm eligible for a subsidized marketplace plan that would cost me around $75/month with my current UI income level. The rep also mentioned that I should report my income change within 10 days to avoid any overpayment issues later. She emphasized that it's better to be upfront about the UI benefits now rather than deal with potential payback requirements down the road. For anyone else in this situation, I'd really recommend calling early in the morning - the wait times are much shorter and the representatives seem to have more time to explain your options thoroughly.
@Luca Romano Thank you so much for sharing your experience with calling this morning! This gives me hope that I can actually get through and get real answers. I m'the original poster Jeremiah (and) have been really anxious about this whole situation. The $75/month cost is honestly much more reasonable than I was expecting - I was imagining I d'be looking at $400+ per month. I m'definitely going to try the 8am calling strategy tomorrow. One question about the documentation - when you updated your income information, did you need to have your UI payment statements ready, or could you just provide the weekly benefit amount? I want to make sure I have everything prepared before I call. Also, did the rep mention anything about how this affects prescription coverage compared to Apple Health? I have a couple of medications I need to keep taking during my job search. Really appreciate you taking the initiative to call and sharing what you learned!
@Luca Romano This is incredibly helpful information! I m'dealing with a similar situation - UI benefits around $620/week - and was really panicking about potentially losing my health coverage. The $75/month cost you mentioned is actually much more manageable than I expected. I was imagining marketplace plans would be $300+ monthly. Your 8am calling strategy sounds like a game-changer - I ve'avoided calling because I assumed I d'be on hold for hours. Quick question: when you updated your income in the portal, did the system walk you through the marketplace options right away, or did you need to complete a separate application? I want to understand the process before I call tomorrow. Also really appreciate the reminder about the 10-day reporting window - I had no idea that was a requirement and definitely want to stay compliant. Thanks for being proactive and sharing your experience with all of us!
Collins Angel
Don't stress too much about the process. Washington state is pretty good about processing restaurant worker claims since it's such a common industry here. Your tips will be included in the benefit calculation, and you should be able to get approved without major issues.
0 coins
Xan Dae
•Thank you everyone for all the helpful advice! I feel so much more confident about filing my claim now.
0 coins
Collins Angel
•You're welcome! This community is great for supporting each other through these situations. Good luck with everything!
0 coins
Felix Grigori
As someone who just went through the unemployment process as a restaurant worker myself, I can confirm everything others have said - you absolutely qualify! Your tip income is crucial for calculating your benefits, so make sure you have documentation ready. One tip I'd add: when you create your online account, save your login info somewhere safe. You'll be logging in weekly to file claims, and it's frustrating if you get locked out. Also, don't be discouraged if the website is slow or crashes sometimes - it happens, especially on Sundays when everyone is filing their weekly claims. Just try again later. The whole process was less scary than I expected once I got started.
0 coins
Liam O'Reilly
•This is such great practical advice! I hadn't thought about saving my login info, but you're absolutely right - I can see how getting locked out would be really frustrating when you need to file weekly claims. The tip about the website being slow on Sundays is really helpful too. I'm feeling much more prepared now thanks to everyone's input. It's reassuring to hear from someone who just went through the same process recently!
0 coins