PFQ — APM Project Fundamentals Qualification Cheat Sheet

Focus on:

• Definitions: know the precise difference between similar terms.
• Purpose: understand why an artifact, role, or process exists.
• Sequence: know what happens before and after key controls.
• Accountability: distinguish sponsor, project manager, team, users, and governance bodies.
• Application: select the best next action in a simple scenario.

The PFQ mindset is not “memorise every possible project document.” It is:

• know the language of project management;
• recognise who is responsible for what;
• understand how projects are justified, planned, controlled, changed, and closed;
• distinguish similar terms such as risk vs issue, quality assurance vs quality control, and output vs benefit;
• choose the most disciplined next step in scenario-style questions.

For current exam rules, policies, and official information, always refer to the Association for Project Management.

Lifecycle types

Basic control cycle

Governance, assurance, and control

Governance provides the framework for decision-making, accountability, escalation, and alignment with organisational objectives. Assurance gives confidence that the project is being managed appropriately.

Project control cycle

Common mistake: reporting variance without explaining impact or proposing action.

RACI quick distinction

Common trap: responsible and accountable are not the same. The project manager may be responsible for managing delivery, while the sponsor is accountable for business justification.

Roles and responsibilities

RACI-style thinking

Common trap: if a question asks who is accountable, do not choose the person who merely performs the task unless the scenario supports that accountability.

Output-outcome-benefit chain

Business case and justification

The business case is the continuing reason for investing in the project. It normally connects the project to organisational objectives, costs, risks, expected benefits, and options.

Decision rule: if the business case is no longer valid, the correct answer is rarely “continue because the plan says so.” Review, escalate, and make a governed decision.

Dependency types

Core schedule formulas

Use these formulas only when the scenario provides the needed network data. For many PFQ-style questions, the main concept is that the critical path is the longest path and has the least scheduling flexibility.

Scheduling essentials

Schedule compression logic

Decision rule: do not compress a schedule casually. Assess impacts on cost, quality, risk, scope, and stakeholder expectations.

Cost terms

Common trap: a project can be under budget but behind schedule, or over budget but ahead of schedule. Read both cost and schedule indicators separately.

Risk terms

Risk response choices

Risk vs issue vs change

Fast distinctions

Risk management flow

1. Identify uncertainty.
2. Assess probability and impact.
3. Plan responses and assign owners.
4. Implement responses.
5. Monitor and review risk status.
6. Communicate and escalate as needed.

Risk response examples

Event handling decision path

    flowchart TD
	    A[New information appears] --> B{Has it already happened?}
	    B -- No --> C[Record as risk or opportunity]
	    C --> D[Assess probability and impact]
	    D --> E[Assign owner and response]
	    E --> F[Monitor and communicate]
	    B -- Yes --> G{Does it require a baseline change?}
	    G -- No --> H[Manage as issue or action]
	    H --> I[Record, resolve, and report]
	    G -- Yes --> J[Raise change request]
	    J --> K[Assess impact on scope, time, cost, quality, risk, and benefits]
	    K --> L[Decision by agreed authority]
	    L --> M[Update plans and communicate if approved]

PFQ trap: once a risk occurs, it is no longer merely a risk; it becomes an issue or event requiring action.

Change control

Change control protects the project from uncontrolled scope, cost, time, risk, quality, and benefits impacts. It does not mean “never change”; it means change deliberately.

Common mistake: choosing an answer that implements a stakeholder’s requested change immediately. The better answer is usually to assess and follow the agreed change process.

Quality examples

Quality management

Quality is about fitness for purpose and meeting agreed requirements, not simply “gold-plating” the deliverable.

Decision rule: build quality in through planning and process, then verify through control activities.

Stakeholder engagement choices

Stakeholder and communication review

Stakeholders are individuals or groups who can affect, be affected by, or perceive themselves to be affected by the project.

Stakeholder engagement steps

Communication planning

PFQ trap: “communicate more” is not always the answer. Communicate the right information to the right people at the right time using an appropriate method.

Team development cues

Leadership and teamwork

PFQ candidates should recognise basic leadership and team concepts in project situations.

Team-stage thinking

Trap: conflict is not automatically bad. Poorly managed conflict is harmful; constructive disagreement can improve decisions.

Procurement decision cues

Procurement and supplier awareness

Even at fundamentals level, recognise that supplier work must be planned, specified, managed, and accepted.

Common mistake: assuming outsourced work no longer needs project management. Supplier deliverables still affect the project’s schedule, cost, quality, risk, and stakeholders.

Escalation cues

Final rapid review checklist

Before your next PFQ practice session, confirm you can:

• define project, programme, portfolio, operations, output, outcome, and benefit;
• explain the purpose of the business case;
• match key responsibilities to sponsor, project manager, team, users, governance, PMO, and suppliers;
• outline a typical project life cycle and the purpose of each stage;
• distinguish WBS, schedule, milestone, dependency, float, and critical path;
• apply the basic control cycle: baseline, actuals, variance, forecast, action, report;
• handle risks, issues, opportunities, and changes using the correct records and processes;
• separate quality planning, assurance, control, and acceptance;
• plan stakeholder engagement and communication based on need, influence, and timing;
• recognise when to escalate and when to manage within authority.

Decision rule: projects deliver outputs and enable change; benefits are realised when the organisation uses those outputs effectively.

Lifecycle types

PFQ questions often test the purpose of lifecycle control: it supports decision-making, governance, learning, and progressive commitment. It is not just an administrative diagram.

Work breakdown and product breakdown

Trap: a WBS is not simply a task list in chronological order. It is a structured decomposition that helps estimate, assign, schedule, and control work.