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

# Build your first project planning

> Select the important activities and milestones, clarify their dates, and build a readable project overview in the OPUS web Table and Gantt views.

To build a useful OPUS planning, start with the important periods and events that someone overseeing the project needs to understand. Enter those items, check their dates, and read the result as a whole.

## Prepare the information

An existing schedule, a project discussion, or a file listing proposed items can be your starting point. Select the important information before entering it into OPUS.

For each proposed item, establish:

* A name that identifies its scope.
* Whether it is an activity or a milestone.
* A starting and delivery date for an activity, or one date for a milestone.
* An optional group.
* A predecessor, if a dependency is meaningful.
* Whether the dates are agreed, estimated, or still uncertain.

Clarify ambiguous instructions such as “next month,” “after approval,” or “windows.” They do not specify a complete dated item. Ask for the year, the intended activity or event, and the dates or assumptions needed to place it.

These are preparation questions, not additional required fields in OPUS. See [Best practices](https://docs.opus-world.com/planning-best-practices.md#prepare-information-from-an-existing-schedule-or-file).

## Open Planning

Open the project's **Planning** page and select **Table**.

If there are no items yet, you can start with **Add your first activity** or **New activity**. A blank planning is not a ready-made project schedule; its meaningful information still needs to be supplied.

## Create groups when they help

1. Select **Create a group**.
2. Enter a meaningful group name.
3. Submit the group.

Start with a few understandable categories. Groups are optional; a small planning can remain ungrouped.

## Create an activity

1. In the intended group, select **New activity**.
2. Edit **Activity Name** to describe the period of work.
3. Set **Starting Date** and **Delivery Date**.
4. Review the resulting dates before creating the next item.

A new activity starts with today's date and a delivery date 30 calendar days later. Replace these defaults with the project's intended dates. They are not an estimate of the work.

Choosing a starting date after the existing delivery date also proposes a new delivery date. Review both dates; the proposed end is a convenience, not a project estimate.

## Create a milestone

1. In the intended group, select **New milestone**.
2. Give it a name describing the event.
3. Set **Delivery Date** to the event's date.

A new milestone initially uses today's date. Its separate starting-date cell is not editable.

## Connect dependent items

In an item's **Dependency** field, choose the item it depends on. For example, on **Install external windows**, select **Windows delivered**.

Set the dependency on the successor. Adding the link does not adjust its dates automatically.

Use only meaningful dependencies. You can leave the field empty.

## Review the Gantt

Select **Gantt** and check the whole schedule:

* Do the important activities cover the intended project periods?
* Are major milestones visible at the correct dates?
* Are overlaps intentional?
* Are dependency directions correct?
* Have any creation defaults been left in place?
* Can someone unfamiliar with the detailed operational schedule understand the overview?

Use the time scale and display controls to make the timeline easier to read. Changing the view does not change the schedule.

## Example: a selected window package overview

The following dates are illustrative, not a template or a recommendation for construction durations.

| Group | Kind | Name | Start | End or event date | Predecessor |
| :- | :- | :- | :- | :- | :- |
| Design | Activity | Finalize external window design | 2 Nov 2026 | 13 Nov 2026 | None |
| Design | Milestone | Window design approved | Not applicable | 16 Nov 2026 | Finalize external window design |
| Procurement | Activity | Manufacture external windows | 17 Nov 2026 | 18 Dec 2026 | Window design approved |
| Procurement | Milestone | Windows delivered | Not applicable | 21 Dec 2026 | Manufacture external windows |
| Construction | Activity | Install external windows | 4 Jan 2027 | 15 Jan 2027 | Windows delivered |

This overview communicates the important sequence. It does not reproduce every manufacturing task, delivery movement, or installation operation.

## Keep it reliable

When information changes, revise the existing item's dates and explain the reason where the change form offers **Description**. After an item's end has passed, confirm completion if it is finished or correct the dates if the schedule no longer reflects reality.

Continue with [Manage your planning](https://docs.opus-world.com/manage-planning.md), [Date history](https://docs.opus-world.com/planning-date-history.md), and [Best practices](https://docs.opus-world.com/planning-best-practices.md).


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