Skip forward into hiring notes
RosterAcorn

Two notice periods to plan for employee changes

What are the two notice periods this post covers?

Two official notice periods apply when you change an employee's terms: 30 calendar days for a New Jersey benefit year change, and a full 60/120 day period when a change results in a worse offer under OPM guidance.

Two official sources give a fixed notice period for a change to an employee's terms, and they cover very different situations. The first is a New Jersey rule that requires 30 calendar days' written notice before an employee's earned sick leave benefit year is changed. The second comes from the U.S. Office of Personnel Management's Vet Guide for HR Professionals, which covers veterans in a Reduction In Force, and it requires a full 60/120 day notice period when a change results in a worse offer. Neither one is a general rule for every employer. Two scopes: a New Jersey benefit year change, and a Reduction In Force change that produces a worse offer.

Key Takeaways

  • Count backward from your target effective date to find the latest day you can send a notice.
  • The New Jersey rule covers only changing the earned sick leave benefit year, not every leave or pay change.
  • The OPM 60/120 day period applies to federal Reduction In Force changes that produce a worse offer.
  • Send any notice in writing, to the named office, and keep a record of the date and method.
SourceSituation coveredNotice periodSource
New Jersey ruleChanging the earned sick leave benefit yearAt least 30 calendar days prior to the proposed change NJDOL
OPM Vet GuideChange resulting in a worse offer Full 60/120 day notice period required by regulationOPM

For a recruiter or hiring manager, the practical lesson is that a change to pay, schedule, leave, or an offer can carry a deadline you did not choose. Before anything changes, find out which rules apply to the person and the role. Then count backward from the date you want the change to take effect, and build the calendar from that date instead of from the day someone asks for the change.

How does the New Jersey 30-day notice work?

The New Jersey Department of Labor and Workforce Development says on its earned sick leave page that "To change the benefit year, you must provide notice in writing to the NJDOL Commissioner at least 30 calendar days prior to the proposed change." Read the full page to confirm who "you" refers to in your situation before you act on it.

Element of the ruleRequirement statedSource
Form of noticeMust be in writingNJDOL
RecipientNJDOL CommissionerNJDOL
Timing At least 30 calendar days prior to the proposed changeNJDOL
Scope caveatNotice requirements differ depending on the type of leave you need NJDOL

Three parts of that sentence matter for planning. The notice has to be in writing. It has to go to a named office, the NJDOL Commissioner. And it has to be given at least 30 calendar days before the proposed change, so a notice given 20 days ahead does not meet the rule. The word "calendar" means you count every day on the calendar, not only working days. Put the deadline on the calendar with the day of the week beside it, so nobody has to do the arithmetic twice.

The same page makes a point that is easy to miss: "Notice requirements differ depending on the type of leave you need." A single benefit setting can therefore carry different notice rules for different kinds of leave. Before you send a notice, confirm which leave types the change touches and check each one against the guidance. Do not apply one notice period to everything and hope it fits.

Keep a record of the notice. Save a copy of the written notice, the date it was sent, the method used, and the office or person it went to. If the change affects a group of employees, keep one master copy and a list of who was covered. A clean record is the difference between a change you can defend and one you must rebuild from memory.

When does a worse offer need 60/120 days' notice?

SituationNotice or deadline stated in the source Official source
New Jersey earned sick leave: changing the benefit year Written notice to the NJDOL Commissioner at least 30 calendar days prior to the proposed change NJDOL
Federal Reduction In Force: employee appeal to MSPB Normally filed within 30 days of the Reduction In Force effective date; MSPB may accept later appeals filed within 30 days of the employee becoming aware of the change OPM

The table sets the three facts side by side. OPM's guidance puts the offer rule this way: "If such a change results in a worse offer, the affected employee must be given a full 60/120 day notice period required by regulation." The word "such" points back to a change described earlier in that section, so read the surrounding text before you apply it to your own case. The guidance is federal, so it may not reach your employer, but the trigger it names is worth copying into your own process: a worse offer is treated as a change that needs formal notice, not a routine edit.

The New Jersey rule is a count of calendar days before a change. The federal offer rule is a 60/120 day period, and the quoted sentence does not say which figure applies to which case. Do not pick one from memory. Read the regulation the guidance cites and your own HR policy before you set a date.

Route the flagged revision to HR or counsel before the new letter goes out, so the review happens while the calendar still has room. This is a sound habit, not a rule, and your employer's policy decides the details.

What should you do when an offer gets worse after it was made?

Stop the change, confirm which rules apply, and set the notice date before anyone sends a revised offer or changed terms.

Start by writing the original terms and the proposed terms side by side. A plain two-column list shows every difference, including the small ones, such as a start date that moves or a benefit that changes its timing. Mark each difference that leaves the person worse off. Those are the items that may trigger a notice period under the rules in this post, and they are the ones to bring to a reviewer.

Next, name an owner. In a small staffing team these may be the same person, and that is workable as long as someone checks the notice before it goes out. Assign one named person to the notice and set a review point with the hiring manager. Keep it simple: one owner, one approver, one date.

A risk at this stage is a change that reaches the employee after its notice period has already run. Treat the notice date as fixed, and move the effective date to fit around it. The timeline comes later in this post.

Does a change to an offer differ from a change to a current employee?

The planning steps are the same, but the reasons to slow down are different.

