PFQ — APM Project Fundamentals Qualification Study Plan
Practical 7-day, 14-day, 30-day, and 60/90-day study schedules for the Association for Project Management PFQ exam.
Orientation
This Study Plan is for candidates preparing for the Association for Project Management APM Project Fundamentals Qualification (PFQ), exam code PFQ.
PFQ preparation should focus on clear understanding of project management fundamentals, not memorising isolated terms. Your goal is to recognise how concepts fit together across the project life cycle: business case, governance, roles, planning, scope, scheduling, risk, quality, communication, stakeholders, change, issue management, and project closure.
Use the latest Association for Project Management syllabus and candidate guidance as your source of truth. Use this plan to organise your time, decide what to study next, and build a repeatable practice-and-review rhythm.
Which plan should you use?
| Your situation | Best plan | Main objective | Practice priority |
|---|---|---|---|
| Exam is in 7 days or less | 7-day final review | Consolidate, test, and fix weak areas | Mixed timed sets and explanation review |
| Exam is in about 2 weeks | 14-day focused plan | Cover all core topics and practise daily | Topic sets, then mixed timed sets |
| Exam is in about 1 month | 30-day balanced plan | Learn steadily and retain concepts | Alternating study, recall, and mock practice |
| Exam is 2-3 months away | 60/90-day full path | Build understanding from the ground up | Low-pressure topic practice, then timed exams |
| You have project experience but little exam prep | 14-day or 30-day plan | Convert experience into exam-ready terminology | Definitions, process links, and scenario wording |
| You are new to project management | 60/90-day path | Build the vocabulary and relationships first | Concept checks before full mocks |
Core PFQ study areas to rotate through
Do not study PFQ as disconnected definitions. Build a map of how each topic supports project delivery.
| Study area | What to know | Practice focus |
|---|---|---|
| Project context and life cycle | Why projects exist, phases, start-up, delivery, closure | Identify where an activity belongs in the life cycle |
| Business case and benefits | Justification, expected value, benefits, continued viability | Distinguish outputs, outcomes, and benefits |
| Governance and organisation | Sponsorship, decision-making, reporting, assurance | Match roles to responsibilities |
| Roles and responsibilities | Sponsor, project manager, team, stakeholders, governance bodies | Avoid confusing ownership, support, and approval |
| Planning and estimating | Project management plan, scope, time, resources, cost basics | Select the best planning action in a situation |
| Scope and requirements | Requirements, deliverables, acceptance, scope control | Recognise scope creep and change control needs |
| Scheduling | Activities, dependencies, milestones, critical path concepts | Interpret simple sequencing logic |
| Risk and issue management | Risk identification, assessment, response, issue escalation | Separate uncertain risks from current issues |
| Quality | Quality planning, assurance, control, acceptance | Identify prevention versus inspection activities |
| Communication and stakeholders | Stakeholder identification, engagement, reporting | Choose suitable communication responses |
| Change control | Change requests, impact assessment, approval, baselines | Decide when formal control is needed |
| Procurement and suppliers | Buying goods/services, contracts, supplier coordination | Understand accountability and interface risks |
| Agile, predictive, and hybrid awareness | Delivery approach differences at a fundamental level | Recognise when approach affects planning and control |
Daily practice rhythm
Use the same rhythm on most study days. Short, repeated review is more effective than reading for long periods without testing.
| Time block | Activity | Output |
|---|---|---|
| 5-10 minutes | Recall yesterday’s topics without notes | Short list of remembered concepts |
| 25-40 minutes | Learn or review one topic area | Annotated notes or flashcards |
| 20-30 minutes | Answer topic-specific practice questions | Marked question set |
| 15-25 minutes | Review every missed or guessed answer | Error log entries |
| 5 minutes | Choose tomorrow’s focus | One topic and one practice target |
If you have only 30 minutes on a weekday, do this:
- Review 5 missed questions.
- Study one small concept.
- Answer 10-15 focused questions.
- Record the top reason you missed any question.
If you have 90 minutes, add a mixed practice set and a short timed section.
Missed-question review method
A missed question is useful only if you diagnose why it was missed. Do not simply read the correct answer and move on.
| Error type | What it means | Fix |
|---|---|---|
| Definition gap | You did not know the term | Add the term to a flashcard and write one example |
| Role confusion | You mixed up who owns or approves something | Create a role-responsibility table |
| Process sequence error | You knew the topic but not the order | Draw the life-cycle or control flow |
| Risk/issue confusion | You treated a current problem as an uncertain event, or the reverse | Write one risk example and one issue example |
| Scenario wording error | You missed clues such as “best next step” or “most appropriate” | Underline command words before answering |
| Overthinking | You used workplace habits instead of exam logic | Re-answer using PFQ terminology and syllabus concepts |
| Guess correct | You got it right but were unsure | Review as if it were wrong |
Use this format for your error log:
| Date | Topic | Question issue | Correct principle | Review date |
|---|---|---|---|---|
Review the error log every 2-3 days. In the final week, it becomes more valuable than rereading full chapters.
7-day final review plan
Use this plan if the PFQ exam is close. The goal is not to learn everything from scratch. The goal is to stabilise your knowledge, practise under time pressure, and remove repeat errors.
| Day | Main focus | Study actions | Practice actions |
|---|---|---|---|
| 1 | Diagnostic check | Take a mixed question set before reviewing notes | Build a weakness list by topic |
| 2 | Life cycle, business case, governance | Review project phases, justification, sponsorship, controls | Topic set on roles, governance, and business case |
| 3 | Planning, scope, schedule | Review requirements, deliverables, estimating, dependencies, milestones | Topic set on planning and schedule logic |
| 4 | Risk, issues, change | Review risk responses, issue escalation, change control steps | Mixed scenario set on risk/change/issue decisions |
| 5 | Quality, communication, stakeholders | Review stakeholder engagement, reports, quality assurance/control | Topic set plus missed-question review |
| 6 | Timed mock or full mixed set | Sit a timed practice attempt in exam-like conditions | Review explanations deeply; no passive rereading |
| 7 | Light final review | Review error log, key definitions, role table, weak flashcards | Short confidence set only; stop heavy study early |
Final 7-day rules
- Do not add large new sources in the final 48 hours.
- Stop chasing obscure details if core concepts are still weak.
- Review why correct answers are correct and why distractors are wrong.
- Keep practice mixed from Day 5 onward.
- If a topic repeatedly fails, reduce it to a one-page summary and practise immediately.
14-day focused plan
Use this plan if you have two weeks and can study most days. It is designed for candidates who need full coverage but cannot spend months preparing.
| Day | Topic focus | Output |
|---|---|---|
| 1 | Diagnostic mixed set and syllabus mapping | Weakness ranking |
| 2 | Project context, life cycle, project versus business-as-usual | One-page life-cycle map |
| 3 | Business case, benefits, success criteria | Output/outcome/benefit comparison |
| 4 | Organisation, governance, sponsorship, roles | Role-responsibility table |
| 5 | Planning overview, project management plan, baselines | Planning checklist |
| 6 | Scope, requirements, deliverables, acceptance | Scope control notes |
| 7 | Schedule, milestones, dependencies, estimating | Practice on sequencing and schedule terms |
| 8 | Risk management | Risk process summary and response examples |
| 9 | Issue and change control | Risk/issue/change comparison table |
| 10 | Quality and configuration/control concepts | Quality assurance versus control notes |
| 11 | Stakeholders and communication | Communication and engagement practice |
| 12 | Procurement, suppliers, handover, closure | Closure checklist and supplier accountability notes |
| 13 | Timed mock or full mixed timed set | Error log and final weakness list |
| 14 | Final review | Light mixed practice and targeted correction |
14-day practice pattern
| Days | Question style | Review method |
|---|---|---|
| 1-5 | Topic-specific | Correct concept gaps immediately |
| 6-10 | Topic-specific plus short mixed sets | Track repeated errors |
| 11-12 | Mostly mixed | Practise switching topics quickly |
| 13 | Timed mock | Review every missed and guessed answer |
| 14 | Light mixed review | Protect confidence and avoid overload |
30-day balanced plan
Use this plan if you want a realistic route that includes learning, practice, and retention. This is the best option for many candidates who are working full time.
Weekly structure
| Week | Goal | Main work | Practice target |
|---|---|---|---|
| 1 | Build foundation | Project context, life cycle, business case, roles, governance | Short topic sets after each study session |
| 2 | Build planning knowledge | Scope, requirements, scheduling, estimating, resources, cost basics | Topic sets plus weekly mixed set |
| 3 | Build control and delivery judgment | Risk, issues, change, quality, communication, stakeholders, procurement | Scenario-style mixed practice |
| 4 | Convert knowledge into exam readiness | Timed practice, weak-area review, final summaries | Timed mocks and error-log review |
30-day schedule
| Day range | Focus | Actions |
|---|---|---|
| Days 1-2 | Diagnostic and setup | Take an untimed mixed set, create topic checklist, start error log |
| Days 3-5 | Project context and life cycle | Review project characteristics, phases, start-up, closure |
| Days 6-7 | Business case and benefits | Practise distinguishing justification, success, outputs, outcomes, benefits |
| Days 8-10 | Governance and roles | Build sponsor/project manager/team/stakeholder responsibility map |
| Days 11-13 | Planning fundamentals | Study project management plan, baselines, estimation, resources |
| Days 14-15 | Scope and requirements | Practise acceptance criteria, deliverables, and scope control |
| Days 16-17 | Scheduling | Review dependencies, milestones, sequencing, critical path concepts |
| Days 18-20 | Risk, issues, and change | Practise choosing correct responses to risk events, live issues, and change requests |
| Days 21-22 | Quality | Review quality planning, assurance, control, acceptance |
| Days 23-24 | Stakeholders and communication | Practise engagement and reporting decisions |
| Days 25-26 | Procurement and closure | Review supplier basics, handover, lessons learned, project closure |
| Day 27 | Timed mixed mock | Sit a full or near-full timed practice attempt |
| Day 28 | Mock review | Review explanations and rebuild weak-topic notes |
| Day 29 | Targeted repair | Drill only weak areas and repeat missed-question themes |
| Day 30 | Final readiness | Light review, definitions, role table, and short confidence set |
30-day weekly checkpoint
At the end of each week, ask:
- Can I explain each core term without looking?
- Can I identify who is responsible for common project activities?
- Can I distinguish risk, issue, and change scenarios?
- Can I answer mixed questions without needing the topic label?
- Are my mistakes decreasing, or am I repeating the same error type?
If the same topic remains weak for two checkpoints, move it to the next day’s first study block.
60/90-day full preparation path
Use this path if you are new to project management, have a busy schedule, or want more time to build confidence. The 60-day version is more compressed; the 90-day version adds more review spacing and lower-pressure repetition.
Phase overview
| Phase | 60-day timing | 90-day timing | Goal |
|---|---|---|---|
| Foundation | Days 1-15 | Days 1-25 | Learn vocabulary and project life-cycle structure |
| Core knowledge | Days 16-35 | Days 26-55 | Study all main PFQ topic areas with topic practice |
| Integration | Days 36-48 | Days 56-72 | Connect topics through scenarios and mixed sets |
| Exam readiness | Days 49-60 | Days 73-90 | Timed mocks, final review, and weak-area repair |
Foundation phase
| Focus | Actions |
|---|---|
| Project basics | Define project, programme, portfolio if covered by your materials; understand project versus operations |
| Life cycle | Map start-up, planning, delivery/control, handover, closure |
| Business case | Connect justification, benefits, success criteria, and continued review |
| Roles | Build a table of sponsor, project manager, team, users, stakeholders, and governance responsibilities |
| Practice | Use short untimed topic questions; focus on explanation quality |
Core knowledge phase
Rotate through the major syllabus areas. Do not wait until the end to practise.
| Topic block | Study output | Practice output |
|---|---|---|
| Planning and estimating | Planning checklist and key definitions | Topic set with explanation review |
| Scope and requirements | Requirements-to-deliverables map | Scope/change questions |
| Scheduling | Dependency and milestone notes | Sequencing questions |
| Risk and issue management | Risk register concept summary | Risk versus issue drills |
| Change control | Change request flow | Scenario questions on approval and impact |
| Quality | Assurance/control comparison | Quality scenario questions |
| Stakeholders and communication | Stakeholder engagement table | Communication-response questions |
| Procurement and suppliers | Supplier interface notes | Accountability questions |
| Closure and handover | Closure checklist | Lessons learned and handover questions |
| Delivery approaches | Predictive/agile/hybrid awareness, where relevant to your materials | Questions on approach implications |
Integration phase
This is where many candidates improve. Move from “I recognise the term” to “I can choose the best answer when several options sound plausible.”
| Practice type | Purpose | Frequency |
|---|---|---|
| Mixed untimed sets | Build topic switching | 2-3 times per week |
| Short timed sets | Build pace without fatigue | 2 times per week |
| Scenario review | Improve judgement | After every mixed set |
| Error-log review | Prevent repeated mistakes | Every 3-4 days |
| One-page summaries | Compress weak topics | As needed |
Exam readiness phase
| Timing | Action |
|---|---|
| 10-14 days before exam | Take a timed mock or full mixed timed set |
| 7-10 days before exam | Review explanations and repair top 3 weak areas |
| 5-7 days before exam | Take another timed mixed set if available |
| 3-4 days before exam | Stop adding new major resources; focus on error log and definitions |
| 1-2 days before exam | Light review only; avoid exhausting study sessions |
What to practise next
Use this table after every practice session.
| Your result | What it means | Next action |
|---|---|---|
| High score, few guesses | Topic is stable | Move to mixed practice |
| High score, many guesses | Knowledge is fragile | Review explanations and repeat a small set later |
| Low score in one topic | Targeted gap | Study that topic, then answer topic questions immediately |
| Low score across many topics | Foundation issue | Return to syllabus map and core definitions |
| Good untimed score, poor timed score | Pace issue | Use short timed sets before full mocks |
| Repeated role errors | Responsibility confusion | Rebuild role table and practise governance questions |
| Repeated risk/change/issue errors | Control process confusion | Create examples and compare them side by side |
| Mistakes from wording | Exam technique issue | Underline command words and eliminate distractors deliberately |
Timed mock exam use
Do not use every mock too early. Timed practice is most valuable after you have covered enough content to learn from the results.
| Preparation stage | Mock use |
|---|---|
| Very early | Use a short diagnostic set, preferably untimed |
| After 50-60% coverage | Use short timed mixed sets |
| After full first pass | Use a full or near-full timed mock |
| Final 2 weeks | Use timed mocks for readiness and review, not for learning new content |
| Final 48 hours | Avoid a heavy mock unless you know it will not damage confidence or recovery |
When reviewing a mock:
- Mark every missed and guessed question.
- Sort misses by topic.
- Sort misses by error type.
- Re-study only the concepts that caused errors.
- Re-answer similar questions within 24-48 hours.
- Update your final review sheet.
Final-week rules
| Rule | Why it matters |
|---|---|
| Stop adding new major material 3-4 days before the exam | New sources can create confusion and overload |
| Review your own error log daily | It targets your actual weaknesses |
| Keep practice mixed | The real exam will not label questions by topic |
| Practise definitions actively | PFQ depends on clear understanding of terms |
| Sleep and pacing matter | Tired candidates misread simple questions |
| Do not ignore guessed correct answers | They reveal unstable knowledge |
| Keep final notes short | You need recall, not a second textbook |
Exam-readiness checks
You are likely ready to sit PFQ when you can do most of the following without notes:
- Explain the purpose of a project life cycle.
- Distinguish business case, benefits, outputs, outcomes, and success criteria.
- Match common project roles to their responsibilities.
- Explain why governance and control are needed.
- Recognise the difference between scope, requirements, deliverables, and acceptance.
- Identify what belongs in planning, scheduling, monitoring, and control.
- Distinguish a risk from an issue.
- Explain the purpose of change control.
- Recognise quality planning, assurance, and control activities.
- Choose appropriate stakeholder and communication actions.
- Answer mixed practice questions at a steady pace.
- Review wrong answers using a clear reason, not “I just missed it.”
Practical next step
Choose the schedule that matches your remaining time, take a diagnostic practice set, and create an error log today. Your next study session should be based on evidence from your answers, not on the chapter you feel like rereading.