Collaborative editing
Multiple team members can edit the same project at the same time. Plenar manages concurrent changes so your team never runs into conflicts.
How concurrent editing works
When you make a change — edit an estimate, add a task, reassign work — it enters a queue in the New Plan panel. Plenar tracks three:
Your changes
Your own edits, not yet applied — estimate changes, tasks you added or removed, dependency changes, and scope or assignment changes. Listed under Your Changes, where you review the diff and decide to apply or discard.
Incoming changes
Edits a teammate applied after your last refresh — someone else changed an estimate, added tasks, or reassigned work. Listed under Incoming, so you can see what changed and how it affects the schedule before it folds into your view.
Synced changes
Changes from connected integrations — a Google Calendar event that books time off, a Jira status update, a SCIM membership change. Listed under Synced. They mirror an external source of truth, so they can’t be discarded — only applied.
Preview before you apply
All changes flow into the New Plan , regardless of who made them. Before you Apply your pending changes, you see how the New Plan differs from the Plan of Record :
- Which tasks moved and by how much
- Goal ETA changes
- Assignment shifts
- Whether the plan is still feasible, and how its quality compares — the full set of plan states shows on the panel as a colored dot
This means you always know the impact before you apply. See Preview and apply for the full edit → preview → apply flow.
No merge conflicts
Plenar does not have merge conflicts in the traditional sense. Changes are aggregated, not merged:
- If Alice changes an estimate from 3 to 5, and Bob later changes it from 5 to 4, the result is 4.
- If Alice adds a dependency and Bob removes a different dependency, both changes apply independently.
- If Alice adds a task and Bob changes an estimate on a different task, both apply.
Each change is applied in order. The final Plan of Record reflects all applied changes. There is no “conflict resolution” step because changes apply to the plan, not to a shared document.
Integration changes
Changes from connected integrations land in the Synced queue — applied automatically, since they mirror an external source of truth:
- Calendar sync — new time off from calendar events appears as an availability change
- Jira sync — status updates from Jira appear as task status changes
- SCIM — new or removed team members appear as team changes
They flow into the same New Plan, so you see the impact before the Plan of Record updates.
Best practices
Review incoming changes regularly. When you open the New Plan panel, check the Incoming section first — a teammate may have made changes that affect your work.
Use the preview to verify impact. Before you apply a batch of changes, review the combined diff carefully. Multiple small changes can compound into a significant shift in the plan.
Stack changes, then apply once. Make all your edits (estimates, dependencies, assignments), then review the combined New Plan and apply in one batch. This is more efficient than applying after every individual edit.
What to do next
- Preview and apply — the edit → preview → apply flow that every change goes through
- How scheduling works — the model behind the Plan of Record
- Manage your plan — apply, discard, and review changes day to day