Page 22

BEM 230A 22 of 26 EMPLOYMENT AND/OR SELF-SUFFICIENCY RELATED ACTIVITIES: FIP BPB 2022-020 10-1-2022

BRIDGES ELIGIBILITY MANUAL STATE OF MICHIGAN DEPARTMENT OF HEALTH & HUMAN SERVICES

client’s hours for six months. Determine the average number of hours worked per week and document the actual hours on the FSSP. Example: Amber submits three consecutive paycheck stubs for pay dates of January 5, 12 and 19. One paycheck stub shows 25 hours worked, one paycheck stub shows 30 hours worked and one pay check stub shows 32 hours worked. The average of the three paycheck stubs is 29 hours per week on average. Example: Jordan submits two consecutive paycheck stubs for pay dates of January 5 and January 19. The client is paid bi-weekly. One paycheck stub states 60 hours worked and one paycheck stub states 55 hours worked. The average of the two paycheck stubs is 28 hours per week, dropping the fraction (60+55 divided by four weeks) to obtain the weekly average. Project hours for the next six months by using the week begin date and the weekend date on the FSSP on the Activity screen. The FSSP will not allow entries greater than six months. Set the target date to allow collection of new verification in time to project the next six-month projection. The specialist must monitor clients working 40 hours per week at or above state minimum wage who are not participating in PATH and deferred volunteers who may be working. Change in hours of Work Activity When a client reports a change in the number of hours of employ- ment during the six-month projection, the specialist must gather actual paycheck stubs that reflect the change. Change the actual hours previously recorded in the FSSP to the actual participation as verified. Use a minimum of two new consecutive paycheck stubs, wage statements or the collateral contact to project the new six- month period that begins the month after the month with the change. Non-Paid Activities Activities assigned to a MDHHS-served client on the FSSP must be verified using a DHS-630, Weekly Activity Log, when monitoring is required. Report weeks are always Sunday through Saturday. The activity log due date is always the Friday after the weekend date. Use the target date on the FSSP Activity screen as a follow-up date for receipt of the activity log. Run the Target Date report available