- Post History
- Subscribe to RSS Feed
- Mark as New
- Mark as Read
- Bookmark
- Subscribe
- Printer Friendly Page
- Report Inappropriate Content
6 hours ago
Overview
This article outlines all the topics detected by the Project Insights engine, focusing on Task Management and Milestones. For each topic, it explains what is monitored, when an insight is triggered, the default thresholds, and the value it provides to your project team.
How to Read This Guide
Each insight topic includes:
-
What it does — A plain-language description of what the insight monitors
-
When it fires — The specific conditions that trigger the insight
-
Default configuration — Out-of-the-box thresholds and parameters
-
Data scope — The date range or project scope used
-
Severity — How urgency is communicated (where applicable)
-
Value delivered — What problem it solves for your team
Summary of Topics Covered
| Insight Name | Category | What It Detects |
|---|---|---|
| Task Delay Issues | Task Management | Alerts when project tasks have slipped past their planned completion date |
| Task Overdue Issues | Task Management | Surfaces high-priority tasks that have missed their deadline |
| Tasks With No Progress | Task Management | Identifies tasks stuck at 0% completion as their deadline approaches |
| Tasks With No Clear Ownership | Task Management | Flags tasks that have no assigned owner — active or upcoming |
| Internal Dependency Issues | Task Management | Highlights tasks at risk because their predecessors are behind schedule |
| Missed Milestone Deadlines | Milestones | Alerts when key milestones have passed their planned date without being achieved |
| Milestones With No Clear Ownership | Milestones | Identifies milestones that have no responsible owner assigned |
| Milestone Dependency Delays | Milestones | Warns when predecessor tasks to a milestone are running late |
Task Management
Task insights monitor the day-to-day execution health of your project, surfacing delays, stalled work, accountability gaps, and dependency risks across all project tasks.
1. Task Delay Issues
Alerts when project tasks have slipped past their planned completion date
What it does
Monitors all project tasks and identifies those that have passed their planned completion date without being marked complete. Tasks are ranked by how overdue they are, ensuring the most critical delays are always visible first.
When it fires
- A task's planned end date (end_date field) has passed the run date AND the task's actual end date (work_end field) is not populated — the work_end field is the sole completion signal; percent_complete and state are not evaluated here
- Days overdue is calculated as the difference between the run date and the planned end date; 1+ days triggers minor, 3+ days moderate, 7+ days critical
- Tasks missing either start_date or end_date are skipped entirely
- Completed tasks are excluded — a task is considered complete only when work_end is populated, regardless of state or percent_complete
Default Configuration
Minor: 1+ days overdue | Moderate: 3+ days overdue | Critical: 7+ days overdue
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Note: The cadence window is platform-level behaviour controlled by the project's cadence setting — it is not configurable per topic. For resource topics, the analyser applies an additional timeRange filter on top of this window (see Default Configuration above).
Severity
Critical (7+ days overdue) / Moderate (3–6 days) / Minor (1–2 days)
Value delivered
Prevents delays from going unnoticed. Gives project managers a prioritised list to act on immediately, with the most impactful delays surfaced first.
2. Task Overdue Issues
Surfaces high-priority tasks that have missed their deadline
What it does
Specifically tracks high-priority tasks (Priority 1 and 2) that are past their planned end date and still open. This insight focuses exclusively on the tasks that carry the most weight for project success.
When it fires
- A task's priority field value is '1' (Critical) or '2' (High) — priority values '3', '4', and '5' are not evaluated by this insight
- The planned end date (end_date) has passed the run date AND the actual end date (work_end) is not populated — completion is determined by work_end, not by state or percent_complete
- Days overdue is calculated and the task is sorted by most overdue first — no minimum day threshold applies; any positive overdue count qualifies
Default Configuration
Monitored task states: Open, Work in Progress | Priority filter: Priority 1 (Critical) and Priority 2 (High) only
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
All qualifying tasks treated as high priority — no sub-tiers
Value delivered
Ensures critical and high-priority work gets immediate management attention before it derails project delivery.
3. Tasks With No Progress
Identifies tasks stuck at 0% completion as their deadline approaches
What it does
Finds tasks that have not recorded any progress and are approaching or past their planned end date. The closer the deadline, the higher the urgency. Tasks with significant time remaining are not flagged — only those where inaction is becoming a risk.
When it fires
- A task's percent_complete field is exactly 0 — this is the progress check, not work_end or state; a task in WIP state with 0% progress will still be flagged
- The task must have an end_date field populated — tasks without an end date are skipped
- Days remaining is calculated as end_date minus run date; tasks with more than 14 days remaining are skipped entirely as not yet at risk
- Only periods with allocation > 0 are considered — tasks not yet started with no hours are excluded to avoid noise
Default Configuration
Overdue: deadline already passed | Critical: up to 3 days remaining | Moderate: up to 7 days | Minor: up to 14 days | Tasks beyond 14 days are not yet flagged
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
Overdue (already past deadline) / Critical (1–3 days remaining) / Moderate (4–7 days) / Minor (8–14 days)
Value delivered
Catches stalled work before it becomes a missed deadline. Gives managers time to investigate blockers and intervene while there is still time to recover.
4. Tasks With No Clear Ownership
Flags tasks that have no assigned owner — active or upcoming
What it does
Reviews all tasks in the project and identifies those where no individual or group has been assigned responsibility. A task is considered unowned only if it has no assignment across any ownership field — assigned user, resource assignee, assignment group, or additional assignees.
When it fires
- Five distinct ownership fields are checked on every task: assigned_to (individual user), resource_assignee (resource assignee), group_resource_assignee (group assignment), additional_assignee_list (co-owners), and assignment_group (team queue) — a task must be empty across all five to be considered unowned
- A task is classified as active if its planned start date has already passed or if it has no dates — active unowned tasks are surfaced first as higher priority
- A task is classified as upcoming if its planned start date is in the future — these are included so ownership can be established before work begins
- Active tasks are sorted by planned end date ascending (most urgent first); upcoming tasks are sorted by planned start date ascending
Default Configuration
No numeric thresholds — ownership is a binary check across all assignment fields. All tasks with no owner are flagged.
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
No severity tiers — active tasks listed before upcoming tasks by urgency
Value delivered
Prevents accountability gaps. Unowned tasks are the most common reason work falls through the cracks on projects.
5. Internal (Task) Dependency Issues
Highlights tasks at risk because their predecessors are behind schedule
What it does
Identifies tasks that depend on other tasks within the same project where the predecessor task is overdue. This enables project managers to see downstream risk before a delay in one area cascades into a larger schedule problem.
When it fires
- A task's has_conflict field is set to true — this is a platform-computed field on pm_project_task that ServiceNow sets automatically when it detects scheduling conflicts due to predecessor dependencies
- For each conflicted task, the dependency table (planned_task_rel_planned_task) is queried to find all predecessor tasks where external=false — only internal project dependencies are considered, not cross-project links. We honor external too but, in the cases, only where Project WS sets has_conflict=true for external links
- For each predecessor found, the engine checks whether its end_date has passed the run date and its work_end is not populated — if so, it is considered overdue
- Severity is determined by the most-delayed predecessor: 1+ days overdue = minor, 3+ days = moderate, 7+ days = critical — the same scale as task delay
Default Configuration
Minor: predecessor 1+ days overdue | Moderate: 3+ days | Critical: 7+ days | Severity is driven by the most-delayed predecessor
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
Critical (predecessor 7+ days overdue) / Moderate (3–6 days) / Minor (1–2 days)
Value delivered
Turns reactive fire-fighting into proactive risk management by showing the domino effect of delays before they fully materialise.
Milestones
Milestone insights focus on the key commitment points in your project, alerting you when milestones are missed, at risk from upstream delays, or lack a clear owner.
6. Missed Milestone Deadlines
Alerts when key milestones have passed their planned date without being achieved
What it does
Monitors all project milestones and flags any that have gone past their planned completion date without being marked complete. Milestones represent critical commitment points in a project, so missed deadlines are surfaced immediately.
When it fires
- A milestone's planned date (start_date field — milestones use start_date as their target date) has passed the run date AND the actual end date (work_end) is not populated
- Completed milestones are identified by a populated work_end value and are excluded regardless of their planned date
- Severity is determined by days elapsed since the planned date: 1+ days minor, 3+ days moderate, 7+ days critical
- Milestones missing a start_date are skipped
Default Configuration
Minor: 1+ days overdue | Moderate: 3+ days overdue | Critical: 7+ days overdue
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
Critical (7+ days) / Moderate (3–6 days) / Minor (1–2 days)
Value delivered
Milestone misses often signal broader project health issues. Early visibility enables escalation before commitments to stakeholders are missed.
7. Milestones With No Clear Ownership
Identifies milestones that have no responsible owner assigned
What it does
Checks all milestones in the project for missing ownership. A milestone without an owner has no one accountable for its delivery, creating risk that it will be overlooked as its date approaches.
When it fires
- The same five ownership fields checked for task ownership are applied here: assigned_to, resource_assignee, group_resource_assignee, additional_assignee_list, and assignment_group — a milestone must be empty across all five to be flagged
- A milestone is classified as active if its planned start date has passed or is missing — these are surfaced first
- A milestone is classified as upcoming if its planned start date is in the future — included so ownership can be assigned before the date arrives
- Active milestones are sorted oldest-first (most overdue first); upcoming milestones are sorted by planned date ascending (soonest first)
Default Configuration
Monitored states: Open, Work in Progress | Ownership check is binary — any milestone without an owner across all assignment fields is flagged
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
No severity tiers — active milestones listed before upcoming ones
Value delivered
Ensures every milestone has a clear accountable owner, reducing the risk of missed commitments through unclear responsibility.
8. Milestone Dependency Delays
Warns when predecessor tasks to a milestone are running late
What it does
For each upcoming milestone, checks whether the tasks that must complete before it can be achieved are on track. If any predecessor tasks are overdue, the milestone is flagged as at risk — even before the milestone date itself has arrived.
When it fires
- For each milestone in the project, the dependency table (planned_task_rel_planned_task) is queried to find all predecessor tasks — those where the milestone is the child/successor record
- Each predecessor task is checked: if its end_date has passed the run date AND its work_end is not populated, it is considered overdue
- Severity is driven by the most-delayed predecessor — the maximum days overdue across all overdue predecessors for that milestone determines the severity tier
- Already-completed milestones (those with a populated work_end) are excluded from the analysis
Default Configuration
Minor: predecessor 1+ days overdue | Moderate: 3+ days | Critical: 7+ days | Severity is driven by the most-delayed predecessor task
Data Scope
Cadence-bounded window — records are pre-filtered at the database level before analysis. Only records whose date range overlaps the window are loaded.
| Cadence | Window | Boundary Start | Boundary End |
|---|---|---|---|
| Weekly | Today ± 7 days | Start of current week (Mon) | End of next week (Sun) |
| Bi-weekly | Today ± 14 days | Start of week, 2 weeks back | End of week, 2 weeks ahead |
| Monthly | Today ± 31 days | 1st of previous month | Last day of next month |
Severity
Critical (max predecessor delay 7+ days) / Moderate (3–6 days) / Minor (1–2 days)
Value delivered
Provides advance warning of milestone risk — enabling recovery action before the milestone date is missed, not after.
Final Note
These insights help shift project management from reactive tracking to proactive risk management, enabling faster decisions and better project outcomes.
Read More
- Article 1: What is Now Assist for SPM Project Insights and How It Works
- Article 2: Configuring Project Insights and Understanding Severity Levels
- Article 4: What Project Insights Detects — RIDAC, Financials & Schedule (coming soon)
