Before
Project completion: Fri 17:00
Alice
- Release checksFri 15:00–Fri 17:00
Hard deadline: Fri 17:00Tight headroom
Scheduling / Priorities
If everything comes first, nothing does.
Priority controls how eligible planned work competes for limited resource time. Can You Just uses four levels: Critical, High, Normal and Low. Stages inherit their project’s priority.
Understand the model ↓See the worked example →Four levels, with a practical meaning.
Critical means Interrupt; High means Next opportunity; Normal means Planned order; Low means Fit around other work. Ready planned work is allocated in that order. New projects default to Normal.
Within an equal level, existing stage sequence and identity ordering keep results deterministic. There is no extra numeric ranking hidden between the four levels.
Priority doesn’t remove the constraints.
The scheduler still respects prerequisites, earliest starts, working calendars, fixed commitments, existing interruption reservations and the resources required. Critical does not make a shared window appear or automatically move an anchored commitment.
The planned-work model orders eligible work; it does not introduce a new automatic pre-emption or natural-boundary algorithm. Ordinary accepted Can You Just interruptions reserve capacity through their own workflow.
A request is not always a commitment yet.
A request assigned to someone else stays in their Incoming queue until accepted, even when Critical. Its priority helps order the queue and inform suggestions, but a floating request reserves no capacity.
Changing a project’s local planning priority recalculates its schedule. For linked work, that edit does not change the external system’s priority.
A FICTIONAL SCHEDULING STORY
The deadline that cannot move
Before
Alice’s two hours of release checks fit from 15:00 to the hard deadline at 17:00.
The change
A committed urgent fix reserves her first hour, from 15:00 to 16:00.
After
Project completion: Fri 18:00
Alice
- Interruption · Customer export fixFri 15:00–Fri 16:00
- Release checksFri 16:00–Fri 18:00
Hard deadline: Fri 17:00Hard deadline threatened
Example assumptions. Friday 23 October 2026. Alice works until 18:00. No priorities or dependencies are changed to hide the capacity shortfall.
THE CONSEQUENCE
The deadline creates no extra capacity. Release checks now need 16:00–18:00.
THE REVISED PLAN
The hard deadline remains Friday 17:00. Completion is forecast for 18:00: one calendar hour beyond the commitment.
Work, time and consequences.
Explore the connected product ↗Register your interestComing in a later release · registration is not open yet