When Your Employees Cross City Lines: Local Wage and Sick Leave Rules

Written from our own experience running California businesses, for owners and operators rather than lawyers. This is our perspective on how these rules work in practice — not legal advice. See the note at the end.

An employee drives from the county into the city, works a two-hour job, and drives back.

Two separate obligations just changed for those two hours, and neither one appears anywhere on a normal timesheet.

The same drive triggers two different rules

Minimum wage. California sets a floor. Many cities set a higher one. The rate that applies to any given hour is the highest of the federal, state and local rates for the place the work was physically performed — not where your office is, and not where the employee lives.

Paid sick leave. Several California cities have their own ordinances, and they generally trigger on hours worked inside the city. San Diego's covers an employee who performs as little as two hours of work within city limits in a week. Los Angeles uses a similar threshold. Accrual is typically earned on the hours worked in that city, on top of the statewide entitlement.

So the same two-hour job can raise the wage owed for those hours and start an accrual clock under an ordinance the employer may not have known applied to them.

The numbers move, and not together

As we write this, California's floor is $16.90 and rises to $17.40 on 1 January 2027. The City of San Diego sits at $17.75. Certain hospitality workers in some jurisdictions fall under separate rates in the $19 to $21 range.

We would not treat any of those figures as current by the time you read this. That is the point, not a caveat: state rates, city rates, and industry carve-outs each move on their own schedule, and there is no single authority that updates them all at once.

Two honest ways to handle it

Pay each hour at its own local rate. Precise, and cheapest in wages. It also drags in two consequences people tend not to anticipate. Once an employee works at two rates in a week, overtime has to be computed on a weighted average of those rates, not on whichever rate was in effect when the overtime hour happened to fall. And Labor Code section 226 requires the wage statement to itemize the hours worked at each rate. A precise approach on the wage side creates work on the overtime and reporting side.

Pay every hour that week at the highest rate that applied to any hour. More expensive — you are paying the city rate for hours worked outside the city — but it clears every floor by construction, keeps one rate on the wage statement, and avoids the weighted-average calculation entirely.

For a business where employees occasionally cross a line, we think the second approach is usually the better trade. The wage difference on a handful of hours is small next to the cost of getting a weighted-average overtime calculation wrong across a workforce, quietly, for a year.

Sick leave has a similar simplification available. Applying your single most generous accrual rule to everyone, company-wide, can never leave you short of any individual ordinance's floor. It costs some leave you did not strictly owe, and it removes an entire category of tracking error.

What you still have to track either way

Here is the part we find owners underestimate: both approaches still require knowing where the hours were worked.

Paying the highest applicable rate means knowing which rates applied that week — which means knowing where people went. The simplification saves you from per-hour rate arithmetic. It does not save you from the underlying fact.

If your timekeeping records only when someone clocked in and out, you do not have that fact, and no amount of policy will produce it after the fact. A worksite per punch, or at minimum a default location with an exception when someone works elsewhere, is the smallest version of this that actually works.

Why we do not think your software should hand you the number

This is where we will state a position that runs against how most compliance products are sold.

We do not believe a payroll or timekeeping vendor should be supplying you with minimum wage rates. Rates vary by city, by county, sometimes by industry classification, and they change on independent schedules. A vendor-supplied number that is three months stale does not protect you — it underpays your employees with your name on the paycheck, and the fact that software provided the figure is not a defence anyone will accept on your behalf.

Our own product takes the position that the employer configures the rates and the software applies them consistently, flags where hours crossed a boundary, and keeps the records that prove what was paid. We think that division is the honest one. The employer, with their counsel, owns what the number should be. The software owns whether it was applied correctly to every hour and can still be demonstrated three years later.

If your current system supplies rates for you, we would at least find out when it last updated them, and who is accountable when it is wrong.

---

This article describes California law in general terms and reflects our own opinion. It is not legal advice. Minimum wage and paid sick leave ordinances change frequently, vary by jurisdiction and industry, and the thresholds mentioned here may be out of date. Consult your HR specialist or employment counsel about your own operations.