Straight into the service manual page
WrenchQuarry
More

Sick time caps in New Jersey and California: 40 hours

WrenchQuarry Editorial Team · Published · 12 min read · How these guides are written

New Jersey gives most workers up to 40 hours of paid sick time each benefit year; California's rules depend on the employer's 12-month period. When a dispatcher books a tech, the usual questions are about skills, truck stock, drive time, and what the customer needs. Paid sick time adds one more question. If a tech has used most of their paid sick time, a planned day off may not be covered the way the schedule assumes, and an unexpected sick call can leave a customer waiting with nobody to send. Small shops feel this more than large ones, because one or two techs often carry most of the board.

Key takeaways

  • Check each New Jersey tech's sick time balance and benefit year with payroll before you book a multi-day job.
  • Ask payroll how your firm sets its California 12-month period, because that period controls when balances reset.
  • Check new California hires against their start date before you commit them to a long job.
  • Decide ahead of time which jobs need a fully available tech.

This post explains, in plain words, how the New Jersey and California rules work at the level a dispatcher or team lead needs. It is not legal advice.

New Jersey: up to 40 hours each benefit year

The New Jersey Department of Labor and Workforce Development says the Earned Sick Leave law requires employers to provide employees with up to 40 hours of paid sick time each benefit year. Two phrases in that sentence matter for scheduling. "Up to" sets a ceiling, not a promise that every tech has 40 hours available on every day of the year. "Each benefit year" ties the amount to a yearly period, not to the calendar month.

The law applies to almost all workers in New Jersey. That is broader than many shop owners expect, so do not assume a tech falls outside it because they work in the field or only part-time. For California part-time techs, see California paid sick leave: 4 numbers for part-time techs.

Family relationships need a closer look, because definitions vary from state to state. Washington State's rules, for example, define the term this way: "Family member means a child, grandchild, grandparent, parent, sibling, or spouse of an employee, and also includes any individual who regularly resides in the employee's home…" A brother-in-law who lives in the owner's house, or a relative who works a part-time route, could fall under a broad definition like that one. Do not assume the answer from another state. Ask how New Jersey and California treat your specific relatives, and write down what you learn.

One situation every dispatch desk eventually meets is covered too: an employee has taken all 40 hours of their NJ Earned Sick Leave but needs more time. Your firm's own policies and any other applicable rules decide what happens next, so the dispatch desk should confirm it with payroll. Settle that question before a tech runs out of hours, not in the middle of a rush.

New Jersey: questions for payroll

Before you need an answer, bring these questions to payroll for each New Jersey tech. You do not need to understand the whole law to ask them.

  1. What is the tech's current sick time balance, in hours?
  2. When does the benefit year start and end for this employee?
  3. How much has been used in the current benefit year, and on which dates?
  4. How are sick hours recorded when a tech leaves a job early or comes in late? Ask for the rule in writing.
  5. Who approves sick time, and how quickly do they answer a request?
  6. What happens when the balance reaches zero? Ask what the firm's written policy says.

The answers matter most in the moment. Question 4 is the one dispatchers usually miss. A tech who leaves a job at noon may have a different hour count than one who leaves at the end of the shift, and if the rule is unclear, the first conflict will land on the schedule.

California: the employer sets the year

The California Department of Industrial Relations explains that the employer determines how the year will be calculated, whether it tracks a typical calendar year, fiscal year, or other 12-month period. That choice controls when a balance resets.

For a dispatcher, the question is what period your company uses for each tech. A firm on a fiscal year, a hire anniversary, or a calendar year will see balances behave differently near the start of each period. If techs were hired on different dates, they may reset on different days, even inside one company.

When a tech asks why their hours changed in the middle of the year, check the period first. Many surprises come from a reset the dispatch desk did not know about, and the period is usually the fastest way to explain the change.

California: up-front policies

Under one setup, an up-front policy makes the full amount of sick leave for the year available immediately at the beginning of a year-long period. The full yearly amount is available from the first day of the period, which makes the balance easier to plan around.

That does not mean every tech has the full amount on every day. The new-hire timing described below adds an exception. It also does not mean your firm uses an up-front policy at all. Ask payroll which approach applies, because a wrong guess can leave a tech short of time on a job.

California: new hires take longer

The new-hire exception is the part that surprises most small firms. Under an up-front policy, initial hires must have 3 days or 24 hours available by the 120th calendar day of employment and 5 days or 40 hours by the 200th calendar day of employment. Use these checkpoints as dispatch actions:

CheckpointWhat dispatch should do
120th calendar day of employmentConfirm 3 days or 24 hours is available before booking a long job
200th calendar day of employmentConfirm 5 days or 40 hours is available for planned time off

In practice, a new tech may not have the full amount ready on the first day. Their hire date is the key number. Count calendar days from the start date and put both checkpoints on the calendar when you hire someone, so the desk does not discover the gap in the middle of a busy week.

A new hire is also a poor choice for a long job that depends on paid time off, even when the balance looks fine on paper. Plan a shorter first assignment, or pair them with a senior tech until the balance is clear.

California: the January 1, 2024 change

Some older schedules still reflect a transition that took place in 2024. If an employer uses an annual start date other than January 1 and implements a 12 month use cap, that cap must change to 40 hours or 5 days on January 1, 2024. The employer has the choice to frontload the two additional days on January 1, 2024 or move the measurement of the yearly period to January 1, 2024 and frontload five days.

That date has already passed, so the question for your firm is not what the rule said in 2024. The question is what your current policy says. An old spreadsheet, a handbook, or a note on the wall may still describe a cap that no longer applies.

A worked example shows why this matters. An employee started on May 1, 2021, and the employer used that anniversary date to frontload 3 days or 24 hours on May 1, 2023. On January 1, 2024, the employer had two options:

