Picture a slow Tuesday afternoon. The lunch rush never materialized, the forecast says snow by evening, and you tell two scheduled servers to clock out after 45 minutes. Reasonable call — except that in nine US jurisdictions, you just bought hours you never received. The paycheck for that 45-minute shift could legally owe three or four hours instead.
That is reporting-time pay — often called "show-up pay" — and small employers trip over it constantly. Not because the rules are complicated in any single state, but because federal law says nothing about it at all, so owners assume no rule exists. Here is what each jurisdiction actually requires, the scheduling laws that stack on top, and the bookkeeping habits that keep a slow day from becoming a back-pay claim.
What Reporting-Time Pay Actually Is
Reporting-time pay is a minimum payment owed to a nonexempt employee who shows up for a scheduled shift but is given little or no work. The policy logic is simple: the employee spent time and money getting to work based on your schedule, so the cost of your over-scheduling should not land entirely on them.
Three things it is not:
- It is not federal law. The Fair Labor Standards Act requires pay only for time actually worked. An employee who reports for an eight-hour shift and is sent home after 15 minutes is owed 15 minutes of pay under federal law — unless a state law says otherwise.
- It is not overtime. It is compensation for showing up, and in most jurisdictions it does not count as hours worked toward overtime thresholds.
- It is not about firing or layoffs. It fires shift by shift, on ordinary days: slow afternoons, double-booked crews, deliveries that never arrived, weather that killed foot traffic.
Only a handful of jurisdictions have these laws, but they include California and New York — so a large share of American small businesses operate under at least one of them.
The Nine Jurisdictions, Side by Side
Eight states plus the District of Columbia require some form of reporting-time or show-up pay. Oregon's rule covers minors only; everywhere else on this list it covers all nonexempt employees:
| Jurisdiction | Minimum owed when a scheduled employee reports but gets little or no work |
|---|---|
| California | Half the scheduled shift, minimum 2 hours, maximum 4 hours, at the regular rate |
| New York | 4 hours or the scheduled shift, whichever is less, at the minimum wage |
| Massachusetts | 3 hours at the minimum wage (only if the shift was scheduled for 3 or more hours) |
| Connecticut | 4 hours in mercantile establishments, 2 hours in hotels and restaurants, at the minimum wage |
| District of Columbia | 4 hours, or the regularly scheduled hours if fewer |
| Rhode Island | 3 hours at the regular rate, even if the shift was scheduled shorter |
| New Hampshire | 2 hours at the regular rate |
| New Jersey | 1 hour at the applicable wage rate |
| Oregon | Minors under 18 only: half the scheduled shift or 1 hour, whichever is more, at the regular rate |
Note the fault line running through the table: some jurisdictions pay the employee's regular rate, others pay only the minimum wage. Paying the wrong rate is one of the most common violations, and it is covered in the mistakes section below.
California: Half the Shift, Two to Four Hours
California's rule, found in Section 5 of the Industrial Welfare Commission Wage Orders, is the one most employers encounter first:
Each workday an employee is required to report for work and does report, but is not put to work or is furnished less than half the usual or scheduled day's work, the employee is paid for half the usual or scheduled day's work — but never less than two hours nor more than four hours, at the regular rate of pay.
Work through the math on an eight-hour shift at $22 per hour:
- Sent home after one hour: half the shift is four hours, so you owe four hours ($88), not one.
- Sent home after five hours: that exceeds half the shift, so you owe only the five hours worked.
- Sent home immediately from a three-hour shift: half would be 90 minutes, but the two-hour floor lifts it to two hours ($44).
Three California wrinkles catch experienced operators off guard:
A second reporting earns its own minimum. If you send someone home and call them back later the same workday, the second reporting carries its own two-hour minimum. Splitting one shift into two pieces around a slow midday can cost more than keeping the employee on the clock.
Short meetings count. An employee required to attend a staff meeting or training session that lasts less than two hours is owed a two-hour minimum. The 30-minute all-hands you scheduled on everyone's day off is two hours of pay per attendee.
Phoning in about an on-call shift can itself be "reporting." California courts have treated a required call-in to learn whether an on-call shift is happening as reporting for work — meaning a "don't come in" answer can still trigger reporting-time pay for the shift that never happened. If you run on-call scheduling in California, budget for this or restructure the shifts.
California does excuse reporting pay in narrow circumstances: when operations genuinely cannot commence or continue because of threats to employees or property, a utility failure, or an act of God beyond your control. Read that narrowly. A store closed all day by a blackout qualifies; a merely slow snow day where you opened the doors and then sent people home early likely does not.
New York: Call-In Pay at the Minimum Wage
New York calls it "call-in pay," and the rule sits in the state wage orders: an employee who reports for work by the employer's request or permission is paid for at least four hours — or the number of hours in the regularly scheduled shift, whichever is less — at the basic minimum hourly wage.
Two practical notes:
- The rate is the minimum wage, not the regular rate. A server earning well above minimum wage who is sent home after one hour of a six-hour shift is owed four hours at the minimum wage for the unworked time, plus actual earnings for the hour worked. New York applies a weekly reconciliation: if the employee's total earnings for the week already exceed what the minimum-wage guarantee would add, nothing extra is owed.
- Hospitality has its own mirror rule. Restaurant and hotel employees fall under the Hospitality Industry Wage Order rather than the miscellaneous-industries order, so look up the version that covers your workforce.
New York also has a spread-of-hours rule that fires on long days rather than short ones: when a workday spans more than 10 hours from start to finish — a split shift is the classic case — the employee earns an extra hour of pay at the minimum wage. New York once proposed a sweeping expansion of its scheduling rules in 2017, but the proposal was never finalized, so call-in pay plus spread-of-hours remains the framework.
The Other Seven in Brief
Massachusetts guarantees at least three hours at the minimum wage, but only when the employee was scheduled for three or more hours. A two-hour shift that evaporates owes nothing beyond time worked; a six-hour shift cut to one hour owes three.
Connecticut splits by industry: mercantile establishments owe four hours at the minimum wage when a reporting employee is not given a full shift, while hotels and restaurants owe two. There is a narrow written-agreement exception for shifts regularly scheduled under four hours, but it requires paying at least double the minimum wage and state approval — not a DIY workaround.
The District of Columbia requires four hours for each day an employee reports but is given no work or fewer than four hours. Employees regularly scheduled for fewer than four hours are paid their scheduled hours instead. Unworked guarantee hours are paid at no less than the minimum wage.
Rhode Island frames it as "wages for failure to furnish shift work": at least three hours at the regular rate, even when the scheduled shift itself was shorter than three hours.
New Hampshire requires at least two hours at the regular rate whenever an employee reports at the employer's request — even if zero work is performed.
New Jersey sets the lowest floor in the country: one hour at the applicable wage rate. Small per incident, but it still generates penalties and paperwork when ignored across a workforce.
Oregon is the outlier: its reporting-pay rule covers only workers under 18, who get half the scheduled shift or one hour, whichever is more, at the regular rate. Adult employees have no state show-up guarantee — but many work under Oregon's statewide fair-workweek law, which is the next layer.
The Scheduling Laws That Stack on Top
Reporting-time pay covers what happens after someone shows up. A separate wave of fair-workweek and predictive-scheduling laws governs what happens before — and these can cost you money even when nobody reports at all.
San Francisco, Emeryville, Seattle, New York City, Philadelphia, Chicago, Los Angeles, and the state of Oregon all run some version of these rules, typically aimed at large retail, hospitality, and food-service employers. The common shape:
- Advance notice. Schedules must be posted 14 days out (the exact window varies by city).
- Predictability pay. Employer-initiated changes inside the notice window trigger a premium — often an extra hour of pay at the regular rate — per change.
- Consent and premium for added shifts. Last-minute extra shifts can require the employee's written consent plus premium pay.
- Right to rest. Some ordinances penalize "clopening" — scheduling a closing shift followed by an opening shift with fewer than 10 or 11 hours between them.
The key insight for small operators: these laws and reporting-time pay are cumulative, not alternative. A late schedule change that you then partially reverse can trigger predictability pay for the change and reporting-time pay when the employee shows up to a shortened shift. If you operate in a covered city, map both layers before you touch the schedule.
Six Mistakes That Turn Slow Days Into Back-Pay Claims
1. Paying minimum wage where the regular rate is required. California, New Hampshire, New Jersey, and Rhode Island (plus Oregon for minors) require the employee's regular rate — not the minimum wage. Payroll systems default to minimum-wage premiums for "show-up" codes, so verify the rate per jurisdiction instead of trusting the default.
2. Treating on-call shifts as free. In California, a required call-in can be reporting for work, and the resulting obligation attaches even when the answer is "stay home." Audit every on-call arrangement in reporting-pay states; a schedule full of maybe-shifts is a schedule full of liabilities.
3. Assuming a last-minute text fixes everything. Telling an employee not to come in before they report generally avoids the obligation — but the text has to beat the commute. Once the employee has reported, the guarantee has attached, and no amount of apologetic texting un-attaches it. Managers who wait to see whether it gets busy, then send arrivals home, are manufacturing claims.
4. Forgetting California's second-report and meeting minimums. The callback minimum and the two-hour meeting minimum live in the same Wage Order section as the main rule and are missed just as often. Any policy that splits shifts or schedules short meetings in California needs these priced in.
5. Counting guarantee hours as hours worked for overtime. Reporting-time pay compensates the inconvenience of showing up; in California it is generally not wages for hours worked, so it does not push employees toward daily or weekly overtime thresholds and does not enter the regular-rate calculation. Folding it into overtime math overpays every week — and misstating hours worked creates its own record-keeping exposure. Confirm the treatment with employment counsel for your state rather than assuming.
6. Running one payroll rule across every location. The table above is nine different answers. A single national "show-up pay = 2 hours at minimum wage" rule underpays California, Rhode Island, and New Hampshire while overcomplicating New Jersey. Configure the earnings code per worksite, and re-check it whenever you hire in a new state.
How to Book It Cleanly
Compliance here is mostly a record-keeping problem, which makes it a bookkeeping problem. Four habits cover most of the exposure:
- Give it its own earnings code. Reporting-time pay should never hide inside regular hourly wages. A dedicated pay code —
RPTorSHOWUP— makes the amounts auditable, keeps them out of overtime math, and proves you paid them if a wage claim ever asks. - Reconcile schedules against timecards weekly. The liability lives in the gap between "scheduled 8, worked 1.5." A weekly report joining scheduled hours to clocked hours, filtered to reporting-pay jurisdictions, surfaces every owed guarantee before payroll closes.
- Log every schedule change with a timestamp. Predictive-scheduling premiums turn on when the change was made relative to the shift. A scheduling tool that records who changed what and when is the difference between a defensible position and a guess.
- Track it by worksite, not by employee home address. The law that applies is the law where the work happens. Employees who float between locations need their guarantee hours tagged to the site of each shift.
Accurate books do more than satisfy auditors — they reveal the true cost of your scheduling habits. When show-up pay shows up as its own line item month after month, chronic over-scheduling stops being invisible and starts being fixable.
Keep Your Payroll Records Audit-Ready
Reporting-time pay is a small rule with an outsized paper trail: per-shift guarantees, per-jurisdiction rates, schedule-change timestamps, and payroll codes that all have to agree with each other. The employers who handle it well are the ones whose records already tie schedules to timecards to paychecks without manual detective work.
As you tighten up scheduling compliance, maintaining clear financial records is essential. Beancount.io provides plain-text accounting that gives you complete transparency and control over your financial data — no black boxes, no vendor lock-in. Get started for free and see why developers and finance professionals are switching to plain-text accounting.
