PFQ vs PMQ: What's the Difference, and Which Comes First?

A delegate asked me last month whether she needed to "do the PFQ first" before booking PMQ. She wasn't asking because she'd read the syllabus and formed a view. She was asking because a colleague had done it that way, and it had settled into the office as the correct order, the way these things do. Nobody had actually checked whether it applied to her.

It's a fair question to ask and a genuinely common assumption to hold. APM offers two qualifications early in its suite, and it's natural to read them as a beginner tier and an advanced tier, sat one above the other like belts in a martial art. Pass the first, then you're allowed to attempt the second. That reading isn't reckless. It's just wrong more often than it's right, and the cases where it's wrong tend to be the ones with something real riding on them.

Start with what each qualification actually tests, because the two are built for genuinely different purposes rather than different difficulty settings of the same purpose.

The Project Fundamentals Qualification is a one hour, sixty question, multiple choice exam. There's no prerequisite experience, no case study to interpret, no requirement to have worked on a project at all. It exists to give someone a working vocabulary: what a business case is for, how a risk register differs from an issues log, what a sponsor is meant to do that a project manager isn't. If you've never sat in a project meeting and don't yet know whether "scope" means the same thing to a client as it does to a delivery team, PFQ is built for exactly that gap. It rewards recognising the right term for the right concept. It doesn't ask you to apply anything under pressure, because it isn't designed to.

The Project Management Qualification is a different exercise entirely. It runs two and a half hours, covers forty questions built around defined learning objectives, and has done since the format changed in September 2024. Rather than checking whether you recognise a term, it checks whether you can reason with it, applying project management concepts to scenarios that behave the way real projects behave: constrained, political, short of information in at least one place that matters. It assumes the candidate already has some exposure to how a project actually moves, even if that exposure came from watching one closely rather than running one.

That difference in what's being tested is the thing the "PFQ first" assumption misses. PFQ measures vocabulary. PMQ measures judgement under realistic conditions. Vocabulary is a prerequisite for judgement in the sense that you need words before you can reason with them, but plenty of people already have the words. They picked them up on site, in meetings, coordinating a delivery schedule for two years without ever calling it project management formally. For someone in that position, sitting PFQ first doesn't build a foundation. It delays a test they're already equipped to pass, in favour of one that mostly confirms what they already knew.

I've watched this play out from both directions in the same cohort. One delegate, newly moved into project support from an admin role, had never encountered a RACI chart or a stage gate before her course started. PFQ gave her something PMQ never would have: a settled, confident vocabulary before she was asked to apply it under exam pressure. She sat PMQ eight months later and passed comfortably, because by then the terms weren't new, only the application was. Another delegate on the same programme had been informally running delivery for a construction subcontractor for six years, without the title and without the qualification, but with every one of the underlying skills already in daily use. He'd been told, by someone well meaning, that PFQ was "just how you start." He sat it, passed easily, and told me afterwards that the hour had taught him nothing he didn't already know from the job. He wasn't wrong to sit it. He just didn't need to.

Neither of those outcomes was a mistake exactly, but only one of them was efficient. And efficiency is usually what people actually want when they ask which one comes first. They're not asking a philosophical question about the shape of the qualification ladder. They're asking how to get where they're going without spending time on a step they don't require.

So the honest answer to "which comes first" isn't PFQ, and it isn't PMQ either. It's a question back: what does your current work already involve? If project terminology is unfamiliar and you haven't yet been close to how a business case gets built or a risk gets escalated, PFQ earns its place, not as a formality but as real preparation that will make PMQ noticeably easier when you get there. If you're already doing the work in substance, coordinating scope, chasing dependencies, managing a sponsor's expectations, without the credential to show for it, going straight to PMQ isn't skipping a step. It's recognising that the step was already climbed somewhere else, on the job, before the exam existed to measure it.

That's a less tidy answer than a fixed order would be. It's also the one that actually holds up once you look at what each exam is built to test rather than which one sounds more junior. If you want a straight read on where your own experience sits against that line, get in touch about your APM training options and we'll work it out honestly rather than defaulting to the ladder everyone assumes exists.

Andre Malowney is a project management trainer accredited across PMI, APMG, APM and PeopleCert frameworks, working with both traditional plan-driven practitioners and Agile delivery teams. Find him on LinkedIn: www.linkedin.com/in/andremalowney.