< Back to Washington Unemployment

Ravi Kapoor

ESD distance requirements - How far is 'too far' to decline a job offer?

Hi everyone, I'm in a bit of a predicament with my job search requirements. I got a job offer yesterday that technically matches my skills (administration/office work), but it's quite a distance from my home in Spokane. My car isn't super reliable for long commutes, and gas costs would eat up a big chunk of my paycheck. I'm worried if I decline, ESD might disqualify me from benefits. Does anyone know what Washington ESD considers a reasonable commuting distance? Is there an official mile radius or commute time that's considered 'too far' to have to accept? I've heard mixed things from friends - one said 25 miles, another said it's based on commute time, not distance. Any clarity would be super helpful before I make my decision!

Freya Nielsen

•

WA ESD generally considers jobs within a 1-hour commute (one way) or approximately 25-30 miles from your home to be reasonable. Anything beyond that gives you grounds to decline without penalty. But here's the thing - you need to document WHY it's unreasonable. If your car is unreliable, get that documented somehow. Calculate exactly what percentage of your wages would go to transportation costs. ESD looks at these cases individually, so build your case with specifics. Also worth noting - if public transportation is available that would get you there in under an hour, they might consider that reasonable even if driving would be too far.

0 coins

Ravi Kapoor

•

Thanks for the detailed info! That actually really helps. The commute would be about 40 miles each way, and there's no direct public transportation option that would work with the job hours. I'll definitely document the costs and my car issues. Do you know if I need to fill out a specific form when declining, or just explain it during my weekly claim?

0 coins

Omar Mahmoud

•

be careful!! i turned down a job that was 35 miles away last year and got my benifits cut off completely!! had to go through this whole appeal process that took WEEKS. i think it depends on what adjudicator looks at your case tbh. some are reasonable some are NOT. when u do your weekly claim there's a section to explain why u turned down work and u gotta be SUPER specific there

0 coins

Chloe Harris

•

THIS!! The same thing happened to my brother-in-law. ESD can be really inconsistent with these decisions. He ended up having to take a job that was costing him almost $400/month in gas because they said it was "reasonable distance" even though it was like 45 mins each way.

0 coins

Diego Vargas

•

The ESD handbook (which is buried on their website) says the standard is what's "customary for your occupation in your local labor market." So if you're in a field where people typically commute farther, they might expect you to do the same. Since you mentioned office/admin work, I'd say anything over 30 miles would be considered unreasonable in most WA areas. When you decline, be very specific about the exact distance, estimated commute time, lack of public transit options, and most importantly, the economic factor - calculate exactly what percentage of your wages would be consumed by transportation costs. If it's over 20% of your net pay, that's a solid argument. By the way, if you need to speak directly with an ESD agent about this before making a decision (which I highly recommend), check out Claimyr (claimyr.com). I was stuck in the phone queue for days trying to get an answer on a similar situation, but their service got me through to an actual ESD agent in under 2 hours. They have a video showing how it works: https://youtu.be/7DieNd3C7zQ?si=26TzE_zGms-DODN3. It's worth it for something this important where you need a definitive answer.

0 coins

Ravi Kapoor

•

Thank you for the detailed response! I hadn't thought about the occupational expectations angle. You're right that I should calculate the exact percentage of wages that would go to transportation - I'm guessing it would be around 25% with current gas prices and my car's poor mileage. I'll look into Claimyr because getting a definitive answer before I decline would definitely be less stressful than hoping I explain it well enough in my weekly claim.

0 coins

NeonNinja

•

Everyone saying there's some magical number of miles is wrong. The law actually says: "the work either offers wages less than the prevailing wage for similar work in the locality, or involves conditions substantially less favorable than those prevailing for similar work in the locality." So one big factor they look at is if other people doing your type of job typically commute that far. I've had claims both approved and denied for distance reasons...depends on who reviews your case!!! Good luck with ESD's awful system!!!!!

0 coins

Freya Nielsen

•

You're partially correct, but the administrative guidelines ESD uses do actually specify some general distance parameters. While there's no absolute cutoff, they typically use 25-30 miles or one hour as a baseline. You're right that it's not the only factor though - they also consider occupation norms, transportation availability, and economic factors. The key is documenting everything thoroughly.

0 coins

When I was on unemployment in 2022, I declined a job that was about 35 miles away from my house. I explained in my weekly claim that 1) I calculated the commute would be 1hr15min each way during rush hour, 2) gas would cost me about $85/week with my vehicle's mpg, and 3) there was no reliable public transportation option. I didn't have any issues - they continued my benefits without question. Just make sure you're super detailed in your explanation!

0 coins

Sean Murphy

•

