Can You Just

Planning / Projects & stages

A project is a promise. Stages make it schedulable.

A project groups work towards an outcome. Its stages describe the pieces of work, estimated working duration and resources needed to get there.

Understand the model ↓See the worked example →

Define the work before choosing the date.

A project brings together stages, a priority, an optional target and a hard deadline. A stage has its own details, status, Estimated Duration and assigned resources. External waiting can use a release date without consuming productive staff time.

Effort and elapsed time answer different questions.

Estimated Duration sizes the planned work in working minutes. Remaining is calculated from scheduled intervals relative to the planning clock; it is not a separate editable estimate. A two-hour stage may span a break or continue tomorrow.

Sequence orders eligible stages, but does not create a prerequisite. Add an explicit dependency when a review really must wait for a build.

One finish depends on all the required work.

Project completion follows the latest required stage finish. An unfinished stage with no feasible forecast leaves project completion unknown; Can You Just does not invent a date just to fill a column.

Archive projects to remove them from future planning while retaining history. Archive is not the same as marking unfinished work complete.

A FICTIONAL SCHEDULING STORY

The person who wasn’t interrupted

Calculated with the CYJ scheduler

Before

Alice prepares the work from 09:00 to 11:00. Ben reviews it from 11:00 to noon.

The change

Alice takes a committed one-hour export fix at 10:00. Ben’s calendar, estimate and assignment stay unchanged.

Before

Project completion: Mon 12:00

Alice
  • PreparationMon 09:00–Mon 11:00
Ben
  • ReviewMon 11:00–Mon 12:00

After

Project completion: Mon 13:00

Alice
  • PreparationMon 09:00–Mon 10:00
  • Interruption · Customer export fixMon 10:00–Mon 11:00
  • PreparationMon 11:00–Mon 12:00
Ben
  • ReviewMon 12:00–Mon 13:00

Example assumptions. Monday 19 October 2026. Both people work 09:00–18:00 without breaks in this isolated example. One explicit stage dependency connects preparation to review.

THE CONSEQUENCE

Preparation finishes at noon. The finish-to-start dependency prevents Ben reviewing it at 11:00.

THE REVISED PLAN

Ben reviews from 12:00 to 13:00. His work moved because its prerequisite moved, not because someone edited his task.

Work, time and consequences.

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