Can You Just

Understanding / The timeline

The bars are the result. The model explains them.

The Can You Just timeline displays scheduled work against resource availability. It shows the result of effort, priorities, dependencies, interruptions and calendars, rather than a collection of manually drawn dates.

Understand the model ↓See the worked example →

Read working time, not just a long bar.

Day and Week show exact productive fragments. Month and Quarter show broader spans, with hatched gaps that are not working effort. Resource lanes make it possible to see who is doing the work, including shared contributions.

Breaks, non-working periods and interruptions explain gaps. Full-day display helps inspect overnight work. A long span does not mean someone works every hour between its endpoints.

Keep different dates distinct.

The current-time indication follows Europe/London time. Forecast completion, desired targets and hard deadlines have separate markers. Selecting work shows its dates, resources, prerequisites and Why this date explanation.

Dependencies follow selected work; a textual project summary complements the picture. Dragging expresses planning intent, and the scheduler still applies the constraints.

Let actual history stay factual.

Recorded actual intervals appear separately from future forecasts, including completed work retained after project archival. Done work consumes no future capacity. Earlier unrecorded activity is not invented from the old forecast.

Use forecast movement and history alongside the timeline to understand which changes brought the plan here. The public example below is illustrative, not an interactive copy of the workspace.

A FICTIONAL SCHEDULING STORY

The 45-minute interruption

Calculated with the CYJ scheduler

Before

Alice has seven hours of build work. Ben’s one-hour review waits for it. Friday’s 17:00 commitment fits.

The change

At 10:17, Alice commits a 45-minute request: ‘Can you just fix the customer export?’

Before

Project completion: Fri 17:00

Alice
  • BuildFri 09:00–Fri 16:00
Ben
  • ReviewFri 16:00–Fri 17:00

Hard deadline: Fri 17:00Tight headroom

After

Project completion: Fri 17:45

Alice
  • BuildFri 09:00–Fri 10:17
  • Interruption · Customer export fixFri 10:17–Fri 11:02
  • BuildFri 11:02–Fri 16:45
Ben
  • ReviewFri 16:45–Fri 17:45

Hard deadline: Fri 17:00Hard deadline threatened

Example assumptions. Friday 23 October 2026. Both people have a deliberately simple 09:00–18:00 calendar without breaks. The fix is committed work; actual effort has not been recorded.

THE CONSEQUENCE

The build now finishes at 16:45. Ben’s review moves with it, despite receiving no interruption.

THE REVISED PLAN

Completion is Friday 17:45. The 17:00 hard deadline stays fixed, so the forecast shows a threatened commitment.

Explore the model:Can You Just interruptions →The timeline →Targets & deadlines →

CONNECTED IDEAS

The rest of the story.

Dependencies A dependency says that work must wait for other work to finish. Can You Just combines those prerequisites with calendars, capacity and priorities when calculating the forecast.Can You Just interruptions A Can You Just interruption records unplanned work against a resource. Once committed, it reserves productive capacity and the scheduler recalculates the planned work that uses the time left.Activity & forecast history Activity records meaningful saved changes. Forecast history records meaningful observations of the schedule. Together with actual work, they help explain the gap between the original plan and what happened.

Work, time and consequences.

Explore the connected product ↗
Register your interestComing in a later release · registration is not open yet