Overview
The PM Command Center brings project and task signals together in one place so Project Managers can quickly identify what needs attention.
For Project Managers, delivery leaders, and managers coaching PMs, it helps answer one practical question:
What needs my attention right now, and where should I focus first?
Use the report to review project workload, identify schedule risk, find task-level blockers or ownership gaps, and drill into the specific projects or tasks behind those signals.
What you can learn from this report
Use the PM Command Center to understand:
Which projects may need attention
Where project schedules are at risk
Which projects are late or forecasted late
Where task work is overdue or blocked
Which tasks may be missing ownership
What work is approaching its due date
Whether attention is concentrated in a few projects or spread across the portfolio
Which individual tasks or projects are contributing to a signal
Unlike a report focused only on projects or only on tasks, PM Command Center brings both levels together.
That makes it useful for the daily question:
Where should I start?
Filter the report
PM Command Center uses the standard GUIDEreports filters.
These include:
Customer
Project and task custom fields
Project status
Task status
Project tags
Task tags
Task responsibility
Task start and due dates
Project start and end dates
Combine filters when you want to turn the Command Center into a more focused review.
For example, you might narrow the report to:
A particular customer
Projects with a specific status
Work associated with a certain implementation type
Tasks due within a particular period
Customer-owned or internally owned tasks
For complete filtering behavior, see Use GUIDEreports: Filters, drilldowns, sorting, and navigation.
Use the Command Center as an attention queue
The PM Command Center is most useful when you do not treat every signal as equally urgent.
A practical way to read it is:
Review layer | Question to ask |
Portfolio | How much work am I responsible for? |
Project risk | Which projects may miss expectations? |
Task risk | Which pieces of work are blocked, overdue, or approaching their due dates? |
Ownership | Does the work that needs attention have someone responsible for it? |
Investigation | Which project or task should I open next? |
This creates a natural flow from a high-level signal to an actionable record.
Review project workload and health
Start with the project-focused areas of the report to understand the portfolio before jumping into individual tasks.
Project-level signals can help you investigate:
Project status
Current project health
Due dates
Forecasted completion
Late projects
Projects forecasted late
Projects forecasted ahead
RAG status
Portfolio concentration
Use these signals to answer:
Which projects deserve a closer look?
Separate current problems from future risk
One of the most useful distinctions in project reporting is the difference between:
Already late
and:
Forecasted late
A project that is already late represents a current delivery issue.
A project forecasted late represents a potential future issue.
That gives a PM two different action queues:
Signal | PM question |
Late | What needs recovery now? |
Forecasted Late | What can I address before this becomes late? |
Forecasted Ahead | Is the current plan still realistic, or is delivery progressing faster than expected? |
Forecasting is most useful before the due date is missed.
Use the project drilldown to compare fields such as Due Date, Forecasted End Date, and Forecasted Variance Days when investigating schedule risk.
Review task work that needs attention
Once you understand the project picture, move into the task-focused signals.
These help answer questions such as:
What work is overdue?
What work is currently Stuck?
What is due soon?
Which work has no assignee?
Is the problem internal, customer-owned, or partner-owned?
Is task risk concentrated in a particular project?
A project can appear healthy at a high level while still containing individual tasks that deserve attention.
Likewise, one overdue task does not automatically mean the entire project is at risk.
The Command Center helps you move between those two levels.
Prioritize blocked work
Tasks marked Stuck have been explicitly identified as blocked.
Use Stuck work as a strong investigation signal.
When you find it, review:
Project Name
Responsibility
Assignee Names
End Date
Status Label
Status Explanation, when available
Days Open
The Stuck status tells you that work is blocked.
It does not tell you what caused the problem.
Review the underlying task and project context before deciding what needs to happen next.
Review overdue work
Overdue work tells you that the task's planned timing has already been missed.
When reviewing overdue tasks, ask:
Is the work assigned?
Who owns it?
Is it currently Stuck?
Is the responsibility Internal, Customer, or Partner?
Is this one isolated task or part of a larger project pattern?
This prevents every overdue task from being treated as the same problem.
For example:
An unassigned overdue task may need an ownership decision.
A customer-owned overdue task may require customer follow-up.
An internal Stuck overdue task may require escalation or dependency resolution.
Check ownership before escalating
Ownership is one of the most useful ways to prioritize task follow-up.
The task drilldown includes:
Is Assigned
Assignee Names
Responsibility
Use these together.
Situation | What it may tell you to investigate |
Overdue + unassigned | Ownership may need to be established. |
Stuck + assigned | The owner may need help resolving a blocker. |
Customer responsibility + overdue | Customer follow-up may be needed. |
Internal responsibility + overdue | Internal delivery follow-up may be needed. |
These are investigation starting points, not automatic conclusions about why work is delayed.
Understand the two drilldown types
PM Command Center is different from many Standard reports because different widgets can lead to different kinds of records.
Some widgets are task-focused.
Others are project-focused.
Drilldown type | Use it to investigate |
Task drilldown | Individual tasks, responsibility, ownership, dates, completion, overdue status, Days Open, and current task status. |
Project drilldown | Individual projects, customers, planned and forecasted timing, project status, RAG, phases, milestones, and project-level context. |
The type of signal you select determines which drilldown is most useful.
For complete field definitions, see the GUIDEreports drilldown field reference.
Use the task drilldown
Task-focused areas of PM Command Center can open task records containing fields such as:
Task Name
Project Name
Responsibility
Priority
Visibility
Sign Off Required
CSAT Enabled
Start Date
End Date
Assignment information
Completion and overdue indicators
Days Open
Subtask indicator
Status fields
Brand information
Every drilldown column header can be sorted A → Z or Z → A.
Useful task investigations
If you're trying to find... | Review... |
Missing ownership | Is Assigned, Assignee Names |
Past-due work | End Date, Is Overdue |
Blocked work | Status Label, Status Explanation |
Customer dependencies | Responsibility |
Long-running work | Days Open |
Recently completed tasks | Completed At |
Recently changed task status | Status Updated At |
Use the project drilldown
Project-focused widgets can open project records containing information such as:
Project Name
Customer Name
Start Date
Due Date
Done Date
Forecasted End Date
Cash Value
Billing Rate
Forecast indicators
Duration fields
Forecasted Variance Days
Phase Names
Milestone Names
Status
RAG information
Useful project investigations
If you're trying to understand... | Review... |
Schedule risk | Due Date, Forecasted End Date, Forecasted Variance Days |
Current health | Status Label, RAG information |
Forecast direction | Is Forecasted Late, Is Forecasted Ahead |
Project structure | Phase Names, Milestone Names |
Financial context | Cash Value, Billing Rate |
Recent changes | Updated At, Status Updated At |
Move from a signal to an action
The Command Center works best when you follow a consistent investigation flow.
1. Find the strongest signal
Start with the project or task area that most clearly needs attention.
For example:
Forecasted-late projects
Late projects
Stuck tasks
Overdue tasks
Unassigned work
2. Determine whether the signal is isolated or concentrated
Look for whether the issue appears across many projects or is concentrated in one or two implementations.
3. Open the drilldown
Use the task or project drilldown to identify the underlying records.
4. Review ownership and timing
For tasks, focus on responsibility, assignees, dates, and status.
For projects, focus on planned versus forecasted timing and current health.
5. Open the underlying work
The report tells you where to investigate.
Review the actual project or task before deciding why the issue exists and what action is appropriate.
Example: Run a Project Manager morning review
The following is an illustrative Professional Services scenario.
A Project Manager starts the day with several active onboarding projects.
Instead of opening every project individually, they use PM Command Center.
1. Look for project risk
They first review project-level signals.
Two projects are showing future schedule risk.
One project is already late.
2. Check task blockers
They review the task-focused areas.
One of the forecasted-late projects contains several Stuck tasks.
3. Review ownership
In the task drilldown, they find:
One internal task that is assigned and Stuck
One customer task that is overdue
One task with no current assignee
Those are three different follow-up situations.
4. Compare planned and forecasted project timing
They open the project drilldown and compare the project's:
Due Date
Forecasted End Date
Forecasted Variance Days
Status
RAG information
5. Decide what to address first
Instead of spending the morning reviewing every project equally, the PM now has a focused action list:
Resolve the internal blocker
Follow up on the overdue customer action
Assign the unowned task
Review the project forecast after those issues are addressed
The Command Center has done its job:
It narrowed a large portfolio into a manageable set of conversations and actions.
Use PM Command Center for coaching and portfolio reviews
The report can also support conversations between Project Managers and delivery leaders.
Instead of reviewing activity broadly, a manager can use the report to discuss:
Projects showing schedule risk
Patterns of blocked or overdue work
Ownership gaps
Upcoming commitments
Where a PM may need support
These conversations should use the report as evidence for investigation, not as a standalone performance score.
A count of overdue tasks or forecasted-late projects does not by itself explain:
Project complexity
Customer readiness
Dependencies
Scope changes
Resource constraints
Why the current condition exists
Review the underlying work before drawing conclusions.
Best practices
These are suggested reporting practices rather than product requirements.
Start with exceptions
PM Command Center is most valuable when you use it to identify what needs attention rather than reviewing every healthy project in equal detail.
Start with risk, blockers, overdue work, and ownership gaps.
Separate project risk from task risk
A project-level signal tells you where the portfolio may need attention.
A task-level signal helps explain what individual work may be contributing.
Use both before deciding what needs to change.
Address forecasted risk before current status changes
A project forecasted late gives you an opportunity to investigate before the project becomes Late.
Use forecasting as an early-warning signal.
Check ownership early
Before escalating an overdue or Stuck task, verify whether it has an assignee and which responsibility group owns it.
That often determines the next conversation.
Look for concentration
Five overdue tasks across five different projects can mean something very different from five overdue tasks inside one project.
Use project breakdowns and drilldowns to understand concentration.
Don't use the dashboard as a PM scorecard by itself
PM Command Center can support coaching and accountability conversations.
It should not replace project context.
Use the records behind the metrics before deciding what a number says about an individual PM's performance.
Build a repeatable review rhythm
Use the same sequence each time:
Project risk → task blockers → overdue work → ownership → drilldown → action
A consistent review makes it easier to notice meaningful changes without reviewing the entire portfolio manually.
Frequently asked questions
What is PM Command Center designed for?
PM Command Center brings project workload, schedule risk, and tasks needing attention into one reporting view.
It helps Project Managers and delivery leaders decide where to focus.
How is PM Command Center different from Projects Overview?
Projects Overview is primarily a portfolio-level project report.
PM Command Center combines project-level and task-level signals so you can move from project health into the specific work that may need attention.
How is it different from Task Management?
Task Management provides deeper task-focused reporting across the portfolio.
PM Command Center uses task signals alongside project health and schedule information to support a PM's broader operating review.
Why do different PM Command Center widgets show different drilldown columns?
The report contains both task-focused and project-focused signals.
Task widgets open task-oriented records.
Project widgets open project-oriented records.
See the GUIDEreports drilldown field reference for both schemas.
Can I sort the drilldown?
Yes.
Every drilldown column header can be sorted A → Z or Z → A.
Does every widget have a drilldown?
No.
Hover over the widget.
If your cursor changes to a pointer hand, select it to open the available underlying records.
Does a forecasted-late project mean the project is already Late?
No.
Forecasted late is a forward-looking schedule signal.
A project can be forecasted late before its current status becomes Late.
Does a Stuck task explain why the project is at risk?
Not by itself.
Stuck tells you the task has been identified as blocked.
Review the task, status explanation when available, ownership, dates, dependencies, and project context before deciding what is causing the risk.
Should I treat every overdue task as equally urgent?
No.
Review factors such as:
Responsibility
Assignee
Project
Current status
How long the task has been open
Whether other work depends on it
before deciding priority.
Can managers use this report during PM one-on-ones?
Yes.
The combined project and task signals can provide useful starting points for delivery and coaching conversations.
Use the underlying records and project context rather than treating dashboard totals as standalone performance measures.
Can I filter the report?
Yes.
PM Command Center uses the standard GUIDEreports filters.
What if I need a different PM-focused dashboard?
Check the GUIDEreports widget library for the available project and task widgets.
If the Standard report does not answer your team's question, you can build a custom GUIDEreport.
Continue learning about GUIDEreports
GUIDEreports overview — Choose the right Standard report.
Projects Overview — Review project health, timing, forecasting, and portfolio risk.
Standard report: Customer Engagement — Review customer-owned work and engagement.
Standard report: Historical Trends — Understand how delivery changes over time.
Use GUIDEreports: Filters, drilldowns, sorting, and navigation — Learn shared report mechanics.
GUIDEreports widget library — Understand individual widgets and their built-in scope.
GUIDEreports drilldown field reference — Understand task and project drilldown fields.
Build a custom GUIDEreport — Create a different reporting view when needed.