Amplifying Labor Rights: An Overview of Chicago’s Paid Leave and Sick and Safe Leave Ordinance

On November 9, 2023, the Chicago City Council passed the Chicago Paid Leave and Paid Sick and Safe Leave Ordinance (the “Ordinance”), set to take effect on December 31, 2023. This groundbreaking legislation expands on the current City of Chicago Paid Sick Leave Ordinance (PSLO) by introducing a significant increase in the number of days of paid leave that employers must provide to their employees. In this article, we will delve into the key provisions of the Ordinance, its coverage, accrual requirements, caps, carryover rights, payout obligations, and compliance measures.

Expansion of Paid Leave

The existing PSLO guarantees a minimum of five days of paid sick leave. However, under the new ordinance, employers are now obligated to offer an additional five days of general paid leave to covered employees. This noteworthy expansion ensures that employees have more flexibility to utilize leave time for various purposes beyond just sickness.

Coverage and Eligibility

The scope of the Ordinance is vast, as it applies to all employers, regardless of their size, operating within the city limits of Chicago. Furthermore, the Ordinance covers all employees who perform at least two hours of work within the City of Chicago in any given two-week period. This comprehensive approach ensures that a wide range of employees will benefit from the additional paid leave entitlements.

Accrual of Paid Leave and Paid Sick Leave

Starting from January 1, 2024, or on the first calendar day of employment, covered employees must accrue a minimum of one hour of paid leave and one hour of paid sick leave for every 35 hours worked. This accrual system ensures that employees earn paid leave benefits in proportion to their hours worked, allowing for a fair distribution of time off throughout the year.

To promote responsible usage, the ordinance imposes caps on the accumulation of both paid leave and paid sick leave. Each covered employee may accumulate up to 40 hours of paid leave and 40 hours of paid sick leave, although an employer can choose to set a higher limit. Notably, the ordinance grants a carryover option, enabling employees to roll over up to 16 hours of paid leave and a substantial 80 hours of paid sick leave from one 12-month accrual period to the next.

Payout and Separation

In a move to protect employees’ rights, the ordinance stipulates that employers must pay out any remaining paid leave time to a covered employee upon their separation from the company. This provision ensures that employees receive appropriate compensation for any accrued but unused leave, aiming to ease the transition period during job changes.

Compliance and Penalties

Employers must proactively review the requirements outlined in the Ordinance ahead of its implementation on December 31, 2023. Failure to comply with the Ordinance can result in significant penalties. Employers found in violation can face fines ranging from $500 to $3,000 per offense. To avoid penalties and maintain a positive work environment, it is crucial for employers to stay current with their obligations under the Ordinance.

The Chicago Paid Leave and Paid Sick and Safe Leave Ordinance represent a major milestone in employee rights. By expanding the existing PSLO, employees in the city gain additional paid leave days, leading to an improved work-life balance, increased employee well-being, and enhanced productivity. Employers must familiarize themselves with the ordinance’s provisions, such as accrual rates, caps, carryover rights, and payout obligations, to ensure compliance and avoid penalties. By embracing these changes, employers can foster a culture that values employee welfare while keeping their organizations in line with evolving labor standards.

Explore more

Transforming APAC Payroll Into a Strategic Workforce Asset

Global organizations operating across the Asia-Pacific region are currently witnessing a profound metamorphosis where payroll functions are shedding their reputation as stagnant cost centers to emerge as dynamic engines of corporate strategy. This evolution represents a departure from the historical reliance on manual spreadsheets and fragmented legacy systems that long characterized regional operations. In a landscape defined by rapid economic

Nordic Financial Technology – Review

The silent gears of the Scandinavian economy have shifted from the rhythmic hum of legacy mainframe servers to the rapid, near-invisible processing of autonomous neural networks. For decades, the Nordic banking sector was a paragon of stability, defined by a handful of conservative “high street” titans that commanded unwavering consumer loyalty. However, a fundamental restructuring of the regional financial architecture

Governing AI for Reliable Finance and ERP Systems

A single undetected algorithm error can ripple through a complex global supply chain in milliseconds, transforming a potentially profitable quarter into a severe regulatory nightmare before a human operator even has the chance to blink. This reality underscores the pivotal shift currently occurring as organizations integrate Artificial Intelligence (AI) into their core Enterprise Resource Planning (ERP) and financial systems. In

AWS Autonomous AI Agents – Review

The landscape of cloud infrastructure is currently undergoing a radical metamorphosis as Amazon Web Services pivots from static automation toward truly independent, decision-making entities. While previous iterations of cloud assistants functioned essentially as advanced search engines for documentation, the new frontier agents operate with a level of agency that allows them to own entire technical outcomes without constant human oversight.

Can Autonomous AI Agents Solve the DevOps Bottleneck?

The sheer velocity of AI-assisted code generation has created a paradoxical bottleneck where human engineers can no longer audit the volume of software being produced in real-time. AWS has addressed this critical friction point by deploying specialized autonomous agents that transition from simple script execution toward persistent, context-aware assistance. These tools emerged as a necessary counterbalance to a landscape where