Handle Schedule Changes
Schedules change. Estimates are wrong, scope grows, people go on vacation. This guide covers how to handle common scenarios in Plenar without losing control of your plan.
Estimate was wrong
You estimated 3 days but the task is taking 5:
From the dashboard: Click the task in the Scope Table, edit the estimate. Plenar previews the impact — which downstream tasks shift, whether any goals slip.
From Claude Code:
Update the auth middleware estimate to 5 days — the edge cases
are more complex than we expectedReview the preview. If a goal goes off-track, consider:
- Reducing scope — flip some tasks from Must to Nice
- Parallelizing — remove a dependency so two tasks can run simultaneously
- Reassigning — move work to someone with more availability
Scope grew
New requirements appeared mid-sprint:
Add a task: "Handle edge case for expired tokens", 1 day,
must-have, depends on the OAuth taskPlenar shows you exactly how the new work affects your timeline. If it pushes a goal past its deadline, you see that immediately and can make a scope trade-off before committing.
Someone is out unexpectedly
A team member calls in sick for the week:
From Claude Code:
Mark Alice as sick Monday through Friday this weekPlenar previews the schedule shift. All of Alice’s tasks during that period move to her next available dates. Dependent tasks cascade. You see the full ripple effect before applying.
If the impact is severe, consider reassigning Alice’s critical-path tasks to another team member.
A task is blocked
External dependency is not ready:
I'm blocked on the deployment task — waiting on the
infrastructure team to provision the staging environmentPlenar marks the task as Blocked and shows alternative tasks you can pick up. Blocked tasks do not progress in the schedule, and downstream work adjusts accordingly.
When the blocker is resolved, start the task again to resume normal scheduling.
New team member joined
- Add them to the organization (Settings > Members)
- Assign them to the project (Settings > Team)
- Optionally set their skills
- Trigger a Recompute if auto-assignment is enabled — this lets Plenar redistribute work across the updated team
You do not have to recompute immediately. If you plan to manually assign tasks to the new member, just add the tasks and assignments, and the normal change impact preview handles it.
Team member left the project
- Reassign their tasks to other team members (or enable auto-assignment)
- Remove them from the project team
- Trigger a Recompute to re-optimize the schedule
Plenar will not schedule work for removed members, so any tasks still assigned to them will show warnings.
Goal deadline moved
Stakeholders pushed the deadline earlier:
From the dashboard: Open the goal detail panel, change the target date.
From Claude Code:
Move the API Launch goal deadline to April 15Plenar shows whether the new deadline is feasible with current scope and capacity. If not, the preview shows which goals go off-track and by how many days. You can then adjust priorities, scope, or assignments to recover.
Multiple changes at once
You can stack changes before applying. Edit three estimates, add a dependency, reassign a task — Plenar batches them and shows the combined impact as a single preview. This is useful for grooming sessions where you want to make several adjustments and see the net effect.
Apply or discard the entire batch. There is no partial apply.