Read Dashboard metrics, labels, and thresholds
Dashboard widgets turn app data into review signals. A widget may show a score, count, percentage, list, distribution, trend, progress bar, status label, or details panel.
Use widget signals to:
- Decide what to inspect first.
- Understand risk, overdue work, blocked work, stale work, and planning gaps.
- Compare current results with the previous period when available.
- Open source work before making decisions.
Status labels
Most dashboard widgets use these labels:
| Label | Meaning |
|---|---|
| On Track | The signal is healthy for the selected scope and period. |
| Watch | The signal has early warning signs. Review it before it becomes a risk. |
| Risk | The signal needs active review. |
| Critical | The signal needs urgent review. |
| No Data | The widget cannot calculate a useful result from the current source data. |
| N/A | The widget result is not available for the current state. |
Standard threshold rules
These are the main threshold patterns used across dashboard widgets.
Lower-is-better risk rates
Widgets that measure risk rates, overdue rates, affected-work rates, or risky-owner rates generally use:
| Rate | Label |
|---|---|
| 0% to 9% | On Track |
| 10% to 24% | Watch |
| 25% to 39% | Risk |
| 40% or higher | Critical |
Examples include At-Risk Work, Overdue Exposure, Risk Drivers, Risk by List, overdue hotspots, aging work, and many goal-risk signals.
Health-style scores
Widgets that calculate a health or quality score generally use:
| Score | Label |
|---|---|
| 85 to 100 | On Track |
| 70 to 84 | Watch |
| 55 to 69 | Risk |
| Below 55 | Critical |
Examples include Work Health Score and Planning Quality.
Personal load rates
Personal queue widgets can use a stricter personal load pattern:
| Personal load rate | Label |
|---|---|
| No open work | No Data or neutral state |
| 0% to 19% | On Track |
| 20% to 34% | Watch |
| 35% to 49% | Risk |
| 50% or higher | Critical |
Completion flow
Completion Flow compares completed work with created work in the selected period.
| Completion / creation ratio | Label |
|---|---|
| No created or completed work | No Data or neutral state |
| 90% or higher | On Track |
| 60% to 89% | Watch |
| Below 60% | Risk |
Activity and collaboration density
Activity-style widgets can use positive thresholds where higher is better. For example, a high activity rate or higher collaboration density is healthier than a low one. Read the widget info tooltip for the exact calculation before comparing activity widgets.
How date range affects widgets
The dashboard date range can affect widgets in two ways:
| Widget behavior | Meaning |
|---|---|
| Event in range | Counts created, completed, due, updated, comment, chat, CRM, reminder, or time-log events inside the selected period. |
| Snapshot as of range | Reviews open work as of the selected range end. |
If a widget changes when you move from This Month to Last Month, the widget is following the selected review period.
How Subtasks affects widgets
The dashboard Subtasks toggle controls whether subtasks are included in dashboard results for the current review.
If a dashboard count differs from a List count, check Subtasks on both surfaces before assuming the widget is wrong.
Common risk drivers
Risk widgets commonly count these drivers:
| Driver | What it means |
|---|---|
| Overdue | Open work has passed its due date. |
| Blocked | Open work is blocked by status or dependency indicators. |
| Stale | Open work has not been updated within the stale-work window. |
| Missing owner | Open work does not have a clear owner. |
| Missing due date | Open work has no due date. |
| High priority | Open high-priority work may need closer attention. |
How to read key widgets
Work Health Score
Read it as an overall health indicator.
- Check the score and label.
- Review supporting indicators such as overdue, stale, no due date, and goal-risk percentages.
- Open source work when a supporting indicator is high.
- Treat the score as a pointer to investigation, not a final explanation.
At-Risk Work
Read it as “how much open work has risk drivers.”
- Compare at-risk count with open count.
- Check the status label.
- Review driver counts such as overdue, blocked, stale, missing owner, missing due date, and high priority.
- Open details or source work to resolve the underlying issue.
Overdue Exposure
Read it as “how much active work is already late.”
- Compare overdue count with open count.
- Check the overdue percentage.
- Confirm the due dates in source tasks.
- Update due dates or statuses only after confirming the work state.
Risk Drivers
Read it as “why work is at risk.”
- Find the top driver.
- Open source work for that driver when available.
- Resolve the driver directly, such as adding an owner, adding a due date, unblocking work, or updating stale work.
Needs Attention
Read it as a triage queue.
- Start with the highest-score items.
- Review why each item is flagged.
- Update source tasks rather than editing the widget.
- Recheck the widget after sync.
Planning Quality
Read it as a planning hygiene score.
The score is lowered by missing due dates, missing owners, missing priority, stale work, and blocked work.
- Check the score label.
- Fix missing dates and ownership first.
- Review stale and blocked work next.
- Recheck after source work updates.
Widget details and source work
Some widgets open a details panel or source work when selected. Details can show grouped rows, affected tasks, owners, deadlines, or report rows.
If details do not open:
- The widget may not support details.
- The source work may be restricted.
- The result may be sample or preview data.
- The current date range may have no matching details.
No-data states
| No-data message type | Common cause | What to check |
|---|---|---|
| No matching work found | Filters or date range exclude all results. | Expand date range or edit filters. |
| No open overdue work | There is no overdue open work in scope. | Confirm due dates and status. |
| No risk drivers found | No open work currently matches risk drivers. | Check if source tasks are complete or excluded. |
| No activity in this period | No comments, chat messages, CRM activity, time logs, or movement in range. | Change date range. |
| No goals available | No active goals are available in the selected scope. | Create or link goals if goal tracking is used. |
Troubleshooting
A label seems wrong
- Symptom: A widget says On Track, Watch, Risk, or Critical unexpectedly.
- Cause: The widget may use specific thresholds, date range, subtasks setting, source scope, filters, or source data that differ from your manual review.
- Resolution:
- Open widget info.
- Check the date range.
- Check Subtasks.
- Compare widget filters with source filters.
- Open the source work.
Counts changed after switching date range
- Symptom: Widget numbers change after selecting a different period.
- Cause: The widget uses the selected review period.
- Resolution:
- Use the same date range when comparing widgets.
- For ongoing work, choose a current period.
- For retrospectives, choose the historical period intentionally.
Two dashboards show different numbers
- Symptom: Similar widgets on two dashboards do not match.
- Cause: The dashboards may have different filters, widget settings, date ranges, subtasks settings, or source scope.
- Resolution:
- Compare dashboard date range and Subtasks.
- Compare widget filters and settings.
- Confirm both dashboards are in the same Space.
- Confirm both widgets are the same widget type.
FAQ
Are status labels exact performance ratings?
No. They are review signals based on app data and thresholds. Open source work before making important decisions.
Why can the same task appear in multiple risk drivers?
One task can be overdue, blocked, stale, missing an owner, and high priority at the same time. Driver widgets count each driver so you can see what to fix.
Why does a widget show No Data instead of On Track?
No Data means the widget does not have enough matching source data to calculate a meaningful signal. On Track means it found data and evaluated it as healthy.