> 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/governance/benefits.md).
# Benefits
A benefit is a measurable outcome a programme exists to deliver. Benefits are **programme-only**: projects deliver outputs, programmes deliver benefits.
## Where benefits live
On a programme's **Overview** tab, reviewed on its **Reviews** tab, and aggregated in **Governance → Benefits Register**.
At the top of **Governance → Benefits Register**, a summary card totals the register with a bar splitting it into achieved, delayed and in progress; hovering a segment names it and gives its share.
## Adding a benefit
* **Title** and **description**: what the outcome is
* **Target date**, **owner**, contributing **projects** and linked **risks**
* **Unit**, **baseline** and **target**: what the value is read in, e.g. tickets / month, where it starts and the value that counts as realised, as on a key result
A target below the baseline means the value is meant to fall, as tickets or cost are. The measure fields are optional; a benefit without a baseline and target is simply not measured. How often benefits are reviewed is the programme's **measurement cycle**, not each benefit's. You can add benefits when creating a programme, or any time afterwards.
## Delivered and realised
A benefit is **delivered** when the work behind it is done: every contributing project completed, or, with no contributing projects, marked delivered by hand. The owner and PMO managers are notified when it happens.
It is **realised** when its measurements reach the target. Measurements are recorded for every benefit at once in a [benefit review](/portavi-docs/tracking-delivery/programme-detail.md#reviews), so a benefit's trajectory is visible rather than only its endpoint.
## Benefits versus objectives
These are easy to confuse:
| | Benefits | [Objectives](/portavi-docs/strategy/objectives-and-strategy.md) |
| --------- | ---------------------------------- | --------------------------------------------------------------- |
| Belong to | A programme | A portfolio |
| Answer | "What did this programme deliver?" | "Are we investing in the right things?" |
| Timeframe | The programme's life | Ongoing, reviewed on a cycle |
A programme delivers benefits. A portfolio pursues objectives. If you find yourself wanting a benefit on a portfolio, what you probably want is an objective.
## Reading a benefit
Selecting a benefit opens it in full: its baseline, target, latest value and next review, a chart of its measurements against the target, its description and the projects delivering it.
The \*\*Owner\*\* credit names the champion. Their avatar carries their role colour, and selecting it opens their \[profile]\(../tracking-delivery/member-profile.md).
## Who can edit
The programme's owner, or a PMO manager.
