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.
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.
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.Calendar position and completion
Calendar position is derived from dates. Completion confirmation is a separate acknowledgement.
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.
