PQM Training
Knowledge Base
PQM Training Center
Practical onboarding guide for Production Queue Manager: learn the system philosophy, core workflow, roles, screens and go-live process.
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
The philosophy of PQM
PQM is not a simple checklist and not only a WordPress plugin screen. It is a production operating layer: orders become production tasks, tasks move through real departments, communication stays attached to the work, and reports show whether production is under control.
For a beginner, the most important idea is this: the task is the source of truth. If a customer calls, a manager should open the task. If an employee needs instructions, the employee should open the task. If management wants to know whether production is profitable, reports should read data from tasks and related costs.
Tasks = source of truthDepartments = responsibilityStatuses = progressReports = control
Recommended learning path for a new user
Start with the big picture, then learn the screens in the same order a company normally uses them during implementation. Do not begin with reports or modules. Reports only become useful after tasks, statuses and departments are used consistently.
1. SetupCore and roles
2. Create taskAdd Task / orders
3. Run workflowDepartments/statuses
4. MeasureReports/KPI
Read the Core Configuration lesson to understand statuses, departments and safe defaults.
Create one realistic test task in the Add Task screen. Use real wording, real departments and a real deadline.
Open the same task as a manager, employee and customer/client user. Confirm that each role sees only what it should see.
Send one test message and one test email notification, then check whether the message is attached to the correct task.
Open reports only after several tasks have moved through statuses. Empty reports at the beginning do not mean the system is broken.
Core terminology explained simply
| Term | Plain-language meaning | Example in a printing / production company |
|---|---|---|
| Task | A production job that needs to be done and tracked. | Print 1,000 business cards, prepare a banner, pack a customer order. |
| Status | The current state of a task. | New, in progress, waiting, completed, cancelled, complaint. |
| Department | A production stage or team responsible for part of the work. | Graphic design, digital print, finishing, packaging, shipping. |
| Deadline | The expected completion or delivery date. | The customer needs the order by Friday at 12:00. |
| Employee Portal | A frontend work area for people doing production work. | A finishing employee sees only finishing tasks and updates their own stage. |
| Client Panel | A frontend area where customers can see updates and communicate. | A customer checks the status without entering WordPress admin. |
| Reports / KPI | Management information generated from real production data. | How many tasks were completed this month, which tasks are late, which jobs lost money. |
Roles in a healthy PQM installation
AdministratorOwns the technical configuration. This person should manage plugin settings, modules, licenses, updates and health checks. A normal production worker should not use this role.
Manager / SupervisorOwns daily control. This person creates tasks, reviews open production, checks deadlines, reads reports and decides what should be prioritized.
Worker / EmployeeOwns the assigned stage. This person should see clear instructions, update their stage and add notes without having access to dangerous admin settings.
How to use this knowledge base
Each lesson is written for a person who does not know PQM yet. It explains what the screen is for, where to click, what each area means, what a normal workflow looks like and what to check when something appears empty.
For your public site, paste every file from wordpress-snippets into a WordPress Custom HTML block. Keep the entire snippet together, including the <style> block. Do not convert it into normal Gutenberg blocks.
Training lessons
Production DashboardDaily command center, open work, cards, shortcuts and operational routine.Core ConfigurationDepartments, statuses, roles, permissions and safe production defaults.Tasks and Add TaskCreating tasks, editing tasks, field meaning, filters and lifecycle.Departments and WorkflowReal workflow stages, bottlenecks and responsibility rules.Calendar and Standard GanttCalendar dates, timeline bars, planning pressure and clickable task views.Email Queue and CommunicationEmail queue, templates, triggers, customer messages and safe communication.Reports and KPIKPI, margins, loss tasks, exports and data quality rules.Modules / MarketplaceModule states, activation, license entitlements and expansion strategy.Setup WizardFirst-run guided setup and post-wizard verification.License and Demo ModeActivation, demo mode, expiration, domain and module entitlements.Help and TrainingDocumentation hub, support path, FAQ and what to send to support.Admin PanelNextCore controls, health checks, registry, capabilities and diagnostics.Client PanelCustomer-facing status, messages, files and privacy rules.Employee Worker PortalWorker portal, assigned tasks, stage updates and production notes.Shop Manager / SupervisorSupervisor routine, operational controls and safe role boundaries.Implementation ChecklistGo-live checks for technical, business, roles, emails and reports.