Philadelphia Fair Workweek Law: Notice, Predictability Pay, and Manager Checklist

The philadelphia fair workweek law shows up in the back office on a Thursday afternoon, when the weekend schedule still is not final and two people have already texted that they cannot close.

You are not trying to make anyone’s life harder. You are trying to cover dinner rush, a Saturday hotel desk, a clinic front desk, or a retail floor that gets slammed after work. But in Philadelphia, last-minute schedule edits can carry legal and payroll consequences if your business is covered.

The risk is not just one missed poster or one late schedule. It is the pattern: schedule posted late, shift moved, hours cut, closer brought back early, employee not paid correctly, records too thin to explain what happened.

Philadelphia’s Fair Workweek law generally requires covered retail, hospitality, and service employers to give predictable schedules, provide advance schedule notice, pay predictability pay for certain employer-initiated changes, and allow nine hours of rest between certain shifts unless the employee consents and receives required pay.

Philadelphia Fair Workweek Law Basics for Managers

Who is usually covered

Philadelphia’s Fair Workweek law applies to certain larger employers in service, retail, and hospitality. The city’s guidance describes covered employers as those with at least 250 employees and 30 locations worldwide.

That means a single independent restaurant, salon, or gym may not be covered just because it operates in Philadelphia. A national chain location, hotel group, large retailer, or multi-location service business may be.

Do not guess based on the size of one store. Coverage can depend on the wider company footprint, not only the number of people working at your Philadelphia site. If you manage a local branch of a bigger brand, confirm coverage with your HR, payroll, or legal team.

For more shift compliance topics, see the /category/labor-law hub.

What the law is trying to control

The law is about predictability. Employees should know when they are expected to work early enough to plan child care, transit, school, second jobs, and rest.

For managers, the practical message is simple: build the schedule earlier, document employee availability, track changes after posting, and know when a change triggers extra pay.

The law does not mean operations stop when someone calls out. It means the reason for the change, who initiated it, whether the employee consented, and what pay is owed all matter.

Philly Predictive Scheduling: What to Do Before You Post

Start with availability and qualifications

A compliant schedule starts before you drag names into boxes. You need current availability, role qualifications, time-off requests, overtime exposure, and enough notes to explain why a person was scheduled for a certain role.

For example, a hotel may need one front desk worker who can handle night audit, one housekeeper trained on inspection, and one manager on call. A restaurant may need a certified food protection manager, two line cooks, a bartender, and hosts who are available through the rush.

If you wait until the final hour, every constraint becomes a surprise.

Give a good faith estimate

Covered employers must provide employees with a written good faith estimate of their expected work schedule. In practice, this should describe what the employee can generally expect: average hours, days, times, and whether on-call work or variable scheduling may happen.

Treat the estimate as a baseline, not a throwaway form. If the actual schedule keeps drifting away from the estimate, review whether the estimate needs updating and whether your staffing model is realistic.

A good faith estimate does not freeze the schedule forever. It gives the employee a fair picture of what the job is likely to require.

Build a scheduling calendar

Managers often miss schedule notice rules because the posting deadline is not treated like payroll. It should be.

Use a recurring scheduling rhythm:

Task	Manager action	Why it matters
3 weeks out	Collect time-off requests and availability updates	Reduces avoidable late edits
2.5 weeks out	Draft coverage by role, location, and qualification	Finds gaps before notice deadline
2 weeks out	Post and provide the written schedule	Supports Philadelphia schedule notice compliance
After posting	Track every employer-initiated change	Determines predictability pay
Payroll review	Match changes to pay codes and records	Prevents missed premiums

The goal is not a perfect schedule. The goal is a schedule you can defend.

Philadelphia Schedule Notice Rules

The 14-day notice standard

Philadelphia schedule notice rules generally require covered employers to provide work schedules 14 days in advance. This is the core rule managers feel first: the schedule cannot live in someone’s notes until the week starts.

A posted schedule should be clear enough that employees know their workdays, start and end times, work location, and role where relevant. If your location uses multiple departments, stations, or teams, make the assignment clear enough to avoid confusion.

For related coverage planning, the retail scheduling foot traffic guide is useful when demand changes by hour, day, or event.

What counts as a change

After the schedule is posted, an employer-initiated change can include adding time, reducing time, changing the shift time, changing the date, changing the location, canceling a shift, or making certain on-call changes.

Small timing differences may be treated differently under the rules, and exceptions can apply. But from a manager’s perspective, do not rely on memory. Record the original posted shift, the changed shift, who initiated the change, when it happened, and whether the employee requested or agreed to it.

That record is what payroll and compliance teams need later.

Employee-requested changes are different

If an employee asks to swap a day, leave early, call out sick, use time off, or change availability, that is different from the employer changing the schedule.

The key is documentation. A text, email, written request, or system record can help show that the employee initiated the change. Without a record, a later dispute may look like a manager changed the schedule and failed to pay what was owed.

Keep this practical. You do not need a legal memo for every change. You do need a reliable habit.

Philadelphia Predictability Pay

When predictability pay may be owed

Philadelphia predictability pay is extra compensation for certain employer-initiated changes to a posted work schedule. If the employer changes the schedule after the required notice period, the employee may be owed extra pay even if the manager had a good operational reason.

Common examples include adding hours, moving a shift, changing the work location, canceling a shift, shortening a shift, or not calling in an employee who had been scheduled for on-call work.

The reason matters, but the payroll result still has to be checked.

How the pay generally works