Once it is accepted, a change to it can feel like a broken promise, even when the change is small.

With a current employee, the change reaches terms the employee already depends on, such as pay, schedule, benefits, or leave. Because the employee is still working, you can usually give written notice in advance and set the change for a date that leaves room for the full notice period. Talking it through in person helps, but a conversation does not replace the written notice a rule requires.

Who should review a change before it goes out?

Anyone who can change pay, hours, or start dates should review the change, and any change that carries a notice period needs a named reviewer who can confirm its scope.

For a small staffing team, a short review list works better than a long policy. The hiring manager confirms the business reason and the effective date. HR or the payroll contact checks the terms against what the organization can pay and provide. A compliance reviewer reads the rule and confirms that its notice period and scope apply. Where a federal or state rule is involved, that last review belongs with employment counsel rather than with whoever drafted the letter.

Set a time limit for reviews too. Ask reviewers to finish within a fixed window, so a change does not sit unreviewed until its notice deadline has nearly passed. The window is your choice. It should be short enough that the calendar still works.

Record each approval in the same file as the notice. When someone asks later, the file should show who checked what and when. A reviewer who signs off on a worse offer without the rule in front of them is the failure this process is meant to prevent.

Worked example: counting back 30 calendar days

Suppose a New Jersey team plans to change an employee's benefit year, with the change set to take effect several weeks from today. Counting back at least 30 calendar days from that effective date gives the latest day to send the notice. This example is invented.

That leaves the team a fixed window to draft the notice, complete the review, and send the written notice to the NJDOL Commissioner, as the guidance requires. If the review runs past that deadline, the notice goes out late, and the team must move the effective date later. The team cannot send the notice after the deadline and keep the original date.

The example also shows why the scope needs checking first. If the change touches more than one type of leave, each type may need its own check, because the guidance says notice requirements differ depending on the type of leave. A team that skips that check may send a notice that covers the wrong leave type and then has to start over.

The arithmetic is the easy part. The harder work is confirming which rule applies and getting the notice to the right office in time. A simple calendar entry for each step, with an owner beside it, catches timing problems early.

What if the employee disagrees with the change?

The federal rule in the OPM guidance is that the Merit Systems Protection Board normally requires an appeal within 30 days of the Reduction In Force effective date.

Appeal or retention pointDetail stated in the source Source
MSPB normal appeal windowWithin 30 days of the Reduction In Force effective date OPM
MSPB later appeal option Within 30 days of the employee becoming aware of the changeOPM
Retention preference findingEligible employee not provided retention preference consistent with P.L. 105-85 OPM
Recommended remedy Agency takes appropriate corrective actionOPM
Applies to RIFs effective on or afterNovember 18, 1997 OPM

The rest of that statement matters as much as the first half. The same guidance adds that MSPB "may, at its option, accept later appeals filed within 30 days of the employee becoming aware of the change." The normal federal MSPB appeal window runs from the Reduction In Force effective date, and the date the employee became aware of the change matters only for later appeals that MSPB may accept at its option. MSPB is a federal board, so this window may not apply to your employer. The habit still carries over: record when and how each employee was told about a change, so the timeline is clear if anyone disputes it.

The same OPM guidance covers retention preference, a federal rule that applies to eligible employees in layoffs. It says that where an agency finds an eligible employee "was not provided retention preference consistent with P.L. 105-85," OPM "recommends that the agency take appropriate corrective action." The guidance applies this to Reduction In Force separations or downgrading effective on or after November 18, 1997.

For a staffing team, the lesson is that a change touching an eligible person's layoff or downgrade is not a routine task. Involve HR or counsel early, document each decision, and be ready to correct an error quickly if one comes to light. Corrective action is the outcome the guidance names, so build a path to it into the process rather than planning for it after a complaint.

How should you deliver a change notice?

Deliver the notice in writing, state the change and its effective date plainly, and keep a record of when it was sent and to whom.

Writing is the common thread across the rules in this post. A notice you cannot prove you sent is weak support for either. Use a format you can store and retrieve, such as a letter or email saved in the personnel file.

A useful notice is short and specific. It should say what is changing, what is staying the same, the effective date, and where the employee can ask questions. If a rule gives the employee a window to appeal, say so in the notice rather than leaving the person to find it. Use plain words, and avoid vague phrases such as "soon" or "in due course." These are drafting habits, and your reviewer may add requirements that fit your situation.

Do not rely on a conversation alone. A call can explain the change well, but it leaves no record of the date.

How do you build a planning timeline for changes?

Start from the effective date, count back through each notice period that applies, and mark the latest day a notice can be sent.

Then work through these steps:

  1. Confirm the rule and its scope, including every leave type or term the change touches.
  2. Draft the notice and route it for review.
  3. Send the notice in writing and record the date and method.
  4. Confirm the effective date and check that the change takes effect as written.

If the latest sending day has already passed, the effective date moves later. It does not move earlier, and a notice dated after the fact is not a fix for a missed deadline.

A small team can run this with one shared tracker and a standing checklist. The two notice periods in this post come from two official sources, and they may not match your change. Read the full page for each rule you rely on, and involve employment counsel when a change touches pay, leave, or an accepted offer.

Related guides: 3 benefit facts for offers under equal pay and the ACA · Election-day time off: 4 state rules for offers · Leave and family data in 3 states' employee files.

Sources