This report provides a detailed breakdown of what tasks are starting soon or overdue for managed service providers.
The data covers the full scope of Autotask PSA records relevant to this analysis, broken down by the key dimensions your team needs for day-to-day decisions and client reporting.
Who should use this: Service desk managers, dispatch leads, and operations teams
How often: Daily for queue management, weekly for trend analysis, monthly for capacity planning
Overview of all open project tasks — overdue, in progress, and approaching start date — queried directly from Autotask PSA.
EVALUATE SUMMARIZECOLUMNS('BI_Autotask_Projects'[project_status_name], "ProjectCount", COUNTROWS('BI_Autotask_Projects'), "AvgDurationDays", AVERAGE('BI_Autotask_Projects'[duration_days]))
EVALUATE
SUMMARIZECOLUMNS(
'BI_Autotask_Tasks'[status_label],
CALCULATETABLE(
'BI_Autotask_Tasks',
'BI_Autotask_Tasks'[end_date] < TODAY(),
'BI_Autotask_Tasks'[status_label] <> "Complete"
),
"Overdue Count", COUNTROWS('BI_Autotask_Tasks')
)
ORDER BY [Overdue Count] DESC
| Project | Overdue Tasks | Share of Total | Priority |
|---|---|---|---|
| Project Happy | 132 | 30.4% | Critical |
| Project Bag | 51 | 11.8% | High |
| Project Anyone | 42 | 9.7% | High |
| Project Set | 40 | 9.2% | High |
| Project Professional | 21 | 4.8% | Medium |
| Project Feel | 11 | 2.5% | Medium |
| Project Him | 11 | 2.5% | Medium |
| Project Allow | 11 | 2.5% | Medium |
EVALUATE
TOPN(
10,
SUMMARIZECOLUMNS(
'BI_Autotask_Tasks'[project_name],
CALCULATETABLE(
'BI_Autotask_Tasks',
'BI_Autotask_Tasks'[end_date] < TODAY(),
'BI_Autotask_Tasks'[status_label] <> "Complete"
),
"Overdue Count", COUNTROWS('BI_Autotask_Tasks')
),
[Overdue Count], DESC
)
The "Starting Soon" measures rely on task start_date values within a rolling window relative to today's date. This demo dataset contains historical task records that predate March 2026, so no tasks fall in the upcoming 1–2 week window. In a live PSA environment connected to current project schedules, these cards would populate with real upcoming tasks.
-- Tasks starting today
EVALUATE
ROW(
"Starting Today", CALCULATE(
COUNTROWS('BI_Autotask_Tasks'),
'BI_Autotask_Tasks'[start_date] = TODAY()
),
"Starting This Week", CALCULATE(
COUNTROWS('BI_Autotask_Tasks'),
'BI_Autotask_Tasks'[start_date] >= TODAY(),
'BI_Autotask_Tasks'[start_date] <= TODAY() + 7
),
"Starting Next Week", CALCULATE(
COUNTROWS('BI_Autotask_Tasks'),
'BI_Autotask_Tasks'[start_date] > TODAY() + 7,
'BI_Autotask_Tasks'[start_date] <= TODAY() + 14
)
)
The headline number here is 434 overdue tasks — and the breakdown tells a clear story. Of those, 313 (72%) have a status of "New," meaning they were scheduled, had an end date assigned, and then were never actually started. This is scheduling debt, not work-in-flight that ran over.
The remaining 114 tasks are In Progress and past their deadline. That is a smaller but more operationally urgent group: engineers are actively working on these, but the original timeline has already slipped. Project Happy is the single biggest contributor at 132 overdue tasks, which warrants a focused review of whether its scope, resourcing, or timeline is realistic.
On the "starting soon" side, the demo dataset shows no upcoming tasks in the next two weeks. In a live environment, this view gives project managers a two-week runway to prepare resources, confirm client readiness, and surface any conflicts before tasks go active.
313 out of 434 overdue tasks have a "New" status. These were put on the schedule and given a deadline but work never began. This signals a systemic planning problem: tasks are being created and dated without a realistic plan to execute them. A triage session to close, reschedule, or reassign these tasks will clean up your backlog significantly.
With 132 overdue tasks, Project Happy is the single largest contributor to task backlog. This volume suggests either a scope creep issue, under-resourcing, or a project that has been de-prioritized but not formally closed or rescheduled. A project health review is overdue.
Service call tasks are typically time-sensitive and client-visible. Three are currently past their scheduled end date. These should be reviewed immediately to confirm whether work was completed but not marked done, or whether the client is waiting on delivery.
The tasks starting today/this week/next week measures are most valuable when used proactively — reviewed every Monday morning to identify what is coming up, who owns each task, and whether the client has been informed. Building this into a weekly standup removes last-minute surprises from your project delivery pipeline.
end_date is earlier than today's date and its status is not "Complete". This excludes tasks that were completed on or before their deadline, even if they finished late relative to original estimates.start_date falling within the next 1–14 days relative to March 2026. In your live PSA environment, these measures will return real upcoming task counts based on your current project schedules.primairy_resource_name column (note: this is the column name in the source data, including the typo). If a task has multiple resources, only the primary is used in this report. Additional resources can be found in the task assignments table.Connect Proxuma Power BI to your PSA, RMM, and M365 environment, use an MCP-compatible AI to ask questions, and generate custom reports - in minutes, not days.
See more reports Get started