Planner

The planner is a Gantt view for operational timelines.

For project-linked work, it shows this hierarchy:

1. Project
2. Work order
3. Phase or milestone

Projectless work orders can also appear directly with their phases and milestones. Projects and work orders show computed date ranges. Phases are editable date ranges; milestones are editable point-in-time markers.

Related docs: Projects, Work Orders, Phases, Workspace Settings, Organizations

Where you use it

• Open the global planner in Planner. This shows all non-archived projects, non-archived work orders, and all non-cancelled phases and milestones. Work orders without a project appear as top-level work-order rows.
• Open a project planner from Projects or a project detail page. This scopes the chart to one project and its work orders.
• Open a work-order planner from Work Orders or a work-order detail page. This scopes the chart to one work order and its phases.

Data model

Projects

• Project rows are summary rows.
• Their start and end are computed from all visible descendant phases and milestones.
• Projects can exist without planner data, but they only get a timeline once work orders and planner items exist.

Work orders

• A work order can belong to a project, but the project link is optional.
• Work-order rows are summary rows.
• Their start and end are computed from child phases and milestones.
• New work orders created in the planner inherit the selected project.

Phases

• A phase belongs to exactly one work order.
• Phase rows carry the real schedule.
• Fields used by the planner: title, description, work order, start date, end date, status, sort, and optional color.

Milestones

• A milestone belongs exactly to one work order.
• Milestone rows mark one scheduled datetime.
• Fields used by the planner: title, description, work order, scheduled at, occurred at, completed at, status, and sort.

Planner statuses

• planned: scheduled but not started
• in_progress: active work
• completed: finished work
• on_hold: paused work
• cancelled: hidden from the planner

Create flow

1. Create a project when the schedule belongs to a larger delivery container.
2. Create a work order for that project, or create a standalone work order if no project is needed yet.
3. Add one or more phases or milestones to the work order.

The global planner supports this directly:

• Hover a project row to add a work order.
• Hover a work-order row to add a phase or milestone.
• Use the planner header action to add a project.

The scoped planners are narrower:

• Project planner: add phases and milestones to existing work orders in that project.
• Work-order planner: add phases and milestones to that work order only.

Editing behavior

• Click a phase row or phase bar to edit it.
• Click a milestone row or marker to edit it.
• Right-click a row in the left hierarchy panel to open the same item actions for projects, work orders, phases, and milestones.
• Drag a phase bar to move the whole phase.
• Drag a milestone marker to move its scheduled date; the time is preserved.
• Drag a phase edge to change its duration.
• Drag a project or work-order summary bar to shift all descendant phases and milestones by the same number of days.
• Summary rows cannot be resized.

The planner works with day-level positioning. A phase must end after it starts; a milestone keeps its scheduled time when moved.

What the chart shows

• Projects and work orders are expanded by default.
• The left panel is the hierarchy tree.
• The right panel is the timeline grid.
• Weekends are shaded.
• Today is marked with a vertical line.
• Tooltips show the rendered date range, total duration, or milestone datetime.

Setup dependencies

Work-order numbering

New work orders need an issuer organization and a numbering setup.

• Workspace-wide defaults are configured in Workspace Settings.
• Issuer organizations can override work-order naming and reset rules in Organizations.

In the UI this is managed in Workspace Settings and Organizations.

Downstream work

The planner only covers timeline structure. Execution and reporting happen elsewhere:

• Track labor in Work Times and Work Times.
• Collect field output in Reports and Reports.
• Manage the parent records in Projects and Work Orders.

Constraints and filters

• Archived projects are not shown by default.
• Archived work orders are not shown by default.
• Cancelled phases and milestones are filtered out of the planner.
• Planner items cannot be attached directly to a project; they must belong to a work order.
• Work orders without a project are still valid planner parents for phases and milestones.

Recommended structure

• Use projects for the customer or delivery container.
• Use work orders as execution packages. Link them to a project when they belong to a larger delivery container.
• Use phases for the actual schedule blocks that need to move on the timeline.
• Use milestones for decisions, deadlines, handovers, and other single-point schedule markers.
• Keep phases short and specific so shifts stay predictable.