You got lucky! Mine was similar distance and they put me in adjudication for 6 weeks! Finally got approved but it was so stressful. But good point about being detailed - I think that's what eventually helped my case.

0 coins

Ravi Kapoor

•

Thanks everyone for the helpful responses! I'm going to call ESD directly using that Claimyr service before making my decision, but I'm also going to prepare a detailed explanation with exact mileage (40.3 miles one-way), calculated gas costs based on my car's MPG, documentation of my car's repair history showing its unreliability, and the lack of public transit options for the specific work hours. I'm feeling much more confident about how to handle this now. Really appreciate all the advice!

0 coins

Diego Vargas

•

Smart approach. Calling ahead is definitely the way to go. Just make sure to document who you speak with and what they tell you. Get their ID number if possible. Keep us posted on how it goes!

0 coins

Sofia Price

•

Just wanted to add another perspective here - I work in HR and deal with ESD issues regularly. The 40+ mile commute you're describing would almost certainly be considered unreasonable, especially with an unreliable vehicle. One thing I'd suggest documenting is not just the gas costs, but also the wear and tear on your car (maintenance, potential breakdown costs, etc.). Also, if you do end up calling ESD, ask specifically about the "suitable work" provisions in WAC 192-170-050. This regulation covers when work can be considered unsuitable due to distance/transportation issues. Having the specific regulation number when you explain your situation shows you've done your homework and might help your case. The fact that you're being proactive about this rather than just declining and hoping for the best shows you're handling it the right way. Good luck with whatever you decide!

0 coins

This is incredibly helpful, thank you! I hadn't thought about documenting the wear and tear costs - that's a great point. My car already needs some repairs and adding 80+ miles daily would definitely accelerate that. I'll make sure to mention WAC 192-170-050 when I call - having the specific regulation number is a smart tip. Really appreciate the HR perspective on this!

0 coins

Ava Kim

•

I went through something very similar last year in Tacoma! My situation was a 38-mile commute for an office job, and I was really nervous about declining. What helped me was creating a simple spreadsheet that broke down all the costs - gas, parking fees at the workplace ($8/day!), extra car insurance for higher mileage, and estimated maintenance costs. When I calculated everything, it would have eaten up almost 30% of my take-home pay. I also took photos of my car's odometer and kept receipts from recent repairs to document the reliability issues. When I explained it in my weekly claim, I was super specific: "Job located 38.2 miles from residence, estimated 1hr 20min commute each way during work hours, no public transit available, transportation costs would equal 28% of net wages, vehicle has documented reliability issues with recent repairs totaling $800." They approved it without any issues. I think the key is really showing you did the math and that it genuinely wasn't economically viable. The detailed documentation seems to make all the difference with ESD reviewers.

0 coins

Axel Far

•

This is exactly the kind of documentation I needed to see! Creating a spreadsheet with all the breakdown costs is brilliant - I'm definitely going to do that. The parking fees angle is something I hadn't even considered yet, and you're right that showing the actual percentage of take-home pay makes it much more concrete. 28% is definitely unreasonable! I'm feeling much more confident about how to present my case now. Thanks for sharing your successful experience - it's really reassuring to hear from someone who went through the same thing and got approved.

0 coins

I just want to echo what everyone else is saying about documentation being key! I had a similar situation in Bellingham where I was offered a job 42 miles away. What really helped my case was that I called the employer and asked about flexible work arrangements (remote work, adjusted hours, etc.) and documented their response when they said no. ESD seemed to appreciate that I had explored all options before declining. One thing I'd add to the great advice already given - if your current unemployment benefits are based on a previous job that was much closer to home, mention that too. It shows that the long commute isn't typical for your work history. Also, don't forget to factor in the time cost - 80+ miles of daily commuting is basically adding an unpaid 2.5-3 hours to your workday, which effectively reduces your hourly wage even further. The fact that you're asking these questions and planning to call ahead shows you're being really responsible about this. Most people just decline and hope for the best. Your approach is definitely the right way to handle it!

0 coins

That's a really good point about contacting the employer to ask about flexible arrangements first! I hadn't thought of that, but it shows ESD that you made a genuine effort to make the job work before declining. And you're absolutely right about the time factor - I calculated that the 2.5+ hours of daily commuting would effectively drop my hourly wage below what would be reasonable. I'm also going to mention that my previous job (which my benefits are based on) was only 8 miles from home, so this would be a completely different situation than what I'm used to. Thanks for the additional perspective - it's really helpful to hear from someone else who successfully navigated this in Washington!

0 coins

Carmen Diaz

•

