nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Status changes

Matthew Fratkin_sk7dv3

We are new to using Atlas and might be asking a basic question regarding the status. If we start a project and set the "When it will be done" to March 2025 and the status to "On Track", how do we handle deviations for the target date.

For example, do we say "Off Track" with a due date of April 2025 or do we keep the status at "On Track" since we now know we will finish on April?

In one sense, its helpful to see all projects that have deviated from the original due date but we might have all projects "Off Track" if they shift for one month or so.

If we keep changing them to On Track, then when would you ever use the other statuses if you keep changing the completion date?

Comments

Andrew Culver

Whenever you submit a project update you will be prompted to set the status (on track, etc) and update the end date. It's up to the updater to decide whether a change in the end date is considered on track, delayed, at risk, etc.

This will likely depend more on your PM practices than the specifics of the tool. In many PM cases, falling behind the target end date would change the status of the project to at risk of missing the completion date until a formal project change is approved by the project sponsor to push the end date back and give the project more time, which would return the project to bring on track again.

Jay_j2n0yr

In general, I use 'off track' based on the current plan. If the date has been officially pushed out (and communicated to stakeholders), then I move to 'on track' with the new date.

Matthew Fratkin_sk7dv3

Ok, I like this thinking. Until, I officially communicate a date change it will be "off track" or "at risk". Once that has been communicated, the new date is updated and use the "On Track" status.

David Washbrook

There was also discussion on this topic last year: https://community.atlassian.com/t5/Atlas-questions/Project-status-and-date-relationship/qaq-p/2640238

Essentially it is up to each organisation to define how these statuses will be reported and if you search on the web you will find a variety of definitions.

For our organisation 'At risk' is set when there is a possibility that, without taking mitigating actions, the project deadline or other objectives will not be achieved. There is no date change associated with an 'At Risk' status. The status report should record the details of the risk and the mitigating actions being taken to correct the situation.

'Off track' is set when the project deadline or other objective (e.g. budget) cannot be achieved. If there is a new deadline set (or revised budget), then the post for the week the deadline is pushed out will always be 'Off track'. This post should detail the reasons for changing the date. The post for the following week will report the status against the new deadline, and if the project has been adequately been rescheduled then it would be expected that the new status will be 'On track'.

The timeline at the top of the project page will provide an overview of the project status changes.

Welcome!

It looks like you're new here. Sign in or register to get started.