Working together on a schedule: discussion, presence, the change feed and rebasing edits
Discuss an activity in threads with @mentions and private notes, see who else has the Planner open and what they are editing, read the schedule's change feed and what changed since you last looked, and keep your unsaved edits when someone else saves first.
On this page
A schedule is rarely the work of one person. The superintendent questions a duration, the project manager asks why a milestone moved, and two schedulers edit the same plan on the same afternoon. The Planner keeps that conversation on the activities themselves, shows who else is working, and lets nobody’s edits be lost to someone else’s save.
Activity discussion
Every activity has a Discussion. In the Planner it’s a tab in Activity Details. Everyone else with Schedule access reaches it from the Activity page (Schedule › Update › Activity), which is also where comment links and mention notifications land.
- Threads. Write a comment (up to 5,000 characters; Ctrl+Enter posts it) and reply to it. Only the first comment of a thread can be resolved. Filter by open or resolved threads.
- @mentions. Type
@, or use @ Mention…, to pick a person. Up to 20 mentions per comment. Only people who currently have Schedule access to that activity can be mentioned or notified. A reply also notifies the thread’s earlier participants. Editing a comment notifies only people newly mentioned. - Private notes. Tick Private note (only you). A private thread is visible to its author only, mentions nobody and notifies nobody. Its replies are private too.
- Edit and delete. You can edit your own comments. You can delete your own, and Schedule admins can delete anyone’s. A deleted comment keeps its place in the thread without its text.
Discussion follows the activity ID, so it carries across saved versions. If the activity is no longer in the current saved plan, the discussion says so. You need a saved plan to start one.
Reading needs Schedule view. Commenting, replying, resolving and editing need Schedule edit. People who aren’t Schedule admin see discussion only on activities linked to a field task they can see, the same rule as the field schedule. Every change is audited, without the comment text.
Two Planner columns, Open Comments and Comments, count the discussion on each activity, so you can filter on Open Comments > 0 or group by it. They refresh every minute.
Who else is here
When someone else has the same project’s Planner open, a bar at the top shows them, with the activity each has selected. A pencil (✎) means they have unsaved edits to it. Click the activity to go to it.
- If you select an activity someone else is editing, a notice says so. You can still edit it; if you both save, the second save offers to merge.
- When someone saves a newer version, a notice names the version and who saved it. With no unsaved edits, Load the latest version. With edits, keep working; you can rebase them when you save.
Presence is advisory: it never blocks a save. Each open Planner reports in every 15 seconds and disappears 45 seconds after it stops. A person who has selected an activity you can’t see shows as (activity hidden).
The change feed
The Activity page lists what happened to the schedule, newest first, 40 at a time with Older activity:
| Filter | What it shows |
|---|---|
| Saves | Each saved version, how it was made (a save, field progress, an import merge, resource leveling, a scenario or an adopted import) and a summary, such as Activities: 3 changed, 1 added · Dependencies: 2 added · Plan: calendars |
| Calculations | Recalculations of a version |
| Baselines | Named baselines |
| Updates | Update period and submittal package events |
| Scenarios | Adopted scenarios, with the version they became |
| Imports | Imported files, and whether they were applied |
| Discussion | Comments and replies you can read |
The feed is read from the records the schedule already keeps, not a second log. Schedule admins see everything. Other Schedule users see the discussion they can read. A save’s summary is worked out while the save is calculated and stored with the version, so the feed reads it straight back. Summaries of a 30,000-activity change take about 0.15 seconds. Saves from before this release, and imports adopted as the first version, are still summarised the first time someone reads them, at most three per page load, so one of those may briefly show Change summary pending.
What changed since you last looked
When you open the Planner, a banner shows what happened since the version you last acknowledged: the versions saved since, by whom, and one combined summary of the activities and dependencies that changed, plus comments by others. Show details names up to 25 changed activities; click one to go to it. Every changed activity can be paged through the Schedule API. Got it acknowledges the current version.
If you’re one save behind, the banner reads that save’s stored summary without loading either version. Further behind, it compares the two versions.
The first time you open a project’s Planner, the current version is recorded and nothing is reported. Your own saves and rebases are acknowledged for you. The banner needs Schedule admin, because it describes the full network.
Keep your edits when someone else saves
Saves are versioned. If someone else saved after you loaded the plan, your save is refused rather than overwriting theirs. Instead of only Reload latest version, which discards your edits, you can rebase them.
- Choose Rebase my edits onto the latest version. The Planner loads the new version and re-applies your changes on top of it.
- Resolve conflicts. A conflict is a field you both changed to different values, a row one of you edited and the other removed, or the same new row added differently. For each, see the original, Yours and Theirs, and pick one, or use Keep all mine or Keep all theirs. Go to selects the activity.
- Apply rebase. Everything that didn’t conflict is merged: their changes stay and yours are applied on top. Your undo history moves with you, so Undo still steps back through your own edits.
- Review, then save and calculate. The rebased draft saves through the normal versioned path.
Merging works row by row on activities, relationships and plan-level lists such as calendars, WBS and resources. Plan-level settings merge as single fields.
Limits
- Presence is polling, not live: a new person or selection can take up to 15 seconds to appear.
- A soft lock is a hint. Two people can still edit the same activity; the second save is the one that rebases.
- The change summary compares saved versions. It doesn’t say why a change was made; use the discussion or the update narrative for that.
- What changed since you last looked lists up to 50 saves.
- Private notes never notify anyone and appear in nobody’s feed but their author’s.
- Discussion isn’t exchanged through XER or P6 XML.
Mistake: Reloading the latest version after a refused save
In the app: Reloading discards your edits. Rebase them instead and resolve only the fields you both changed.
Mistake: Asking a question in a private note
In the app: Private notes notify nobody. Untick Private note and @mention the person.
Mistake: Treating presence as a lock
In the app: It’s a hint. Talk to the person editing, or expect to resolve a conflict when you save.
Related
Keep exploring
Related across os.construction
- GlossaryChange FeedA running, newest-first list of what happened to a shared record, such as a schedule's saves, calculations, baselines, imports and discussion, with who did it and what changed.
- DocsScheduling: CPM planning, analysis and evidence in one workspaceA native critical path scheduling workspace with a P6-validated engine, P6-style layouts and views, Line of Balance and takt planning, Last Planner weekly work plans, activity discussion and a change feed, P6 import options, DCMA health, three-point risk, a reviewed update cycle, portfolio programs, reports, baselines, versions, resources, costs and period performance.
- DocsSchedule: CPM planning, field tasks and the look-aheadPlan the project in a native critical path Planner or bring in a P6 or Microsoft Project file, then publish reviewed dates to the field task list your team reads as a list, 3-week look-ahead, calendar and Gantt.
- GlossaryField Mode (Offline Sync)A way to keep a schedule on a phone, record progress on site without signal, and sync the updates as one new version when the connection returns.
- BlogPublish a native field schedule from PlannerChoose task policies, review field changes, and preserve exact identities when removing or restoring native activities.
- BlogWrite a monthly schedule narrative that explains what changedTurn a schedule update into a clear account of progress, forecast movement, logic changes, risks and decisions with a practical narrative structure.
Was this helpful?
Run it on your own project.
Start a 14-day free trial. Want a say in what ships next? Join the founding program.
14-day free trial. Pricing for paid plans isn't set yet. Talk to us. Already have an account? Sign in →