When the change comes from outside and moves your scope

Think of the last regulation that landed on your sector. It arrived with nobody asking for it, and the first thing that happened was an emergency meeting. What almost never happens first is somebody working out how much that regulation moves the project you already have running.

Some changes are born inside the project, when someone spots something or the sponsor changes their mind, and some arrive from outside with nobody asking for them, because a regulation changed, a technology appeared, a government moved or the market stopped wanting what you were about to deliver. The PMP outline has a task dedicated only to the second kind, and it is one of the most frequently answered wrong.

The last task of the domain that grew the most

In the July 2026 outline, the Business Environment domain weighs 26 per cent, the jump we covered in full in the Business Environment post. That domain has eight tasks and the eighth is called evaluate external business environment changes.

There are three enablers. The first asks you to survey changes to the external business environment, and in brackets the outline names four sources, regulations, technology, geopolitical and market. The second asks you to assess and prioritise the impact on project scope or backlog based on those changes. The third asks you to continually review the external business environment for impacts on scope or backlog.

The three enablers and the four sources are those of the official PMP examination content outline, July 2026 edition.

The verb is not modify, it is prioritise

Here is the trap, and it shows up when you read the second enabler slowly. It says assess and prioritise the impact, it does not say modify the plan or update the baseline.

That is not sloppy wording. Modifying the plan is another task in the same domain, the third one, called manage and control changes, which starts by executing the change control process. The outline deliberately separated the work of sizing from the work of approving, and that is why the right answer to a question about an external change is almost never to change something. It is to measure how much it affects you and to rank that impact against the rest of what you already had.

Prioritising also implies that the impact does not arrive alone. A new regulation is not the only thing happening in your project, so the outline asks you to put it in the same queue as the rest and decide what gets attention first.

Scope or backlog, the two words always together

Two of the three enablers say scope or backlog, and that slash is deliberate. The outline does not assume you work predictive, nor that you work agile.

In a predictive project the external change reaches the scope baseline and goes through change control. In an adaptive one it reaches the backlog and gets resolved by reprioritising, with no formal request, because the backlog exists for that. The task is the same in both cases and the only thing that changes is the vehicle. If the exam describes a team working in sprints and offers you an option that talks about a formal change request, be suspicious.

Continually is the word that turns this into a routine

The third enabler looks like a repetition of the first until you notice the adverb. Continually reviewing the external environment turns this into a routine with a cadence, not into a reaction to the news of the day.

Think of it as the beam of a lighthouse. It is not useful for what it lights up in one instant, it is useful because it comes back round to the same point every so often, and what shows up between one sweep and the next is exactly what you care about. An environment reviewed at the start and never again is an old photograph, and it will hurt you when the project already carries commitments. The same happens with the degree of compliance, which is also measured while the project runs and which we took apart in the compliance post.

What PMI measured in 2026

Its Pulse of the Profession report for 2026, titled Driving Success in Complex Projects and published in May 2026, puts numbers on it. Ninety-seven per cent of the professionals surveyed managed at least one complex project in the previous year, and more than half classified it as significantly complex. Around a third of complex projects fail, nearly twice the 13 per cent the report gives for projects overall. And those who navigate complexity effectively multiply the likelihood of project success by five.

The public summary of the report names rapid technological change, expanding stakeholder networks and ongoing economic and regulatory uncertainty as the drivers, which is almost the same list of four sources the outline puts in brackets. It is not a coincidence, the outline is describing what the report measures.

There is a finding that matters for the exam and for the work. Top performers do not face less complexity, they navigate it differently, putting outcomes ahead of activity, alignment ahead of formal compliance and learning ahead of certainty.

If what reached you from outside is a change of direction from your own organisation rather than from the market, the problem is a different one and we worked it in the post on strategy losing coherence.

Let’s take it to an exam question

The stem tells you that halfway through the project a new regulation is published that affects one of the deliverables. The options offer you stopping work on that deliverable, immediately updating the scope baseline, informing the sponsor, or assessing the impact on scope and prioritising it against the rest of the work.

The last one is the outline’s. Stopping and informing can come later, and updating the baseline without going through change control is precisely what the outline does not ask of you here. First you size it, because until you know how much the regulation moves you there is nothing to escalate and nothing to change.

The environment does not warn you when it changes, it warns you once it has already reached you. Looking outward too late looks a lot like not looking at all.

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.