Your project activity feed used to label every entry “No impact”, whether it was a routine update or the thing that had just put your go live date at risk. The information existed — your dashboard was already telling you the project was at risk, and why — but the history you scroll through said nothing about which events mattered.

Each entry now carries its real effect on your go live date:

• Delays go live — a milestone that has to finish before you go live is past its date and still open, or an invoice is unpaid and past due.
• Minor delay — a milestone is past its date but does not hold up go live, or a blocker on your project is still open.
• No impact — everything else, including work that has since been completed and blockers that have since been cleared.

These read from exactly the same information as the go live status on your dashboard, so the two can never tell you different things about the same milestone, blocker or invoice. An entry about something that has since been put right goes back to “No impact” — the feed records that it happened, not that it still hurts.

Two kinds of update now reach the feed that never used to appear there at all: a milestone moving to a new stage — started, complete, blocked — and a blocker being raised or cleared on your project. Together with the impact tags, that means the feed finally answers “what changed, and did it cost me time?” without you having to ask your delivery team.

Entries are also written in plainer language than before. Where the feed used to show the platform’s own shorthand for an event, it now shows what actually happened — “Requirements approved” rather than an internal label.

Nothing you need to do, and no history has been rewritten: older entries stay as they were and continue to read “No impact”, because the tag is worked out from your project as it stands rather than stored against the entry.