Employer choiceWhat is provided on January 1, 2024
Keep the May 1 anniversary date2 days or 16 hours
Reset the frontload date to January 1, 20245 days or 40 hours

You do not need to work through that example for your daily board. It shows why a balance can change on a date you do not expect. If your firm uses a hire anniversary, the reset may fall in the middle of a busy month, so mark those dates.

A quick check before you assign a job

Before you lock in a tech for a multi-day job, run a short check:

  1. Confirm the tech's current sick time balance with payroll. Date the answer, because a balance from Monday may not be the balance you need on Thursday.
  2. Confirm the 12-month period that the balance covers.
  3. If the tech was hired recently, check their start date against the California new-hire checkpoints, or confirm how the firm handles new hires in New Jersey.
  4. Note any scheduled time off or known medical appointments.
  5. Decide who is the backup if the tech calls out sick.

If the check reveals a low balance, you have options. You can move the tech to a shorter job, pair them with a second tech, or shift the job to a day when the balance is clearer. The purpose of the check is not to keep a tech off the schedule. It is to make sure the schedule matches what the firm can actually support. For the approval step itself, see Check 4 leave counts before you approve time off.

When a tech is running low

A low balance is a planning problem, and planning works best when it starts early. Tell the tech what you know, and ask what they expect. A short conversation a week ahead beats a surprise call at seven in the morning.

Keep the conversation factual. Say what the balance is, when it resets if you know, and what the firm's policy says. Do not promise what the policy does not promise. If you do not know the answer, say so and send the question up to payroll or the owner. A tech who hears "I'll find out and get back to you by Friday" trusts the desk more than one who hears a guess.

Decide ahead of time which jobs need a fully available tech and which can flex. Emergency calls, no-heat calls in winter, and no-cooling calls in summer usually need the most reliable coverage. Routine maintenance and scheduled installs often have more room to move. Agree on that list before the busy season starts, so you are not inventing it under pressure.

Writing a sick-call script

Most sick calls come in fast, and the dispatcher is usually the first person who hears about them. A short script keeps the call short and consistent:

  • Thank the tech for calling early, and note the time of the call.
  • Ask which jobs are affected, and whether any customer has already been given a time.
  • Tell the tech who will confirm their balance and when they will hear back.
  • Move the affected jobs to a backup or reschedule them, and tell the customer the new window.

Do not ask the tech to prove how sick they are, and do not comment on their health or reasons. The dispatch desk's job is to keep the schedule working. Medical questions belong with whoever handles leave decisions.

Keep records you can read later

For each sick-time request, keep a simple log with the tech's name, the date of the request, the hours requested, the decision, the balance payroll showed that day, and any note about customer impact. Store it where dispatch and payroll can both see it, and limit access to the people who need it. Leave medical details out. Record the dates, the hours, and the decision.

Review the log once a month. Look for patterns, such as a tech who always runs low at the same point in the year, or a backup who is overloaded. Those are scheduling problems you can solve before they become emergencies. When a tech asks why their hours changed, the log answers the question without anyone having to remember.

Common mistakes to avoid

Some mistakes show up again and again in small firms:

  • Treating a balance from a month ago as current. Balances change, so date every number.
  • Assuming every tech follows the same reset date. Hire dates can differ, and so can the period a company uses.
  • Forgetting the California new-hire checkpoints. A tech hired last month may not have the full amount yet.
  • Letting a sick call go to voicemail. A missed call can leave a customer waiting for hours and makes the tech feel unsupported.
  • Promising the tech a day, a pay outcome, or a job type you have not confirmed.

Each of these mistakes is easy to avoid with a short written procedure. Post it where the dispatch team works, and review it when the rules or your payroll setup change.

Talking with techs about their balance

Many techs do not know their own balance, or know it only roughly. Make it easy for them to ask. Send a monthly message with each tech's balance, or post a simple chart in the shop.

When a tech asks for time off, respond quickly. Confirm the request, the dates, and what you need from them. If the request is denied or changed, explain the reason in plain words and give the next step. Apply the same procedure to every tech, whether they are the owner's cousin or the newest hire. Inconsistent handling is one of the fastest ways to create a complaint.

What to do when the rules are unclear

Sometimes the rule is not clear for your situation. A tech may have worked in two states, or moved between jobs inside your company. A firm may offer a policy better than the minimum, or a contract may cover time off in a different way. When that happens, do not guess. Write down the facts and send them to an employment attorney or your payroll provider.

The New Jersey Earned Sick Leave page and the California paid sick leave FAQ are the right starting points before you ask for help. The California FAQ also shows which parts of the rule depend on your firm's setup.

The bottom line

Paid sick time is a scheduling input, just like a truck, a license, or a parts list. The rules in New Jersey and California differ. California's details depend on how the firm sets its year and handles new hires, and New Jersey's benefit year should be confirmed with payroll. You do not need to memorize the rules. You need a reliable way to check the balance, a clear backup plan, and a respectful way to talk with your techs.

Start today with one change. Ask payroll for every tech's current balance and the period it covers, and write the answers down with today's date. The next time a tech calls in sick, you will know what you are working with, and the customer will hear a plan instead of an apology.

Frequently asked questions

Do I need to know the full law to schedule a tech?

No, you need each tech's current balance and the period that balance covers, and the payroll questions above cover the rest.

Can a dispatcher decide whether a tech is too sick to work?

No, do not ask the tech to prove how sick they are, and leave medical questions with whoever handles leave decisions.

Is this post legal advice?

No, it explains the rules in plain words for scheduling, and unclear cases belong with an employment attorney or your payroll provider.

Sources

More field guides