Setting up a project
What this page is — The guided set-up: six questions that turn a bare project into one that is ready to plan — how the work is measured, whether it carries a value, who is on it, what its task types and categories are, and what its phases look like.
Planning workspace
What this page is — A sandbox for a project's sprints and phases. You plan placements, assignees, estimates, capacity and goals inside a named scenario; nothing reaches the live tasks until you press Commit.
Define — sizes, skills, people and hires
What this page is — The Define tab, the first tab of Planning. It holds what a plan is made of before anything is assigned: the size scale, the skills the project plans with and who has them, each person's hours per week, and the planned hires.
Phases, sprints and milestones
What this page is — The rules that relate the three kinds of Roadmap entry — a phase contains sprints and milestones; a task sits in one time box and may contribute to one milestone.
Capacity and planned hires
What this page is — A grid of net plannable hours — one row per person or planned hire, one column per time box of the scenario — computed from the organisation's working calendar, holidays, approved leave, each person's allocation and the project's focus factor.
Dependencies
What this page is — The two steps of Plan by → Dependencies: mapping what waits for what, then fitting the sprints around it.
Scenarios and commit
What this page is — The life of a scenario: seed it from the live tasks, shape it on a drag-and-drop board (by hand or with an AI suggestion), keep it in step with reality through drift and rebase, compare it with others, and commit it in one transaction.
Invoicing a time box
What this page is — How a finished (or running) stage becomes an invoice in Orbit Books, and the bills that go to the contractors who did the work.
Goals, burndown and insights
What this page is — What a time box is for — its goal and success criteria — and the ways the committed plan is watched afterwards: an AI goal check, a daily burndown, five Risk radar signals, a delivery forecast that follows the plan's links, and new report fields.
Planning settings
What this page is — The per-project rules Planning works by: how tasks are estimated (hours, points or days), how a size becomes hours, how much of a day is plannable, what the team calls a sprint or a phase, what happens when dates fall outside their phase, and whether a commit tolerates drift.
Planning for integrators and assistants
What this page is — Every way software, rather than a person at the Planning screen, reaches the plan: the Orbit Public API, the planning.committed webhook, the MCP tools an AI agent uses, the client SDKs, and the questions the Orbit Assistant can answer about plans, capacity and hires.