This article explains how to update a project’s status in TeamDynamix (TDX), with a focus on using the Status, Health, Percent Complete, and Comments fields correctly. It is intended to help project managers communicate progress, risk, and overall project condition clearly to leadership, stakeholders, and governance teams.
The goal of a project status update is not detailed task reporting, but to provide a clear and accurate summary of where the project stands at a given point in time. By keeping these fields accurate and aligned, departments support transparency, stronger governance, and better decision making throughout the project lifecycle.
Table of Contents
Overview
Overview
The Project Status Update screen provides the Project Manager with an easy to access view within the TDX Project of a Project's key status metrics. Here the Project Manager can update these metrics and add a comment, if necessary, to provide additional context for the status.
A complete and effective status update allows reviewers to quickly understand:
- Where the project is in its lifecycle
- Whether the project is on track or at risk
- How much progress has been made
- What has changed since the last update
Status updates should be reviewed and updated regularly throughout the project.
Accessing the Project Status Update Screen
To update project status:
- Navigate to Applications → Projects
- Select the project you want to update
- Choose Update Project Status
This opens the status update panel for the selected project.
Understanding and Completing Update Fields
Status
The Status field describes where the project is in its lifecycle.
Examples may include:
- New
- In Progress
- On Hold
- Completed
Status should reflect the structural phase of the project, not whether the project is going well or poorly.
Health
The Health field provides a high level signal of overall project condition.
Health should answer the question:
If leadership reviewed this project today, should they be concerned?
Common health indicators include:
- Green: The project is on track and behaving as expected
- Yellow: The project is at risk but issues are manageable and there exists a plan for resolving the risks and issues.
- Red: The project is off track and requires intervention or escalation
Health should be updated based on current risks, issues, and overall predictability. (See specific Project Health Article for more detailed guidance.)
Percent Complete
Percent Complete represents a high level estimate of overall project progress.
Guidance for using this field:
- The Project Plan will indicate a percentage of completeness based upon the completion of the tasks in the plan.
- Directionally, the completion of a Project Plan, including a Project Kick-off meeting, represents approximately 20% of a plan. Use this as a guide only as each plan contains its own details.
- It should be updated when progress is made
A percent complete value that does not change over time may raise questions during review.
Comments
The Comments field provides context for the status update and is often the most important section for reviewers.
A strong status comment typically includes:
- What has been completed since the last update
- What work is planned next
- Any key risks, issues, or decisions requiring attention
Comments should be clear, concise, and honest. They do not need to be lengthy, but they should explain the story behind the status and health selections.
How Status, Health, and Comments Work Together
All status update fields should align with one another.
For example:
- A Green health status should be supported by stable progress and manageable risks
- A Yellow or Red health status should be explained clearly in the comments
- Increasing risks or unresolved issues should be reflected in health
These fields work together to provide a complete and accurate picture of the project.
Common Mistakes to Avoid
When updating project status, avoid the following:
- Leaving health set to Green to avoid escalation
- Updating percent complete without a supporting update of progress in the Project Plan.
- Using vague or repetitive comments
- Failing to update status when conditions change
The purpose of status updates is to reduce surprises.
When to Update Project Status
Project status should be reviewed and updated:
- During regular reporting cycles
- After major milestones
- When risks or issues change
- When scope, timeline, or priorities shift
Even when little has changed, the update should be intentional and reviewed.
Additional Support
- OU Technology Center
- 44 Oakland Center
- Rochester, MI 48309-4479
- (248) 370-4357
- Office Hours: M-F 8:00am - 5:00pm