Skip to the page

DocsPlanning

DocsPlanning

When plans change: the cascade preview

Before a task slips, see which booked time would move, which outcomes would be late and who is affected, then commit the reshuffle or discard it.

When a task is going to run late, the work that depends on it has to move too. The cascade preview shows that knock-on effect before anything changes: which booked time would move, which due dates and outcomes would be at risk, and whose week is affected. You then commit the reshuffle, try an alternative, or walk away.

Anyone can open a preview. Committing one that moves other people’s time is for owners and admins. See who can commit.

Start a preview#

From the task: What if…?#

A task that isn’t done has a What if…? card on its page, unless its project is archived.

  1. Choose the change:

    • It slips: the task finishes a number of working days later.
    • Takes longer: the estimate goes up to the hours you type.
    • Due later: the due date moves to the date you pick.
  2. Choose Preview impact →.

From the Gantt: drag a bar#

On a project’s Gantt view, drag a task’s bar to the right. The bar shows how many days you’ve moved it, and when you let go a small prompt asks what you meant:

  • A solid bar (booked time) asks “Slip AL-003 by 2 working days?”. The days counted are the assignee’s working days that the bar passed over.
  • A hollow bar (planned from its due date) asks “Move AL-003’s due date to Wed 21 May?”.

Choose Preview impact → to open the preview, or Cancel. Back to timeline on the preview returns you to the Gantt.

A few drags don’t open a preview, and the bar goes back where it was:

  • Dragging earlier. Pulling work earlier isn’t previewed. Move the time in the Calendar instead.
  • Dropping where no working day passes, such as Friday to Saturday. Nothing would slip.
  • A task whose booked time has all started. A slip can’t move time that has already begun.

Done tasks, tasks with no bar and tasks in archived projects can’t be dragged, and bars can’t be resized: use Takes longer on the task for that. Dragging needs a mouse or a pen. On a touch screen it scrolls the timeline.

Drag a task later and preview what moves

Read the preview#

The page title states the change, for example “If AL-003 slips by 2 working days…”. Nothing is saved until you commit.

  • The summary counts the tasks that shift and the outcomes and due dates at risk, says how many people are affected across how many projects, and gives each late outcome’s new date against its target.
  • Before · current plan and After · proposed reshuffle draw the same tasks and outcomes side by side, each with its finish date. Dates that change are highlighted, and an outcome’s target date is marked on its row. The legend underneath names the colours.
  • What would change lists each task with its old and new finish date, and a note where one is needed.
  • Show the booking changes opens a table of every block that would move, be added or be released, with whose it is and the old and new times.

How Projik works it out#

Projik follows the task’s dependencies outward: the tasks that depend on it, and, through its outcome, the tasks that depend on that outcome.

  • Booked work moves. When a task can no longer start as booked, its blocks that haven’t started yet are moved later, into the first free time in the assignee’s working hours. They’re placed around the person’s other bookings and the meetings in their connected calendar. A block keeps its length, and may be split to fit the free time.
  • Started work never moves. A block that has already begun stays where it is, and done tasks and outcomes are left out altogether.
  • Meetings move with everyone in them. A booking with other people invited to it (a meeting) moves as one block, to the first time the organiser and everyone invited are free, inside all their working hours. It’s never split. Everyone invited is asked again, since they accepted the old time. If no time in the next 90 days suits everyone, that task is reported as having no room, with the reason. A task with a meeting booked can’t be handed to someone else here.
  • Unbooked work is never booked for you. A task with no booked time is flagged Due date at risk when its work no longer fits before its due date.
  • Outcomes follow their tasks. An outcome finishes when its last open task does. If that’s after its target date, it’s at risk by that many working days.

What each change does depends on whether the task has booked time:

ChangeTask with booked timeTask with no booked time
It slipsIts blocks that haven’t started move later by that many of the assignee’s working days.Its due date would move by that many working days.
Takes longerThe extra work is booked after its current blocks, in the assignee’s free time and at their speed.Nothing moves. Check the due date still fits.
Due laterNothing moves. Booked time is the schedule, so the due date doesn’t drive it.Its due date would move, and whatever depends on it follows.

A task with no booked time and no due date has nothing to preview: nothing depends on when it finishes.

When the preview can’t finish the plan#

The preview says so plainly, and Commit reshuffle is switched off, when:

  • some work has no room in the next 90 days, or its meeting has no time that suits everyone;
  • a task waits on work that has no room, so its finish can’t be worked out;
  • the change reaches more than 200 tasks.

If tasks depend on each other in a loop, Projik stops at the loop and names the tasks so you can fix the dependency. If someone’s connected calendar can’t be read, the preview tells you and plans their time as free.

The alternatives Projik considered#

Under the plan, Alternatives lists other ways to absorb the change, each already worked out. Choose Try it to redraw the after pane with one. The alternative on screen is marked Showing, and it’s the one Commit reshuffle commits.

  • Let it slip. The default: move the work, and accept where the outcomes land.
  • Hand it to someone else. Active people who have every skill the task asks for and room to take it. Each shows when they’d finish, how that compares with letting it slip, their free hours in the next two weeks and the effect on the outcomes. Committing releases the current assignee’s blocks that haven’t started and books the remaining work in the new person’s free time, at their speed.
  • Hand it to an AI worker. The same, for AI workers with the skills. Each worker’s speed is shown beside its name, and its time is booked at that speed.
  • Take a task out of the outcome. When the plan makes an outcome late, any task in the plan that belongs to it can be taken out, so the outcome no longer waits for it. Each shows where the outcome would then land.

Handing the task over is offered only when the task has booked time and the change is a slip or a bigger estimate. Projik lists up to four people and four AI workers, best finish date first.

Commit or discard#

The bar at the bottom sums up what a commit would do and who is affected. Discard goes back to the task with nothing changed. Commit reshuffle applies the plan on screen.

Outcome dates#

When the plan makes an outcome late, Outcome dates lists each one with a tick box: “Push outcome from its target to its new date”. For owners and admins the boxes start ticked. Untick one to leave that outcome’s target where it is. Only an owner or admin can move an outcome’s date, so for everyone else the boxes are switched off.

Who can commit#

  • Owners and admins can commit any plan, including the alternatives and pushed outcome dates.
  • The task’s assignee can commit when every booking that moves or is added is their own. They can’t commit one of the alternatives or push an outcome date.
  • Everyone else can preview and discard.

What a commit does#

Projik works the plan out again at the moment you commit. If anything has changed since you opened the preview, nothing is committed and you’re shown the up-to-date plan to check and commit again.

A commit is all or nothing. It moves the bookings, adds or releases blocks, updates the task’s estimate or due date, and pushes the outcome dates you ticked. If any step can’t be applied, everything is put back and you’re told.

Afterwards the page confirms “Reshuffle committed” with a one-line summary. Moved bookings update in people’s connected calendars in the background.

Who is told#

Everyone whose booked time the reshuffle changed is told, on My Work, in the bell and by email: people whose blocks moved, were added or were taken off them, and the person handed the task. The person who committed isn’t told, and nor are AI workers.

Undo a reshuffle and schedule notices covers what they see, and how to put a reshuffle back.

    Type to search every page. ↑ ↓ to move, Enter to open.