Under the city’s framework, adding time to a shift or changing the date, time, or location without a loss of hours can generally trigger one hour of predictability pay at the employee’s regular rate.

Reducing hours, canceling a regular shift, or certain on-call changes can generally trigger pay based on a portion of the employee’s regular rate for hours not worked.

Use this as a manager’s guide, not a substitute for payroll review. The exact result can depend on the facts, current city guidance, employee classification, tipped wage treatment, and exceptions.

Common exceptions to review

Predictability pay is not always owed. It may not apply when the employee requested the change in writing, when employees voluntarily trade shifts under an employer policy, when operations are affected by certain emergencies, or when other listed exceptions apply.

Still, exceptions are where mistakes happen. If you are relying on an exception, record the reason at the time. “We all knew what happened” is weak documentation two pay periods later.

A simple change log beats a scramble through texts.

Philadelphia Rest Between Shifts

The nine-hour rest rule

Philadelphia rest between shifts rules generally protect employees from being scheduled too close together after a previous day’s shift or a shift that spans two days.

The basic standard is nine hours of rest between certain shifts. If an employee closes late and is asked to come back early, check the gap before you finalize the schedule.

This is especially relevant for restaurants, hotels, gyms, security teams, clinics, and warehouses where closing, overnight, and opening shifts can overlap. For more on the operational strain of back-to-back shifts, see the guide to clopening shifts.

Consent and extra pay

If a covered employer schedules an employee with less than the required rest period, the employee generally must provide advance written consent and receive the required payment.

City materials describe a $40 payment tied to this less-than-nine-hour rest scenario. Because rates and guidance can change, managers should verify current city rules before building this into payroll settings.

Do not treat consent as implied because the employee showed up. Get the written consent before the shift sequence when the rule requires it.

Manager checklist for close-open shifts

Before assigning a close-open sequence, ask:

Question	If yes	If no
Is the employer covered by the Philadelphia law?	Apply the rest rule workflow	Follow company policy and other applicable law
Is the gap less than nine hours?	Check consent and pay requirements	Schedule may be acceptable under this rule
Did the employee give advance written consent?	Keep the record	Do not rely on verbal agreement
Is the required payment coded for payroll?	Review before payroll closes	Fix before wages are processed

This is one of the easiest rules to catch if your scheduling process flags short rest gaps automatically.

A Practical Compliance Workflow

Lock the schedule earlier than the deadline

If the law requires 14 days of schedule notice, do not aim for exactly 14 days. Aim earlier internally so manager edits, approvals, and coverage gaps do not push you late.

A realistic workflow is to draft at least several days before posting, review overtime and qualifications, then publish on a fixed day every week.

The habit matters more than the tool. Employees learn when to expect schedules, and managers learn when decisions are due.

Track changes in one place

The most dangerous schedule is the one that exists in three places: a wall printout, a manager spreadsheet, and a string of text messages.

Use one source of truth for the posted schedule and one change log for edits after posting. For each change, capture:

Field	Example
Original shift	Friday, 3 p.m. to 11 p.m., front desk
Changed shift	Friday, 5 p.m. to 11 p.m., front desk
Initiated by	Manager
Reason	Forecasted occupancy dropped
Employee consent	Not needed for reduction, payroll review required
Pay review	Check predictability pay for hours reduced

This is also where team communication matters. If you are tightening schedule workflows, the guide to team communication for shift workers can help reduce missed updates.

Train assistant managers

Fair workweek mistakes often come from well-meaning assistant managers trying to solve a coverage problem fast.

Train them on four questions:

1. Has the schedule already been posted?
2. Who is asking for the change?
3. Does the change add, move, reduce, cancel, or shorten hours?
4. Does the change create less than nine hours of rest?

If they cannot answer those questions, they should pause and document before changing the schedule.

How ShiftSynch helps

ShiftSynch makes compliant scheduling easier to keep up: set rotation patterns, manage time-off and availability, and keep advanced reports and PDF/Excel exports for your records — all from web or mobile.

Start free — no credit card required (1 team, up to 10 staff); paid plans start at $19/month with a 14-day trial.

Start free on ShiftSynch

Philadelphia scheduling compliance is mostly about rhythm: build earlier, post clearly, document changes, and pay correctly when the rules require it. If you manage a covered team, make the law part of your weekly scheduling process instead of a payroll surprise.

Frequently Asked Questions

Q: What is Philly predictive scheduling? Philly predictive scheduling refers to Philadelphia’s Fair Workweek rules for certain larger service, retail, and hospitality employers. Covered employers generally must provide predictable schedules, good faith estimates, advance schedule notice, predictability pay for certain employer-initiated changes, and rest protections between certain shifts. Managers should verify current city guidance before applying an exception.

Q: How much Philadelphia schedule notice is required? Covered employers generally must provide Philadelphia schedule notice 14 days in advance of the workweek. The schedule should be provided in writing and should clearly show when and where the employee is expected to work. If the employer changes the posted schedule later, the change may need documentation and payroll review.

Q: When is Philadelphia predictability pay owed? Philadelphia predictability pay may be owed when a covered employer makes certain employer-initiated changes after the schedule is posted, such as adding hours, moving a shift, changing location, reducing hours, canceling a shift, or changing on-call work. Some employee-requested changes and other exceptions may not trigger pay, but documentation is critical.

Q: What are the Philadelphia rest between shifts rules? Philadelphia rest between shifts rules generally protect covered employees from being scheduled with less than nine hours of rest after certain shifts. If an employee works with less than that rest period, the employer may need advance written consent and required payment. Managers should verify the current city rule before scheduling close-open combinations.