Laserfiche WebLink
that the definition of eligible worker, which includes "any work performed by an employee of <br />a ... Tribal government," also include an employee of a "Tribal enterprise" to remove <br />uncertainty regarding which employees are included. <br />Finally, commenters made suggestions for the process by which the chief executive (or <br />equivalent) of a recipient government may designate additional non-public sectors as critical. <br />Commenters asked that Treasury adopt a requirement that Treasury must approve or deny any <br />additional non-public sector identified by the chief executive of a recipient government prior to <br />implementation of the recipient's program. <br />Some commenters asked Treasury to clarify whether their chief executive (or equivalent) <br />could designate particular, and in some cases all, employees of the recipient government as <br />eligible for premium pay. <br />Treasury Response: In the final rule, Treasury will preserve the definition of "eligible <br />worker" as it was defined in the interim final rule with minor modifications to clarify that all <br />public employees of recipient governments are already included in the interim final rule <br />definition of "eligible worker." A more specific eligibility system (e.g., linking eligibility to <br />specific occupational or industry codes) would have provided more certainty but would have <br />been much more rigid. In contrast, the current definition is flexible enough to give recipients the <br />ability to tailor their premium pay programs to meet their needs while ensuring that programs <br />focus on sectors where workers were forced to shoulder substantial risk as a result of the <br />COVID-19 pandemic. Furthermore, the critical infrastructure sectors defined in the interim final <br />rule already include many of the occupations that commenters requested be added. For example, <br />Treasury received many comments from public workers asking to be included in the definition of <br />"eligible worker" even though these workers already fall within the scope of "any work <br />223 <br />