PQM Training Dashboard
PQM Training / Production Dashboard
Command Center
Production Dashboard
Daily control screen for managers: metrics, open tasks, urgent work, quick actions and production overview.
Production OSWordPress CoreRole-based workflowTraining Center
Training pages
Training HomeProduction DashboardCore ConfigurationTasks and Add TaskDepartments and WorkflowCalendar and Standard GanttEmail Queue and CommunicationReports and KPIModules / MarketplaceSetup WizardLicense and Demo ModeHelp and TrainingAdmin PanelClient PanelEmployee Worker PortalShop Manager / SupervisorImplementation Checklist
Purpose in plain language
The Production Dashboard is the first screen a manager should open in the morning. It answers the question: what is happening in production right now? It is not meant to replace the task list, reports or calendar. It is a command center that points the user to the right next action.
A beginner should treat the dashboard like the cockpit of a production floor. The cards summarize current workload, the latest tasks, urgent items, completion numbers and shortcuts. When something looks wrong, the user clicks deeper into Tasks, Reports, Calendar or Add Task.
Where to click
Log in to WordPress with a manager or administrator account.
In the left WordPress admin menu, open PQM or Production Queue.
Choose Dashboard. In some builds the dashboard is the first screen after opening the PQM menu.
Use the top metric cards first, then the quick-action buttons, then the recent/open task lists.
Screen map: what every area means
| Area | What it means | What the user should do |
|---|---|---|
| Total / active tasks card | Shows how much work exists in the system and how much is still open. | Click through to the task list when the number looks too high or does not match reality. |
| In progress / done / overdue cards | Shows production pressure and completion level. | Use these cards to decide whether the day starts with normal work or urgent cleanup. |
| Recent tasks | Shows new or recently changed tasks. | Open the newest task and verify that status, department, deadline and notes are correct. |
| Quick actions | Shortcuts to Add Task, Task List, Reports, Calendar, Settings or portals. | Use shortcuts instead of searching through the WordPress menu. |
| Charts / KPI preview | Visual summary of production activity, status mix or trend data. | Do not panic if charts are empty on a fresh installation. Charts need real task data and correct dates. |
| Module widgets | Optional cards from modules such as warehouse, CRM, documents or analytics. | Use them only if the module is installed and activated for the license/site. |
Daily manager workflow
Open Dashboard at the beginning of the day. Look at open, in-progress, overdue and completed numbers.
Click the task list or recent task card and review tasks created since the last production meeting.
Open tasks with missing department, missing deadline or unclear notes. Fix them before production starts.
Check whether any task is late or close to the deadline. Move it to the correct priority or assign it to the responsible person/department.
Open Calendar or Gantt when the dashboard suggests too many tasks in the same period.
At the end of the day, compare completed tasks against open tasks and check whether anything must be escalated tomorrow.
Beginner example
Example: a new shop manager opens PQM for the first time
The manager sees 12 open tasks, 4 in progress and 2 overdue. Instead of clicking randomly, the manager first clicks the overdue card or opens Tasks with a date/status filter. Then they open each overdue task, check which department is responsible, read the notes and decide whether to update the deadline, change priority or contact the customer.
Good practice
- Use the dashboard as a morning control screen, not as the only place where work is managed.
- Do not judge reports from the dashboard until tasks have correct statuses and deadlines.
- Every visible number should be traceable to a task list or report. If a number looks strange, click deeper before assuming a bug.
- Keep dashboard widgets clean. Too many widgets make beginners ignore the screen.
Common beginner mistakes
| Mistake | Why it causes problems | Better habit |
|---|---|---|
| Creating tasks without deadlines | Dashboard and calendar cannot show urgency correctly. | Always add a realistic date before production starts. |
| Leaving tasks in “new” forever | The dashboard shows work as not started even if someone is already working. | Move the task to the correct production status or department stage. |
| Using admin account for every worker | Reports, permissions and accountability become unclear. | Create role-based accounts or use frontend worker portals. |
| Ignoring empty states | A fresh installation may look broken even though it only lacks data. | Add demo/test tasks and complete a full workflow once. |
Screenshot reference
How to use screenshots
Click any screenshot to open it in a new tab. This is useful for zooming in while following the step-by-step instructions.
Production Dashboard
Main production dashboard reference. Use it to explain daily command center cards, shortcuts and operational overview.
KPI Dashboard
KPI dashboard reference. Use it to explain production indicators, charts and quick health checks.
Who should use this screen?
AdministratorConfigures PQM, licenses, modules, health checks, capabilities and technical maintenance. This role should be limited to trusted users.
Manager / Shop ManagerControls daily production, creates tasks, checks reports, follows deadlines and supervises employee work without changing technical settings.
Production EmployeeWorks mainly in the frontend Employee Portal and updates assigned production stages without using the WordPress admin area.
Troubleshooting for beginners
| Symptom | Simple explanation | What to check first |
|---|---|---|
| The page looks empty | The system may have no demo data yet, or the current user may not have access to the required role/capability. | Create one test task, assign a department, then refresh the screen. Also check the user role. |
| A button opens a login page or My Account | The visitor is not logged in or the page is using a frontend-safe route that requires authentication. | Log in with a test user that has the expected role. Check whether the shortcode/page is visible only to logged-in users. |
| Data exists but does not appear in a report/chart | Filters, date range, status rules or completion dates may exclude the task. | Clear filters, expand the date range and verify that the task has the status/date required by the report. |
| Something changed but the screen still shows old data | Browser cache, WordPress cache or AJAX response cache may show old information. | Refresh the page, clear cache for this page and test in an incognito window before debugging code. |
| The layout is broken on a small screen | Wide tables and timelines need horizontal space; this is normal if the content remains readable. | Use the mobile breakpoint, keep cards in one column and allow horizontal scroll only inside tables/timelines. |
Readiness checklist
A beginner can explain what this screen is for after reading the first two sections.
The correct role can open the screen and restricted roles cannot see unsafe actions.
There is at least one realistic test task visible in the screen.
Buttons and links go to the expected place.
The empty state explains what to do next instead of looking broken.
The page remains readable on tablet and mobile.
Related training pages
Training HomeTraining overview and recommended learning path.Core ConfigurationSystem settings, statuses, roles, capabilities and safe defaults.Tasks and Add TaskHow to create, read and update production tasks step by step.Departments and WorkflowHow production stages and responsibilities are modeled.Calendar and Standard GanttDate planning, deadlines and visual timeline overview.Email Queue and CommunicationCustomer messages, email queue and communication templates.Reports and KPIKPI, margins, bottlenecks, exports and production analysis.Modules / MarketplaceOptional modules, activation state and upgrade path.