Delegates usually ask this question in one of two ways. Either they want a number, something to write on a whiteboard and justify the course fee against, or they ask it more warily, half expecting to be told the qualification alone will not do very much. Both instincts are reasonable. Neither gets the full picture.
Here is the part that tends to disappoint people first: no certificate, on its own, moves a payslip. Nobody's employer opens a spreadsheet, sees "PMQ" next to a name, and adjusts a figure accordingly. If that is the mental model you are working from, the numbers below will feel smaller than promised, and the qualification will feel like a poor trade against the study hours it costs.
What actually happens is less tidy and, for anyone in construction, infrastructure, engineering or defence, considerably more useful.
Start with what is verifiable. The Association for Project Management runs its own Salary and Market Trends Survey, conducted through YouGov, and it has tracked the profession since 2015. The most recent figures show the average salary for a project professional in the UK rising from £47,500 to £52,500, an increase of just over ten per cent. That is the first rise the survey has recorded since before the pandemic, and it comes alongside a reported uptick in confidence among project professionals about their own prospects. That average sits across the whole profession, every sector, every seniority band, which is exactly why it is not, by itself, an answer to what you personally can expect.
The more useful cut is by experience. APM's own data breaks the headline figure down further: professionals with two decades or more behind them report averages well above £70,000, and senior project managers as a group sit meaningfully higher than the profession-wide mean. That range is not something a qualification produces on day one. It is what the profession pays for depth, and depth is built over years, not exam sittings.
So where does PMQ actually sit in that picture. Not as a multiplier on your current salary. As the credential that gets you considered for the roles where those higher averages exist at all.
This matters more in some sectors than others, and it matters most in exactly the sectors Omega's delegates tend to come from. Construction, infrastructure and defence employers ask for APM PMQ by name in a way that other sectors simply do not, because the Building Safety Act and the wider competence framework around it have made a recognised, chartered-body qualification something procurement teams can point to, not just something a candidate mentions in an interview. In those industries, PMQ is frequently a filter before it is ever a differentiator. Without it, a CV may not clear the first screen regardless of experience. With it, the conversation moves to what the experience is actually worth, which is where the real salary numbers live.
A composite illustration makes this concrete without pretending to be a case study. Picture a delivery coordinator on a regional infrastructure programme, five years into the profession, doing genuinely capable work but stuck applying for roles that keep asking for a qualification she does not hold. She sits PMQ, not expecting a pay rise the following Monday, and nothing changes the following Monday. What changes is which roles she is now eligible to be shortlisted for. Six months later she moves into a project manager post on a scheme that specifically required the qualification as a condition of application, at a salary closer to the mid-career average the APM survey reports, not because PMQ argued her case, but because it stopped being the reason her application was filtered out before anyone read it.
That is the honest mechanism. PMQ does not negotiate on your behalf. It removes a specific, checkable barrier that a specific set of UK employers have built into their hiring process, and it does that reliably, because it is the credential those employers were already asking for.
None of this means the qualification is a guaranteed route to the higher bands in APM's survey. Sector, location and years of delivery experience still do most of the work, and London roles in particular continue to command a premium over the rest of the UK. Energy, utilities and consultancy tend to sit above the profession-wide average too, for reasons that have nothing to do with any single qualification and everything to do with how those sectors budget for delivery risk. PMQ does not override any of that. A delegate in a lower-paying sector who adds PMQ is still, most likely, in a lower-paying sector afterwards.
What PMQ changes is narrower and more durable than a single salary bump. It decides whether you are in the room where those higher figures are even on the table, and it does that specifically in the sectors, construction, infrastructure, engineering, defence, where the qualification is asked for by name rather than treated as one acceptable option among several. That is a smaller claim than "PMQ raises your salary." It is also a truer one, and it is the version that actually holds up when someone checks it against their own experience two years later.
If you are weighing PMQ against what it costs in time and fees, that is the calculation worth doing, not "will this add a number to my payslip" but "will this let me apply for the roles where the number is already higher." For a project manager working toward chartered-adjacent sectors, that is usually not a close call. If you want to talk through where you currently sit against that filter, get in touch about your APM PMQ training options and we can look at your specific position rather than the average one.
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.