A change feed lists the events on a record in time order, newest first: who did what, when, and a short summary of the change. It answers the question people ask when they come back to a shared record: what happened while I was away?
Why it matters
On a schedule, the dates that matter can move because of a save, an import, an adopted scenario or an update. Without a feed, people find out by noticing that a bar has moved. A feed with change summaries tells them which activities changed and who changed them, and links to the conversation about it.
Worked example
Illustrative: the project manager opens the schedule on Monday. A banner says Version 41 → 44 · 3 saves, with Activities: 12 changed, 2 added · Dependencies: 3 added and 4 new comments. The details show the scheduler resequenced the Level 5 pour after an RFI answer. The PM reads the discussion on that activity and marks the changes as seen.
Common mistakes
- Treating a feed as an audit trail. A feed summarises; the audit trail and the saved versions are the evidence.
- Reading a change summary as the reason for a change. It says what changed, not why.
How os.construction handles it
The Schedule Activity page lists saves with change summaries, calculations, baselines, update events, adopted scenarios, imports and discussion, filterable by kind. Schedule admins see everything; other users see the discussion they can read. The Planner’s What changed since you last looked banner summarises the versions saved since you last acknowledged one. See Working together on a schedule.