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

# Planning definitions

> Learn what activities, milestones, groups, dates, dependencies, calendar status, and completion mean when reading or maintaining your OPUS planning.

OPUS Planning represents a project through selected activities and milestones. These definitions explain what each element means and how to interpret the schedule without confusing planned timing with actual work performed.

## Planning

A planning is the project's organized schedule of important activities and milestones. The Table and Gantt views display the same information.

A planning is intended to support project oversight. Its level of detail should make the project's important periods and events easy to understand.

## Item

An item is an individual entry in the schedule. There are two user-facing kinds: an **activity**, representing a period, and a **milestone**, representing an event on a single date.

Items can belong to a group or remain ungrouped.

## Activity item

An activity item is a named, individually identifiable period of work in the project's schedule, with a planned start and end. Its dates can be revised, and completion can be confirmed after its scheduled end has passed.

Choose an activity whose timing is meaningful at project level, such as **Develop the detailed design** or **Install external windows**.

| Property | Meaning |
| :- | :- |
| Identity | The same item remains identifiable when you rename, move, or reschedule it. Its name is a label, not a unique identifier. |
| Name | A clear description of the work represented by the item. |
| Group | The optional group containing the item. An item belongs to at most one group. |
| Order | Its position in the displayed sequence. Changing order does not change dates or dependencies. |
| Starting date | The day on which the activity is currently scheduled to start. |
| Delivery date | The day on which the activity is currently scheduled to end. It does not necessarily mean a physical delivery. |
| Baseline dates | Reference start and end dates used to compare the initial and current plans. |
| Dependency | An optional link to one predecessor item. |
| Completion confirmation | Acknowledgement that the item is finished, associated with its current scheduled end date. |
| Date history | Recorded changes to the item's scheduled dates. |

An activity can last a single day. Equal start and end dates alone do not make it a milestone.

## Milestone item

A milestone is a named event represented by one date. Use it for an important decision, delivery, or other event where the date matters more than a period of work.

For example, **Design approved** is a milestone; **Develop the design** is an activity.

In the table, edit a milestone through **Delivery Date**; it has no separate editable starting date. On the Gantt, a milestone is represented by a diamond. Moving its date keeps its start and end aligned.

Milestones can be grouped and connected through dependencies. They also require completion confirmation once their date has passed.

## Group

A group is a named collection of items that makes the overview easier to read. For example, groups might represent **Design**, **Procurement**, and **Construction**, or distinct areas of the project.

A group is an organizational container. It does not have an independently entered activity period or a completion confirmation of its own. The group structure is flat; groups do not contain other groups.

Items without a group can appear under **Others**. Removing a group preserves its items and makes them ungrouped.

## Current dates and baseline dates

**Current dates** describe the schedule as it stands now. These dates determine where an item appears on the timeline and its calendar position.

**Baseline dates** provide the reference shown as the initial plan in date history. They are initially set when the item is created. Ordinary date edits update current dates rather than replacing the baseline.

A baseline date is not proof of an approved contractual commitment. In particular, creation defaults should not be mistaken for an agreed initial schedule.

Neither baseline nor current dates are actual start or actual finish records.

## Calendar days and duration

Planning dates are calendar days, not appointments with a time of day.

The end date is inclusive: an activity ending on 12 November remains scheduled on 12 November. It becomes past its end on 13 November.

The period includes weekends and holidays. Planning does not provide a working-day or resource calendar for calculating the item.

Duration describes the interval between the scheduled dates. It does not measure hours worked, effort, or percentage complete.

## Dependency, predecessor, and successor

A **dependency** is a directional link expressing that one item depends on another.

If **Install external windows** depends on **Windows delivered**:

* **Windows delivered** is the predecessor.
* **Install external windows** is the successor.
* The successor's **Dependency** field identifies the predecessor.

An item can have one predecessor. A predecessor can have several successors, and a chain can contain indirect successors.

Grouping two items, placing them next to each other, or scheduling them consecutively does not create a dependency.

The link does not store a dependency type or a required waiting period. Adding it does not automatically recalculate dates. Dates must still represent the intended sequence.

## Cascading a date change

A cascade moves dependent items along with the item being moved. In the supported whole-period move, successors' start and end dates shift by the same number of calendar days, including indirect successors.

For example, moving an activity three days later and applying the cascade moves its dated successors three days later as well. Their durations stay the same.

A cascade is not a general scheduling calculation. Do not assume that every date edit, resize, or new dependency automatically reschedules the chain. See [Move an activity and its dependents](https://docs.opus-world.com/manage-planning.md#move-an-activity-and-its-dependents).

## Calendar position and completion

Calendar position is derived from dates. Completion confirmation is a separate acknowledgement.

| Situation | Meaning |
| :- | :- |
| Start is after today | The item is upcoming in the schedule. |
| Today falls between start and end, inclusive | The item is in progress according to the calendar. This does not verify that work has started. |
| End is before today, without confirmation for that end date | The item has passed its scheduled end and needs confirmation or a date correction. |
| End is before today, with confirmation for that end date | Completion has been confirmed against the current scheduled end. |
| A usable start or end date is missing | The item cannot be reliably placed on the timeline. |

The web interface can label calendar-past items or groups **Completed** based on dates. Check the separate completion prompt before treating an item's completion as confirmed.

A group's calendar label summarizes its items' dates. It does not confirm that every item is finished. Mixed past and future items can produce an **In progress** group label even if none is individually active today.

### Completion confirmation

Confirming completion means acknowledging that the item is finished. The acknowledgement is tied to its scheduled end date, not to a separately entered actual finish date.

Changing that scheduled end clears the acknowledgement. A fresh confirmation will be needed once the new end is past. Confirmation is unavailable while the scheduled end is today or in the future.

A pending confirmation does not establish that an item is delayed. The work might be finished but unconfirmed, or the dates might need updating.

### Progress

Elapsed time, calendar status, and confirmed completion are different facts.

The Planning table and Gantt do not measure physical progress as a percentage of work performed. Do not interpret a period that is halfway through its dates as 50% complete.

## Date change and date history

A date change revises an item's scheduled start, end, or both. Its history can explain the previous dates, new dates, and whether the change came directly from an edit or from a dependency cascade.

The **effective date** of a recorded change is when it takes effect in the schedule's history. The **recording date** is when the change was entered. Neither is an actual completion date.

The history is subject to the web's initial editing grace period and to restoration rules. See [Date history](https://docs.opus-world.com/planning-date-history.md).

## Information an item does not establish

An item's name and dates do not, by themselves, assign a person or company, define a budget or quantity, record actual work performed, or approve a deliverable. Those facts require their own evidence in the project.


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