Contract changes with a future effective date

A future-dated contract change is a written employment event whose effective date is after today: role, manager, compensation, or terms. You record it now so payroll, letters, and the directory apply it then — not when someone next remembers. This page owns effective-dating mechanics. Which event you are recording (raise versus promotion versus other) stays on raises and promotions as employment-record events. Product surface: Dayzen employee lifecycle, which includes future-dated contract change processing (verified) and raise/promotion proposals. Pay runs that must honour the effective date sit on Dayzen payroll. Today’s org chart should not pretend the future already happened.

Not legal advice. Changing terms may need a letter your counsel cares about. This page requires that the HRMS date and the letter date tell the same story.

Two dates that must not collapse

Decision or approval date is when someone with authority accepted the change. Effective date is when the employee record, pay calculation, and reporting line should look different. They are often days or a month apart. Collapsing them is the usual bug: HR types a promotion on the day of the email, payroll has already closed that month, and the directory shows a new manager while the old team still has the person on this week’s roster.

A third date sometimes appears: letter issue date. If you generate a letter on 20 June that says “effective 1 July,” the record’s effective date is 1 July. Do not set effective date to 20 June because that is when you clicked. Do not set it to 1 July in the letter and 20 June in the HRMS.

Dayzen lifecycle processes future-dated contract changes: you can hold the event before it applies. Use that. A spreadsheet titled “July changes” that nobody loads until August is not future-dating. It is late typing.

What you may future-date

Typical fields that should move on an effective date, not on approval day:

• Designation and department.
• Reporting manager and dotted lines you actually store.
• Work location or entity if the person moves on a named date.
• Pay structure, CTC, or named components payroll calculates.
• Employment classification when the stage change is dated (for example probation confirmation effective the first of next month) — the probation article owns the stage words; this page owns “not yet.”
• Hours or work pattern if you store them as contract facts that attendance or pay uses.

Do not future-date gossip. If the change is not approved, there is no event. A manager’s plan to “move them in Q3” is not a contract change until an approver and an effective date exist. Draft proposals are fine; treating drafts as today’s directory is not.

Event type labels — raise, promotion, renewal, and the rest — belong on the raise/promotion article. Here, every type still needs an effective date if the facts should apply later. A raise without a date is a chat. A promotion that applies immediately is a same-day effective date, which is allowed. Future-dated only means effective > today, not that same-day is forbidden.

What should stay true until the effective date

Until the effective date:

• Directory search and org chart show the current manager and title, unless you have a separate “pending” display you trained people to read. Default: current facts are current.
• Payroll cycles whose period ends before the effective date use the old structure. Dayzen payroll calculates from the structure in force for that period; it does not file or pay the bank. Do not hand-edit a component in the closed month to “get ready” if the event is next month — you will create a false history.
• Access that depends on role: decide whether privileged access follows the new role early, on the day, or after. That is an IT schedule, not an excuse to change the HRMS title early.
• Letters: you may issue early (“this will apply on…”). The letter must state the effective date. The record must match.

After the effective date, the opposite: title, manager, and pay should match the event without a second manual pass “when we remember.” If processing is future-dated, the system should apply. If something failed to apply, that is an incident, not a culture of cleanup Fridays.

Payroll and mid-period seams

If the effective date sits inside a pay period, you need a rule: split the month on that date, apply from the first of the next month only, or another issued method. This page does not invent a nationwide proration statute. Pointer: joiner/leaver proration is a related payroll topic; a mid-month raise is the same family of “which days use which structure.” Write the rule in payroll ops. Lifecycle’s job is to give payroll one effective date, not three versions in email.

LOP, attendance, and advances still attach to the person, not to the old title. Changing designation does not wipe unpaid days. Do not use a future-dated title change to hide a current attendance problem.

Back-dated changes (effective date before today) are a different operational risk: they rewrite history payroll may already have paid. If you must back-date, treat it as an adjustment path you already have, not as “future-dated but yesterday.” This article’s happy path is record now, apply later.

Org chart and the person who still has them this week

Managers approve leave and interview on the team they have now. If you move reporting on the HRMS three weeks early, the new manager gets a queue for someone they do not staff yet, and the old manager loses a queue they still run. Future-date the manager change. If you need the new manager in the loop early, give them a named coordination role outside the reporting field, or wait.

Transfers that include location, entity, or attendance policy need the same discipline. A future office move recorded as today’s location breaks geofence and holiday calendars for the remaining days.

Who may create the event, who may see it

HR operations typically records. A compensation approver or department head typically approves. The employee may see a pending letter or a self-service “upcoming change” if you offer that. They should not see a live title that is not live. Managers should see pending moves that affect roster once approved, so they can plan, without the public directory lying.

Dayzen employee lifecycle is where those proposals and future-dated processing live. Employee management is the directory that should display current truth. Do not maintain a third “secret org” spreadsheet as the real system. If the spreadsheet is ahead of the HRMS, you are not future-dating; you are shadow-dating.

If a pending change is withdrawn before the effective date, cancel or supersede the event in the same trail. Do not leave a future-dated promotion in processing and also tell the directory it was a joke. A replacement event with a new effective date should point at what it replaces so payroll does not apply both.

Failure modes

Symptom	Date bug	Fix
Payslip changed this month, letter said next month	Effective = click date	Set effective date; reverse in-period if your adjustment path allows
Org shows new manager, old manager still runs the week	Reporting applied early	Future-date manager; current queue stays
July increment typed in August	No event until after effective	Record when approved, effective 1 July (or issued date)
Two raises in chat, one in HRMS	Event type confusion plus missing date	One event, two dates; types on sibling article
Letter 1 July, HRMS 20 June	Issue date used as effective	Match letter and record
Back-pay surprise	Back-dated effective after payout	Do not treat as future-dated; use adjustment process

A recording sequence

1. Approved change with a written effective date (and event type on the raise/promotion page’s vocabulary).
2. Create the lifecycle event now, effective then. Dayzen’s future-dated processing is the container.
3. Generate letters from those two dates.
4. Leave directory and current pay structure alone until effective, except pending indicators you trained.
5. On effective date, title, manager, and structure match without re-keying from a spreadsheet.
6. Payroll period that includes the date follows your issued split/apply rule.

Approval is when you decided. Effective is when the world should change. Dayzen can process the contract change in between. Payroll follows the structure in force. The sibling article names raise versus promotion. This article refuses to move the org chart early to celebrate.

Keep employee lifecycle as the event and the future-dated processor. Keep payroll as calculation from the structure that is in force for the period. Keep raise and promotion as the event-type explainer. Stop here so you do not also write appraisal methodology or a second “what is a promotion” essay. The operating test: a change approved on the 12th, effective on the 1st of next month, is visible as pending to people who must plan, invisible as current title to the rest of the company, and boringly correct on the payslip that includes the 1st.