> 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/lessons-learned.md).
# Lessons learned
A lesson records something worth remembering: what happened, why, and what to do differently.
## Where lessons live
Like risks, a lesson belongs to exactly one parent: a **project** or a **programme**. Manage them from that entity's **Lessons** tab, or see them all in **Governance → Lessons Learned**.
At the top of **Governance → Lessons Learned**, a summary card totals the register with a bar splitting it by RAG rating; hovering a segment names it and gives its share.
Unlike risks, lessons have no promotion mechanism. Each belongs to one parent, full stop.
## Adding a lesson
* **Title**: required
* **RAG rating**: red, amber or green: whether this is a warning, a caution, or something that went well
* **Category**: schedule, budget, technical, scope, resource or external
* **Early signs**: what the warning signals were, in hindsight
* **Action taken**: what you did
* **Recommendations**: what future projects should do
Only the title is required. A lesson captured quickly is worth more than a perfect one never written, and **Early signs**, **Action taken** and **Recommendations** can each be rephrased, shortened or expanded once written, so a hurried note can be tidied later without retyping it. See [AI in Portavi](/portavi-docs/ai/ai-in-portavi.md).
## Lessons from sprint reviews
When you [review a sprint](/portavi-docs/tracking-delivery/sprint-reviews.md), any lessons you record land here automatically, tagged with the sprint that produced them.
The sprint name shows as a pill on the lesson wherever it appears, in the project's Lessons tab and in the workspace register, so the lesson keeps its origin. You can open it later and fill in the fuller detail.
## Green lessons matter
The register is not only for failures. A green lesson records something that worked and should be repeated. Teams under-record these, and they are the ones worth copying.
## Reading a lesson
Selecting a lesson opens it in full: early signs, action taken and recommendations, which the row itself does not show. The **Logged by** credit names who wrote it. Their avatar carries their role colour, and selecting it opens their [profile](/portavi-docs/tracking-delivery/member-profile.md).
## Who can edit
The owner of the parent project or programme, or a PMO manager.
