Skip to content

Dashboard and filters

WorkOrder V3 is not only for opening and closing individual records. It also gives supervisors and managers a way to see backlog, approval pressure, assignee throughput, and issue patterns across a plant or portfolio.

Use this workflow when you need to move from a single work order to an operational view of the whole queue. Filters help teams narrow the list to the right slice of work, while dashboard views help leadership understand status, aging, and exposure.

Placeholder for the WorkOrder dashboard and filters view

  • a supervisor wants to review open backlog and overdue work
  • a manager wants to compare workload or risk across plants
  • an operator needs to narrow the list by plant, area, category, priority, requester, or assignee
  • the team wants to monitor approval queues and rework trends
  1. Start from the work order list or dashboard view.
  2. Filter by the dimensions that matter for the decision you are making, such as plant, area, category, priority, requester, assignee, status, or date range.
  3. Use section-based views such as pending approval, action needed, or history when reviewing workflow-specific queues.
  4. Review KPI and trend views to understand backlog, throughput, review volume, and plant-level risk.
  5. Save or repeat the same filter logic during team reviews so discussions stay consistent across shifts and meetings.
  • teams find the right work faster instead of scanning the whole queue
  • supervisors can focus on the items that require approval or intervention
  • managers gain clearer visibility into open backlog, rework, and risk concentration
  • portfolio reviews become easier because work order data is organized for operations, not just storage
  • Dashboard access is typically aimed at supervisor or admin users because it supports queue governance and performance review.
  • Filter logic is most useful when teams apply it consistently during daily and weekly reviews.
  • my-tasks may appear in some environments as a beta assignee-focused convenience view, but it should not replace the main shared workflow and dashboard model.
  • History views are useful for understanding what has already been reviewed, not just what is open right now.