Keep the inputs current
Set realistic project start/due dates, task deadlines and estimates; update task and stage status and log effort and expenses. Missing dates or no completed work can leave forecasts unavailable. A dash is not a promise that the project is on schedule.
Distinguish progress measures
Portfolio project progress counts completed live tasks, including subtasks, equally; when there are no tasks it falls back to completed stages. Overview’s Stage progress card specifically counts completed stages. Neither measure weights work by its estimated difficulty or effort.
Review health reasons
Health starts at 100 and loses points for high budget usage, forecast schedule delay, overdue or soon-due tasks, and a missed project deadline. Healthy is 80 or more, Watch is 60–79, At Risk is 35–59, and Critical is below 35. Review the stated reasons and open the relevant project, task, finance or Inbox context.
Treat forecasting as a trend
Completion forecasting extrapolates elapsed calendar days against completed-work percentage. Schedule variance compares that date with the project due date; positive days mean later than planned. It does not model holidays, resource capacity, dependency chains or changes in task size. Update your plan instead of treating the forecast as a guaranteed delivery date.
See it in the app
Fictional demo data. Click an image to open the larger screenshot. Labels and dates may differ from your version.