Just wanted to add another data point from someone who went through this process recently in Vancouver, WA! I was offered a position that was 45 miles away in Portland, and I was terrified about declining because I really needed to keep my benefits. What ended up working for me was being extremely methodical in my documentation. I created a folder with: - Google Maps screenshots showing the exact distance and drive times during work hours - A gas cost calculator based on current prices and my car's actual MPG (I used the EPA rating from my car manual) - Photos of my car's maintenance records showing recent issues - A letter from my mechanic stating that long daily commutes would likely accelerate needed repairs The crucial thing for me was the economic impact calculation. With gas, wear and tear, and the bridge tolls to Oregon, I calculated it would cost me $127 per week, which was 31% of the net wages. I presented it as "This position would result in a net hourly wage of $X after transportation costs, which is below the minimum wage equivalent." I submitted all this with my weekly claim explanation and got approved without any follow-up questions. The whole process was way less scary than I thought it would be once I had everything documented properly. One tip I'd add - if you do end up calling ESD, ask them to email you a summary of what they tell you. Having their guidance in writing can be really helpful if there are any issues later!

0 coins

Avery Saint

•

This is incredibly thorough documentation - thank you for sharing the specific details! I love the idea of getting the mechanic's letter about long commutes accelerating repairs, that's something I wouldn't have thought of but makes perfect sense. The 31% cost calculation really drives home why it would be unreasonable to accept. And that's a great tip about asking ESD to email a summary of their guidance - having it in writing could definitely save headaches later. Your methodical approach is exactly what I'm planning to do. It's so reassuring to hear from multiple people who have successfully navigated this process with proper documentation!

0 coins

Reading through all these responses has been incredibly helpful for understanding how to handle this situation properly! As someone who's been navigating unemployment benefits for the past few months, I really appreciate seeing the detailed experiences everyone has shared. One thing I'd add that hasn't been mentioned yet - if you do decide to decline the job, make sure you also document any safety concerns with your unreliable vehicle making that long of a commute daily. ESD considers safety as part of the "suitable work" determination. If your car has had breakdowns or has known issues that could leave you stranded on a 40+ mile commute (especially in winter weather here in Washington), that's definitely worth documenting. Also, I noticed someone mentioned checking if the employer offers any transportation assistance or commuter benefits. Some larger companies have shuttle services, carpooling programs, or transit subsidies that might change the calculation. It's worth asking before you decline, and documenting their response either way shows ESD you explored all options. The consensus here seems clear though - 40+ miles with an unreliable vehicle and no public transit would almost certainly be considered unreasonable by ESD standards, especially when you factor in the economic impact. Your proactive approach of calling ahead and documenting everything thoroughly is definitely the smart way to handle this. Best of luck with whatever you decide!

0 coins

Jade Santiago

•

Great point about the safety concerns - I hadn't thought about documenting that angle but it makes total sense! My car has actually broken down twice in the past 6 months, once on I-90 in pretty bad weather, so adding 80+ miles daily would definitely increase the risk of getting stranded. That's definitely something I'll include in my documentation along with all the economic factors everyone has mentioned. And you're right about asking the employer about any transportation benefits or assistance programs - even if they say no, having that documented shows I tried to make it work. Thanks for adding these additional considerations to an already really helpful thread!

0 coins

Ravi Kapoor

•

Wow, this thread has been incredibly informative! I'm dealing with a similar situation right now - got offered a job that's 36 miles away and was really stressed about whether I could decline without losing my benefits. Reading everyone's experiences, it seems like the key is really thorough documentation. I'm going to follow the advice here and create a detailed breakdown of all costs (gas, wear and tear, time, etc.), document my car's reliability issues, and call ESD ahead of time using that Claimyr service someone mentioned. One question for those who have been through this - did anyone have success stories with distances in the 30-35 mile range? Most of the examples here have been 38+ miles, so I'm curious if there's anyone who declined something closer to that 30-mile threshold that gets mentioned and how it went. Thanks to everyone who shared their experiences - this community is so helpful for navigating ESD's complicated system!

0 coins

KingKongZilla

•

I actually declined a job at exactly 32 miles last summer and didn't have any issues! The key for me was really emphasizing the economic impact - even at 32 miles, the gas costs plus wear and tear would have been about 22% of my net pay, which I argued was unreasonable. I also documented that the commute would be 55-65 minutes each way during work hours due to traffic patterns, which put it right at that "1 hour threshold" several people mentioned. ESD approved it without any follow-up questions. I think as long as you can show the economic burden is significant and document everything thoroughly like everyone's suggesting, you should be fine even in that 30-35 mile range. The fact that you're being proactive about calling ahead will definitely help your case!

0 coins

Washington Unemployment AI

Expert Assistant
Secure

Powered by Claimyr AI

T
I
+
20,095 users helped today