> 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/status-updates.md).
# Status updates
Health is worked out from the tasks Portavi syncs, and it can only say what the numbers say. A status update is the sentence a person adds beside it: where things stand, in their own words. Every project, programme and portfolio carries one in its header, with the whole history behind it.
## Where it appears
The latest update sits in the header, under the owner, dates and health badge, with how long ago it was posted and a **History** link. A page with no update yet shows nothing there; the header does not grow until someone has something to say.
The description that used to sit in the header now lives in an **About** card at the top of the Overview tab.
## Posting an update
The square-plus beside the Reports and Edit icons opens the post modal. It is available to the entity's owner and to PMO managers; everyone else reads.
The modal shows the entity's current status beside its title, so you can see what you are describing. The text takes formatting and mentions, the same as every other text field, and runs to 500 characters at most: an update is a line, not a report. Mentioning someone notifies them in the usual way.
Each update records the status the entity had when it was posted. That is what makes the history worth reading later: "At risk" next to the update that explained why, "On track" next to the one that said it was fixed.
## The history
**History** in the header opens every update, newest first, each with the status at the time and who posted it. Selecting the avatar or the name opens that person's [profile](/portavi-docs/tracking-delivery/member-profile.md). If you can post, a **Post update** button sits at the bottom of the history too.
## When the status changes
Moving a project, programme or portfolio between **Active**, **Inactive** and **Completed** from its status badge asks for an update before it saves, and will not save without one. The person changing the state is the person who knows why, and the history should say so. The modal names the state you are moving to. Archiving and restoring do not ask.
## Where else it shows
Every update is also an entry in the **Activity** tab, in date order with the sync events and chat signals, so the story of a project reads as one feed.
## On a phone
The square-plus is not shown. On a project or programme, use **Post update** in the header's **⋯** menu instead. The History link works the same everywhere.
