> 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/tracking-delivery/stakeholders.md).
# Stakeholders
A project's **Stakeholders** tab records who has a stake in the work, how much they can affect it, how much they care, and how engaged the project needs them to be. It replaces the Team tab when **Stakeholder engagement** is on in **Settings → Features**; the Team view is still there, as the first view of the tab.
Switch the feature off and the tab goes back to **Team** only. Nothing is deleted: the stakeholders come back as they were when it is switched on again. Stakeholder engagement is included in every plan.
## Who sees it
Stakeholder analysis names people as resistant and records how to handle them, so it is not shown to everyone:
* **See it:** the project owner, PMO managers, and the owners of the project's programme and portfolio.
* **Change it:** the project owner and PMO managers.
Anyone else, executives included, keeps the plain Team tab.
## Adding a stakeholder
Select **Add stakeholder** and choose who:
* **Team member**: someone synced from the project's tool.
* **Portavi user**: anyone in the workspace.
* **Someone else**: a person without an account, such as a client, a regulator or a supplier. Search first: the people already added anywhere in the workspace are listed, with how many projects they are on. If they are not there, add them as someone new with their name, organisation, role and, optionally, email.
A person is one record across the workspace. Their name, organisation and role are shared; their scores and engagement are set for each project, because the same person matters differently to different work.
Then give them:
* **Power** and **interest**, each from 0 to 10.
* **Current** and **desired engagement**: Unaware, Resistant, Neutral, Supportive or Leading.
* An **engagement strategy**: how you will keep them engaged.
* A **relationship owner**: who in the workspace looks after them.
## The views
**Analysis** is the stakeholder register: how many stakeholders there are, the key players, how many are below the engagement the project needs, and when the analysis was last reviewed, then one row per person. Select a row to edit it.
**Last reviewed** is the last time anyone added, changed or removed a stakeholder on the project, including a quick change such as moving an engagement marker. RACI changes do not count.
**Power–interest** places everyone on the four-quadrant grid. A score of 6 or more counts as high:
| Quadrant | Power | Interest |
| ------------------ | ----- | -------- |
| **Manage closely** | High | High |
| **Keep satisfied** | High | Lower |
| **Keep informed** | Lower | High |
| **Monitor** | Lower | Lower |
Select a person to open their details, where the scores are changed with sliders. Programme and portfolio owners, who can see the analysis but not change it, see the person's details beside the grid instead.
**Engagement** is the engagement assessment matrix: a row per person, a column per level, a **C** where they are now and a dashed **D** where the project needs them, and how many steps apart the two are. Choose which marker to move, then select a cell. Select a person's name to open their details. On a phone the column narrows to their picture, and it stays in place while the levels scroll sideways.
## RACI
**RACI** lists the project's scope items as rows and names, for each one, who is:
* **Responsible**: does the work. Every row needs at least one.
* **Accountable**: signs the work off. Exactly one person per row.
* **Consulted**: asked before decisions are made.
* **Informed**: kept up to date after decisions are made.
Select a cell to add or remove people. You can name anyone on the stakeholder register, a team member synced from the project's tool, or any Portavi user in the workspace; someone who is not on the register yet is added to it. Choosing a new Accountable replaces the last one, and a person holds only one role on a row.
Each row is checked against the two rules: a row that meets them shows a check mark, and one that does not says **No one accountable** or **No one responsible**.
### Drafting from tasks
Select **Draft from tasks** and Portavi AI reads the project's epics, parent tasks and phases and proposes its scope as a handful of deliverables and workstreams, such as *Data migration* or *User acceptance testing*, each covering several of them. Each row shows what it was drawn from. It suggests Responsible people from who actually works on those tasks, and Accountable, Consulted and Informed people from the stakeholder register. It only names people already on the register.
Drafted rows carry the Portavi AI sign after their name, and stay shaded as suggestions until you accept them; the sign stays after, so you can always tell which rows Portavi AI proposed. **Accept** or **Discard** each row, or settle them all at once with **Accept all** or **Discard draft**, which removes every row you have not accepted. Drafting again replaces the previous draft and leaves accepted rows alone.
Each draft uses one generation of the workspace's monthly AI allowance, however many rows it proposes; accepting, discarding and editing rows use none. A draft needs at least one stakeholder and some epics, parent tasks or phases to work from.
Taking someone off the project's stakeholders also takes them out of its RACI.
## Programmes
A programme's **Team** tab becomes **Stakeholders** too, with the same switch in **Settings → Features**. It is shown to PMO managers, the programme owner and the owner of its portfolio; the programme owner and PMO managers can change it.
**Analysis** rolls up the programme's own stakeholders and everyone on its projects, one row per person, with every place they appear. Turn off **Include project stakeholders** to see only the programme's own people.
* **Programme stakeholders**, such as the sponsor and benefit owners, are added and edited here. Select **Add program stakeholder**.
* **People from its projects** are edited on their project. Selecting one opens the project that rates them most powerful.
* Where the programme has its own entry for someone, its scores are the ones shown. Otherwise the programme shows the project that rates them most powerful.
* When projects score the same person 3 or more apart, on power or interest, the power is flagged. Point at the flag to see each project's scores.
**Power–interest** places the same people on the grid.
**RACI** at programme level has a row for each of the programme's **benefits** and for its own **programme work**, such as a quarterly benefits review. A benefit row is named after its benefit and shows the projects that deliver it. Cells can name anyone on the roll-up or any Portavi user; a user who is not on it yet becomes a programme stakeholder.
**Draft from benefits** proposes a row for each open benefit that has no row yet, plus a few rows of programme work, with suggested people. It works like **Draft from tasks** on a project.
## Portfolios
A portfolio's **Team** tab becomes **Stakeholders** for PMO managers and the portfolio owner. Nothing is edited here: people live on the programmes and projects under it.
**Governance** shows:
* **Steering committee:** the committee from the portfolio's latest strategy review, with how many reviews each member attended. Change it in the next strategy review.
* **Key players across the portfolio:** people who are in **Manage closely** on two or more of its programmes and projects.
**Coverage** checks every programme and project in the portfolio. Select a row to open its Stakeholders tab.
| Column | Shows |
| ----------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **People** | How many stakeholders it names. None is a gap. |
| **Key players** | How many are in **Manage closely**. |
| **RACI** | No RACI yet, how many rows break a rule, or all rows complete. Suggested rows that have not been accepted do not count. |
| **Last reviewed** | When its stakeholder analysis last changed: within 30 days reads as current, over 90 days as a gap. |
