The scheduling UI is an interactive Gantt chart embedded on the project record. It supports task creation, dependencies, baselines, critical-path highlighting, and both single- and multi-project views. For setup and how scheduling ties into resources and labor cost, see Scheduling and Resources.
?multi=true in the URL) — all projects as top-level rows with their schedules beneath, filtered by your subsidiary access. To protect data across projects, multi-project view does not allow editing top-level project rows, creating dependencies between different projects, moving tasks across projects, reordering project rows, or MSP import.| Column | Shows |
|---|---|
| WBS | Auto-generated Work Breakdown Structure numbering |
| Name | Task name |
| Start / End Date / Duration | The schedule (grouped, collapsed by default; uses your date-format preference) |
| Cost Code | Per-project dropdown of cost codes |
| Resource Assignment | Assigned resources as avatar badges; supports drag-and-drop |
| % Done | Circular progress indicator |
| Predecessors / Successors | Dependency links |
Right-click a task to Add (Task Above, Task Below, Subtask, Successor, Predecessor), Indent / Outdent to change hierarchy, or Delete Task (with confirmation — deletes clean up dependencies, assignments, and baselines). The task editor includes a Cost Code field on the General tab, populated per project.
Assigned resources appear as avatar badges in the Resource Assignment column. From the Gantt you can manage those assignments directly:
For allocating resources to the project, the Resource Utilization panel, and cascade-to-subtask behavior, see Resource Allocation.
You can capture up to 3 baselines per project. Baseline creation runs in the background, and baselines surface delayed-start and overrun indicators in task tooltips. Save any pending changes before setting a baseline — the UI enforces this.
The Gantt resolves conflicts automatically so you're not interrupted by pop-ups: invalid dependencies are removed, and dependency cycles are broken by dropping the last dependency in the cycle.
Import reads both Microsoft Project and Primavera P6 XML (it auto-detects which), bringing in tasks, calendars, resources, assignments, and dependencies. Import is only offered when the project has zero existing tasks, so you start a project from an existing plan rather than overwriting work in progress. Export to MSP preserves resource categories and codes for round-trip fidelity.