Study PMI-CP scenarios by naming the method and the contract term before reading the options. Keep a decision log: for every practice item, record which schedule or cost technique applies, which contract clause drives the answer, and which construction-specific action (RFI, notice, change proposal, updated look-ahead) is available alongside any generic one.
Telling CPM, Look-Ahead Planning, and Time Impact Analysis Apart
CPM is whole-project network logic; a look-ahead is a short-interval plan of imminent work; a time impact analysis (TIA) tests how one new event changes the contract schedule. Scenario vocabulary signals which one applies: float and logic ties, constraint lists, or a fragnet.
In a CPM scenario, the useful vocabulary is the forward and backward pass, total float, and the near-critical path. When a question describes a schedule submittal, an update, or a dispute over which activities drive completion, your first step is to trace the logic ties rather than the crew sizes. A reading habit that pays off: underline every date and every dependency in the stem, then ask whether the critical path as described can actually support the claimed completion date.
A look-ahead answers a different question — what can start in the next few weeks and what constraints block it — so a scenario that mentions a three-week window, material deliveries, or permit availability is asking about constraint clearing, not network recalibration. A TIA is narrower still: you insert a small fragment of new logic (a fragnet) into the accepted schedule to forecast one event's effect. Practice by labeling ten short scenario stems as CPM, look-ahead, or TIA; a reliable self-check is naming the question each method answers before looking at any answer options.
- CPM: whole-project network, float, and critical path — use when the stem concerns baseline logic or a schedule update.
- Look-ahead: short-interval constraints (deliveries, permits, inspections) — use when the stem concerns imminent work readiness.
- TIA: insert a fragnet into the accepted schedule — use when one specific event's schedule consequence must be forecast.
Matching the Contract and Delivery Type to the Decision
Design-bid-build, design-build, and construction-management delivery change who holds design risk; lump sum, GMP, unit price, and cost-plus change how payment is earned. Many scenario answers only make sense once you identify which of these the stem has named.
Delivery method governs who coordinates design and constructability. In design-bid-build, a design ambiguity typically becomes an RFI to the designer through the owner's channel; in design-build, the same ambiguity is often an internal constructability review inside one contracting entity. When a practice stem describes a drawing conflict, ask which party holds design responsibility under the stated delivery method before evaluating the options — the same field condition produces different correct actions in each structure.
Payment terms govern how money moves and what must be documented. Under lump sum, progress is measured against milestone or percentage-complete rules; under unit price, measured quantities drive payment, so quantity surveys become the controlling record; under cost-plus, auditable cost records matter most. Use the table below as a decision aid while drilling: read a stem, name the payment basis, then predict which document the scenario should turn on — a pay application, a measured quantity sheet, or a cost ledger. The table is a routing aid for scenario decisions, not a ranking of which contract is best.
| Payment basis | Price certainty for owner | What drives payment | Scenario cue to notice |
|---|---|---|---|
| Lump sum | High for the owner | Agreed price, often tied to milestones or percent complete | Disputes over what the fixed price included |
| Guaranteed maximum price (GMP) | Shared: contractor absorbs overruns up to the cap | Reimbursable costs within the cap, plus fee and savings terms | Cost reporting, contingency use, savings-share language |
| Unit price | Quantity risk stays partly with the owner | Measured installed quantities times unit rates | Quantity surveys and remeasurement disputes |
| Cost-plus (with fee) | Low unless capped | Documented, allowable costs plus the fee | Audit trails and allowable-cost definitions |
Separating Earned Value, Committed Cost, and Amounts Billed
Earned value compares planned, earned, and actual amounts for performance; committed cost captures what contracts and purchase orders obligate you to spend; billed amounts reflect invoicing. Conflating them produces forecasts that look healthy while obligations quietly exceed budget.
Worked scenario: at month six of a lump-sum fit-out, the schedule shows planned value of 500,000, earned value of 450,000, and actual costs of 520,000. A plausible mistake is to report a cost variance of negative 70,000 and a CPI of about 0.87, then stop — declaring performance known. The better decision adds the commitment layer: subcontracts and purchase orders already obligate 640,000 against a 1,000,000 budget, so future spend is largely locked before any remaining work is priced. The two views answer different questions, and only together do they forecast the outcome.
Why it matters: earned value indices describe performance to date; commitment analysis describes exposure to come. A project can show a modest CPI erosion while its committed position makes the estimate at completion far worse — or vice versa when change orders are pending but uncommitted. In practice drills, compute CV, SV, and CPI, then separately list committed, incurred, and remaining-to-commit amounts, and write one sentence on what each layer implies. If your one-liner for either layer could describe the other, rerun the exercise until the distinction holds without notes.
- Performance layer: EV, PV, AC → CV, SV, CPI, SPI.
- Obligation layer: committed (contracts and POs) versus incurred versus remaining to commit.
- Self-check: any forecast sentence that mixes the two layers fails the exercise.
Routing Issues Through RFIs, Notices, Change Orders, and Claims
An RFI seeks information; a notice preserves rights under a contract provision; a change proposal or change order settles scope, time, and price; a claim resolves disagreement after settlement fails. Choosing the wrong instrument — or skipping the notice step — changes the outcome of scenario answers.
Worked scenario: an excavation crew exposes soil materially different from the geotechnical report. The superintendent emails the owner's site representative informally, keeps working, and submits a full cost and time claim twenty days later. The plausible mistake is treating the email as sufficient: many construction contracts contain notice provisions requiring written notice within a stated timeframe as a condition of entitlement, supported by contemporaneous daily records as the cost basis. The better decision is a written notice referencing the relevant provision that day, stand-down or revised-method documentation in the daily report, and a change proposal once scope and cost are quantified — with the claim reserved only if settlement fails.
Why it matters: the entitlement analysis in such scenarios runs through procedure, not just merit. An RFI is the right instrument for a drawing ambiguity, but it cannot recover time or cost; a change order needs agreement, so unresolved disagreement routes to the claims mechanism the contract names. Drill this as a routing exercise: for each stem, name the instrument, the clause that governs it, and the record that supports it. A completed self-check entry should read like: 'differing condition → notice under the changes/differing-conditions provision → daily reports and photos → change proposal.'
Reading Delay Scenarios: Baselines, Windows, and Concurrency
Delay analysis compares an as-planned baseline against as-built progress, usually across time windows, to find which events actually delayed the critical path. Concurrency and float ownership decide how two overlapping delays are treated — assumptions the stem must supply.
Start every delay scenario by asking three questions. First, against which schedule — the accepted baseline or an update — is impact measured? Second, did the event actually push the critical path, or only an activity with float? Third, do two delays overlap on the same critical path (concurrency), and does the contract or governing provision say how concurrent owner and contractor delays are treated? A stem that says an activity 'slipped ten days' is incomplete until you check whether that activity held float; the completion-date consequence may be zero.
A short worked comparison makes the mechanics concrete: suppose an owner-directed change adds ten days to a critical design activity while a contractor staffing shortage stalls a parallel critical activity for five overlapping days. Under a windows-style analysis, the window containing both events shows a critical path driven by concurrent impacts, and the treatment of the overlapping period depends on the contract's concurrency language — it is not a universal rule you can assume. Practice by sketching two bars, marking float, and writing which window controls. If you cannot name the schedule, the window, and the concurrency assumption, you are not ready to evaluate the options yet.
Ethics, Safety Documentation, and Standards in Case Analysis Items
Case-style scenarios in the ethics, safety, and professional-standards area call for documented, standards-aligned action over expedient fixes: accurate daily reports, honest progress reporting, inspection records, and exercising stop-work authority through proper channels.
The teachable pattern in these scenarios is that the defensible action leaves a record and follows the defined channel. Reporting a schedule forecast honestly even when it is unwelcome, recording a safety observation in the daily log, documenting an inspection refusal, or escalating through the contractually defined route all share a structure: identify the standard at issue, choose the action consistent with it, and preserve the documentation. When an option offers a convenient silence — adjusting a report, skipping an inspection entry, backdating a record — treat it as a distractor in your practice drills, whatever the field pressure described.
For safety-specific stems, keep the reasoning on paper: recognize the hazard, name the documentation it should generate (toolbox talks, inspection entries, corrective-action tracking, stop-work per the project's defined authority), and select the procedural response. Never treat these scenarios as instructions for field practice — the learning objective is deciding and documenting, not performing hazardous work unsupervised. A quick rubric for each ethics or safety stem: could you point to the standard violated by the wrong option, the clause or policy that authorizes the right action, and the record the right action produces? Three yes answers indicate a sound decision.
A Preparation Sequence, Decision-Log Exercise, and Readiness Checks
Sequence preparation in three passes: concepts and terminology, scenario drills with a decision log, then timed case analysis. Finish with readiness checks tied to what you can demonstrate — labeling methods, computing indices, routing instruments — not to a predicted score.
A realistic, adaptable sequence: weeks one and two, build fluency in the named methods — CPM mechanics, EVM formulas, contract and payment types, the RFI/notice/change/claim routing — making one summary card per method that states the question it answers. Weeks three and four, drill scenario items and, after each one, write a decision-log entry (method, contract term, action, record) before checking the explanation; wrong answers become log corrections, not memorized letters. Week five, mix timed case sets, then review the log for categories where your routing or computations hesitate.
The core exercise is the decision log itself. Take ten practice scenarios and, for each, record before answering: the schedule or cost method invoked, the contract or policy term that governs, the construction-specific action, and the supporting record. Expected observations after ten entries: your hesitations cluster — commonly at payment-basis routing, TIA versus CPM labeling, or notice timing — rather than spreading evenly. Suggested milestone checks (learning targets, not passing predictions): label the governing method in under a minute; compute CV, SV, CPI, and SPI without notes; state which schedule a delay is measured against; name the instrument and clause for a change scenario. Administrative details such as eligibility and scheduling sit with the issuer — verify current requirements directly on PMI's certification pages.
- Pass 1 (concepts): one summary card per method stating the question it answers.
- Pass 2 (drills): decision-log entry before checking any explanation.
- Pass 3 (case sets): timed mixed practice, then review the log for weak routing categories.
- Readiness check A: ten labeled scenarios with zero method-mislabels on retake.
- Readiness check B: EVM indices computed unaided; commitment layer described separately.
- Readiness check C: every change scenario answered with instrument, clause, and record named.
References and further reading
Use these references to explore the concepts and check the latest information from the relevant organizations.