Scheduled and retroactive changes

Scheduled and retroactive changes

Plan future changes to your organization structure and policies, and apply changes retroactively when needed.

Overview

mTime lets you schedule changes to take effect on a specific future date, or apply changes retroactively to a past date. This is useful when:

  • Upcoming reorganizations — Schedule org unit changes to go live at a future date
  • Policy updates — Set new time-off or allowance policies to activate at the start of a period
  • Employment changes — Update employment terms with a future effective date
  • Corrections — Apply retroactive changes to fix historical data

Scheduled changes work with:

  • Organization units
  • Employees
  • Employment terms
  • Time-off policies
  • Allowance policies

Scheduling a change

To schedule a change for a future date:

  1. Open the entity you want to change (organization unit, employee, policy, etc.)
  2. Make your changes in the form
  3. Click the dropdown arrow next to Save
  4. Select Schedule for later
Save button with scheduling options
Save button with scheduling options
  1. Pick the effective date from the calendar
  2. Click Schedule change
Schedule dialog for selecting an effective date
Schedule dialog for selecting an effective date

The change is saved but won’t take effect until the scheduled date.

Viewing scheduled changes

When an entity has pending scheduled changes, a calendar icon appears in the header.

Calendar icon showing pending scheduled changes
Calendar icon showing pending scheduled changes

Click this icon to open the version history drawer, which shows:

  • Scheduled changes — Future changes waiting to be applied
  • History — Past changes that have already been applied
Version history drawer showing scheduled and applied changes
Version history drawer showing scheduled and applied changes

Each entry shows:

DetailDescription
StatusScheduled (future) or Updated/Created (applied)
Effective dateWhen the change takes effect
Changed byWho made the change
Created atWhen the change was created

Reviewing changes

Click View JSON on any entry to see the exact changes that will be (or were) applied.

Change details showing the fields that will change
Change details showing the fields that will change

Cancelling a scheduled change

To cancel a scheduled change before it takes effect:

  1. Open the version history drawer
  2. Find the scheduled change you want to cancel
  3. Click Cancel

The scheduled change will be removed without affecting the current state of the entity.

How scheduled changes are applied

Scheduled changes are applied automatically by a daily batch job. When the effective date arrives:

  1. The Apply scheduled changes job runs (typically daily at midnight)
  2. All changes scheduled for that date (or earlier) are applied
  3. The entity is updated to reflect the new values
  4. The change moves from “scheduled” to “applied” in the version history

For more details, see Apply scheduled changes.

Retroactive changes

Retroactive changes let you apply updates with a past effective date. This is useful for:

  • Correcting historical data
  • Applying changes that should have been made earlier

Making a retroactive change

  1. Open the entity you want to change
  2. Make your changes in the form
  3. Click the dropdown arrow next to Save
  4. Select Apply retroactively
  5. Pick the effective date from the calendar (up to 90 days in the past)
  6. Click Apply retroactive change
Retroactive dialog for selecting a past effective date
Retroactive dialog for selecting a past effective date

Current limitations

Retroactive changes are recorded in the version history but currently have limited effect on calculations. Future versions will use retroactive data for:

  • Historical reporting
  • Recalculating time-off accruals
  • Adjusting past period calculations

For now, retroactive changes primarily serve as an audit trail and preparation for reporting features.

Identifying retroactive changes

In the version history, retroactive changes are marked with a purple “Retroactive” badge to distinguish them from regular updates.

Timeline example

Here’s how changes appear in the version history for an organization unit:

Timeline showing past, present, and future changes
Timeline showing past, present, and future changes

This example shows:

  1. A future scheduled change — Will be applied when the date arrives
  2. Today’s applied change — Currently in effect
  3. A past retroactive change — Applied with a historical effective date

Changes are displayed in chronological order by effective date, making it easy to understand how an entity evolved over time.

Permissions

ActionRequired permission
Schedule future changesEdit permission for the entity
Apply retroactive changesEdit permission + “retroactive” permission
View version historyView permission for the entity
Cancel scheduled changesEdit permission for the entity

Administrators can enable retroactive permissions through role configuration.