How status values and progress indicators work – and how they support daily project work
Status and Progress Logic for Planning Objects in Can Do
How status values and progress indicators work – and how they support daily project work
Status: Planned
A planning object (e.g. project, subproject, phase, milestone, or work package) is in the "Planned" status when it has been scheduled and integrated into the project plan, but no actual work has started yet.
Typical characteristics of this status:
-
The object is freely movable in time, especially the start date.
-
It is usually scheduled in the future, shown to the right of the red timeline in the project plan.
-
No working time has been recorded, and no activity has begun.
Special case: "Planned" but in the past
If an object is still marked as "Planned" but appears to the left of the red timeline, the situation is unclear.
→ The system cannot tell whether the object was forgotten, already started, or simply needs to be updated.
→ The project manager should review and update the object if needed.
Status: Started
The "Started" status is a special feature of the Can Do software.
It signals that a work package has been intentionally marked as active by someone involved – even if no time has been recorded yet.
Typical characteristics:
-
Team members set this status in their personal app to indicate:
→ "I haven’t forgotten this task – I plan to work on it." -
The start date becomes fixed and can no longer be changed.
-
The end date remains flexible – it can still be moved or extended.
This status helps to highlight priorities – even before real work begins.
Status: In Progress
The status "In Progress" means that real work has begun on the planning object.
The status can be:
-
Set manually by a project manager or team member,
-
Or set automatically when someone logs actual working time ("actuals").
Important:
-
The start date becomes fixed, since work has officially started.
-
The end date can still be adjusted – for example, if delays occur.
This status shows that the work package is now beyond the planning stage and real progress is being made.
Status: Completed
A work package is marked as "Completed" when the planned work has been fully finished.
This status can only be set manually – by the project manager or a team member.
Effects of this status:
-
The end date is fixed and can no longer be changed.
-
No further time entries are possible – the package is locked for editing.
Important rule:
A package should not be marked as completed if its end date lies in the future.
Best practices:
-
Project managers should regularly check:
→ Are there packages that ended in the past but are still open?
→ Ask the team whether the task is truly finished – and update accordingly.
Field: Percent Complete
The "Percent Complete" field shows the subjective progress of a work package – between 0% and 100% – regardless of the actual effort used.
Key points:
-
Set manually – by team members or the project manager.
-
Applies to the entire work package, not individuals.
-
Can be automatically aggregated up to phases or full projects.
Communication support
This field is a valuable communication tool:
-
It helps the project manager estimate:
→ Is the package on track or delayed? -
Combined with status and time entries, it provides a clear picture of current progress.
Automatic status change at 100%
→ When progress is manually set to 100%,
the software automatically sets the status to "Completed".
Unique Can Do behavior: Completion ≠ 100%
In Can Do, a package can be marked as "Completed" even if progress is only 80% (or any other value).
→ This means: The team finished work, even if some goals weren’t fully achieved (e.g. due to time or budget constraints).
Also possible: Completion at 0% – e.g., if time was booked but no usable result was delivered.
These special cases can be evaluated statistically – for example:
-
As a list of unfinished or failed tasks,
-
Or as candidates for rework in a later phase.
Visual progress in the timeline
Can Do shows progress as a bar inside the time axis.
-
Left of the timeline → Delays likely
-
On the timeline → On track
-
Right of the timeline → Ahead of schedule
Methodical notes
-
Percent values are subjective estimates, not exact forecasts.
-
Early in the process, progress is often overestimated:
→ Example: "80% done" – but the remaining 20% requires much more time. -
Final interpretation always lies with the project manager.
Organizational Role: Transparency in Daily Project Work
Fields like Status, Percent Complete, and Actual Time are not just technical – they are practical tools to manage and communicate daily project progress.
For project managers: Use the timeline daily
-
Review the timeline view of your project daily or weekly.
-
Focus on packages that cross the red line (today):
-
Are there delays?
-
Are there overdue packages still open?
-
Are planned packages still untouched?
-
Tip: Some project managers keep the Planner app always open – like Outlook – and react immediately when something changes (e.g. sick leave, delays).
For team members: Regular system check-in
-
Every 1–2 days:
-
Log time
-
Check assigned packages
-
Update progress
-
This habit ensures:
-
A reliable data basis
-
Transparency for all
-
Fewer coordination meetings
Conclusion
If everyone maintains these fields consistently and regularly, it creates:
-
Transparency
-
Fast reaction to issues
-
Less manual coordination
A modern project habit – just like checking your email inbox daily, not once a week.