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

Mongolia Aims to Become a Global Green Data Center Hub

International investors are being offered a unique value proposition that combines low-cost green energy with a stable, democratic regulatory environment. Mongolia has effectively repositioned itself as a prime candidate for hosting energy-intensive digital infrastructure, leveraging its vast Gobi Desert for wind and solar power generation. This shift reflects a broader strategy to diversify the national economy away from traditional mining

Can Nuclear Power Solve Ireland’s Data Center Energy Crisis?

The emerald hills of the Irish countryside are increasingly housing massive, humming concrete monoliths that consume electricity at a rate capable of powering entire cities. Currently, this island nation serves as the primary European base for sixteen of the world’s twenty most influential technology corporations. This concentration of digital infrastructure has turned a prestigious economic title into a significant utility

How Will AI and Automation Shape the Future of Cloud DevOps?

The relentless acceleration of global data throughput in the modern enterprise has reached a critical point where human intervention is no longer the safety net but the primary point of failure. As digital infrastructures evolve into sprawling, interconnected webs of microservices and ephemeral containers, the traditional methods of manual oversight are being dismantled in favor of autonomous intelligence. This shift

How Do Terraform and Ansible Compare in Modern DevOps?

The technical distinctions between these two prominent Infrastructure as Code tools often dictate the architecture of a company’s deployment strategy. In the current landscape where cloud-native ecosystems have become the standard for enterprise operations, selecting the right automation framework is no longer a matter of preference but a core requirement for scalability. As engineering teams manage thousands of microservices across

How Modern DevOps Strategies Drive Engineering Success

A complex digital outage often stems not from a lack of technology, but from a fundamental breakdown in how teams communicate across their automated pipelines. While organizations spent years chasing the promise of seamless delivery, many discovered that adding software layers only increased the distance between developers and users. Success now depends on moving past superficial tool adoption to foster