07.08.2015 Views

Out of Sync

Out-of-Sync-Report

Out-of-Sync-Report

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

with employers only when doing so is reasonableand not futile;b. Excuse quits related to volatile schedules,regardless <strong>of</strong> whether such schedulingpractices are customary in an industry oroccupation;c. Clarify rules about how long individualsare expected to “test out” changed workingconditions before quitting and at what pointcontinuing in a job indicates acceptance <strong>of</strong>changed working conditions.3. States should update their partial UI rules toprotect workers subject to volatile scheduling andencourage jobless workers to accept part-time jobs.4. State agencies should engage in outreach effortsto increase transparency and improve publicunderstanding <strong>of</strong> UI rules for workers experiencingvolatile schedules.UI laws, policies, and agency practices leave manyworkers subject to volatile scheduling practices in thelurch. A primary failing <strong>of</strong> existing rules and practicesis that, while workers under traditional schedulingarrangements who experience significant changes intheir working conditions may be able to leave their jobswith good cause and maintain eligibility for UI, theexperience <strong>of</strong> volatility, which is different from a onetimechange, is <strong>of</strong>ten not recognized under UI law. Inshort, the UI system has not caught up with the realities<strong>of</strong> today’s labor market and <strong>of</strong>ten fails workers withvolatile schedules when they are most in need. Withthe changes advocated here, we can bring UI programsmore into sync with the realities <strong>of</strong> workers experiencingvolatile scheduling.2 NELP | HOW UNEMPLOYMENT INSURANCE RULES FAIL WORKERS WITH VOLATILE JOB SCHEDULES

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!