Contracts, Change & Risk Response

Risk response planning assigns a deliberate strategy to each risk. For threats, PMBOK recognizes five strategies: avoid (eliminate the cause), transfer (shift financial impact to a third party, as with insurance or fixed-price contracts), mitigate (reduce probability or impact), escalate (hand off risks outside the project’s authority), and accept (passively, or actively with a contingency reserve). Opportunities have parallel strategies: exploit, share, enhance, escalate, and accept. A common trap confuses mitigate and transfer: mitigation reduces likelihood or severity but the project still owns the risk, whereas transfer moves the financial consequence elsewhere without removing it.

Contingency reserve is budget or schedule buffer allocated inside the cost and schedule baselines to address known unknowns — identified risks whose probability and impact have been quantified. Because it sits within the baseline, the project manager can authorize its use without escalating to senior management, a direct tool for risk response. The key exam distinction is from management reserve, which covers unknown unknowns, sits outside the baseline, and typically requires a formal change request and change control board approval to access. Knowing which reserve the PM can spend autonomously is one of the most frequently tested nuances.

A fixed-price contract sets a single agreed price for a clearly defined scope, transferring cost risk almost entirely to the seller. Because the seller absorbs overruns, thorough scope definition before signing is essential; ambiguous requirements shift the risk dynamic and breed disputes or change-order battles. Three variants appear on the exam: Firm Fixed Price (FFP), Fixed Price Incentive Fee (FPIF), and Fixed Price with Economic Price Adjustment (FPEPA). The key distinction: FPIF still places primary risk on the seller while offering a shared savings incentive, whereas cost-reimbursable contracts shift risk toward the buyer.

A cost-reimbursable (CR) contract reimburses the seller for allowable, allocable, and reasonable costs incurred, then adds a fee for profit. PMBOK recognizes three variants: Cost Plus Fixed Fee (CPFF), a set dollar fee; Cost Plus Incentive Fee (CPIF), where a sharing ratio adjusts the fee against a target cost; and Cost Plus Award Fee (CPAF), where the buyer subjectively scores performance to set the award. CR suits work too uncertain to price up front, but cost risk shifts largely to the buyer. A common trap is confusing CR with Time and Material (T&M), a hybrid using negotiated rates with no defined scope, best for smaller jobs.

A time and materials (T&M) contract pays the seller pre-negotiated hourly or daily labor rates plus the actual cost of materials, making it a hybrid of fixed-price and cost-reimbursable contracts. It suits work that cannot be fully scoped upfront, such as staff augmentation or short consulting engagements. The key exam nuance is cost control: without a Not-to-Exceed (NTE) ceiling, total cost is unbounded, placing most financial risk on the buyer. T&M must be closely monitored to prevent runaway costs, contrasting with firm-fixed-price, which shifts that risk to the seller.

Integrated Change Control is a process in the Monitoring and Controlling process group that governs how all change requests are received, reviewed, approved or rejected, and communicated across the project. It enforces traceability by ensuring no deliverable, schedule, or cost baseline is updated without a formally approved change request, protecting the integrity of the project management plan. The key exam nuance is that it is integrated: a scope change must simultaneously be evaluated for its impact on schedule, cost, quality, risk, and resources before approval. Confusing it with the Change Control Board (CCB) is a common trap: the process reviews requests, while the CCB is the body that approves or rejects them.

A Change Control Board (CCB) is a formally constituted group that reviews change requests and holds the authority to approve, defer, or reject them. Its membership, voting rights, and escalation thresholds are defined in the change management plan, so it operates within a pre-agreed governance structure rather than ad hoc. The exam nuance is distinguishing the CCB from the project manager’s own authority: minor changes within the PM’s approved tolerance need no CCB review, while changes outside those thresholds are escalated. On agile or hybrid projects, the product owner reprioritizing the backlog often fulfills this role, but the governance principle holds.

The cost baseline is the approved, time-phased budget formed by summing work package cost estimates plus contingency reserves for identified (known-unknown) risks. It is established in the Determine Budget process and is the reference against which actual cost performance is measured. Management reserve sits above the baseline for unknown-unknowns and requires a change request to access, so it is outside the performance measurement baseline. Cost baseline plus management reserve equals the total project budget. Earned value metrics—CV, SV, CPI, SPI—are calculated against the cost baseline, not the total budget. Any baseline change passes through integrated change control.

Quality Management spans three activities: Plan Quality Management (identifying standards and how to meet them), Manage Quality (auditing the quality processes themselves for conformance), and Control Quality (inspecting deliverables against requirements). It covers both the management process and the product, ensuring outputs satisfy stakeholder needs without gold-plating. The key exam distinction is that Manage Quality is process-level — confirming the right methods are used — while Control Quality is product-level, measuring actual results against the quality baseline. Under cost of quality, prevention (training, design reviews) is preferred over appraisal and failure costs.

Resource Management covers planning, acquiring, developing, managing, and controlling both team members and physical resources such as equipment, materials, and facilities. The Resource Management Plan defines roles, responsibilities, reporting relationships, and the staffing approach. A common exam trap conflates resource leveling with smoothing: leveling resolves over-allocation by delaying activities, which can extend the schedule and change the critical path, while smoothing adjusts work only within available float and leaves the critical path unchanged. Choose smoothing when the finish date is fixed.

Communications management is the knowledge area covering how project information is planned, collected, distributed, stored, retrieved, and disposed of. The communications management plan, the primary output of Plan Communications Management, documents who needs what information, in what format, how often, and through which channel; it draws on the stakeholder register, since each stakeholder’s needs shape it. A key exam nuance: managing communications concerns the flow and format of information, while stakeholder engagement concerns attitudes and participation. The n(n-1)/2 formula counts potential communication channels as team size grows.