PMQ — APM Project Management Qualification Study Plan
A practical 7-day, 14-day, 30-day, and 60/90-day study plan for the APM Project Management Qualification (PMQ) exam.
Who this Study Plan is for
This Study Plan is for candidates preparing for the Association for Project Management APM Project Management Qualification (PMQ), exam code PMQ.
Use it to turn your available time into a realistic preparation schedule. The PMQ rewards more than memorising project management terms. You need to explain concepts clearly, apply them to project situations, and write structured answers under time pressure.
The plan below is built around five preparation activities:
- Domain review - project lifecycle, governance, roles, planning, risk, quality, change, stakeholders, communication, leadership, benefits, procurement, and delivery approaches.
- Written-answer practice - short, clear responses that answer the command verb and include project context.
- Scenario judgment - choosing the right action for a project situation, not just recalling a definition.
- Missed-question review - turning weak answers into reusable answer patterns.
- Timed mock practice - building speed, structure, and confidence before exam day.
Which plan should you use?
Choose the shortest plan that still gives you time to practise written answers. If you are starting from little project management experience, use the 60/90-day path where possible.
| Time available | Best fit | Main goal | What to prioritise |
|---|---|---|---|
| 7 days | Final review plan | Convert knowledge into exam-ready answers | Timed practice, weak-topic review, answer structure |
| 14 days | Focused plan | Cover high-value topics and practise daily | Domain refresh, scenario answers, mini-mocks |
| 30 days | Balanced plan | Build breadth, depth, and timing | Full syllabus cycle, targeted practice, mock exams |
| 60 days | Standard full path | Learn, apply, and refine | Weekly domain blocks, repeated written practice |
| 90 days | Extended path | Best for new PM candidates or busy schedules | Gradual learning, spaced review, multiple mocks |
Quick decision guide
| Your current position | Use this approach |
|---|---|
| You have completed a course and have notes, but little exam practice | Start with the 14-day or 30-day plan and emphasise timed written answers |
| You understand project management at work but not PMQ terminology | Use the 30-day plan and build a glossary plus answer templates |
| You are new to project management | Use the 60/90-day plan and do not rush into full mocks too early |
| You have one week left | Use the 7-day plan; stop trying to learn everything and focus on scoring method |
| You keep running out of time | Add daily timed answer drills and strict answer planning |
| Your answers are too vague | Use the missed-question review method and practise “definition + purpose + project example” responses |
PMQ preparation priorities
For the APM Project Management Qualification (PMQ), your study should move from recognition to explanation to application.
| Preparation level | What it looks like | How to practise |
|---|---|---|
| Recognition | You know the term | Create a concise definition |
| Explanation | You can explain why it matters | Add purpose, benefit, and consequence |
| Application | You can use it in a project situation | Answer scenario questions with context |
| Judgment | You can choose between options | Compare trade-offs, risks, stakeholders, constraints |
| Exam performance | You can write clearly under time pressure | Timed short-answer and mock practice |
Core PMQ study areas to rotate through
Use your official syllabus, course materials, and notes as the source of truth. Organise your review into these practical study blocks:
| Study block | Topics to review | Practice focus |
|---|---|---|
| Project context and lifecycle | Project characteristics, lifecycle phases, handover, closure, success criteria | Explain how lifecycle choice affects control and decision-making |
| Governance and assurance | Sponsorship, business case, governance, reviews, assurance, reporting | Describe who makes decisions and how control is maintained |
| Roles and organisation | Sponsor, project manager, team, users, stakeholders, governance bodies | Match responsibilities to project situations |
| Planning and scheduling | Scope, estimating, dependencies, critical path concepts, resources, baselines | Explain how plans are built, controlled, and updated |
| Risk and issue management | Risk identification, assessment, responses, ownership, issues, escalation | Choose suitable responses and explain consequences |
| Change control and configuration | Change requests, impact assessment, baselines, configuration control | Explain why uncontrolled change damages delivery |
| Stakeholder and communication management | Identification, analysis, engagement, communication planning | Tailor communication to stakeholder power, interest, and attitude |
| Quality management | Quality planning, assurance, control, acceptance, lessons learned | Distinguish prevention, checking, and continuous improvement |
| Benefits and value | Benefits identification, ownership, realisation, business case alignment | Link outputs to outcomes and organisational value |
| Procurement and contracts | Supplier selection, contract considerations, buyer/supplier roles | Identify risks and control points in external delivery |
| Leadership and teamwork | Motivation, conflict, delegation, team development, communication | Explain appropriate leadership action in context |
| Delivery approaches | Predictive, agile, iterative, hybrid, product and project considerations | Explain when an approach fits the uncertainty and governance needs |
Daily practice rhythm
Use this rhythm for most study days. Adjust the duration, but keep the sequence.
| Step | Time | Action | Output |
|---|---|---|---|
| 1. Recall warm-up | 10 minutes | Write definitions or key lists from memory | 5-10 recalled points |
| 2. Topic review | 30-60 minutes | Review one PMQ topic using notes or syllabus materials | Condensed notes |
| 3. Written-answer drill | 30-45 minutes | Answer 2-4 short questions without notes | Exam-style responses |
| 4. Mark and compare | 20-30 minutes | Compare against model points, notes, or marking guidance | Gap list |
| 5. Missed-question log | 10-15 minutes | Record why marks were lost | Next review target |
| 6. Spaced review | 10 minutes | Revisit yesterday’s weak points | Stronger recall |
Minimum daily version
If you only have 30-40 minutes:
- Review one small topic.
- Write one timed answer.
- Mark it.
- Rewrite the weakest paragraph.
- Add one missed-question note.
This is better than passively rereading notes for an hour.
How to write stronger PMQ answers
Many candidates know the material but lose marks because their answers are too general. Practise building answers in layers.
| Answer layer | What to include | Example prompt to ask yourself |
|---|---|---|
| Definition | What is it? | Can I define the term in one clear sentence? |
| Purpose | Why is it used? | What problem does it solve for the project? |
| Process | How is it done? | What steps, roles, or documents are involved? |
| Context | When would it matter? | What project situation makes this important? |
| Consequence | What happens if it is not done well? | What risk, delay, cost, quality, or stakeholder issue could result? |
Useful written-answer structure
For most explanation-based PMQ responses, practise this structure:
- Direct point - answer the question immediately.
- Project reason - explain why it matters in delivery.
- Example or consequence - show application.
- Link back - connect to control, value, risk, stakeholder confidence, or successful delivery.
Avoid long introductions. The examiner should see the answer quickly.
Missed-question review method
Do not simply count right and wrong answers. For PMQ, classify the reason you missed marks.
| Miss type | Symptom | Fix |
|---|---|---|
| Knowledge gap | You did not know the concept | Relearn the topic and create a 5-line summary |
| Vague explanation | You knew the term but could not explain it | Add purpose, benefit, and consequence |
| Wrong command verb | You listed when asked to explain or describe | Underline the command verb before answering |
| No project context | Your answer was generic | Add a project example or delivery consequence |
| Role confusion | You mixed up sponsor, project manager, team, or governance roles | Create a role-responsibility table |
| Process order error | You knew the activities but not the sequence | Draw a simple workflow |
| Timing issue | You ran out of time | Practise shorter answers under a timer |
| Overwriting | You spent too long on one answer | Set a time limit and move on when reached |
| Scenario misread | You answered the topic but not the situation | Restate the scenario problem before writing |
| Weak review | You repeated the same mistake later | Schedule the miss for 24-hour and 7-day review |
Missed-question log template
Use a simple table after every practice session.
| Date | Topic | Question type | What I missed | Root cause | Correct answer pattern | Review date |
|---|---|---|---|---|---|---|
| Risk | Explain | Did not mention ownership | Vague explanation | Define risk, assign owner, response, review | ||
| Change | Scenario | Did not assess impact | Process gap | Log request, assess impact, decide, update baseline |
How to turn mistakes into answer patterns
For each weak topic, create a reusable answer pattern.
| Topic | Reusable pattern |
|---|---|
| Risk response | Identify risk, assess probability/impact, assign owner, choose response, monitor and report |
| Change control | Record request, assess impact, seek approval, update baselines, communicate decision |
| Stakeholder engagement | Identify stakeholders, analyse interest/influence, plan communication, engage, monitor attitude |
| Business case | Justify investment, compare benefits/costs/risks, support decision-making, review viability |
| Quality | Define standards, plan assurance and control, verify outputs, correct defects, learn lessons |
| Governance | Set decision rights, define reporting, monitor progress, escalate exceptions, maintain accountability |
When to use timed mock exams
Timed mocks should be introduced after you have enough topic coverage to learn from them. Do not spend all your preparation time on full mocks too early.
| Stage | Mock type | Purpose |
|---|---|---|
| Early study | Untimed topic questions | Learn answer structure and identify knowledge gaps |
| Middle study | Timed question sets | Build speed and command-verb discipline |
| Final third | Partial mocks | Practise topic switching and time control |
| Final 10-14 days | Full timed mocks | Rehearse exam rhythm and stamina |
| Final 48 hours | Light timed drills only | Maintain confidence; avoid exhausting yourself |
Mock review rules
After each timed mock or partial mock:
- Mark or compare your answers as objectively as possible.
- Identify the top 5 topics that cost the most marks.
- Identify whether the issue was knowledge, application, structure, or timing.
- Rewrite 3-5 weak answers in improved form.
- Schedule a short retest within 48 hours.
- Update your final review list.
A mock is not finished when the timer stops. It is finished when you have converted weak answers into better answer patterns.
7-day final review plan
Use this if your exam is one week away. The goal is not to relearn the whole PMQ syllabus. The goal is to stabilise recall, improve answer quality, and avoid avoidable timing mistakes.
7-day schedule
| Day | Main focus | Study actions | Output |
|---|---|---|---|
| 7 days out | Diagnostic and triage | Complete a timed question set or partial mock. Review every missed mark. Rank weak topics. | Top 8 weak-topic list |
| 6 days out | Governance, lifecycle, roles | Review sponsor, project manager, governance, lifecycle, business case, assurance. Write short answers. | Role and governance summary |
| 5 days out | Planning, risk, change | Practise planning, estimating, scheduling, risk, issue, and change-control questions. | Process answer patterns |
| 4 days out | Stakeholders, communication, leadership | Practise scenario answers involving conflict, communication, engagement, motivation, and escalation. | Scenario response notes |
| 3 days out | Quality, benefits, procurement, delivery approaches | Review quality, benefits realisation, supplier issues, predictive/agile/hybrid considerations. | Final topic flash sheet |
| 2 days out | Timed mock or large timed set | Sit one substantial timed practice session. Review answers carefully. Do not add new materials afterwards. | Final gap list |
| 1 day out | Light final review | Review missed-question log, formulas/concepts if relevant, definitions, and answer structures. Stop heavy study early. | Exam-day checklist |
7-day rules
| Rule | Why it matters |
|---|---|
| Stop adding new sources after Day 2 | New material can create confusion without enough practice time |
| Practise writing every day | PMQ performance depends on producing clear answers, not recognising notes |
| Review weak answers, not just weak topics | Marks are lost in wording and structure |
| Use a timer | Time pressure changes answer quality |
| Keep final notes short | You need recall triggers, not a second textbook |
14-day focused plan
Use this if you have two weeks and already have some course notes or project management background. The plan balances topic refresh with daily written practice.
Week 1: rebuild core coverage
| Day | Topic block | Practice task |
|---|---|---|
| 1 | Diagnostic | Timed short question set; create weak-topic list |
| 2 | Project context, lifecycle, success, handover, closure | 3 written answers on lifecycle and success criteria |
| 3 | Governance, sponsorship, business case, assurance | 3 written answers on accountability and control |
| 4 | Roles, organisation, teamwork, leadership | 3 scenario answers involving role responsibilities |
| 5 | Scope, planning, estimating, scheduling, resources | 3 process-based planning answers |
| 6 | Risk, issues, escalation | 4 risk/issue scenario questions |
| 7 | Change control, configuration, quality | Partial timed set; review and rewrite weak answers |
Week 2: apply, time, and refine
| Day | Topic block | Practice task |
|---|---|---|
| 8 | Stakeholders and communication | Scenario set focused on stakeholder conflict and communication choices |
| 9 | Benefits, value, procurement, supplier control | Short answers on business case, benefits, and procurement risks |
| 10 | Delivery approaches: predictive, agile, hybrid | Compare approach suitability in different project contexts |
| 11 | Mixed-topic timed set | Practise switching topics and controlling answer length |
| 12 | Full or near-full timed mock | Simulate exam conditions as closely as practical |
| 13 | Mock review and targeted repair | Rewrite weak answers; review top 5 weak topics |
| 14 | Final review | Light recall, missed-question log, answer structure, exam-day plan |
14-day emphasis
| If your mock shows… | Spend extra time on… |
|---|---|
| You know terms but answers are thin | Explanation depth: purpose, benefit, consequence |
| You miss scenario cues | Stakeholder, risk, change, and governance decision practice |
| You confuse roles | Sponsor/project manager/team/governance responsibility mapping |
| You run out of time | Timed short-answer drills and stricter answer planning |
| You score unevenly by topic | Daily mixed-topic sets, not just favourite areas |
30-day balanced plan
Use this if you want a structured month of preparation. This is the best fit for many candidates who have completed training but need exam readiness.
30-day overview
| Phase | Days | Purpose |
|---|---|---|
| Phase 1 | Days 1-5 | Diagnostic and foundation refresh |
| Phase 2 | Days 6-14 | Core domain review and written practice |
| Phase 3 | Days 15-22 | Scenario application and mixed-topic timing |
| Phase 4 | Days 23-27 | Mock exams and targeted repair |
| Phase 5 | Days 28-30 | Final review and confidence maintenance |
Days 1-5: diagnostic and foundation refresh
| Day | Focus | Actions |
|---|---|---|
| 1 | Diagnostic | Complete a timed sample set. Build missed-question log. |
| 2 | PMQ topic map | Organise notes into domain blocks. Identify gaps against your course materials. |
| 3 | Lifecycle and context | Review lifecycle, project environment, success, handover, closure. |
| 4 | Governance and roles | Review sponsor, project manager, governance, assurance, business case. |
| 5 | Answer technique | Practise command verbs, concise explanations, and answer planning. |
Days 6-14: core domain review
| Day | Focus | Written practice |
|---|---|---|
| 6 | Scope and requirements | Explain scope control and consequences of unclear requirements |
| 7 | Estimating, scheduling, resources | Describe planning steps and control methods |
| 8 | Risk management | Apply risk identification, assessment, response, ownership, review |
| 9 | Issue and change control | Practise escalation and impact-assessment answers |
| 10 | Quality management | Distinguish quality planning, assurance, and control |
| 11 | Stakeholder engagement | Scenario answers on power, interest, resistance, and communication |
| 12 | Communication and reporting | Tailor reporting to governance and stakeholder needs |
| 13 | Leadership and team management | Practise conflict, delegation, motivation, and team performance answers |
| 14 | Review checkpoint | Timed mixed set and missed-question analysis |
Days 15-22: scenario application
| Day | Focus | Scenario practice |
|---|---|---|
| 15 | Business case and benefits | Link outputs, outcomes, benefits, value, and continued justification |
| 16 | Procurement and suppliers | Supplier risk, contract control, communication, acceptance |
| 17 | Predictive delivery | Baselines, change control, governance, staged decision-making |
| 18 | Agile and iterative delivery | Uncertainty, collaboration, prioritisation, incremental delivery |
| 19 | Hybrid delivery | Governance plus adaptability; when and why to combine approaches |
| 20 | Integrated scenario set | Stakeholder + risk + change combined practice |
| 21 | Timed partial mock | Work under exam-like timing |
| 22 | Repair day | Rewrite weak answers and retest the weakest topics |
Days 23-27: mocks and targeted repair
| Day | Focus | Actions |
|---|---|---|
| 23 | Full or substantial timed mock | Simulate exam conditions; do not pause for notes |
| 24 | Mock review | Classify every missed mark; build top 10 repair list |
| 25 | Targeted repair 1 | Review weakest technical topics and write improved answers |
| 26 | Targeted repair 2 | Review weakest scenario topics and practise judgment |
| 27 | Second timed mock or partial mock | Confirm improvement and timing control |
Days 28-30: final review
| Day | Focus | Actions |
|---|---|---|
| 28 | Final weak-topic cycle | Review only high-yield gaps from your missed-question log |
| 29 | Light timed drills | Short answer sets; no heavy new material |
| 30 | Exam readiness | Final notes, answer structures, logistics, rest |
60/90-day full preparation path
Use this path if you are starting early, balancing work with study, or building project management knowledge from the ground up.
Weekly rhythm
| Day type | Activity | Duration |
|---|---|---|
| Study day 1 | Learn one domain block | 60-90 minutes |
| Study day 2 | Review and summarise | 45-60 minutes |
| Study day 3 | Written-answer practice | 45-75 minutes |
| Study day 4 | Scenario practice | 45-75 minutes |
| Weekend or longer session | Mixed review or timed set | 90-180 minutes |
| Rest/catch-up | Light recall only | 15-30 minutes |
60-day path
| Week | Focus | Key outputs |
|---|---|---|
| 1 | Orientation, diagnostic, PMQ topic map | Study tracker, weak-topic baseline |
| 2 | Project context, lifecycle, success, handover, closure | Lifecycle answer patterns |
| 3 | Governance, sponsorship, business case, assurance | Governance and role summary |
| 4 | Planning: scope, requirements, estimating, scheduling, resources | Planning process notes |
| 5 | Risk, issues, change, configuration | Control-process answer patterns |
| 6 | Stakeholders, communication, leadership, teamwork | Scenario response patterns |
| 7 | Quality, benefits, procurement, delivery approaches | Integration notes across topics |
| 8 | Timed practice, mocks, final review | Mock review log and final gap list |
90-day path
| Month | Focus | Study outcome |
|---|---|---|
| Month 1 | Build knowledge | Understand terminology, roles, lifecycle, governance, planning basics |
| Month 2 | Build application | Practise risk, change, stakeholders, quality, benefits, procurement, delivery approach scenarios |
| Month 3 | Build exam performance | Timed sets, mock exams, missed-answer repair, final answer technique |
90-day weekly detail
| Week | Focus | Practice target |
|---|---|---|
| 1 | Exam orientation and diagnostic | Short untimed baseline set |
| 2 | Project context and lifecycle | 6-8 short written answers |
| 3 | Governance and business case | Role and decision-making scenarios |
| 4 | Scope, requirements, estimating | Planning explanations |
| 5 | Scheduling, resources, baselines | Process and control answers |
| 6 | Risk and issue management | Scenario drills with response choices |
| 7 | Change and configuration control | Impact-assessment answers |
| 8 | Quality management and lessons learned | Prevention vs checking explanations |
| 9 | Stakeholders and communication | Engagement strategy scenarios |
| 10 | Leadership, teams, conflict | Management action scenarios |
| 11 | Benefits, value, procurement | Business justification and supplier control |
| 12 | Predictive, agile, hybrid delivery | Compare approach suitability |
| 13 | Full review and mocks | Timed mock, repair, final review |
What to practise next
Use this table after each study session.
| Your latest result | Next best action |
|---|---|
| You cannot define the concept | Return to notes and write a one-sentence definition |
| You can define it but not explain it | Add purpose, benefit, and consequence |
| You can explain it but not apply it | Do scenario questions on that topic |
| You can answer untimed but not timed | Use 10-15 minute answer drills |
| You answer too generally | Add project context and role-specific action |
| You miss integrated questions | Practise combined stakeholder, risk, change, and governance scenarios |
| You repeat the same errors | Rewrite model answers and retest within 48 hours |
| Your timing is stable and explanations are clear | Move to mixed-topic mocks |
Predictive, agile, and hybrid study split
PMQ preparation should include delivery approach judgment. You do not need to force every answer into one method, but you should be able to explain how project controls adapt to context.
| Delivery context | What to understand | Practice prompt |
|---|---|---|
| Predictive | Defined scope, staged plans, baselines, formal change control | How does a baseline support control? |
| Agile or iterative | Evolving requirements, collaboration, prioritisation, incremental delivery | How does frequent feedback reduce delivery risk? |
| Hybrid | Governance and assurance combined with adaptive delivery | How can a project maintain control while adapting scope? |
Comparison practice
For each delivery approach, practise explaining:
- How planning is performed.
- How progress is monitored.
- How change is handled.
- How stakeholders are engaged.
- How risk is reduced.
- How benefits and value are protected.
Stakeholder, risk, and change review loop
These areas often appear together in realistic project situations. Review them as an integrated loop, not as isolated topics.
| Situation | PMQ response pattern |
|---|---|
| A stakeholder resists a change | Analyse interest and influence, understand concerns, communicate impact, involve sponsor if needed |
| A risk becomes an issue | Escalate as appropriate, assign ownership, implement response, update plans and reports |
| A change request affects cost or time | Log request, assess impact, seek approval, update baselines, communicate decision |
| A supplier delay threatens delivery | Review contract and plan, assess risk, escalate, agree corrective action, communicate impact |
| Benefits are unclear | Revisit business case, identify benefit owners, define measures, align outputs to outcomes |
| Team conflict affects progress | Identify cause, facilitate resolution, clarify roles, escalate only when necessary |
Final-week rules
In the final week, your study should become narrower and more exam-focused.
| Do | Avoid |
|---|---|
| Use your missed-question log daily | Reading large chapters without practice |
| Practise timed written answers | Spending all day making new notes |
| Review command verbs and answer structure | Writing long unfocused responses |
| Revisit governance, risk, change, stakeholders, and planning | Ignoring weaker topics because they feel uncomfortable |
| Sleep and maintain a normal routine | Exhausting yourself with late-night cramming |
| Stop adding new material near the end | Switching to unfamiliar resources at the last minute |
When to stop adding new material
Stop adding new study sources when you are inside the final 48 hours, unless you discover a critical gap in a core topic. From that point, focus on:
- missed-question log
- concise definitions
- reusable answer patterns
- timed short-answer drills
- exam-day timing strategy
- light confidence review
Exam-readiness checks
You are approaching readiness when you can do the following consistently.
| Readiness check | Yes/No |
|---|---|
| I can define key PMQ terms without notes | |
| I can explain why each major process matters to project success | |
| I can distinguish sponsor, project manager, team, stakeholder, and governance responsibilities | |
| I can write concise answers that match the command verb | |
| I can apply risk, issue, and change control to scenarios | |
| I can explain stakeholder and communication choices in context | |
| I can compare predictive, agile, and hybrid delivery considerations | |
| I can complete timed practice without losing control of answer length | |
| I review missed questions by root cause, not just by topic | |
| I have completed at least one substantial timed practice session before exam day |
If you are not ready
| Problem | Corrective action |
|---|---|
| Weak recall | Create a 2-page final summary and test from memory |
| Weak explanations | Use the definition + purpose + consequence structure |
| Weak application | Practise scenario questions only for two sessions |
| Poor timing | Set strict per-question time limits and move on |
| Uneven topic coverage | Rotate daily through weak domains |
| Low confidence after a mock | Review the mock carefully; repair the highest-value misses first |
Practical next step
Pick the plan that matches your remaining time, complete a diagnostic question set, and build your missed-question log today. Then use each study session to do three things: review one PMQ topic, write at least one timed answer, and repair one weakness before moving on.