> For the complete documentation index, see [llms.txt](https://portavi.gitbook.io/portavi-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://portavi.gitbook.io/portavi-docs/organising-your-work/creating-a-programme.md).

# Creating a programme

A programme groups related projects delivered towards a shared outcome. Create one from the Overview dashboard: **+ New → Programme**.

<figure><picture><source srcset="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-3937889f85682a33b36ded6275fe48b05c7db896%2Fprogramme-new-dark.png?alt=media" media="(prefers-color-scheme: dark)"><img src="https://4189291014-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fx6fERvLd0cQQBYlynE5O%2Fuploads%2Fgit-blob-a649ab8e8553e2a3be836f32530fff66dc407659%2Fprogramme-new.png?alt=media" alt=""></picture><figcaption></figcaption></figure>

## The steps

### Step 1: Identity

Name, description, and an emoji and colour, as for a project. The description supports rich text and [AI rewriting](/portavi-docs/ai/ai-in-portavi.md), as a project's does.

### Step 2: Components

Choose which existing projects belong to this programme. A project can belong to only one programme at a time; projects already in another programme are not offered.

You can leave this empty and attach projects later, either from here or from each project's own edit modal.

### Step 3: Benefits

The outcomes this programme exists to deliver. Each benefit has a title, an optional description and target date, and the projects contributing to it. You can add these later from the programme's Overview tab, where each benefit's unit, baseline and target are also set. See [Benefits](/portavi-docs/governance/benefits.md).

Below the benefits, **Benefit review cycle (months)** sets how often the programme reviews them: the first review is due that many months after the programme's start date, and each one after that the same interval after the latest. It stays greyed out until you add a benefit. See [Reviews](/portavi-docs/tracking-delivery/programme-detail.md#reviews).

### Step 4: Owner and dates

* **Owner**: required. A PMO manager, portfolio manager or programme manager.
* **Start date** and **end date**: a programme normally has a finish; if it does not, mark it open-ended, and its budget becomes a monthly rate.

### Step 5: Budget

Skippable. Covers the programme's own overhead (programme management costs), not the sum of its projects, which Portavi rolls up separately.

### Step 6: Review and confirm

## Programme health

A programme's health comes from all of its projects, with the worst case winning, except that a delayed project makes the programme **at risk**, not delayed. "Delayed" is reserved for a programme past its own end date.

A completed project always counts as best case, so finished work never drags a programme down.

## Editing later

From the programme's detail header. You can change identity, owner and dates, components and budget. Adding or removing projects here does the same thing as changing a project's placement from its own edit modal.