Compliance is the word that makes a lot of people turn the page. It sounds like a binder, a signature and somebody from legal. In the outline it is a task with seven enablers inside the domain that grew the most, and the seventh changes how the other six have to be read.
What the outline means by compliance
In the July 2026 outline, the Business Environment domain weighs 26 per cent, the jump we covered in full in the Business Environment post. Its second task is called plan and manage project compliance.
The first enabler carries its own list of examples, and it is worth reading because it surprises people. Confirm project compliance requirements, and in brackets the outline names security, health and safety, sustainability, and regulatory compliance.
So compliance is not only the law. It is everything the project has to respect because somebody demands it, whether that comes from a regulator, a contract, an internal policy or an environmental commitment. That is why sustainability comes in through this door and not the one almost everyone looks for, something we already took apart in the sustainability post.
The seven enablers are those of the official PMP exam content outline, July 2026 edition.
Classifying is not filing
The second enabler asks you to classify compliance categories, and it sounds like paperwork until you ask what it is for.
It is for the fact that not all requirements get treated alike. One coming from a regulator with power to fine you is not negotiated or postponed. One coming from an internal policy may carry a documented exception. One coming from a contractual commitment gets discussed with the other party. Classifying is deciding in advance which of those three worlds applies, so you are not improvising that conversation the day the conflict shows up.
The concrete examples of rules depend on your industry and your country, and the outline names none of them. That omission is deliberate and it is a clue, because the exam will not ask you about a rule. It will ask what you do with one.
Threats to compliance, not to the project
The third says determine potential threats to compliance. Look at the object of that sentence, because it is not the same as a threat to the project.
A supplier running late threatens your schedule. A supplier running late who pushes you into skipping an inspection threatens your compliance. They are the same fact seen from two places, and the outline asks you to look from the second one too. Half the questions on this topic live right there, in recognizing that the risk being described has a compliance face the scenario does not name.
Consequences get analysed before you decide
The fifth enabler is analyse the consequences of noncompliance and the sixth is determine the necessary approach and actions. In that order, not the other way round.
It is the same pattern that shows up in almost every task in the outline. First you understand the size of what is at stake, then you choose what to do. An option that has you acting before sizing the consequence is the one you discard, however diligent it sounds.
And that sizing is what justifies a different approach on each project, which is exactly what we talk about in the tailoring post. Two projects with the same requirement can deserve very different compliance effort depending on what failing costs.
Measure the extent, not the yes or no
The seventh enabler is the one that earns the article. It says measure the extent to which the project is in compliance.
Read it slowly, because most people treat compliance as a switch. You comply or you do not. The outline does not frame it that way. It frames a continuous measurement, with a degree that can rise and fall, and that carries two uncomfortable implications.
The first is that you need something to measure with, meaning a definition of compliance concrete enough to produce a number or a state. The second is that you have to measure it more than once. Compliance verified at the start and never again is not compliance, it is a memory.
That is why the diagram loops back. When the measurement says the degree dropped, you do not start over, you step back to analysing the consequence and deciding the approach, which are the two enablers you already had.
What it looks like in a question
The scenario describes a project moving along well and an internal audit finding that a requirement stopped being met two months ago. The options offer stopping the work, informing the sponsor, documenting the deviation, or analysing the impact of the noncompliance and defining the actions.
The last one is the outline’s, and it is the least spectacular of the four. Stopping and informing can be part of the actions, but they are chosen actions, not the step that comes next. What comes next is sizing it.
Compliance is not the binder somebody signs at the end. It is a magnitude measured while the project runs, and the day somebody asks how much your project complies, the right answer will never be yes.
Join the waitlist
At The PM Architect we write the PMBOK study guides in five languages, with real classroom cases and exercises that come with an explanation. They will be free. Leave your email on the home page and we’ll let you know the moment they’re ready.
