> ## Documentation Index
> Fetch the complete documentation index at: https://collabase.ch/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> Collabase documentation. Interface labels are quoted in English, as they appear in the product.
> Features marked Enterprise need the Collabase Enterprise Edition licence.

# Planning across projects

> Which Collabase tool answers which planning question: portfolios for the big picture, the Planner for capacity, timelines and phases for dates.

Planning in Collabase works on the real projects and work items, not on a separate plan. Portfolios group projects, the Planner sets people's time against their work, and each project carries its own timeline, phases and status reports. A change you make in one place is visible in all others at once.

<h2 id="building-blocks">
  The building blocks
</h2>

```mermaid theme={"dark"}
flowchart TD
  PF["Portfolio and programmes"] --> PR["Project"]
  PR --> PH["Phases and gates"]
  PR --> CY["Cycles"]
  PR --> WI["Work items with dates and estimates"]
  WI --> DEP["Dependencies"]
  WI --> PL["Planner: load per person and team"]
  PR --> SR["Monthly status report"]
  SR --> PF
```

<h2 id="which-tool">
  Which tool for which question
</h2>

| Question | Tool |
| - | - |
| Which projects need management attention? | [Portfolios](/docs/planning/portfolios), **Overview** tab |
| How do all projects of a programme lie in time? | [Portfolios](/docs/planning/portfolios#gantt), **Gantt** tab |
| Who is overloaded in the next four weeks? | [Planner](/docs/planning/planner-capacity) |
| What blocks what? | [Dependencies](/docs/planning/dependencies) |
| When is each work item of one project scheduled? | Project [Timeline](/docs/projects/roadmap) |
| Where is the project in its lifecycle? | [Phases and gates](/docs/projects/approvals) |
| What does the project manager report this month? | [Status reports](/docs/projects/reports#status-reports) |
| What could go wrong? | [Risk register](/docs/projects/risks) |

<h2 id="get-started">
  Get started
</h2>

<Steps>
  <Step title="Give work items dates and estimates">
    The Planner and the timelines only place work that has a start date, a due date and, for the Planner, an estimate.
  </Step>

  <Step title="Set up workload plans">
    An administrator gives each person or team a workload plan, so capacity is right. See [Holiday and workload schemes](/docs/time-tracking/holiday-workload-schemes).
  </Step>

  <Step title="Build the portfolio tree">
    Create portfolios and assign projects to them under **Settings → Portfolio and budget**.
  </Step>

  <Step title="Switch on what the projects need">
    Under **Settings → Project features**, switch on **Phases and gates**, **Risks** or **Costs** per project.
  </Step>
</Steps>

<h2 id="not-available">
  What Collabase does not offer
</h2>

| Need | Situation in Collabase |
| - | - |
| Scenarios or a sandbox plan | Not available. Every change applies to the real work items |
| Automatic scheduling from dependencies | Not available |
| A program board | Not available. A programme is a portfolio with a parent |
| Releases or fix versions on work items | Not available. Versions exist in Test Management only |
| Exporting a plan | Not available |

## Next steps

<CardGroup cols={2}>
  <Card title="Portfolios" icon="folder-tree" href="/docs/planning/portfolios">
    Group projects and compare them.
  </Card>

  <Card title="Planner and capacity" icon="users" href="/docs/planning/planner-capacity">
    Plan people against their time.
  </Card>

  <Card title="Dependencies" icon="git-branch" href="/docs/planning/dependencies">
    Record what blocks what.
  </Card>

  <Card title="Phases and gates" icon="milestone" href="/docs/projects/approvals">
    Run a project through a lifecycle.
  </Card>
</CardGroup>


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