Most PMP candidates expect integration management questions to ask about sequencing processes or naming the seven integration processes in order. Then the exam hits them with a scenario where a mid-project request lands on the project manager's desk. It seems small. The stakeholder says it won't affect the timeline. The right answer is often not to approve it on the spot, but to route it through formal integrated change control. That's where integration management questions actually live on the current exam: not in definitions of processes, but in judgment calls about how the project manager keeps all moving parts aligned and coordinated. If you understand the processes, this article covers the reasoning patterns the exam actually tests for integration.
The Seven Integration Management Processes and Why Integration Is the "Master" Knowledge Area
Project Integration Management in PMBOK covers seven processes that span all five process groups: Develop Project Charter (Initiating), Develop Project Management Plan (Planning), Direct and Manage Project Work (Executing), Manage Project Knowledge (Executing), Monitor and Control Project Work (Monitoring and Controlling), Perform Integrated Change Control (Monitoring and Controlling), and Close Project or Phase (Closing).
What makes integration management different from every other knowledge area is that it touches all of them. Cost management, schedule management, scope management, quality management, risk management, procurement management, stakeholder management, resource management, and communications management all feed their outputs into integration management. The project charter pulls requirements from initiation. The project management plan pulls subsidiary plans from every other knowledge area. Direct and Manage Project Work pulls from all of them to execute. Integrated Change Control is where competing demands and priorities from different areas get reconciled into one set of decisions. This is why integration management is sometimes called the "master" knowledge area on the exam: the project manager's job is to unify all of these pieces into one coherent project.
A trap question on the exam will describe a scenario where one knowledge area (schedule, risk, procurement) wants something that another area opposes. The project manager needs to pull them together through integration, and the exam expects you to know that the resolution point is not inside one of the individual knowledge areas, but in integration management. Read also our article about PMI Mindset and how it may help at the exam.
Project Charter vs Project Management Plan: The One-Page Authorization vs The Detailed How-To
This distinction is tested repeatedly on the PMP exam in subtle ways, because it trips up people who have managed real projects but never worked in an environment that formally separates these documents.
The project charter is a short, high-level document, typically just one or two pages. It is issued by the project sponsor, not the project manager. The charter's job is to formally authorize the project, give the project manager the authority to apply organizational resources, and set the high-level direction: project purpose, business case, key success criteria, and major stakeholder names. The charter does not detail how the work will be done. It says the project is approved and the PM has permission to proceed.
The project management plan, by contrast, is built during detailed planning and is comprehensive. It contains or incorporates subsidiary plans from all ten knowledge areas (integration, scope, schedule, cost, quality, resource, communications, risk, procurement, and stakeholder management). It describes the methods, tools, baselines, and processes that will govern execution. It is approved by the project manager and the appropriate stakeholders before work begins.
An exam scenario will sometimes describe a decision about execution strategy or resource allocation. If the question asks who makes the decision or who approves it, the answer depends on which document it relates to. Charter-level changes (high-level business case or sponsor-level scope) require charter updates and sponsor approval. Plan-level changes (execution methods, detailed budgets, task sequences) require management plan updates and team/PM approval, and may also need to go through formal change control if they deviate from already-approved baselines.
Integrated Change Control and the Change Control Board: The Formal Approval Process That Stops Scope Creep
This is the most commonly tested integration management concept on recent PMP exams, and the pattern is consistent: a small change request lands, the wrong answer is always to approve it unofficially, and the right answer is to follow the formal change control process.
Perform Integrated Change Control is the process of reviewing all change requests, evaluating their impacts across the project, and approving or rejecting them. The Change Control Board (CCB) is a formally constituted group, usually including the project manager, sponsor, key stakeholders, and subject matter experts, whose job is to review, evaluate, and decide on every change request.
The key exam pattern: a change request is submitted. The stakeholder or team member claims it is minor, or low-impact, or does not touch the critical path. The question asks what the PM should do. The right answer is that every change, no matter how small it seems, must go through the formal CCB review process. The CCB's job is to assess the real impact across the whole project, not just one constraint. A change that does not affect the schedule might still affect budget, risk, resource allocation, or quality. Only the CCB, not the individual who submitted the change or the PM acting alone, can make that integrated assessment.
A related trap: a question describes a change that has already been implemented informally (a team member made a small adjustment without asking). The question asks what the PM should do now. The answer is typically to create a change request retroactively, have the CCB evaluate it, and log the decision. You cannot undo an informal change, but you can formalize the approval and track what actually happened.
Corrective Action, Preventive Action, and Defect Repair: All Are Types of Change Requests
During execution, the Monitor and Control Project Work process identifies problems. Those problems can surface in three forms, and each one leads to a change request. The exam tests whether you know the difference and which one applies to a given scenario.
Defect repair corrects a nonconformity in a deliverable or product. Quality inspections find it. A developer finds a bug in the code, or a construction inspector finds an electrical connection that does not meet specification. The fix is defect repair. Every defect repair, no matter how small, requires a change request.
A corrective action is a future response to a problem. It means realigning the way work is being performed so that it matches the approved plan. If a developer is building features in the wrong order, a corrective action would be to reschedule and redirect the developer to follow the approved sequence. Corrective actions also require change requests, because they change how the work will proceed.
A preventive action is proactive. It anticipates a potential problem that has not yet occurred and takes steps to avoid it. If a team member spots a risk that the database system will not handle the expected data volume, a preventive action might be to upgrade the system before the load testing phase. Preventive actions also require change requests, because they change the project plan.
An exam scenario will describe a problem and ask which category it falls into. The pattern is usually: if it's a fault in an existing deliverable, it's defect repair. If it's a change to how the work is being performed to match the plan, it's corrective action. If it's a proactive change to avoid a risk, it's preventive action. All three require change requests and CCB review.
Project Closure and Why Skipping Formal Close Is an Exam Trap
Close Project or Phase is the final process in integration management, and it gets relatively little study attention because it happens at the end when candidates are exhausted. The exam, however, treats it seriously.
Project closure includes formal activities: verification that all work is complete and accepted, collection and documentation of lessons learned, transition of deliverables to operations or the client, release of project resources, and archiving of project documents. These activities are not optional or nice-to-have. They are part of the project manager's responsibility to formally close the project.
An exam scenario will describe a project nearing the end. The team wants to move on to the next project. The question asks what the PM should do before releasing the team. The right answer is typically to ensure closure is formally completed: deliverables accepted, lessons learned documented, resources released through a formal handoff, and the project officially closed. A wrong answer might be "the team can move to the next project once they finish the current work," because that skips the formal closure activities.
The lessons learned part is tested separately sometimes. A question might ask when lessons learned should be collected. The answer is: during or at the very end of the project, not after everyone has left. If you wait until later, people have moved on and the information is lost. Project closure is the point where institutional knowledge about what worked and what did not is captured and handed over to the organization.
Why Integration Management Gets the Highest Average Difficulty Rating from Candidates
Compared to cost management, which has formulas, or schedule management, which has clear logic trees, integration management is harder to study because it lives in judgment calls. You cannot memorize your way through an integration question that describes a messy stakeholder situation and asks what the PM should do. You have to think through how the different pieces of the project fit together, what the change control process looks like, and who has the authority to make what decision.
This is also why integration management is worth the study effort. The exam is testing the core skill of project management: coordination and unification. Questions about integration management are scenario-based and close to real project dynamics, which makes them harder to guess but also more rewarding once you internalize the patterns. Check the article for additional information about what to write in the first 5 minutes before the exam starts.
Key Takeaways
- Integration management spans all five process groups and touches every other knowledge area. It is the "master" knowledge area because the project manager's job is to unify all moving parts.
- The project charter is a short sponsor-issued authorization document giving the PM permission to proceed. The project management plan is the detailed, comprehensive document guiding execution, built from subsidiary plans in all ten knowledge areas.
- Perform Integrated Change Control routes every change request through a formal Change Control Board, regardless of how small the change seems. The CCB assesses integrated impacts across the whole project, not just one constraint.
- Defect repair fixes a nonconformity in an existing deliverable. Corrective action realigns work to match the approved plan. Preventive action proactively avoids a potential risk. All three generate change requests.
- Close Project or Phase includes formal verification, lessons learned documentation, resource release, and project archiving. Skipping formal closure is a common exam trap.
- Integration management questions are scenario-based and test judgment, not formulas. The exam rewards candidates who think through how all project pieces fit together.
Practice Through Scenario, Not Through Memorization
The gap between knowing integration management concepts and recognizing the pattern in a realistic exam scenario is where most candidates lose points. A well-designed integration management question will include plausible-sounding wrong answers that tempt you to sidestep the formal process, and the right answer is almost always to follow the integration management and change control procedures, even if it seems like overkill for a small change.
pmproad.com offers 1,000+ exam-style practice questions with detailed explanations, including scenario-based integration management questions that mirror the judgment-call style of the current exam. The fastest way to find your gaps is to try the free 20-question demo first, no signup needed. If the format works for you, pmproad.com unlocks the full question bank for 90 days at $39.99.