Our projects report different status definitions. How do we standardize?
Inconsistent portfolio signalsAgree a small common set of evidence-based status rules while allowing relevant project-specific detail. Define unknown and awaiting decision rather than forcing every situation into a reassuring color.
What to do now
- Compare current status definitions
- Agree common thresholds and evidence
- Train owners on interpretation
- Review inconsistent classifications with facts
When to escalate
Escalate when
A status definition hides material exposure or encourages misrepresentation.
Who decides
The portfolio decision authority
Example
At-risk means a forecast breach without an approved credible recovery path, not merely a manager's feeling.
Mistake to avoid
Forcing all projects green until a deadline is actually missed.
Prevent a repeat
Review whether active commitments fit available capacity and current priorities rather than just tracking project counts.
Suggested ApprovedFlow setup
- Projects
- Resources
- Documents
- Approvals
Use project and capacity records to support portfolio decisions, then record approved priorities and consequences explicitly. See the platform
Related cases
- How do we maintain a useful project inventory?Unreliable portfolio baseline
- The same dependency appears in many project plans. Who should own it?Shared dependency governance
- Different reports show different completion percentages. Which one is right?Inconsistent progress definitions
- The team has different standards for done. How do we align them?Inconsistent completion expectations