PQM Training Implementation Checklist
PQM Training / Implementation Checklist
Go-live Plan
Implementation Checklist
Practical checklist for installing, configuring, testing and launching PQM safely.
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 Implementation Checklist is the practical go-live plan. It helps administrators and managers verify that PQM is ready before real production data depends on it. A system can look beautiful but still fail if roles, emails, statuses or reports are not tested.
For a beginner, this checklist answers: what must be checked before we tell employees and customers to use PQM?
Phase 1: technical installation
Plugin is installed and activated without PHP critical error.
WordPress version and PHP version are compatible with the plugin build.
PQM menu appears for administrator.
Dashboard, Add Task, Task List, Calendar, Reports and Settings pages open.
No caching plugin breaks admin AJAX or frontend portal pages.
Backup exists before production use.
Phase 2: core business setup
Define departments using real company workflow.
Define statuses and decide which status means completed, cancelled and complaint.
Create one manager account and one worker account for testing.
Configure basic email sender/templates if notifications will be used.
Configure WooCommerce integration only if online orders should create production tasks.
Create one realistic test task and move it through the full workflow.
Phase 3: role and portal testing
| Role | Must be able to do | Must not be able to do |
|---|---|---|
| Administrator | Open settings, admin panel, license, modules and health checks. | Nothing unsafe beyond normal admin responsibility; protect account with strong security. |
| Manager / shop manager | Create tasks, view operational dashboard, check reports, manage daily production. | Change license, install modules, run migrations unless intentionally allowed. |
| Worker | See assigned tasks, read instructions, update their stage, add production notes. | Open admin settings, see all customers, see financial margins. |
| Client/customer | See own tasks/messages/files intended for them. | See other customers, internal notes, costs, admin pages. |
Phase 4: workflow test
Create a task manually through Add Task.
If WooCommerce is used, create a test order and generate a task from it.
Assign department and deadline.
Open Employee Portal as worker and update the assigned stage.
Send one internal note and one customer-safe message.
Move task to completed status.
Check dashboard, calendar, Gantt and reports after completion.
Cancel one test task and confirm it does not distort normal production reports.
Phase 5: email and communication test
Customer email address is stored correctly.
Task-created notification works if enabled.
Task-completed notification works if enabled.
Email queue shows sent/failed state clearly.
Failed email has readable explanation or log path.
Internal notes are not visible to customer.
Phase 6: reports and data quality
| Report check | How to test | Pass condition |
|---|---|---|
| Task counts | Create several test tasks in different statuses. | Dashboard/task report numbers make sense. |
| Done per day | Complete a task. | Completed task appears on the correct date. |
| On-time KPI | Set deadline and completion date. | On-time/late logic matches expectation. |
| Cancelled tasks | Cancel a test task. | Normal production report does not treat it as completed production. |
| Margin/loss | Use task with revenue and cost data. | Margin/loss logic shows realistic values. |
Go-live decision
Ready for production when:
- At least one full test workflow passes from task creation to completion.
- Roles are tested with real non-admin accounts.
- Email notifications are tested with a safe customer/test address.
- Reports show understandable results for test data.
- Managers and workers know their daily routine.
- Backup and update process are known.
Do not go live when:
- Workers still need administrator accounts to do normal work.
- Customer panel shows internal data.
- Email queue is sending duplicates or failing silently.
- Statuses/departments do not match real production.
- No one knows who will maintain configuration after launch.
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.
Implementation reference
Implementation reference screen for administrators preparing PQM before go-live.
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.Production DashboardDaily command center, active tasks, metrics and quick actions.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.