Try 10 focused PMI-CP questions on Contracts Management, with answers and explanations, then continue with PM Mastery.
| Field | Detail |
|---|---|
| Exam route | PMI-CP |
| Topic area | Contracts Management |
| Blueprint weight | 50% |
| Page purpose | Focused sample questions before returning to mixed practice |
Use this page to isolate Contracts Management for PMI-CP. Work through the 10 questions first, then review the explanations and return to mixed practice in PM Mastery.
| Pass | What to do | What to record |
|---|---|---|
| First attempt | Answer without checking the explanation first. | The fact, rule, calculation, or judgment point that controlled your answer. |
| Review | Read the explanation even when you were correct. | Why the best answer is stronger than the closest distractor. |
| Repair | Repeat only missed or uncertain items after a short break. | The pattern behind misses, not the answer letter. |
| Transfer | Return to mixed practice once the topic feels stable. | Whether the same skill holds up when the topic is no longer obvious. |
Blueprint context: 50% of the practice outline. A focused topic score can overstate readiness if you recognize the pattern too quickly, so use it as repair work before timed mixed sets.
These questions are original PM Mastery practice items aligned to this topic area. They are designed for self-assessment and are not official exam questions.
Topic: Contracts Management
A university laboratory project is at 30% design. Subsurface conditions under the planned foundation are only partially investigated, the city has not confirmed the utility-cut permit, and the campus operations team has not committed shutdown dates for tie-ins. The owner wants to release an early sitework package next month. What is the best front-end risk action?
Best answer: A
What this tests: Contracts Management
Explanation: Several major uncertainties still affect scope, pricing, and execution. A structured front-end risk assessment is the best action because it prioritizes exposure and informs whether the early package and contract approach should be adjusted before commitment.
When a project still has major shaping uncertainties, the right move is a structured front-end risk assessment rather than a downstream workaround. Here, incomplete geotechnical information, unconfirmed permits, and unresolved shutdown interfaces could materially change package scope, cost, timing, and contract fit. A cross-functional IPRA brings the owner, designer, operations team, and other affected parties together to identify and prioritize the risks, assign owners, and decide on responses such as more investigation, resequencing, interface controls, or different risk allocation before procurement. That is better project shaping than forcing bidders to price unknowns or waiting for construction coordination to sort it out. The closest distractor is pushing contingency to bidders, but risk transfer is weaker than first understanding and prioritizing the risk.
A structured IPRA is the best front-end action because it prioritizes uncertain site, permit, and interface risks before committing to package release and contract allocation.
Topic: Contracts Management
A commuter-rail station project has separate civil, structural steel, signaling, and MEP contracts. Rework is occurring because openings, access dates, and package handoffs are discussed in coordination meetings but are not tracked with clear owners, dependencies, or due dates. Which artifact would best improve visibility, accountability, and monitoring across these package boundaries?
Best answer: C
What this tests: Contracts Management
Explanation: The need is active control of package-to-package handoffs, not general risk, change, or claim tracking. An interface register makes each boundary visible, assigns accountability, and supports ongoing monitoring of dependencies and dates.
This scenario is about interface management across multiple contracts. The core problem is that boundaries between packages are being discussed, but not controlled through a structured record. An interface register is designed for exactly that purpose: it identifies each interface point, the parties involved, the dependency or handoff required, the owner, timing, status, and communication path.
Using this artifact turns informal coordination into trackable interface control. It improves visibility by listing all critical package boundaries, accountability by naming owners, and monitoring by showing due dates and current status. On complex construction projects, that is the most direct way to reduce missed handoffs and rework. A risk, change, or claim record may be useful for related events, but those tools do not manage the interface itself.
An interface register is the purpose-built artifact for tracking package boundaries, ownership, timing, and status across interfaces.
Topic: Contracts Management
A public owner plans a fast-track station upgrade. The sponsor wants multiple lump-sum trade contracts because the forms are familiar and easy to administer. Design is only 65% complete, utility relocations are unresolved, and similar projects produced frequent scope-gap and interface claims. What is the best advice to the steering committee?
Best answer: A
What this tests: Contracts Management
Explanation: The proposed approach is easy to administer, but the project conditions make it claim-prone. The best advice is to adjust the contract strategy so interface exposure is reduced and uncertain risks are assigned to the parties best able to manage them.
In construction, a contract strategy should be evaluated by its effect on project outcomes, not just by administrative convenience. Here, multiple lump-sum trade contracts may look simple, but incomplete design and unresolved utility work create predictable claim triggers: scope gaps, coordination failures, and disputed responsibility at package boundaries. Senior stakeholders should be advised to choose a strategy that better matches the uncertainty by clarifying responsibility, reducing interface exposure where practical, and allocating each major risk to the party best positioned to control it.
The key takeaway is that simple administration is not a benefit if it builds claim exposure into the project from the start.
This best addresses the predictable claim drivers created by incomplete design and unresolved interfaces rather than favoring administrative simplicity.
Topic: Contracts Management
A rail-station expansion will start separate civil works, traction power, and signaling contracts next week. A fixed weekend possession requires cable tray handover, power isolation from operations, and signaling testing in sequence; the owner will not move the start date but wants to avoid later coordination claims. What should the project manager do now?
Best answer: C
What this tests: Contracts Management
Explanation: This is an interface-management decision under time pressure. The best balance is to define package boundaries, owners, timing, and escalation paths before mobilization so dependencies are controlled early without delaying the start.
The core concept is early interface planning across package boundaries. In this scenario, the project already knows several critical dependencies among civil works, operations, traction power, and signaling, and the possession window is fixed. The strongest response is to bring the affected parties together immediately, confirm each interface point, and document them in an interface register with owners, required dates, handoff expectations, and escalation paths.
That approach manages the dependency risk before it turns into delivery disruption, claims, or informal blame shifting. It also preserves the immovable start date, which makes it a better tradeoff than delaying all work. Weekly meetings and RFIs can support execution later, but they are reactive tools. A blanket instruction making one contractor responsible may simplify responsibility on paper, but it does not establish the actual interface points that must be managed across separate contracts.
This proactively defines cross-package dependencies, ownership, timing, and escalation before work starts, without sacrificing the fixed start date.
Topic: Contracts Management
A hospital expansion will award separate structural, MEP, and controls packages next week. During pre-award review, the team records this note. Based on the exhibit, what is the best contract action?
Risk ID: R-27
Class: Interface / coordination
Risk event: MEP sleeves and controls conduits may conflict with post-tensioned slab zones
Affected packages: Structural, MEP, controls
Cause: Separate designers release updates on different dates
Preferred allocation: Shared control; owner retains integration oversight
Required response: Define interface points, deliverable dates, review hold points
Escalation trigger: Missed interface deliverable or unresolved clash
Best answer: A
What this tests: Contracts Management
Explanation: This is an interface risk that crosses multiple packages, so the response should strengthen contractual interface controls. Because control is shared and the owner keeps integration oversight, the best action is to define interface duties, timing, and escalation in the contract documents.
Risk classification should drive the treatment method. Here, the exhibit clearly shows an interface or coordination risk affecting several packages, with shared control rather than full transfer to one contractor. That means the contract response should convert the risk note into active interface controls: package boundaries, interface points, deliverable dates, review hold points, and a clear escalation path when a handoff is missed or a clash remains unresolved.
The closest trap is shifting everything to one trade, but the exhibit explicitly says the risk is shared and owner integration oversight is retained.
The exhibit classifies a shared interface risk, so the contracts should formalize package boundaries, handoffs, hold points, and escalation.
Topic: Contracts Management
On a hospital project, the structural steel contractor installed anchor plates to Revision 5 drawings, while the curtain wall contractor fabricated panels to Revision 4. Both revisions were available in the PMIS. The interface register named the steel-to-facade boundary but did not assign who would verify the latest tie-point revision before fabrication. No scope change was approved, and no claim has been filed yet, but the enclosure milestone is now at risk. Which statement best classifies this situation?
Best answer: B
What this tests: Contracts Management
Explanation: The key distinction is that the package boundary was identified but not actively controlled. Missing ownership for tie-point revision verification turned a boundary handoff into an interface issue that has now created schedule impact and potential claim exposure.
This is an interface-management failure, not primarily a change order, dispute, or PMIS problem. In construction, interface management means actively defining package boundaries, assigning ownership, and controlling handoff checks at the right time. Here, the project had the information in the PMIS and had identified the boundary, but it failed to assign responsibility for validating the current revision before fabrication. That means the control breakdown occurred at the interface.
Because the mismatch has already occurred, it is now an issue caused by poor interface management, with likely schedule impact and possible future claims.
The missing boundary ownership and revision check make this an interface-management failure that has now materialized as an issue and may lead to claims.
Topic: Contracts Management
During foundation work on a hospital project, the contractor encounters undocumented utilities and stops excavation in one area for 4 days. The owner and contractor want to assess any entitlement quickly and avoid a formal dispute. Which documentation practice is the strongest sign that the records are sufficient for early resolution?
Best answer: C
What this tests: Contracts Management
Explanation: Documentation is strong enough for early resolution when it is contemporaneous and shows a clear cause-and-effect chain from the event to its time or cost impact. Records that tie notice, field evidence, affected resources, and schedule effect together let the parties evaluate entitlement before the matter escalates.
For claim prevention and early resolution, the key discriminator is whether the documentation is contemporaneous, traceable, and impact-based. In this scenario, the strongest practice is the one that connects the unexpected utility condition to dated notices, field photos, affected labor or equipment, and schedule consequences while the facts are still fresh. That gives both parties a factual record to test causation, responsibility, and potential compensation early.
High-level summaries, frustration notes, or a risk entry may show awareness, but they do not provide the evidence chain needed to keep an issue from growing into a disputed claim.
Contemporaneous, linked evidence gives both parties a verifiable basis to assess causation and entitlement before positions harden.
Topic: Contracts Management
A hospital expansion is finalizing its procurement strategy. In front-end planning, the IPRA captured:
Utility locations: partially verified
Shutdown windows: limited by hospital operations
MEP prefabrication design maturity: 35%
Temporary plant tie-ins: 3 trade-package interfaces
The sponsor asks how this information should be carried into contracts and execution controls before packages are released. Which response is best?
Best answer: A
What this tests: Contracts Management
Explanation: The best response turns early planning assumptions into explicit lifecycle controls. It links the IPRA to risk allocation, delivery method fit, interface planning, change-control triggers, and ongoing monitoring rather than just circulating the report or reacting later.
Early construction risk information should not stop at an IPRA workshop. When assumptions such as unknown utilities, operational shutdown constraints, low design maturity, and shared tie-ins are material, the team should convert them into decisions that shape the contract and delivery setup before procurement. That means using the risk information to decide who retains or carries each risk, whether the delivery method supports the needed coordination, where package boundaries and interface owners must be defined, and what changes in assumptions should trigger formal change review during execution.
Simply broadcasting the IPRA or waiting for field problems increases the chance of claims and avoidable change disputes.
This response converts early assumptions into explicit contract, delivery, interface, change, and monitoring controls instead of leaving them as background information.
Topic: Contracts Management
On a design-build hospital project, unknown buried utilities could delay excavation, while early permit approval could accelerate long-lead equipment release. The project director wants one live project artifact that classifies each item as a threat or opportunity, assigns an owner, defines the response strategy, sets escalation triggers, and tracks status during construction. Which artifact best supports this need?
Best answer: A
What this tests: Contracts Management
Explanation: A risk register is the best fit because it supports ongoing management of both threats and opportunities. It gives the team a single place to classify risks, assign ownership, document responses, and monitor triggers and escalation as the project progresses.
The key need is a live control artifact for construction risk management, not a one-time assessment or a record for another process. A risk register is designed to capture each uncertain event or condition, classify it appropriately, assign a risk owner, define the chosen response strategy, note triggers, show current status, and indicate when escalation is required. That makes ownership, monitoring, and follow-through clear for both threats and opportunities. By contrast, an IPRA summary helps structure and prioritize risk discussions, but it is not usually the main day-to-day tracking record. The best choice is the artifact that keeps risk decisions actionable throughout delivery, not just identified at the front end.
A risk register is the live artifact that classifies risks and records owner, response, trigger, escalation, and status for ongoing monitoring.
Topic: Contracts Management
On a transit-station project, the owner directed relocation of two equipment pads. The contractor submitted one variation order covering the relocation work, 14 days of delay, and extended site overhead. The owner agrees the relocation is a scope change but disputes the delay and overhead, saying the contractor’s late resequencing caused most of the impact. The contract has separate procedures for variation orders and claims. What should the project manager do next?
Best answer: D
What this tests: Contracts Management
Explanation: When the scope change is agreed but the time or cost impact is contested, the matter is no longer just a routine variation. The team should separate the undisputed change from the disputed impact and start the contract claim process with timely notice and records.
A variation order fits an agreed adjustment to scope, price, or time. Here, the relocation work itself is accepted, but the delay and extended overhead are contested because entitlement and causation are disputed. That makes the impact portion a claim, not a routine variation item.
Going straight to dispute resolution skips the normal claim-management path, and logging this as a risk is incorrect because the event has already occurred. The key distinction is agreed change versus disputed entitlement.
Disputed delay and overhead are claim matters, so the team should move that portion into the claim process instead of keeping it in routine variation handling.
Use the PMI-CP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.
Read the PMI-CP guide on PMExams.com, then return to PM Mastery for timed practice.