> ## 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.

# Manage your project planning

> Create, organize, reschedule, and connect OPUS planning items, confirm completion, and understand the consequences of each action in the web interface.

Use the OPUS web Planning page to keep the project's important activities and milestones aligned with current information. This guide describes the available actions and what they change.

You need access to the project and its Planning page. Follow the controls available to your account; documentation does not grant editing access. If an action is unavailable or a save is refused, check your project access before trying again.

## Read the schedule

Select **Table** to read and edit names, dates, and dependencies. Select **Gantt** to read items against a common timeline.

In Gantt view, use:

* **Day**, **Week**, or **Month** to change the time scale.
* **Display as lines** or **Display as bubble** to change the presentation.
* Scrolling and the chart's zoom controls to inspect a period.

The Gantt initially fits the activities to the available width in Lines mode. Display changes affect presentation, not item dates or relationships. Items without usable dates cannot appear as dated bars.

## Create an item or group

| Action | Where | Result |
| :- | :- | :- |
| Create a group | **Create a group** in Table view | Adds a named container for items. |
| Create an activity | **New activity** in the intended group | Adds a period with editable name and dates. Initially starts today and ends 30 calendar days later. |
| Create a milestone | **New milestone** in the intended group | Adds an event with one date, initially today. |

An item can remain ungrouped. Replace default names and dates before treating a new item as project information.

See [Getting started](https://docs.opus-world.com/getting-started.md) for a complete example.

## Rename an item or group

Edit **Activity Name** in the table to rename an activity or milestone. Use the group's rename control to change a group name.

Renaming preserves identity, dates, and dependencies. Choose names that distinguish items with similar scope, for example **Install windows, east wing** and **Install windows, west wing**.

## Reorganize items

Use **Reorganize** to arrange groups and items, then save your changes. You can also drag rows in the table to reorder them or move them between groups.

Reorganizing changes placement and, when applicable, group membership. It does not reschedule the work or create dependencies.

An item belongs to one group at a time. Moving it to **Others** leaves it ungrouped.

## Change dates

### From the table

1. Find the item.
2. Change **Starting Date** or **Delivery Date**. For a milestone, use **Delivery Date**.
3. Review the previous and proposed dates when the change form opens.
4. Add an optional **Description** explaining the change.
5. Select **Save**.

If you choose a starting date after the existing delivery date, the table proposes a new delivery date one month after the new start. Review both dates rather than accepting that proposed duration as a project estimate. Keep the starting date on or before the delivery date.

### From the Gantt

Move an activity horizontally to shift its period, or use its date handles to adjust the period. Review the proposed dates and save when prompted.

Moving a milestone changes its single date. It remains a single-date event.

### Consequences

An ordinary date edit changes the current schedule while preserving its baseline reference. The item's calendar position is recalculated from the resulting dates.

If its delivery date changes, any completion confirmation for the previous end is cleared.

During the first 24 hours after an item's creation, web date changes are saved without the usual date-history record. Changes can therefore save directly without opening the normal explanation form. See [Date history](https://docs.opus-world.com/planning-date-history.md#initial-editing-period).

## Move an activity and its dependents

A whole-period move can affect items connected to it through dependencies.

For an established activity with dated successors, the web flow offers:

* **Move dependent tasks too**: shift direct and indirect successors by the same number of calendar days.
* **Move only this task**: apply the move to the selected item alone.

For example, if an activity moves three days later and you choose to move its dependents, each dated successor's start and end move three days later. Existing durations are preserved.

During the moved item's first 24 hours, the web whole-period move flow applies the dependent moves directly, without the usual cascade-choice dialog. Review the complete chain after moving a newly created activity.

This behavior applies to supported whole-period moves. A single-date edit, a resized end, or a milestone date change must not be assumed to move every successor. Review the actual result.

## Add or replace a dependency

In the successor's **Dependency** field, select its predecessor. Alternatively, in the Gantt, drag the dependency connector from the predecessor to the successor.

Selecting a different predecessor replaces the existing link because each item has one predecessor.

Adding or replacing a dependency does not change dates. Check that the dates still describe a coherent sequence. Do not create circular chains in which an item depends on itself indirectly.

## Remove a dependency

In Gantt view, click the dependency arrow to remove the link.

Removing the link leaves the items and their current dates in place. Future moves through that link will no longer affect the former successor.

## Confirm completion

When an item's delivery date is before today and its completion is unconfirmed, the table and Gantt provide a completion action.

1. Check that the item is actually finished.
2. Select the action labelled **Confirm or adjust end date**.
3. In the dialog, select **Confirm completion**.

If the item is not finished, close the dialog and correct its dates instead.

For an item created within the last 24 hours, selecting the completion action can save the acknowledgement directly without the confirmation dialog. Check the item before selecting the action.

Completion confirmation is associated with the current scheduled end. It does not enter a separate actual completion date or change the scheduled dates. The action is available only after the end day has passed, not on that day.

Changing the delivery date later clears the acknowledgement.

## Read or restore date history

Select **View activity change history** beside an item in the table. The history button appears when the item has recorded date changes.

The history includes an initial-versus-current comparison and recorded versions. Restoration can delete later history, so read [Date history](https://docs.opus-world.com/planning-date-history.md) before using **Restore**.

## Delete items

Select the activity or milestone rows in the table, then choose **Delete** and respond to the confirmation prompt.

Deleting an item removes it from the current schedule. Surviving successors are not deleted; their dependency on the removed item is cleared. Their dates remain in place.

Deletion is not a way to mark work complete. Keep meaningful finished items in the overview and confirm their completion instead.

There is no item-recovery procedure documented here. Date-history restoration is for a surviving item's dates, not for recreating a deleted item.

## Delete a group

Use the group's delete control and respond to the confirmation prompt.

The group is removed, but its items remain. They become ungrouped and can appear under **Others**. Their dates and dependencies are preserved.

## Common questions

### Why is there no completion action?

The end may be today or in the future, the item may already be confirmed for that end date, or usable dates may be missing. Check those conditions before interpreting the missing action.

### Why did completion need confirming again?

Changing the end date clears confirmation for the previous end. Restoring a recorded version also clears completion confirmation.

### Why is there no history button?

The button requires recorded date changes. An unchanged item has no date-change history, and web date edits during its first 24 hours do not create history records.

### Why did moving one item move other items?

They were successors in a dependency chain. The move either used **Move dependent tasks too** or occurred through the automatic cascade behavior during the initial editing period.

### Why did removing a group leave its items?

Groups organize items. Deleting a group ungroups its items; deleting selected item rows is a separate action.


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