> ## Documentation Index
> Fetch the complete documentation index at: https://docs.opus-world.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand and restore planning date history

> Read recorded changes to planning dates, understand the initial editing period, and learn exactly what restoring an earlier activity version changes.

OPUS Planning date history helps you understand how an item's schedule changed. It compares its reference dates with its current dates and shows the recorded revisions available for that item.

Date history concerns scheduled dates. It is not a complete record of every edit, and it does not establish when work actually started or finished.

## Open an item's history

In **Table** view, select **View activity change history** beside the item's name. This button appears when recorded changes exist.

At the top, compare **Initial plan** and **Current plan**. Below, read **Detailed history**, where the recorded versions show date changes and explanations.

The initial plan uses the baseline reference. At creation, that reference is initialized with the item's default dates. If those defaults were not an agreed plan, do not describe the comparison as contractual delay.

## Understand an entry

A date-change record identifies the affected item and keeps the previous and new dates. Depending on the entry, it also records an explanation, the author, when it was entered, and whether it resulted from a direct edit or a cascade.

| Term | Meaning |
| :- | :- |
| Previous dates | The item's schedule immediately before that recorded change. |
| New dates | The resulting schedule for that version. |
| Effective date | When the change takes effect in the schedule history. |
| Recording date | When the change was entered. |
| Direct | A change entered directly for the item. |
| Dependency | A change propagated from another item. |
| Source activity | The item whose move caused a dependency change. |
| Current version | The latest version in the recorded history. |

The date difference shown for an entry describes the scheduled delivery-date movement. A later date is a schedule shift; it does not, by itself, establish fault or responsibility.

A source-activity link can help you trace a cascade to the change that triggered it. The source describes the scheduling relationship, not a contractual attribution.

## Initial editing period

For the first **24 hours after an item's creation**, the web Planning flow lets you adjust dates without creating date-change history entries. Those edits change the current dates, while the baseline remains the creation reference.

After that period, actual date changes create history records. Saving identical dates does not create a new change.

This explains why an item can have different initial and current dates without a history entry for every adjustment.

The 24-hour exception described here is specific to the web editing flow. Do not assume every OPUS interface or integration applies the same history policy.

## Write useful explanations

Where the date-change form offers **Description**, give enough context for someone to understand the change later.

For example:

> Delivery moved from 21 to 23 December following the supplier's revised delivery notice. Installation dates remain unchanged.

This is more useful than “updated dates.” Identify the known reason and affected scope without asserting facts that have not been confirmed.

The description is optional in the web form, but useful explanations improve the value of the history.

## Restore a recorded version

Restoration returns one existing item to the dates stored in a selected history version.

1. Open the item's date history.
2. Find the version whose resulting dates you want.
3. Select **Restore** where offered.
4. Read and accept the restoration warning only if you intend to remove later versions.

> [!WARNING]
>
> Restoring a version permanently deletes later date-history entries for that item and aligns its current dates with the selected version. It does not add a new reversal entry. The web warning states that this cannot be undone.

Restoration also clears the item's completion confirmation. If the restored end is already past, completion will need confirming again.

It does not restore a deleted item, rename the item, change its group, replace its dependency, or rewind the whole project planning. Restoring one item does not automatically restore its successors. Check their dates separately.

## Choose between a new change and restoration

Use a **new date change** when the project has evolved and you want to preserve the sequence of earlier decisions.

Use **Restore** only when you intentionally want the selected version's dates and accept deleting later history for that item.

If dates return to a previous value because of a new project decision, enter those dates as a new change and explain the decision. This preserves the intervening history.

For the rest of the available actions, see [Manage your planning](https://docs.opus-world.com/manage-planning.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.