Free AACE PSP Full-Length Practice Exam: 119 Questions

This free full-length AACE PSP practice exam includes 119 original PM Mastery questions across the exam domains.

The questions are original PM Mastery practice questions aligned to the exam outline. They are not official exam questions and are not copied from any exam sponsor.

Count note: this page covers the 119-question multiple-choice and scenario-question portion of PSP practice. AACE’s official PSP format also includes a communication memo assignment, so use this page as a diagnostic for the question section and rehearse the memo response separately before exam day.

How to run this diagnostic

Set a 240-minute timer and answer the 119 question-section items before reading explanations. Track misses by planning, scheduling, scenario interpretation, or schedule-communication weakness.

How to interpret your result

Use this page as a PSP question-section diagnostic, not as a complete replacement for the full exam experience. The most useful result is the pattern behind your misses.

Score interpretation worksheet

Use this worksheet immediately after the run, before rereading the explanations.

For concept review before or after this set, use the AACE PSP guide on PMExams.com.

What PM Mastery adds after this diagnostic

This static page is useful for one full diagnostic pass through PSP-style questions. PM Mastery is the better place for repeated practice because it gives you varied attempts, focused scheduling drills, and progress history instead of one page you can memorize.

Pacing and review plan

For the cleanest diagnostic result, answer the questions under timed conditions before reading the explanations.

Retake protocol

If you retake this free diagnostic, treat the second attempt as a reasoning check rather than a fresh score. Some stems and answers will be familiar, so the percentage can overstate readiness.

For readiness decisions, give more weight to varied timed attempts in PM Mastery and a separate memo-response rehearsal than to repeating one static page.

Exam snapshot

Full-length exam mix

Practice questions

Questions 1-25

Question 1

Topic: Conduct Scheduling Duties

A contractor asks to rebaseline because overall SPI fell from 0.98 to 0.92 over the last three monthly updates and the owner turnover milestone forecast moved from October 10 to October 24, 2026. The current data date is March 31, 2026; the last detailed critical-path review was February 15, 2026, before two logic revisions, and one turnover-related change request is still pending approval.

Which evidence best validates whether a recovery plan or a rebaseline recommendation is supportable?

• A. A milestone summary showing which Level 1 dates slipped since baseline.
• B. A recovery narrative prepared before the latest logic revisions.
• C. A March 31 driving-path review tying turnover slippage to current logic, float loss, and approved-versus-pending change impacts.
• D. An earned-value chart confirming the three-period SPI decline.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: Trend data can show deterioration, but it does not by itself justify recovery or rebaseline decisions. Because the last path review is stale and a change affecting turnover is still pending, the best validation is a current driving-path analysis tied to the latest status and change-control facts.

The core concept is that schedule trends are screening indicators, not stand-alone proof for recovery or rebaseline decisions. In this scenario, the SPI decline and milestone slip show a problem, but the last detailed critical-path review is older than the latest logic changes, and a turnover-related change is still pending approval. The strongest validation is a current, data-date review of the driving path to turnover that shows which activities are now driving, how float has been consumed, and whether the movement comes from execution slippage or from change impacts that are approved, pending, or rejected.

• Confirm the March 31 update is current and logic-driven.
• Identify the present driving path to turnover.
• Separate approved change impact from baseline performance variance.
• Use that result to support recovery analysis or a formal baseline-change request.

Overall trend charts and older narratives help frame the discussion, but they are too limited or stale to support the control decision alone.

It is the only option that connects the current turnover slip to present driving logic and distinguishes execution delay from change impact.

Question 2

Topic: Conduct Scheduling Duties

A scheduler is finalizing the baseline for a substation upgrade. The contractual energization milestone is September 30. The critical path uses shortest-case field durations, and the schedule includes a separate 12-workday activity named Contingency immediately before energization.

Exhibit:

Cable pull planned = 8d; historical range = 8-12d
Terminations planned = 6d; historical range = 6-9d
Functional test planned = 5d; historical range = 5-7d
Contingency activity = 12d
Risk register link = none
Trigger for using contingency = none

Which diagnostic/correction best addresses the real issue?

• A. Distribute contingency days into critical activities to protect field crews.
• B. Increase contingency until the energization milestone has positive float.
• C. Add a finish-no-later-than constraint on the energization milestone.
• D. Use realistic durations and document risk-linked contingency with clear triggers.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The problem is not that contingency exists by itself; it is that the schedule combines optimistic activity durations with an arbitrary reserve that has no documented uncertainty basis. Credible contingency should be explicit, traceable, and linked to identified uncertainty and use conditions.

Schedule contingency is valid only when it is tied to credible uncertainty, not when it compensates for best-case planning or hides padding. In this scenario, the planned durations sit at the optimistic ends of the historical ranges, while the 12-day contingency has no linked risk, no trigger, and no documented basis. That weakens forecast credibility because the schedule is protected partly by unsupported optimism and partly by an unexplained reserve. The best correction is to restore realistic durations for the field work and keep any contingency transparent, documented, and linked to identified uncertainty or approved risk analysis, including when it may be consumed. Actions that simply add more days, bury reserve inside activities, or force dates with constraints do not improve the integrity of the schedule model.

Transparent contingency supports control; hidden padding and forced dates do not.

This removes unsupported optimism from the activities and makes contingency traceable to documented uncertainty instead of hidden padding.

Question 3

Topic: Conduct Scheduling Duties

An outage project’s integrated baseline schedule has completed review, and the team agreed it is ready for control use as of July 1, 2026.

Current records

Retained: PDF baseline bar chart, emailed milestone dates
Not retained: approved native schedule file, basis of schedule,
              key calendars/constraints record, approval log

Before the first status update, what is the next appropriate step?

• A. Replace the baseline after actual starts are entered in the working file.
• B. Discuss future milestone impacts qualitatively until better records are available.
• C. Proceed with the first update using the PDF as the baseline reference.
• D. Freeze and archive the approved baseline package under change control.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The next step is to preserve the approved baseline evidence before any statusing begins. A PDF and milestone email do not capture the approved logic, calendars, constraints, and assumptions needed for reliable forecast comparison, change control, or schedule-impact discussions.

Baseline control requires more than visible dates on a report. Before the first update, the team should freeze the exact approved schedule model and its supporting basis so later status updates can be compared to a stable reference.

That baseline evidence should preserve items such as:

• the approved native schedule file
• the basis of schedule and key assumptions
• calendars, constraints, and milestone commitments
• the approval record used for change control

Without that package, the working file may change before anyone can prove what was actually approved, which weakens variance analysis and delay or impact discussions. Using only a PDF preserves appearance, not the underlying schedule logic or controls evidence.

A controlled baseline package preserves the exact approved model and assumptions needed for later updates, comparisons, and impact analysis.

Question 4

Topic: Conduct Scheduling Duties

Data date: July 31, 2026. All activities use a Monday-Friday calendar. In the current update, the contractual milestone “Mechanical Completion” has a required finish of August 14, 2026, but the forecast finish is August 21, 2026, so the driving path shows total float of -5 workdays. No change order or baseline-change approval has been issued. The project manager asks the scheduler to “update the baseline to the forecast so the report stops showing negative float.” What is the best action?

• A. Remove the required-finish date so the schedule reflects current execution reality and eliminates the negative float.
• B. Classify the negative float as a future risk and wait until the next update cycle before escalating it.
• C. Rebaseline the milestone to August 21 because negative float confirms the original baseline is no longer achievable.
• D. Keep the baseline unchanged, validate the driving path and required-finish logic, and report the late forecast with recovery or formal change-control options.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: Negative float means the current forecast is missing an imposed required date or similar constraint. Here, the scheduler should verify the cause, keep the approved baseline intact, and communicate the variance plus recovery or change-control needs instead of rebaselining automatically.

Negative float is a schedule-control signal, not approval to rewrite the baseline. In this update, the forecast finish is later than the contractual required finish, so the schedule is showing a real date problem that must be analyzed and communicated. The professional response is to confirm that the required-finish constraint and driving logic are valid, identify the activities causing the slippage, and present recovery options or a formal change request if the commitment truly cannot be met. Because no baseline-change approval exists, replacing the baseline with the forecast would hide variance rather than control it. Removing the required date would also distort the model. The key takeaway is that negative float points to a forecast or constraint issue that needs analysis and decision-making, not automatic rebaselining.

Negative float shows the forecast is later than the required date, so it should trigger analysis, communication, and approved control action rather than an automatic rebaseline.

Question 5

Topic: Conduct Scheduling Duties

At the June 14, 2026 data date, a turnaround update shows:

• Baseline mechanical completion: July 28, 2026
• Current forecast mechanical completion: August 6, 2026
• Critical path: valve replacement -> loop checks -> mechanical completion
• Startup must occur in the outage window ending August 3, 2026; otherwise startup moves to August 18, 2026
• Recovery to July 31 would require 8 instrument technicians for two weeks; only 5 are committed
• Securing the extra technicians would add $120,000 in overtime and premium labor
• Current performance indices: SPI = 0.92, CPI = 1.04

Which message is best for senior stakeholders?

• A. Cost performance is favorable at CPI = 1.04, so the update should emphasize the $120,000 labor premium and not elevate delivery concerns yet.
• B. Because recovery remains possible, the update should report SPI = 0.92 as moderate schedule pressure and wait until the next cycle before discussing startup impact.
• C. The stakeholder message should focus on requesting overtime approval, because the outage window and startup date are operational details rather than executive schedule issues.
• D. As of June 14, mechanical completion forecasts August 6, so startup shifts to August 18 unless management immediately secures three more technicians. The delay is driven by a critical-path resource shortfall, with a $120,000 recovery cost and a direct delivery consequence.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The strongest message starts with the current forecast, then links that schedule result to the resource shortfall, recovery cost, and delivery consequence. Favorable cost performance does not remove the need to communicate that the current forecast misses the outage window.

This item tests integrated schedule-control communication. Senior stakeholders need a message that explains what the schedule now forecasts, why it changed, what it could cost to recover, and what delivery outcome is affected. Here, the key fact is that mechanical completion is forecast for August 6, which is beyond the August 3 startup window, and the recovery plan is not yet credible because the schedule needs 8 technicians but only 5 are committed on the critical path. The best message therefore connects schedule impact, resource constraint, recovery cost, and startup consequence in one decision-oriented statement. A message centered only on CPI or overtime cost drifts into cost-only analysis and misses the real schedule-control issue.

The key takeaway is that integrated schedule reporting must show how date movement affects resources, cost, risk exposure, and delivery commitments together.

This message ties the current forecast to the critical-path resource constraint, the recovery cost, and the startup-window delivery impact.

Question 6

Topic: Conduct Scheduling Duties

During baseline validation for a refinery shutdown schedule, the project restart milestone is forecast for October 14, 2026. The planner confirms the critical path is fully logic-linked and the dedicated shutdown crew is available.

Approved basis of schedule: Shutdown-area work allowed Monday-Friday only, 10-hour shifts
Baseline model: Exchanger removal, install, hydrotest, and startup use a 7-day calendar
Constraints on these activities: none

Which correction best addresses the real issue?

• A. Trace the WBS for omitted shutdown scope
• B. Recalculate using the approved Monday-Friday access calendar
• C. Expand the baseline narrative to justify weekend execution
• D. Add a finish-no-later-than constraint to the restart milestone

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: This is a calendar-assumption problem. The approved basis allows shutdown-area work only Monday through Friday, but the critical activities were modeled on a 7-day calendar, so the forecast date is not credible until the correct calendar is applied and the schedule is recalculated.

Baseline validation checks whether the schedule model matches the approved basis of schedule, not just whether the milestone date looks acceptable. In this case, logic completeness, resource availability, and lack of hard constraints have already been confirmed, so those are not the primary concerns. The actual mismatch is between the approved work-window assumption and the activity calendars used on the critical path.

Because the model assumes 7-day execution for work that is only allowed Monday through Friday, the elapsed dates are understated. The proper fix is to assign the approved access calendar to the affected activities and rerun the network before baseline approval. Adding a constraint or improving the narrative would only hide or describe the issue, not correct the underlying schedule model.

The baseline uses a 7-day work pattern that conflicts with the approved work-window assumption, so the activity calendars must be corrected and the schedule rerun.

Question 7

Topic: Conduct Scheduling Duties

At the August 6, 2026 data date, field status shows activity EL-145 Install MCC lineup needs 3 additional workdays beyond its prior remaining duration. In the current accepted update, EL-145 is on the driving path to the dates below.

The project controls manager asks what this delay affects. What is the next appropriate step?

• A. Submit a rebaseline request because the activity forecast has changed.
• B. Notify stakeholders that all three driven dates slip by 3 workdays before recalculation.
• C. Update EL-145, reschedule, and compare the 3-day delay with float on each driven date.
• D. Evaluate only project-finish float, since intermediate dates do not control delay reporting.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: A late activity can affect different downstream dates differently. The proper next step is to status the activity in the current schedule model, recalculate, and compare the added delay with the float available to each driven handoff, contractual milestone, and project finish date.

The core concept is that delay impact is date-specific. An activity may drive several downstream commitments, and the same delay can consume float on one date, make another date late, and still leave the overall project finish unaffected. The scheduler should first incorporate the new remaining duration at the data date and reschedule the network.

Then review the driving path to each downstream date and compare the 3-workday delay with the available float shown for each commitment. In this case, the handoff is most exposed, the contractual turnover milestone may lose all float, and the project finish may still retain float. That determination should come from the updated logic-driven forecast, not from assumption, rebaseline action, or finish-only reporting.

The closest distractor is the one focusing only on project-finish float, because earlier contractual or interface dates can be affected first.

Delay impact must be tested against each driven handoff, milestone, and finish date in the current schedule model, not assumed from one date alone.

Question 8

Topic: Conduct Scheduling Duties

An outage scheduler proposes the following structure for Area 4 before baseline approval.

Exhibit:

Element 1: "Area 4 turnover" — 0-day contractual event
Element 2: CA-4100 — management control point for piping budget and responsibility
Element 3: PP-4100-02 — authorized future rework scope; detail activities will be defined next update
Element 4: "Area 4 supervision" — should span from first piping start to final test package closeout
Element 5: WBS, area, discipline, and responsible engineer fields — used for sorting and filtering
Proposal: link CA-4100 directly to predecessors and successors until detail planning is finished

Which analysis is best?

• A. Turnover is a milestone; CA-4100 is a control account; PP-4100-02 is a planning package; supervision is a hammock; codes support traceability, and logic belongs on activities or milestones.
• B. Turnover and supervision should be coded elements only, while CA-4100 temporarily carries the forecast dates until the package is decomposed.
• C. CA-4100 should act as the summary activity that carries logic, and PP-4100-02 should be treated as a detailed activity because budget exists.
• D. PP-4100-02 is the control account, supervision should be a summary roll-up, and milestones are reserved for completed work.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The best analysis classifies each element by its modeling purpose, not by convenience. The turnover point is a milestone, the management point is a control account, the not-yet-detailed authorized scope is a planning package, the spanning oversight item is a hammock, and codes are for traceability rather than schedule logic.

In a credible schedule model, each element has a distinct role. The 0-day turnover commitment is a milestone because it marks an event, not duration-based work. CA-4100 is a control account because it is the management control point for budget and responsibility; it should not carry predecessor-successor logic in place of real work. PP-4100-02 is a planning package because the future scope is authorized but not yet decomposed into detail activities. The supervision span is a hammock because it stretches between the start and finish of other work. WBS, area, discipline, and owner fields are coded elements used for sorting, filtering, and traceability. A summary activity, if used, should only roll up subordinate work for display or reporting. The key error in the weaker choices is confusing management or reporting structures with logic-driven schedule elements.

It correctly separates event, management, future-scope, span, and coding functions, and it avoids using the control account as a logic carrier.

Question 9

Topic: Conduct Scheduling Duties

A scheduler is preparing the July monthly review for a substation commissioning project. Which recommendation should be prioritized for the executive review?

Data date: July 31, 2026
Overall SPI (EV/PV): 0.99; prior month 1.01
Project finish: baseline Dec 15, 2026; forecast Dec 22, 2026
Substantial Completion: baseline/required Oct 31, 2026; forecast Nov 12, 2026
Milestone forecast trend: Oct 31 -> Nov 5 -> Nov 8 -> Nov 12
Driving path total float: -8 workdays
What-if recovery: second test crew starting Aug 10 recovers 7 workdays
Resource note: second test crew is available; use requires construction manager approval
Non-driving landscaping float: +18 workdays
No approved baseline change exists

• A. Lead with SPI 0.99 and wait one more update before acting
• B. Escalate the completion milestone slip against baseline and recommend approving the second test crew recovery
• C. Reset the baseline to the current forecast before discussing impact
• D. Accelerate landscaping first because it has the most available float

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The best priority is the worsening Substantial Completion milestone, not the near-plan SPI alone. The milestone is slipping update after update, its driving path already has negative float, and a feasible analyzed recovery exists, while the baseline must remain the control reference because no change has been approved.

Schedule interpretation should combine overall indicators with milestone-level evidence. Here, SPI of 0.99 is close to plan, but the contractual Substantial Completion milestone has moved from its October 31 baseline date to a November 12 forecast, and that forecast has worsened at each update. The driving path already shows -8 workdays of total float, so this is an active schedule-control problem, not something to defer because SPI is near 1.0. Since no approved baseline change exists, the baseline remains the reference for variance reporting and should not be replaced by the forecast. The only supplied corrective action tied to the driving path is the second test crew, and the what-if run shows it can recover 7 workdays if management approves its use.

A near-1.0 SPI does not outweigh a slipping contractual milestone with negative float and a validated recovery option.

It addresses the worsening contractual milestone variance using the baseline as the control reference and the only analyzed recovery on the driving path.

Question 10

Topic: Conduct Scheduling Duties

As of the May 15, 2026 data date, the monthly update is complete and validated. The baseline date for Ready for Start-Up is June 30, 2026, and the current forecast before any new change is July 2, 2026. The driving path is Cable pull -> Terminate panels -> Loop checks -> Ready for Start-Up, all on a 6-day workweek calendar, and that path has 1 workday of total float to the July 3, 2026 contractual required date. Change order CO-08 is approved and adds a 2-workday Client witness test between Loop checks and Ready for Start-Up on the same calendar. What is the next appropriate step?

• A. Add the approved activity and logic to the current statused schedule, recalculate, and record the incremental impact.
• B. Wait until the next status cycle to insert the change so this period’s variance stays comparable.
• C. Extend the milestone forecast by 2 workdays in the report without changing the schedule logic.
• D. Rebaseline the milestone immediately because the approved change has altered the plan.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The next step is to incorporate the approved change into the current statused schedule model and recalculate. That is the only way to evaluate true schedule impact using the actual logic path, the stated calendar, the current forecast, and the baseline or required dates.

In PSP practice, an approved change does not justify manual date edits or automatic rebaselining. The scheduler should first model the approved scope in the current, statused schedule so the impact is calculated through logic and calendar rules.

• Insert the new Client witness test activity with the stated predecessor and successor.
• Assign the same 6-day calendar given in the change facts.
• Recalculate the forecast to see the added effect on the current July 2 forecast, the June 30 baseline, and the July 3 required date.
• Record that impact in the change-control and schedule-impact record.

Because the project is already forecasting later than baseline, the key control step is to isolate the incremental effect of the approved change before any recovery or rebaseline decision.

Approved changes should be modeled in the current schedule with the correct logic and calendar before quantifying impact against forecast, baseline, and required dates.

Question 11

Topic: Conduct Planning Duties

A contractor is seeking approval of the initial baseline schedule for a turbine outage. The owner will use the approved baseline as the contractual control reference for progress reporting. Per the review procedure, post-approval action items are acceptable only if they do not change contractual commitments or invalidate baseline credibility. Which finding should be prioritized first?

Exhibit: Baseline review findings

• A. The baseline milestone misses the contract return date
• B. Two discretionary lags remain on a float path
• C. Near-term procurement remains at planning-package level
• D. Peak scaffolder demand exceeds the draft proposal

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The contract-date mismatch is the highest-priority blocker because it makes the proposed baseline misaligned with an explicit contractual commitment. The other findings are either still allowed by the planning standard, non-driving, or already covered by available resources.

In a baseline-readiness review, the first priority is to remove findings that would make the approved baseline unusable as the control reference. A contractual milestone is not just another planned date; it is a commitment against which performance and variance will be measured. Here, the contract requires return-to-service on May 1, 2027, but the milestone list and schedule show May 8, 2027, and the basis of schedule treats the date as unsettled. That is a direct contract-alignment defect with clear evidence and no sound basis for deferral.

The other findings matter, but they do not presently invalidate approval:

• the planning packages are still outside the detail threshold
• the lags are on a path with float
• the labor peak is already covered by an existing arrangement

The closest distractor is the crew-loading item, but the stem already provides a feasible staffing path.

A baseline cannot serve as the contractual control reference if it already conflicts with an explicit required contract milestone.

Question 12

Topic: Conduct Scheduling Duties

At the June 30, 2026 data date, an EPC project must brief the sponsor on a 21-day slip to the contractual Ready for Startup milestone. The sponsor asks whether to approve immediate recovery overtime or start a rebaseline request before the July steering meeting. No scope change has been approved, no resource-feasible what-if analysis has been completed on the current driving path, and electrical test-crew availability is still unverified.

Exhibit: Recent schedule signals

Which recommendation is the best priority?

• A. Report the slippage now, but require validated current-path recovery analysis before recovery or rebaseline decisions.
• B. Fund steel-erection overtime now because it was the prior update’s driving path.
• C. Start rebaseline approval now because the declining SPI confirms the baseline is no longer valid.
• D. Wait for the July update before communicating so the trend is less uncertain.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The best choice is to communicate the current variance and forecast immediately, but not commit to recovery or rebaseline based on weak evidence. Here, the trend covers only two updates, the driving path changed, and no resource-feasible analysis supports a specific action.

Recovery and rebaseline decisions should be supported by evidence tied to the current critical or driving path, not just by a short trend or an overall SPI decline. In this scenario, the milestone slip is real and should be reported, but the decision basis is still incomplete: only two trend points are shown, the reported driver changed between updates, no approved baseline change exists, and the availability of the electrical test crews on the current path has not been verified.

• Report the baseline variance and current forecast at once.
• Validate the current critical/driving path at the June 30 data date.
• Test feasible recovery options on that path with real resource availability.
• Consider rebaseline only through change control if later evidence justifies it.

Acting on stale or disconnected trend information weakens schedule control just as much as delaying stakeholder communication.

The available trend is limited and the driver changed, so stakeholders should get the current variance now while recovery or rebaseline decisions wait for validated current-path evidence.

Question 13

Topic: Conduct Scheduling Duties

During baseline approval for a refinery shutdown schedule, the scheduler reviews this critical-path activity and basis note. Durations in the schedule must be whole workdays, and any fractional result is rounded up to the next workday.

Use \( \text{required days} = \frac{\text{craft-hours}}{\text{workers} \times \text{hours/day}} \). Which validation conclusion is best?

• A. Accept 6 days; the outage calendar makes the duration achievable.
• B. Change the logic relationship; the duration is not the issue.
• C. Reject as submitted; one crew needs 8 days, so the milestone basis is unsupported.
• D. Delete the Unit Restart milestone until execution confirms resources.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: Baseline validation must test whether durations are achievable under the documented calendar and resource assumptions. Here, 12 workers at 10 hours per day provide 120 craft-hours daily, so 900 craft-hours needs 7.5 days, which rounds up to 8; the 6-day baseline is not credible.

A baseline schedule is only valid if its durations can be achieved with the stated calendars, resources, and basis assumptions. In this case, the basis allows one 12-person crew working 10-hour shifts during a 6-day outage, with no second crew available.

• Daily capacity = \(12 \times 10 = 120\) craft-hours/day
• Required duration = \(900 \div 120 = 7.5\) days
• Whole-day rule => 8 workdays

That means the planned 6-workday duration is not supported by the resource assumption or the basis of schedule. Because this activity directly precedes the Unit Restart milestone on the critical path, the milestone is also not credible as currently baselined. Changing logic or removing the milestone would hide the validation problem rather than fix it.

One crew provides 120 craft-hours per day, so 900 craft-hours requires 7.5 days and rounds up to 8, making the 6-day baseline unsupported.

Question 14

Topic: Conduct Planning Duties

A contractor submits a baseline schedule for a data-center expansion. Contract milestones must be logic-driven, and the basis of schedule must document key interfaces, calendars, and assumptions. The reviewer recommends withholding baseline approval rather than deferring one finding to the first monthly update. Which review result best validates that recommendation?

• A. Logic review shows the substantial completion milestone is held by a mandatory finish constraint and has no tied commissioning or turnover handoffs.
• B. Reporting review shows the monthly status template is still awaiting the owner’s formatting comments.
• C. Resource review shows future electrical crews are assigned by trade category rather than by named foremen.
• D. Coding review shows several noncritical activities are missing an internal area code used for dashboard grouping.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: A baseline should not be approved when a key contractual milestone is being forced by a date constraint instead of being driven by complete logic. Missing commissioning and turnover handoffs mean the schedule model is not a reliable control baseline, while the other findings are administrative refinements that can be corrected later.

The core issue is baseline readiness and schedule-model credibility. Before approval, major contract milestones should be traceable through the work that actually drives them. If substantial completion is achieved only because of a mandatory finish constraint, and required commissioning and turnover handoffs are not tied into the network, the schedule cannot reliably show driving path, float, or true forecast dates.

That is a baseline-blocking defect because the approved baseline would become the reference for future variance and performance analysis. A routine progress update is for recording actuals and revising remaining work, not for repairing missing foundational logic on a key milestone.

By contrast, missing dashboard codes, unnamed future foremen, and unfinished report formatting do not undermine the baseline’s core schedule logic.

A constrained completion milestone without supporting handoff logic makes the baseline forecast noncredible and should be fixed before approval.

Question 15

Topic: Conduct Planning Duties

A utility substation expansion is preparing its first integrated baseline schedule. The owner’s key commitments are to energize the new transformer by October 15, 2027, and place the full yard in service by November 30, 2027. Engineering wants discipline-based planning packages, construction wants area-based progress reporting, and later monthly updates must explain forecast changes by both contractual milestone and yard area. Baseline approval is due in five days.

Which planning action best preserves traceability from project objectives to the work breakdown, basis of schedule, baseline schedule, and later forecast analysis?

• A. Define a WBS crosswalk and schedule-coding plan linking objectives, milestones, disciplines, and yard areas, and document the related assumptions in the basis of schedule before baseline approval.
• B. Approve the baseline now using discipline logic, then add yard-area and milestone codes during the first monthly update.
• C. Reduce the integrated baseline to contractual milestones only and let each team keep its own detailed schedule.
• D. Choose the construction area breakdown for the baseline and explain discipline impacts later through narrative reports.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The best action is to establish traceability before the baseline is approved, not after. A documented crosswalk and coding structure connects project objectives and contractual milestones to the WBS, schedule model, and future forecast reporting views.

This is a planning-basis problem, not just a reporting preference. Because the project must later explain forecast impacts by both contractual milestone and yard area, while different teams want different working breakdowns, the planning team needs a documented structure that ties those views together before the baseline is frozen. The strongest action is to define the WBS crosswalk and schedule codes, then record the governing assumptions, calendars, and logic basis in the basis of schedule so the approved baseline and later updates can be analyzed consistently.

• Link objectives and contract milestones to WBS elements and activities.
• Define the reporting codes needed for both discipline and area views.
• Capture the rules and assumptions in the basis of schedule before approval.

Adding the structure later may save time now, but it weakens defensible variance and forecast analysis against the approved baseline.

It creates a documented pre-baseline link from objectives and commitments to schedule structure and reporting codes, so later forecast analysis stays traceable to the approved baseline.

Question 16

Topic: Conduct Planning Duties

A utility substation upgrade is entering schedule development. The planning team must decompose the work under these constraints:

• The contract requires separate control of civil, electrical, and commissioning deliverables.
• Monthly status must roll up by responsible manager.
• The energization date is a fixed regulatory commitment.
• Detailed commissioning field scope will not be known until factory testing is complete.

Which action is the best way to structure the work so the schedule can be developed and later controlled?

• A. Keep only top-level deliverables and contractual milestones until all commissioning details are known.
• B. Define detailed activities for all commissioning work now so the entire future scope is fully baselined from the start.
• C. Create a deliverable-based WBS, align control accounts with accountable managers, define near-term activities and milestones, and use planning packages for later commissioning work.
• D. Organize the decomposition only by responsible manager and cost code, then map deliverables after the schedule baseline is approved.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: The strongest planning action is to decompose by deliverables first, then place control where responsibility and reporting need it. Known near-term work should become schedulable activities and key commitments should become milestones, while immature future scope should stay in planning packages until it can be defined credibly.

This is a planning-basis and decomposition decision. The project needs a structure that preserves scope traceability, supports manager-based control, highlights the fixed energization commitment, and avoids false precision for commissioning work that is not yet defined. A deliverable-based WBS satisfies the contract requirement, control accounts support accountability and reporting, near-term defined work can be converted into schedulable activities, and the regulatory date belongs in the milestone structure. Later commissioning scope should remain in planning packages until enough information exists to break it into reliable activities.

• Separate civil, electrical, and commissioning scope in the WBS.
• Align control accounts with the managers who will report performance.
• Define the energization commitment and key interfaces as milestones.
• Hold immature downstream scope in planning packages.

Options that force detail too early or stay too summary both weaken schedule development and later control.

It matches deliverable control, reporting accountability, milestone visibility, and the need to defer immature scope without losing schedule traceability.

Question 17

Topic: Conduct Scheduling Duties

The integrated project schedule is being updated for the June 30 data date. On July 2, the electrical superintendent says feeder cable pull activity E-240 started on June 24, had 2 workdays remaining as of June 30, and actually finished on July 2. The monthly report must compare baseline versus forecast as of June 30, and no baseline change has been approved.

What is the best scheduling action?

• A. Enter the June 24 actual start, keep 2 days remaining at June 30, and let the schedule forecast the finish after the data date
• B. Move the data date to July 2 so the activity can be shown as actually finished in this update
• C. Keep the activity 100% complete at June 30 and align the baseline dates to the new finish
• D. Enter the July 2 actual finish now because the work is complete before the report is issued

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: A schedule update must reflect actual status only through the stated data date. Because the activity still had 2 workdays remaining on June 30, the finish on July 2 belongs in the forecast at that update, not as an actual finish posted beyond the data date.

The core concept is status-date discipline. When the update is for June 30, actual starts, actual finishes, percent complete, and remaining duration must represent conditions as of June 30 only. Here, the reliable status is that E-240 started on June 24 and still had 2 workdays remaining at the data date, so the schedule should calculate a forecast finish after June 30.

Using the July 2 completion as an actual finish in the June 30 update would mix future actuals into an earlier status point and distort variance and update reliability. Moving the data date to July 2 would also change the reporting basis. The baseline remains the approved reference and should not be overwritten by current performance.

The key takeaway is: keep the data date fixed, record actuals only through that date, and let future work appear as forecast until the next update cycle.

This preserves status-date discipline by recording only actual progress known as of June 30 and using a forecast, not a future actual, beyond the data date.

Question 18

Topic: Conduct Planning Duties

During baseline planning for a refinery turnaround, the owner asks the scheduler to constrain the Unit Restart milestone to an outage window of October 12-16. The contract makes restart a required milestone, but the outage approval is still marked draft and several vendor dates remain planning assumptions. Before using the date constraint in the schedule model, which documentation package should the planner prioritize in the basis of schedule?

• A. Document expected float loss, reporting thresholds, and post-baseline recovery ideas for management updates.
• B. Document the requested date, stakeholder preference, and a plan to replace baseline dates if the forecast slips.
• C. Document vendor target dates and sequence preferences, then refine missing logic after the constraint is added.
• D. Document the governing source/control reference, approval status, exact window/calendar, constraint type, affected milestone, and supporting assumptions.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: Before a date constraint is used, the planner should document where the required date comes from, whether it is approved or still an assumption, the exact calendar or window it uses, and what schedule element it governs. That preserves model integrity and distinguishes a true external requirement from a preference or unresolved uncertainty.

In PSP practice, a date constraint is not a substitute for incomplete logic or unsupported optimism. Before placing one in the schedule model, the basis of schedule should record the governing source of the required date, its approval status, the exact date or allowable window and calendar, the activity or milestone affected, the intended constraint type, and the assumptions or exclusions that still apply. Those facts let reviewers determine whether the constraint is tied to a real contractual or external requirement or only to a draft request. That distinction matters because constraints can hide float consumption and distort the forecast if they are applied without evidence. Options focused mainly on reporting, future recovery, or preliminary preferences do not create a defensible planning basis.

A date constraint should be backed by documented authority, timing basis, and assumptions so it reflects a real external requirement rather than masking uncertainty.

Question 19

Topic: Conduct Planning Duties

During planning for a utility substation upgrade, the team is developing the baseline integrated schedule. Constraints:

• The contract requires one monthly project data date.
• A permit-to-operate milestone has liquidated damages.
• Vendor fabrication and site installation will be statused by different organizations.
• The owner has rejected prior projects’ vague “50% complete” reporting.

Which planning improvement would most directly reduce later update ambiguity and improve forecast reliability?

• A. Document objective progress rules, evidence sources, calendars, and handoff milestones.
• B. Add finish-no-later-than constraints to interim contract dates.
• C. Let each contractor use its preferred status-reporting method.
• D. Decompose all work to one-week activities across the schedule.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The best planning improvement is to define, before baseline approval, exactly how progress will be measured and evidenced for each activity type and interface. That creates consistent update inputs, clearer handoffs, and more defensible forecast and impact analysis later.

In PSP practice, many forecast and dispute problems begin as planning weaknesses rather than update mistakes. Here, the main risk is inconsistent statusing across multiple organizations plus ambiguous handoffs between vendor and field work on a contract-sensitive milestone. The strongest improvement is to document, in the basis of schedule, objective progress-measurement rules, required evidence sources, applicable calendars, and explicit interface milestones. That gives each updater the same rules for status collection and makes later variance, forecast, and schedule-impact analysis traceable to agreed assumptions. Adding more constraints or more blanket detail may make the schedule look tighter, but it does not solve the core problem of inconsistent status evidence and unclear interfaces.

Clear status rules, evidence, calendars, and interface definitions create consistent update inputs and a defensible forecast basis across organizations.

Question 20

Topic: Conduct Scheduling Duties

Data date is October 31, 2026. The approved baseline shows Substantial Completion on December 15, 2026. After statusing actual progress and revised remaining durations, the current schedule forecast moves Substantial Completion to January 3, 2027 because a critical transformer delivery is already 19 calendar days late on the driving path. The contractor has submitted a time-extension request, but the owner has not approved any change order, rebaseline, or contractual relief. In the monthly schedule update, what is the best action?

• A. Report January 3 as the forecast, keep December 15 as the baseline, and show the request as pending.
• B. Show January 3 as approved contractual relief because the delay cause is documented.
• C. Reset the baseline to January 3 so the update reflects current reality.
• D. Keep the forecast at December 15 until the time-extension request is decided.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: A forecast update shows the current expected finish based on status as of the data date. It does not revise the approved baseline, and it does not mean a pending time-extension request has been granted. The update should show the later forecast against the original baseline and identify the contractual request as unresolved.

The key distinction is between a schedule forecast and formal approval actions. At the October 31, 2026 data date, the scheduler must incorporate actual progress and the known late transformer delivery, so the current forecast should move to January 3, 2027. That later forecast is a status-and-forecast result from the schedule model.

The approved baseline stays at December 15, 2026 until formal change control authorizes a baseline revision or rebaseline. Likewise, a submitted time-extension request is only a pending contractual action; it is not approved relief, accepted claim entitlement, or an approved schedule change. A sound update therefore reports the baseline date, the forecast date, the variance cause, and the pending status of the request.

A later forecast is a control signal for decision-making, not automatic approval of anything.

A forecast update must reflect current status, while baseline changes and contractual relief require separate formal approval.

Question 21

Topic: Conduct Scheduling Duties

At the June 30, 2026 data date, you are preparing a steering-committee update about a critical-path delivery risk. Which statement best supports stakeholder decisions about the August 20 outage commitment, date uncertainty, and response ownership?

Exhibit:

Data date: June 30, 2026
Milestone: Mechanical Completion
Baseline date: August 15, 2026
Deterministic forecast: August 15, 2026
Customer outage commitment: August 20, 2026

Risk: Imported switchgear may clear customs late
Trigger: Final shipping documents not approved by July 5, 2026
Impact if triggered: 10 workday delay to a critical-path delivery
Current probability: 40%
Risk analysis output: P50 August 18, 2026; P80 August 25, 2026
Planned response: Expedite document approval by July 3, 2026
Response owner: Procurement manager

• A. As of June 30, baseline and deterministic forecast remain August 15, but a 40% customs risk triggered after July 5 shifts the range to August 18 at P50 and August 25 at P80; procurement owns the July 3 mitigation, and leaders should confirm contingency for the August 20 outage.
• B. As of June 30, August 25 should replace August 15 in stakeholder reports because the P80 date is the safest commitment.
• C. As of June 30, report August 18 as the single expected date and assign the response to the scheduler because the risk affects the schedule.
• D. As of June 30, mechanical completion is still August 15, so the August 20 outage should be reported as secure unless customs delay actually occurs.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The best communication keeps approved dates, current forecast dates, and risk-adjusted dates distinct. It also states the trigger, the uncertainty range, the response owner, and the management decision needed on the August 20 commitment.

Good schedule risk communication helps stakeholders decide, not just react. In this case, the baseline and deterministic forecast are still August 15 as of the June 30 data date, but there is a defined risk that could threaten the August 20 outage commitment. The strongest statement therefore does four things at once: separates current status from uncertain outcomes, states the trigger date, shows the risk range using the supplied P50 and P80 dates, and identifies who owns the response.

• Keep the approved baseline separate from the current forecast.
• Treat the customs delay as a risk until the trigger is actually hit.
• Show uncertainty explicitly instead of reporting one forced date.
• Name the response owner and the decision leaders must make.

Using a conservative date alone is not the same as changing the commitment or the baseline.

It separates baseline, forecast, and uncertainty while naming the trigger, owner, and decision needed on the commitment.

Question 22

Topic: Conduct Scheduling Duties

As of the May 31 data date, the approved baseline shows system turnover on July 31. In the update, the field team confirms owner-directed retesting will add 6 workdays, moving the forecast turnover to August 8. The retesting direction is real, but no change order or baseline revision has been approved. What is the best control action?

• A. Add a July 31 constraint to preserve the commitment.
• B. Keep baseline dates, forecast August 8, and process a pending change.
• C. Leave retesting out until formal approval is issued.
• D. Reset baseline dates to August 8 in this update.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: When work is expected to occur, the forecast should show its effect even if the change is not yet approved. The approved baseline remains the performance reference until formal change control authorizes a revision, so the scheduler should report the variance and record the pending change impact.

The key control principle is to protect both forecast credibility and baseline integrity. Because the retesting has been directed and is expected to happen, the current schedule update should include that work and show the August 8 forecast. However, the July 31 baseline milestone must stay unchanged until a formal change is approved; otherwise the variance is erased without authorization.

• Status actual progress and remaining work realistically.
• Measure slippage against the approved baseline.
• Record the pending change and its schedule impact through change control.
• Rebaseline only after approval.

The closest trap is excluding the retesting from the update, which makes the report look cleaner but makes the forecast unreliable.

It preserves the approved baseline for measurement while keeping the forecast and change record aligned to known work.

Question 23

Topic: Conduct Planning Duties

During baseline planning, a scheduler is defining objective first-update inputs for activity Cable Pull A. Use the rules and status facts below.

Calendar: Monday-Friday, 1 workday per day
Original duration: 10 workdays
Data date: end of Monday, April 13, 2026
Actual start: Monday, April 6, 2026
Completed workdays from actual start through data date: 6
Installed quantity: 400 of 1,000 m
Earned-progress weights achieved: mobilize 10% + route cleared 15%
Field remaining duration estimate: 5 workdays
First remaining workday after data date: Tuesday, April 14, 2026

Rules:
Percent complete = completed workdays / original duration
Physical progress = installed quantity / total quantity
Earned progress = sum of achieved milestone weights
Forecast finish = data date + remaining duration on the stated calendar

Which status package is correct before the update is entered?

• A. Actual start April 13, 2026; percent complete 60%; physical progress 40%; earned progress 25%; forecast finish April 20, 2026.
• B. Actual start April 6, 2026; percent complete 40%; physical progress 60%; earned progress 25%; forecast finish April 17, 2026.
• C. Actual start April 6, 2026; percent complete 60%; physical progress 25%; earned progress 40%; forecast finish April 17, 2026.
• D. Actual start April 6, 2026; percent complete 60%; physical progress 40%; earned progress 25%; forecast finish April 20, 2026.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: The correct package applies each rule exactly as defined in the basis of schedule. Six of 10 workdays gives 60% percent complete, 400 of 1,000 m gives 40% physical progress, achieved milestone weights total 25% earned progress, and 5 remaining workdays after April 13 forecast a finish on April 20.

Before an update is entered, each status field needs its own objective measurement rule. In this activity, percent complete is based on elapsed workdays, physical progress is based on installed quantity, earned progress is based on achieved weighted milestones, and forecast status is based on the remaining-duration estimate.

• Percent complete: 6/10 = 60%
• Physical progress: 400/1,000 = 40%
• Earned progress: 10% + 15% = 25%
• Forecast finish: 5 workdays after Monday, April 13, 2026 = Monday, April 20, 2026

The key takeaway is that elapsed time, accomplished quantity, earned credit, and remaining work are different update inputs and should not be forced to match.

It correctly separates duration-based percent complete, quantity-based physical progress, milestone-weighted earned progress, and a 5-workday forecast from the April 13 data date.

Question 24

Topic: Conduct Scheduling Duties

At the August 30 data date, the approved schedule baseline shows mechanical completion on December 20. A routine status update using actual progress and revised remaining durations moves the forecast to December 24. Approved change order CO-07 adds scope with an accepted impact of 3 workdays; when inserted, the current forecast becomes December 27. Requested change CR-11 is still pending; a separate what-if analysis shows January 2 if it is later approved. Project procedure states that baseline dates change only after formal baseline-change approval. The steering committee needs tomorrow’s schedule report. Which action is best?

• A. Report December 27 as the forecast, keep December 20 as the baseline, show CR-11 separately as pending impact, and wait for formal baseline approval before changing the baseline.
• B. Report January 2 as both the forecast and the proposed new baseline because the pending change is likely and gives management the worst-case date.
• C. Change the baseline to December 27 now because CO-07 is approved and the forecast has already moved.
• D. Report only December 24 until CR-11 is decided, because approved changes should not affect the current schedule until a rebaseline is issued.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The schedule report should separate baseline, current forecast, and pending change exposure. Status-driven movement and approved CO-07 belong in the live forecast, but the baseline stays at December 20 until a formal baseline-change action is authorized.

This is a schedule-control discipline question. A routine update can move the forecast based on actual progress and remaining duration, and an approved change can be incorporated into the current schedule forecast. But the baseline remains the approved control reference until the project’s formal baseline-change process authorizes a revision. In this scenario, the report should show baseline mechanical completion at December 20, current forecast at December 27 after status plus approved CO-07, and CR-11 as a separate pending impact because it is still only a request. That gives stakeholders a factual status, a current expected finish, and visibility of unresolved exposure without rewriting history. The closest trap is assuming an approved change order automatically authorizes a rebaseline.

It preserves the approved control reference, updates the live forecast with status and approved scope, and keeps an unapproved request out of the baseline and current committed dates.

Question 25

Topic: Conduct Planning Duties

An approved contractual baseline schedule was issued on March 1. On April 30, the scheduler produced the first routine status update, and the contractor also submitted a separate recovery schedule revision that is still pending owner approval. Because all three files use the same revision numbering and similar file names, several stakeholders are treating the April 30 forecast dates as approved contract dates. What is the next appropriate control step?

• A. Create separate, version-controlled baseline, update, and pending-revision files linked to approvals.
• B. Keep one master file and rely on report notes.
• C. Suspend future updates until the recovery proposal is approved.
• D. Use the April 30 forecast as the working baseline.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: A routine update changes the current forecast, not the approved baseline. When forecast files and pending revisions can be mistaken for approved contract dates, the first control action is to enforce clear version control and approval-based labeling.

The core control concept is baseline discipline. The approved baseline remains the reference for variance measurement until a change is formally approved, while a routine update records actual status and the current forecast only. A proposed recovery or contractual revision is also separate until approval. When stakeholders are confusing these artifacts, the next step is to strengthen governance at the file and version level rather than change dates.

• Protect the approved baseline as a controlled reference.
• Issue periodic updates with their own version ID and clear data date.
• Mark proposed revisions as pending and link them to the change log and approval record.

This preserves traceability; replacing the baseline or relying only on explanations does not.

This separates forecast status from approved baseline changes and prevents an unapproved revision from being mistaken for a contractual commitment.

Questions 26-50

Question 26

Topic: Conduct Scheduling Duties

An EPC project’s June 30, 2026 schedule update shows the following:

The project director asks the scheduler to “move the baseline date to October 3 so next month’s report does not show slippage.” What is the most appropriate control action?

• A. Keep the approved baseline, report the variance, and revise dates only after approved change control.
• B. Constrain the milestone to October 3 and use that constrained date for reporting.
• C. Delay issuing the update until the pending change request is approved or rejected.
• D. Replace the baseline milestone with the forecast date because the update confirmed the slippage.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The baseline remains the approved control reference until a change is formally approved. The scheduler should update status and forecast honestly, report the variance against the baseline, and keep any baseline revision within change control.

This tests schedule baseline discipline. A schedule update may legitimately show a later forecast when actual progress and remaining duration change, but that does not authorize changing the baseline. The baseline is the approved reference for measuring performance; the forecast is the current expected finish.

When no approved change exists, the proper control action is to:

• update the schedule status and forecast as of the data date
• report the variance against the approved baseline
• document the impact and, if needed, pursue formal change control separately

This preserves traceability, keeps performance reporting credible, and avoids hiding slippage. Delaying the report or forcing dates to match the forecast would distort the schedule rather than control it.

An update can change the forecast, but only approved change control can change the baseline.

Question 27

Topic: Conduct Scheduling Duties

As of the September 1, 2026 data date, the current driving path to the package turnover milestone has 6 workdays of total float. The team is assessing one risk at a time; if a risk occurs, its delay is added directly to that path. Use expected milestone slip = probability × max(0, potential delay - 6). Assume a 5-day workweek, no holidays, and mutually exclusive risks.

Which risk currently deserves the highest mitigation priority because it has the largest expected slip to the milestone?

• A. Shared crane unavailable
• B. High-wind lift window lost
• C. Vendor equipment rework
• D. Regulatory approval late

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: Compare each risk by the delay that exceeds available float, then multiply by probability. The high-wind lift-window risk creates 3.0 expected slip days, which is greater than the other three risks.

To prioritize schedule risks on the same driving path, first remove the float cushion because only delay beyond total float can move the milestone. Then apply the provided formula to compare the uncertainties on a like-for-like basis.

• Regulatory approval: (12 - 6) × 35% = 2.1 workdays
• Shared crane unavailable: (9 - 6) × 50% = 1.5 workdays
• Vendor equipment rework: (7 - 6) × 60% = 0.6 workdays
• High-wind lift window lost: (18 - 6) × 25% = 3.0 workdays

Even with the lowest probability, the weather-window risk has the largest delay beyond float, so it is the top schedule threat to the milestone.

It has the greatest float-adjusted exposure: 25% × (18 - 6) = 3.0 expected lost workdays.

Question 28

Topic: Conduct Scheduling Duties

A utility expansion project uses a Monday-Friday workday calendar with no holidays. The data date is March 16, 2026. For the contractual milestone Ready for Startup, total float is calculated as required finish - current forecast finish, in workdays; count only workdays after the required finish date up to the forecast finish date, and late values are negative.

Exhibit:

What is the best interpretation?

• A. It has +5 workdays of float; the baseline buffer protects the contract date.
• B. It has -3 workdays of float; remove the required finish date because negative float is never acceptable.
• C. It has -3 workdays of float; the forecast misses the required date and needs recovery analysis, not automatic rebaseline.
• D. It has -8 workdays of float; rebaseline now to the April 8 forecast.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: From April 3 to April 8 on a Monday-Friday calendar, the workdays are April 6, 7, and 8, so total float is -3 workdays. That means the current forecast misses the contractual required date. Negative float is a warning to analyze drivers and recovery, not automatic approval to rebaseline.

Negative float shows that a forecast date is later than a required or constrained date. Here, the question defines total float against the required finish, not against the baseline. Counting only workdays after April 3 up to April 8 gives 3 workdays, so the milestone has -3 workdays of total float. That means the current logic-driven forecast is 3 workdays late relative to the contractual milestone. The proper response is to verify the driving path, validate status and remaining durations, and assess recovery options or formal change control if the required date cannot be met. Rebaselining is a separate approval decision; negative float by itself does not justify changing the baseline or deleting the required date.

April 8 is 3 workdays after April 3, so total float is -3 and the result signals a schedule-control problem rather than automatic rebaselining.

Question 29

Topic: Conduct Planning Duties

An EPC project is finalizing its schedule management plan before baseline approval. The draft sets the monthly data date, update workflow, coding structure, and change-request form. It also says the latest schedule file on the shared drive will supersede prior files, and it does not require retaining approved baselines or update snapshots by version ID. What is the next appropriate step?

• A. Define controlled schedule versioning, archived snapshots, and change-log references.
• B. Require resource leveling before every monthly update.
• C. Adopt the latest forecast as the new baseline each period.
• D. Add weekly narrative status reports from each discipline lead.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The key gap is missing version control and baseline preservation. If approved schedule files are overwritten instead of archived and linked to change approvals, later comparisons lose traceability and weaken variance analysis, recovery evaluation, and defensible stakeholder communication.

Before baseline approval, the schedule management plan should close the control gap by defining how schedule versions are identified, approved, stored, and retrieved. A sound planning procedure keeps the approved baseline immutable and preserves each update snapshot with its data date, version ID, and related approval or change reference. That creates an auditable record for comparing baseline dates, prior forecasts, current forecasts, and approved changes over time.

• assign unique version IDs and file-naming rules
• preserve approved baselines and periodic update snapshots
• link each approved change to the affected schedule version
• define who can authorize baseline or revision releases

Extra reporting frequency may help communication, but it does not replace traceable control records. Replacing the baseline with the latest forecast would erase the very reference needed for performance measurement.

Traceable archived versions tied to approvals are needed to support later variance, recovery, and entitlement analysis.

Question 30

Topic: Conduct Scheduling Duties

A shutdown project has turnover milestone M-110 with a baseline date of September 4, 2026. At the August 14, 2026 data date, the driving activity Pipe testing still leaves the milestone forecast at September 4 because the update narrative says, “recover with a second test crew.”

The construction manager wants the weekly report to state that the turnover date remains unchanged. What is the next appropriate step?

• A. Rebaseline the milestone now to match current field performance.
• B. Reconcile remaining duration and approved recovery resources, then recalculate the forecast before reporting.
• C. Keep the September 4 forecast and note recovery as management intent.
• D. Classify it as a risk and wait for the next update cycle.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The unchanged milestone forecast is not credible because objective progress, budget-hour consumption, and confirmed resource availability do not support the entered remaining duration or the recovery narrative. The scheduler should validate the update and recalculate the forecast using approved resources before issuing the stakeholder message.

Integrated project-controls evidence should support the schedule forecast, not just the update narrative. Here, 45% physical progress after 9 of 12 planned workdays, 78% of budget hours consumed, and no approved second crew do not support only 3 workdays remaining or an unchanged September 4 turnover date. The next scheduling-control step is to challenge the remaining duration and recovery assumption with the responsible field and resource leads, update the model using approved resources only, and then communicate the recalculated forecast.

• Confirm the objective earned-progress result.
• Validate remaining duration against current productivity.
• Remove unapproved recovery assumptions.
• Recalculate before issuing the report.

A stakeholder message should follow supported forecast logic, not optimistic intent.

The current forecast depends on an unsupported recovery assumption and a remaining duration that conflicts with progress and resource evidence.

Question 31

Topic: Conduct Planning Duties

A brownfield compressor-station upgrade must maintain operations during construction. Which planning approach best supports a realistic baseline sequence from these facts?

- Zone A and Zone B share one crane path and laydown area; steel erection can occur in only one zone at a time.
- Hot tie-ins are allowed only during a planned 36-hour shutdown on October 18–19, 2026.
- One relay technician performs electrical cutover in both zones, one zone at a time, after each zone's mechanical completion.
- Zone B civil work cannot start until the environmental permit is approved.

• A. Sequence by discipline and let later resource leveling resolve field conflicts.
• B. Phase by zone and shutdown window, with permit and resource-release milestones.
• C. Maximize overlap across both zones and protect key dates with constraints.
• D. Complete all Zone A field work before starting any Zone B field work.

Best answer: B

What this tests: Conduct Planning Duties

Explanation: The best planning approach is to build the sequence around the real execution constraints, not around a generic discipline order. Here, access sharing, the fixed shutdown, permit release, and one critical technician all need to become explicit phase gates before baseline development.

In planning duties, the goal is to choose an execution approach that reflects how the work can actually be performed in the field. The controlling factors here are site access, a fixed operational shutdown, a permit prerequisite, and a single specialized resource. A realistic approach is therefore to phase work by zone and outage window, then define milestones or handoffs for permit approval, mechanical completion, and relay-technician availability.

• Use area or zone phasing where access limits apply.
• Use a shutdown phase for the tie-ins because the outage window is fixed.
• Use explicit gates for permit release and the single cutover resource.

That preserves constructability and gives the later schedule model logic-driven dates instead of artificial ones.

It turns the actual access, outage, permit, and scarce-resource limits into explicit sequencing gates for the schedule model.

Question 32

Topic: Conduct Scheduling Duties

At the September 10, 2026 data date, turnover milestone T-1 had a baseline date of September 30 and a current forecast of October 4. All remaining work uses a 6-day calendar.

Exhibit: Remaining-path summary

The operations manager proposes weekend overtime on spare-parts labeling because that team is available immediately. No added testers or vendor technicians are yet confirmed for the driving activities. What is the best scheduler response?

• A. Rebaseline T-1 to October 4 now because only non-driving overtime is available.
• B. Explain that compressing spare-parts labeling will not improve T-1; evaluate feasible recovery on the driving activities, confirm resources, and report the October 4 forecast against the baseline.
• C. Approve overtime on spare-parts labeling to show immediate recovery action.
• D. Keep reporting September 30 as achievable until the next update cycle.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The milestone is threatened by the zero-float driving activities, not by the parallel work with 6 days of float. Compressing spare-parts labeling may look proactive, but it does not change the path controlling T-1. The best response is to report the variance clearly and test recovery where it can actually improve the forecast.

A credible recovery plan must target the activity path that is currently driving the threatened milestone or finish date. In this update, loop testing and vendor punch closeout both have 0 days of total float and directly drive T-1, while spare-parts labeling is parallel work with 6 days of float. Shortening that non-driving activity does not change the October 4 forecast for T-1.

• Identify which activities actually drive the milestone.
• Test compression, resequencing, or added resources on those driving activities.
• Confirm the needed resources before promising recovery.
• Keep the approved baseline as the control reference and communicate the current forecast and decision needed.

The closest trap is taking visible action on available work, but visible action is not the same as milestone recovery.

Only recovery on the driving path can improve T-1, so the schedule should keep the approved baseline, show the current forecast, and target feasible compression where it affects the milestone.

Question 33

Topic: Conduct Scheduling Duties

On a compressor installation project, the data date is July 15, 2026. All work activities use a Monday-Friday calendar, and the wait between Pour Pedestal and Set Compressor is a fixed 10-calendar-day curing lag. The Substantial Completion milestone has a Finish On or Before August 28, 2026 required date; the current forecast is September 2, 2026, so the schedule shows -3 working days total float on the current driving electrical/startup path.

Exhibit: Current update

What is the best scheduling response?

• A. Remove the required-date constraint and use the unconstrained result for the status report.
• B. Report the pedestal slippage as a 3-day project delay because negative float exists in the schedule.
• C. Explain that the civil path is not yet driving; report completion risk on the constrained electrical/startup path and monitor the lagged civil handoff.
• D. Reduce the curing lag in the model to regain float and show an on-time finish.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: Constraints and lags must be interpreted separately. Here, the -3 days total float is tied to the constrained completion milestone on the driving electrical/startup path, while the lagged civil path still has +5 days total float. That makes the pedestal slippage a schedule risk, not current proof of a 3-day project delay.

Total float must be interpreted on the relevant path to the constrained milestone, not assigned broadly because a different path slipped. A required-date constraint can create negative float when the forecast exceeds that date, but that negative float belongs to the path currently driving the constrained finish. In this update, the electrical/startup sequence is driving Substantial Completion, while the lagged civil path still retains +5 days total float.

A sound response is to:

• confirm the current driving path to the constrained milestone
• report the -3 days negative float against the required finish transparently
• treat the late civil handoff as a monitored schedule risk because more slippage could consume its remaining float

Removing a valid required-date constraint or arbitrarily shortening a physical curing lag would distort the schedule model instead of improving schedule-impact interpretation.

The civil path still has positive total float, so it is not currently driving the constrained milestone; the negative float is on the electrical/startup path, while the lagged handoff remains a risk to monitor.

Question 34

Topic: Conduct Scheduling Duties

At the July 31 data date, the approved baseline turnover milestone is October 20 and the current forecast is November 3. Schedule analysis shows zero total float on the switchgear path: final drawings, fabrication, installation, and energization. Final drawing approval finished 8 workdays late, and that delay has already occurred. An owner request for extra testing is still pending in CR-17 and is modeled only in a separate what-if copy. Executives want a decision-ready explanation of the forecast movement. Which statement is best?

• A. As of July 31, turnover moved mainly due to reduced field productivity, so executives should focus on the SPI trend instead of the switchgear path details.
• B. As of July 31, turnover moved from October 20 to November 3 because late switchgear drawing approval delayed activities on the current critical path; CR-17 extra testing is excluded, and a recovery decision is needed now.
• C. As of July 31, turnover should be reported as November 10 because the owner may add extra testing; the baseline should be updated now to reflect the likely new finish.
• D. As of July 31, turnover moved because several work fronts are underperforming, so the team should observe one more update cycle before identifying a primary driver or requesting action.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The best explanation is factual, traceable to the current schedule, and tied to a decision. Here, the forecast moved because an actual late approval affected the zero-float path, while the pending extra-testing request stays outside the current forecast until approved.

A decision-ready explanation of forecast movement should separate verified schedule facts from pending scenarios. In this case, the current forecast slipped from the approved baseline because a real event already occurred: final switchgear drawing approval finished late on the zero-float driving path. That is the supported reason for the November 3 forecast.

A strong explanation should:

• state the data date,
• quantify the baseline-to-forecast movement,
• identify the current driving cause,
• distinguish pending what-if changes from the live forecast,
• indicate the decision needed for recovery.

Because CR-17 is not approved, it belongs in what-if analysis, not in the reported current forecast or baseline. A vague statement about general underperformance or a focus on high-level metrics like SPI does not explain the actual finish-date movement as clearly as the driving-path evidence does.

It gives the data date, baseline-to-forecast movement, supported driving cause, treatment of the pending change, and the management action needed.

Question 35

Topic: Conduct Scheduling Duties

During baseline validation of a substation project, the critical path runs through transformer delivery and has 0 workdays total float. The two field activities below both require the same single electrical crew, and no second crew is available. Contract completion cannot move without an approved change.

Both field activities are currently scheduled in parallel next week. Which action is most appropriate?

• A. Add a finish constraint to preserve completion.
• B. Rebaseline to the crew-limited dates now.
• C. Level the schedule and accept a later finish.
• D. Stagger the two field activities using resource smoothing.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: Use resource smoothing because the over-allocation is on noncritical work and each activity has enough float to absorb a 3-workday stagger. That keeps the schedule feasible while preserving the current project finish and critical path.

Resource smoothing is used when a resource conflict can be resolved by shifting activities within available float so the project finish and critical path do not change. Here, the single electrical crew is over-allocated, but the affected activities are not on the critical path and each has 4 workdays of total float. Since each activity lasts 3 workdays, one can be moved to eliminate the overlap and still remain within float.

Resource leveling would be the better method only if the resource limit could not be resolved within float and the schedule needed to extend dates to become realistic. In this case, forcing a later finish, adding a constraint, or changing the baseline would all be poorer control actions than smoothing the noncritical work.

Smoothing is appropriate because the crew conflict can be resolved within available float without moving the critical path or project finish.

Question 36

Topic: Conduct Scheduling Duties

During baseline development for a substation upgrade, the procurement path is driving the energization milestone, and all activities use a 5-day calendar. Historical data show relay panel fabrication is usually 22 workdays, with an observed range of 18-26, and the risk register shows a 30% chance that customs clearance could add 4-6 workdays after shipment. The draft schedule sets fabrication to 30 workdays to be safe, shows no separate contingency, and the project manager says customs risk can be ignored because the vendor sometimes ships early. No approved acceleration plan exists. What is the best action?

• A. Use 22 workdays and assume early shipping will offset customs delay.
• B. Keep fabrication at 30 workdays because embedded protection is safer.
• C. Reduce fabrication below 22 workdays to meet energization, then revise later.
• D. Use the 22-workday duration and carry separate contingency for customs risk.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: Contingency should be explicit, supportable, and tied to an identified uncertainty. Here, 22 workdays is the evidence-based fabrication duration, while the customs exposure belongs in transparent contingency or risk-response control. Hidden padding and hoped-for early delivery both weaken forecast credibility.

Credible schedule contingency must be transparent and traceable to identified uncertainty. In this scenario, the evidence-based fabrication duration is 22 workdays; the possible extra 4-6 workdays belong to the customs risk, not inside a 30-workday deterministic activity and not in an assumption that the vendor will ship early. Keeping the base duration realistic preserves logic, float, and forecast quality during updates. Any contingency should be carried separately, documented in the basis of schedule or risk controls, and linked to the customs trigger so stakeholders can see why it exists and when it may be consumed.

The key takeaway is to separate realistic planned work from explicit, supportable uncertainty.

It keeps the base duration evidence-based and makes contingency explicit for the identified customs uncertainty.

Question 37

Topic: Conduct Scheduling Duties

During baseline QA of an integrated construction schedule, the team confirms that the pump must be on site before installation can start. The current logic fragment is:

A  Approve pump submittal   Pred: —
B  Fabricate pump           Pred: A FS
C  Ship pump                Pred: B FS
D  Receive pump on site     Pred: C FS   TF: 18d
E  Complete foundation      Pred: —
F  Install pump             Pred: E FS   TF: 0d
G  Mechanical completion    Pred: F FS

Which action best corrects the schedule-model credibility problem?

• A. Keep procurement logic separate from construction logic.
• B. Add an FS link from receipt to installation.
• C. Add a finish-no-later-than constraint to receipt.
• D. Add an FS link from shipment to installation.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The real problem is missing required logic between the procurement path and the installation path. Because installation cannot start until the pump is received on site, the model must show that dependency explicitly; otherwise delivery activities carry artificial float and the forecast is less credible.

The core issue is missing logic. In an integrated project schedule, any physically required handoff between procurement and construction should be represented in the network so float, criticality, and forecast dates are credible. Here, the receipt activity ends the procurement chain, but installation is driven only by foundation completion even though the stem states the pump must be on site before installation can begin. That disconnect creates an open end on the delivery path and makes the 18 days of float on receipt misleading. The best correction is to link receipt to installation with the appropriate relationship, typically FS for this fact pattern. Constraints or shortcut links may force dates, but they do not model the real dependency.

This adds the missing required handoff so delivery and installation are logically integrated and float is no longer overstated.

Question 38

Topic: Conduct Scheduling Duties

Data date: June 10, 2026. The approved baseline shows the interface milestone Substation Ready for Energization on July 8, 2026. After the update, the forecast is July 16, 2026, based on a confirmed relay delivery delay and field-reviewed remaining duration. The commissioning contractor cannot start site tests until that milestone, and its mobilized crew is available only through July 14 unless remobilization is approved. The milestone is on the driving path to provisional acceptance, and no approved change has modified the baseline. Which scheduling response is best?

• A. Rebaseline the interface milestone to July 16 and notify commissioning after internal agreement.
• B. Wait to report the slip until the relay is onsite and the milestone is actually missed.
• C. Constrain provisional acceptance to the contract date and direct commissioning overtime to absorb the slip.
• D. Update the forecast, quantify the handoff impact, test feasible recovery, and escalate decision needs without changing the baseline.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The best response is to keep the approved baseline intact, update the current forecast from evidence, and immediately analyze the downstream interface impact. Because the slip affects a driving milestone and another contractor’s mobilization window, the scheduler should coordinate feasible recovery options and escalate the decision need now.

When an interface milestone is forecast to slip, the scheduler should protect schedule control integrity and improve decision quality at the same time. In this case, there is enough evidence to use the July 16 forecast now: the relay delay is confirmed, remaining field duration has been reviewed, and the milestone drives provisional acceptance. Because commissioning cannot start before energization and its crew window ends July 14, the forecasted slip already affects another party’s work.

The strongest response is to:

• keep the approved baseline as the performance reference
• update and report the current forecast using the data date evidence
• quantify the impact on the downstream handoff and final milestone
• test only recovery actions that are logic- and resource-feasible with the affected teams

Any baseline change belongs in formal change control, not in the routine update. Forcing dates or delaying communication would weaken forecast credibility and stakeholder decisions.

This preserves the control reference while using current evidence to coordinate recovery and stakeholder decisions on the driving interface.

Question 39

Topic: Conduct Scheduling Duties

At the July 10, 2026 data date, the approved integrated schedule shows the Ready for Energization milestone required on August 14, 2026 and currently forecast 2 workdays early. The activities on its current driving path each show 2 workdays total float. A site access restriction has already delayed the driving cable-pull activity by 4 workdays. No approved change exists. What is the best scheduling judgment and immediate action?

• A. Wait until downstream activities finish before reporting any milestone impact.
• B. Update the delay; 2 days consume float and 2 days delay the required milestone, then assess recovery.
• C. Rebaseline the milestone to the new forecast date before issuing the update.
• D. Classify all 4 days as float consumption because the path had positive float before the delay.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The delay is larger than the float protecting the required milestone. Two workdays are absorbed by available float, but the remaining two workdays push the milestone forecast late, so the update should show the impact and support recovery analysis.

A scheduler should distinguish delay duration from schedule impact. If a delay is less than or equal to the available total float on the driving path, it reduces schedule flexibility but does not change the required milestone or forecast finish. If the delay exceeds that float, the excess becomes milestone slippage or negative float against the required date.

• Available total float: 2 workdays
• Actual delay on the driving path: 4 workdays
• Result: 2 workdays absorbed, 2 workdays late

So this is not a float-consumption-only event; the current update should show the new late forecast and trigger recovery analysis rather than a rebaseline.

Because the 4-workday delay exceeds the 2 workdays of total float, it both consumes float and pushes the required milestone 2 workdays late.

Question 40

Topic: Conduct Scheduling Duties

At the May 31 data date, a refinery turnaround has an approved resource-loaded baseline schedule. Activities roll up to control accounts, and monthly earned progress is claimed through weighted milestones tied to schedule activities. To reflect an approved access restriction, the scheduler proposes splitting one 12-day cable-pull activity into four activities and moving two earning events into June; the overall completion forecast is unchanged. Which evidence best validates that this change must also be coordinated with the cost baseline, resource plan, and earned-progress reporting?

• A. An approved change-log entry authorizing the access restriction and the related schedule revision.
• B. A schedule-quality check showing no open ends and the same critical path after resequencing.
• C. A reconciliation showing the new activities shift time-phased labor hours and weighted-milestone earning events in the affected control accounts.
• D. An updated resource histogram showing electrician demand still fits the available crew capacity.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: When schedule activities are resource-loaded and also drive earned-progress credit, changing their breakdown or timing is not a schedule-only edit. The strongest validation is evidence that the revised activities alter time-phased hours and earning events inside specific control accounts.

The key concept is integrated schedule control. In this scenario, the schedule is linked to control accounts, resource loading, and weighted-milestone earned progress, so splitting an activity and moving earning events into a later period can change the time-phased cost baseline, the resource plan by period, and when progress is reported. The best validation is a traceability or reconciliation review that proves those links are affected in the specific control accounts involved. That evidence directly supports the need to coordinate the schedule revision with cost and earned-progress structures before treating it as a simple schedule edit. Authorization, logic quality, and crew feasibility all matter, but they do not by themselves prove that baseline budget timing or progress-measurement rules must be updated.

It directly shows that the schedule revision changes both the budget-loaded timing and the earned-progress basis for specific control accounts.

Question 41

Topic: Conduct Scheduling Duties

No actual progress has occurred; evaluate the logic at project start. All activities use the same Monday-Friday 5-workday calendar, with no holidays, resource limits, or date constraints. Use these rules: under FS, a successor starts when its predecessor finishes; under SS + L, a successor starts L workdays after its predecessor starts. The final milestone occurs when both feeder paths finish.

The team proposes changing Design release - Fabrication from FS to SS+3 because fabrication can start after the first package is released. What is the most accurate schedule impact?

• A. Project finish advances 3 workdays; the electrical path still has 2 workdays float, so the mechanical path remains critical.
• B. Project finish advances 2 workdays; the electrical path’s 2-day float is consumed, so it becomes critical for further recovery.
• C. Project finish does not change; the revised dependency only redistributes float within the mechanical path.
• D. Project finish advances 2 workdays; both feeder paths end with 1 workday float, so either path is equally effective for further recovery.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The mechanical path is currently 19 workdays, while the electrical path is 17 workdays. Changing the first mechanical relationship to SS+3 shortens that path to 16 workdays, so the milestone improves only to 17 workdays and the electrical path becomes critical.

This is a dependency-impact question: changing a relationship can shorten one path, but the project finish only improves until another path takes control.

So the milestone moves from 19 to 17 workdays, a 2-workday gain, not 3. The electrical path had 2 workdays of total float before the change, and that float is fully consumed once the mechanical path drops below it. After the logic revision, the electrical path is critical and the mechanical path has 1 workday of float. The key takeaway is that valid overlap can improve the forecast, but it may also shift the critical path and change where recovery effort should go next.

The dependency change cuts the mechanical path to 16 workdays, but the 17-workday electrical path then controls the milestone and uses up its 2 days of float.

Question 42

Topic: Conduct Scheduling Duties

As of the June 30, 2026 data date, the approved baseline for a power-plant project shows Mechanical Completion - Unit 2 on July 28, 2026. In the current forecast, that interface milestone is driven by construction predecessors, has no logical successors to the already defined commissioning activities, and is held to July 28 by a mandatory finish constraint; a downstream test-scope change is still pending approval. Which action best improves credible forecasting and interface control for the next update?

• A. Leave the logic unchanged and manually forecast the milestone each cycle.
• B. Remove the constraint, link the milestone to completion and receipt/start work, and report July 28 separately until change approval.
• C. Keep the constraint and explain the handoff in narrative status.
• D. Replace the milestone with a 5-day turnover activity fixed to July 28.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: An interface milestone should forecast from real predecessor completion and real successor use of the handoff. The best option restores logic on both sides of the milestone, keeps July 28 as a control reference, and avoids embedding an unapproved change into the live control schedule.

In a credible integrated schedule, an interface milestone is a zero-duration event marking a verifiable handoff. It should be logically tied to the work that creates readiness and to the downstream work that depends on that readiness. Here, the mandatory finish constraint can hide slippage, and the lack of successors means the milestone does not control commissioning start or acceptance.

A sound correction is to:

• keep the milestone as the interface event
• drive it from objective construction completion criteria
• connect it to defined commissioning receipt or start activities
• keep July 28 visible as the contractual or baseline comparison date until any change is formally approved

That approach improves forecast credibility, preserves baseline discipline, and gives stakeholders a traceable view of downstream impact. Narrative notes or manual date setting may communicate concern, but they do not repair the schedule model.

This makes the handoff logic-driven on both sides while preserving the contractual date as a control reference instead of forcing the forecast.

Question 43

Topic: Conduct Scheduling Duties

At the June 30, 2026 data date for a substation upgrade, the integrated controls report for the energization work package shows:

The late forecast is driven by a slipped transformer factory test and delivery. In the reporting cycle, what is the next appropriate step?

• A. Treat the variance as cost-only because earned-value performance is favorable.
• B. Rebaseline the energization milestone to the forecast date before reporting.
• C. Escalate energization as a schedule issue and analyze recovery on the driving path.
• D. Defer action until another period confirms the CPI and SPI trend.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: The controlling evidence is the logic-based schedule forecast, not the favorable cost and earned-progress indices. Because the contractual milestone is late and the driving path has negative float, the next step is to report a schedule issue and evaluate recovery.

In integrated project controls, cost and earned-progress indicators add context, but schedule control decisions must follow the logic-driven forecast. Here, energization is forecast later than the contractual date, and the driving path shows -7 workdays of total float. That makes this a current schedule issue, not a cost-only concern.

The next step is to communicate the milestone impact clearly and start recovery analysis on the path causing the delay. Favorable CPI and SPI do not override a late forecasted finish; they only show that cost and earned progress are presently tracking reasonably well. Rebaselining would hide variance without approved change control, and waiting another period would delay response to an already visible schedule problem.

The key takeaway is that milestone forecast and float determine whether the concern is schedule-driven.

A late contractual milestone with negative float is a schedule-driven issue even when CPI and SPI are currently favorable.

Question 44

Topic: Conduct Scheduling Duties

At the June 5, 2026 data date, the integrated schedule shows this turnover sequence for a power-up area. Package B testing cannot start until Package A owner acceptance is signed because both packages share the switchgear room boundary. The contract requires outage turnover by June 20, 2026; the next outage window is July 18, 2026.

Which coordination focus is most appropriate?

• A. Update the baseline to June 22 so future variance reflects the current plan.
• B. Focus recovery only within Package A, because it is the first slipped milestone.
• C. Keep the slippage as a risk until Package B actually misses its start.
• D. Coordinate the A-to-B handoff and escalate the threatened June 20 outage turnover.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: This is no longer just a local delay inside Package A. Because Package B depends on the boundary handoff and the forecast now misses the June 20 contractual turnover, the proper focus is immediate interface coordination and escalation to affected stakeholders.

The key concept is to follow the driving effect of the slippage, not just where the first late milestone appears. Here, Package A acceptance is a hard predecessor to Package B testing, and that handoff delay pushes the contractual outage turnover from June 20 to June 22. That makes the problem an active schedule-control issue affecting package boundaries, turnover sequence, and a fixed commitment.

The scheduler should center coordination on the interface itself:

• confirm the A-to-B handoff requirements
• align Package A, Package B, commissioning, and owner participants
• assess recovery options against the fixed outage window
• escalate the threatened contractual milestone promptly

Treating it as only a Package A problem misses the downstream impact, while changing the baseline or waiting for a later miss would reduce control credibility.

The slip crosses a package boundary and already drives a forecast miss of a fixed contractual milestone, so cross-package coordination and immediate escalation are required.

Question 45

Topic: Conduct Scheduling Duties

At the May 31, 2026 data date, a turnaround schedule update shows mechanical completion forecast on June 24, 2026, versus the baseline June 18, 2026. Before issuing the owner report, the project controls manager must decide whether that forecast is reliable enough to present without qualification. Which review result best validates a decision to lower reporting confidence in the current forecast?

• A. A change review shows one pending scope addition with no approved time impact yet.
• B. A trend review shows the completion milestone slipping in each of the last three updates.
• C. A resource review shows instrument technicians overallocated by two people for one week in June.
• D. A QA review finds finished work missing actual finish dates and driving work keeping the same remaining durations despite added progress.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The best validation is direct QA evidence that the update itself is weak. Missing actual finish dates and unchanged remaining durations on driving work undermine forecast credibility, so the report should not present the finish date as high confidence until the status data are corrected.

Forecast credibility depends first on whether the schedule update is properly statused as of the data date. If work finished before the data date is missing actual finish dates, the network is not reflecting real progress. If driving activities show added progress but keep the same remaining durations, the forecast is also unsupported, because remaining duration should be reassessed based on field conditions and work left to perform.

A QA review that tests actual dates and remaining durations on driving work is therefore the strongest evidence for lowering reporting confidence. A trend chart, a resource over-allocation view, or a pending change may matter for analysis, but none of them proves that the current forecast is reliable or unreliable as an update-quality matter.

The key takeaway is that poor status data weakens the forecast before any higher-level reporting conclusions are made.

This review directly shows update data defects in actuals and remaining duration, so the calculated forecast is not yet trustworthy.

Question 46

Topic: Conduct Planning Duties

A scheduler is preparing a baseline-readiness package for a process-unit upgrade. The draft schedule currently models all construction on a 6-day, 10-hour calendar. Four late stakeholder inputs are received:

- Operations manager: Unit tie-ins may occur only during the approved outage
  window of October 14-20, on a 24-hour outage calendar; supported by
  Contract Exhibit C and a signed outage memo.
- Project sponsor: Prefers milestone charts in a one-page red/green format.
- Construction manager: Prefers activities split to 10 workdays or less;
  no company standard requires this.
- Procurement lead: Expects vendor skids may arrive 2 weeks early, but no
  revised supplier commitment has been approved.

Which action should the scheduler prioritize before seeking baseline approval?

• A. Split long field activities to match the construction manager’s preferred display style.
• B. Convert milestone outputs to the sponsor’s preferred red/green dashboard format.
• C. Shorten vendor fabrication duration to reflect the expected early delivery.
• D. Model tie-ins in the approved outage window and 24-hour calendar, and document that basis.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: The outage window is the only input that is approved, traceable to a control reference, and capable of changing how the schedule must be built. Because it governs access timing and calendar use, it belongs in both the schedule model and the basis of schedule before baseline approval.

A stakeholder preference becomes a planning requirement when it is supported by an approved source, affects how work must be modeled, and needs traceability in the control basis. The outage restriction meets that test: it is backed by Contract Exhibit C and a signed memo, and it changes the allowable timing and calendar for tie-in activities. If that condition is missing from the draft schedule, the baseline is not ready because the model would misrepresent access and forecast dates.

Presentation preferences and display preferences can be addressed later unless they are mandated standards. An expected early delivery without an approved supplier commitment is still uncertainty, not an approved planning assumption. The key takeaway is to incorporate approved access, calendar, and timing requirements first, then document them in the basis of schedule.

This is an approved, evidence-backed access requirement that materially affects schedule development and must be reflected in the model and basis of schedule.

Question 47

Topic: Conduct Scheduling Duties

A scheduler is reviewing a baseline before approval for a substation upgrade. All activity durations use most-likely values from recent similar projects, and the contractual energization milestone is fixed. One identified schedule risk remains: owner-furnished relay panels may require factory reinspection, delaying site delivery by 0 to 5 workdays; the trigger is a failed factory acceptance test on April 18, and the planned response is to consume schedule contingency before field installation starts. Which analysis result is most defensible?

• A. Keep current durations and expect normal testing recovery to absorb delay.
• B. Add a visible 5-workday contingency before installation, linked to the trigger.
• C. Distribute the same 5 days across downstream installation durations.
• D. Shift the energization milestone 5 workdays later as contingency.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: Credible schedule contingency is explicit, traceable, and tied to a documented uncertainty, trigger, and response plan. A visible allowance before installation preserves realistic activity durations and can be removed if the trigger does not occur.

In PSP practice, schedule contingency should be based on identifiable uncertainty, not hidden inside normal activity durations and not replaced by hopeful recovery assumptions. Here, the uncertainty is specific and documented: relay panels may be delayed by up to 5 workdays if the April 18 factory acceptance test fails. The strongest treatment is to place a visible contingency allowance where that uncertainty enters the driving schedule path, before field installation starts.

• Keep planned work durations at most-likely values.
• Tie contingency to a named risk and a clear trigger.
• Put the allowance where the risk affects schedule logic.
• Preserve the contractual milestone as the control target.

Spreading days across activities hides padding, while moving the milestone changes the commitment instead of modeling uncertainty.

A dedicated contingency allowance tied to the FAT-failure trigger keeps uncertainty visible and traceable without padding normal work durations.

Question 48

Topic: Conduct Planning Duties

A capital project is preparing its first integrated schedule baseline. The schedule management plan states:

• technical reviewers may recommend changes but may not directly revise the controlled schedule file
• only the baseline approval board may approve a schedule baseline for performance measurement
• forecast dates may be communicated before baseline approval if they are clearly labeled as forecast only
• each submitted model version must have a unique ID and an archived comment-disposition record

During review, the engineering manager emails marked-up dates and asks the scheduler to overwrite IMS_v0.9 on the shared drive. The client also requests the current expected completion date. Baseline approval has not yet occurred.

Which response best complies with schedule governance?

• A. Create a new version, log reviewer comments, report the date as forecast only, and wait for formal baseline approval
• B. Overwrite IMS_v0.9, adopt the reviewer dates, and use it as the baseline candidate
• C. Accept the reviewer edits directly because the engineering manager owns the technical scope
• D. Issue the latest date only after baseline approval to avoid confusing forecast and baseline

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The best response is to preserve control of the schedule model while still communicating needed forecast information. Governance requires reviewer input to be dispositioned through version control, with forecast dates clearly distinguished from an approved baseline.

This scenario tests baseline discipline and version control. Reviewer authority is limited to recommending changes, so the engineering manager should not directly overwrite the controlled file. Because baseline approval has not occurred, the team may communicate the current expected completion date only as a forecast, not as a baseline or performance-measurement reference.

The compliant sequence is:

• capture the reviewer comments
• update the model in a new uniquely identified version
• archive the comment-disposition trail
• communicate the completion date as forecast only
• wait for formal approval before designating any baseline

The closest distractors fail because they either let a reviewer bypass control, treat an unapproved schedule as a baseline, or unnecessarily suppress valid forecast communication.

This preserves reviewer limits, keeps model-version traceability, and separates forecast communication from formal baseline approval.

Question 49

Topic: Communication Competency

At the July 31 data date, the project manager asks for an executive update on the Mechanical Completion milestone and wants to state that the contractor caused a 12-day delay.

Milestone baseline: August 28
Current forecast: September 9
Open schedule-review items:
- Activity A120 is 60% complete but has no actual start
- Activity A140 started before predecessor A130 finished
- Approved CR-17 adds a 4-day outage but is not yet in the model

What is the next appropriate step?

• A. State analysis is incomplete, validate the update, then report dated variance
• B. Reset the baseline to September 9 before sending the report
• C. Wait until the next update cycle before mentioning any concern
• D. Issue the note and attribute the 12-day slip to the contractor

Best answer: A

What this tests: Communication Competency

Explanation: The forecast change cannot yet support a firm causal conclusion because status data, logic behavior, and approved-change incorporation are incomplete. The right communication step is to say the impact is under validation, correct the schedule data, and then report baseline-versus-forecast variance with the data date and assumptions.

This tests evidence-based schedule communication. A forecast date alone is not enough to assert a confirmed delay cause when the update still contains missing actuals, out-of-sequence progress, and an approved change that has not been modeled. The next step is to communicate that the impact analysis is still in progress, validate the schedule update, and then issue a decision-oriented status message that clearly states the data date, baseline date, forecast date, and any remaining assumptions.

• Verify the missing and out-of-sequence status data.
• Incorporate the approved outage change into the model.
• Reassess the milestone impact and driving path.
• Then communicate the supported variance and recommendation.

The closest distractor is waiting silently, but that withholds a known concern instead of reporting that analysis is underway.

The apparent slip is not yet supportable until status anomalies and the approved change are validated in the schedule model against the baseline.

Question 50

Topic: Conduct Scheduling Duties

Data date: August 8, 2026. A shutdown project has a required Ready for Startup milestone of September 30. The current forecast is October 10, and the current driving path is Hydrotest Area B -> punch clearance -> turnover package approval -> Ready for Startup. The field superintendent proposes recovering 9 workdays by starting punch clearance 3 days before hydrotest finishes and adding a second punch crew. No area-access confirmation, crew-loading check, or what-if analysis has been documented.

What is the next appropriate step?

• A. Approve the overlap and report September 30 as the revised forecast.
• B. Constrain turnover approval to finish by September 30.
• C. Test the recovery in the schedule model for path, access, and crews.
• D. Rebaseline the milestone to October 10 for current reporting.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: The proposed recovery is not yet supported by schedule evidence. Before accepting overlap and added-crew assumptions, the scheduler should test whether the affected work is still on the current driving path and whether access and labor actually make the recovery feasible.

The key concept is evidence-based recovery analysis. A late forecast does not justify immediately accepting a recovery idea, changing the baseline, or forcing dates with constraints. Here, the proposal depends on two unproven assumptions: punch clearance can overlap hydrotest in the field, and a second crew is actually available on the needed dates.

The next step is to validate the proposal in the current schedule model by checking:

• whether the affected activities are still on the current driving path
• whether area turnover and access rules allow the overlap
• whether the second crew is available on the required calendar
• what the revised forecast becomes after a what-if run

That preserves schedule logic and forecast credibility. Simply approving or forcing the date would hide uncertainty rather than analyze recovery.

Recovery dates should be adopted only after the proposal is validated against the current driving path, field feasibility, and resource availability.

Questions 51-75

Question 51

Topic: Conduct Scheduling Duties

During a power-plant outage update, the scheduler reviews this instruction:

Data date: August 15, 2026
Turnover milestone baseline/contract date: November 30, 2026
Logic-driven forecast after status: December 12, 2026
Approved work calendar: 5 days/week
Requested edit: change remaining field work to 7 days/week
Requested edit: add Must Finish On November 30 to turnover
Recovery resources/approval: none

Which response best addresses the real issue?

• A. Delay issuing the update until management approves a recovery plan.
• B. Rebaseline the turnover milestone to December 12 for this reporting cycle.
• C. Apply the requested edits and keep the milestone at November 30.
• D. Keep the factual 5-day update, report variance, and model recovery separately after approval.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The issue is an attempt to force the forecast back to the contractual date with unapproved calendar and constraint changes. A defensible correction is to keep the honest status-based forecast, measure variance against the approved baseline, and test any recovery separately only after the assumptions are approved.

A legitimate schedule adjustment must be supported by actual status, approved logic changes, or approved resource and calendar changes. Here, the requested 7-day calendar and hard finish constraint are not backed by approved recovery resources or an authorized recovery plan; they are being used to make the report align with the contract date. That is misleading because it changes the forecast without evidence.

The proper response is to keep the August 15 update factual:

• retain the approved 5-day calendar
• keep the logic-driven December 12 forecast
• report the variance against the unchanged baseline
• analyze weekend work or other compression in a separate what-if or approved recovery scenario

The key takeaway is that recovery planning can change the future plan, but it should not overwrite honest status or hide current variance.

It separates factual status from unapproved recovery assumptions and preserves the baseline as the control reference.

Question 52

Topic: Conduct Scheduling Duties

Data date is June 30, 2026. The approved baseline includes a required contract milestone, Mechanical Completion, on August 29, 2026. After statusing, the integrated schedule forecasts September 10, 2026, so the milestone now has 8 workdays of negative total float on the piping/turnover driving path. A civil subcontractor asks to use 5 of the 12 workdays float on its own path and says that float belongs to its package. The prime contract states total float is a shared project resource. A piping-overtime recovery could recover 6 workdays but would add cost and needs owner approval. What should the scheduler recommend first?

• A. Approve the civil delay because its path still has positive float.
• B. Reset the milestone baseline to the forecast finish before reporting.
• C. Implement piping overtime now and seek owner cost approval later.
• D. Escalate the negative float, treat float as shared, and present driving-path recovery choices for approval.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: Negative float on a required contract milestone means the project is already forecasting late against a contractual date. The best response is to escalate the issue using the approved baseline, recognize that float is shared, and present feasible recovery options that decision makers can authorize.

The core concept is that negative float on a required milestone is not just a scheduling detail; it signals an active stakeholder and contractual issue because the current forecast misses the committed date. Since the contract states total float is a shared project resource, the civil subcontractor cannot claim exclusive ownership of float for unilateral use. The scheduler should therefore communicate the 8-workday deficit against the approved baseline, identify the driving path, and present realistic recovery choices with their resource and approval implications.

Implementing overtime immediately would bypass required approval, and resetting the baseline would hide variance instead of preserving the control reference. The right priority is evidence-based escalation and decision-oriented recovery planning.

The required milestone is already forecast late, so the negative float is a current contractual issue and recovery must be presented against the baseline with proper approval.

Question 53

Topic: Conduct Planning Duties

During a baseline-readiness review for a refinery outage, the scheduler submits this package:

Data date: May 10, 2027
Purpose stated: "Approve baseline"
Included: statused schedule update with actual starts
Forecast completion: June 28, 2027
CR-12 modeled in logic; approval pending
Meeting note: "Owner accepted the current finish forecast"

The basis of schedule is complete, but no record identifies which schedule becomes the approved performance reference. Which action best corrects the real control problem?

• A. Approve a defined baseline reference and handle the update, forecast, and CR-12 separately.
• B. Approve CR-12 first so the modeled schedule is automatically baseline-ready.
• C. Use owner acceptance of the finish date as baseline approval evidence.
• D. Validate the statused update, then use that accepted forecast as baseline.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: A schedule baseline is a formally approved reference, not just the latest reviewed dates. Accepting a forecast, validating a status update, and approving a change request are separate control actions and do not by themselves establish the baseline.

The key concept is keeping schedule approvals distinct. A baseline schedule is the approved reference used to measure future schedule performance, and it should be clearly identified with supporting approval evidence. A current forecast is only the expected outcome based on the latest status and assumptions. A schedule update validates actual starts, finishes, and remaining work as of the data date. A change request authorizes a proposed scope or schedule change.

In the scenario, the team has mixed all three into a package labeled “approve baseline.” The owner accepted a forecast date, the schedule contains statused progress, and a pending change is already modeled, but none of that explicitly approves the performance baseline. The right correction is to designate and approve the baseline reference and basis of schedule, then manage the update and CR-12 through their own processes.

The main trap is confusing review of the latest forecast with approval of the control baseline.

Baseline approval must explicitly establish the approved reference schedule and basis, while the forecast, update, and pending change remain separate controls.

Question 54

Topic: Conduct Scheduling Duties

As of the May 31, 2026 data date on a refinery turnaround, activity Valve package delivery had 6 workdays of total float to the required Mechanical Completion milestone on June 30. The vendor now confirms a 4-workday delay. A preliminary CPM check shows that, if this delay is accepted, the required milestone and project finish forecast remain unchanged. What is the next appropriate step?

• A. Rebaseline the milestone because the activity can no longer meet its baseline date.
• B. Update the model, report the consumed float, and watch the path as near-critical.
• C. Start schedule recovery now because the vendor delay already affects completion.
• D. Issue a delay-impact notice stating the required milestone is forecast late.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: A delay is not automatically a milestone impact. Here, the 4-workday delay is less than the 6 workdays of total float, so the immediate effect is float consumption, not slippage of the required milestone or forecast finish. The proper next step is to update the schedule, communicate the reduced float, and monitor the path more closely.

The key distinction is between delay duration and schedule impact. This activity had 6 workdays of total float, and the confirmed delay is 4 workdays, so the delay first consumes schedule margin. Because the CPM check shows no movement to the required Mechanical Completion milestone or the project finish forecast, the schedule control response should be an update-and-monitor action, not a recovery or baseline-change action.

• Incorporate the confirmed delay into the current schedule model.
• Recalculate and verify the remaining float and current driving path.
• Report that float has been reduced and the path now deserves closer monitoring.

Recovery, escalation of a missed milestone, or rebaselining becomes appropriate only if the delay actually affects the required date or forecast finish.

The delay uses available float but does not move the required milestone or finish forecast, so the next step is to reflect float erosion and increase monitoring.

Question 55

Topic: Conduct Planning Duties

During front-end planning for a utility upgrade, the team is reviewing an early level-2 schedule. Detailed design is 35% complete, the transformer delivery date is based on a budgetary vendor quote, the environmental permit duration is estimated at 6 to 10 weeks, and no schedule baseline has been approved. The sponsor asks the planner to report that the project “will” meet the December 15 energization date. What is the best professional response?

• A. Present December 15 as a conditional planning date, disclose the vendor and permit assumptions in the basis of schedule, and state that no baseline is yet approved.
• B. Keep December 15 in the summary, but omit unresolved assumptions until they are confirmed.
• C. State that the project will meet December 15, noting that details will be refined later.
• D. Adopt December 15 as the baseline now so all stakeholders work to one firm date.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The schedule date is being presented too confidently for its maturity. A sound planning communication should show December 15 as conditional, disclose the major procurement and permit assumptions behind it, and avoid implying that an approved baseline already exists.

In planning, schedule communication should match the maturity of the underlying assumptions. Here, design is only 35% complete, a key equipment date comes from a budgetary quote, permit duration is still a range, and no baseline has been approved. Those facts mean December 15 may be a useful planning target, but it is not yet a committed control date. The best response is to communicate the date with its material assumptions and uncertainty so decision-makers understand both the opportunity and the conditions required to achieve it.

• State the date as preliminary or conditional.
• Name the assumptions that materially drive it.
• Explain that baseline approval has not yet occurred.

A simpler but firmer message would look cleaner, yet it would reduce schedule credibility.

This matches the communication to the schedule’s maturity and makes the material assumptions visible before any baseline commitment is implied.

Question 56

Topic: Conduct Planning Duties

A project team has approved the WBS and contract milestones but has not yet built the detailed schedule model. During planning, procurement states that a packaged compressor requires approved vendor submittals before fabrication release, the fabricator has a fixed 10-week production window, delivery depends on completion of the temporary access road, and commissioning requires both permanent power and a vendor specialist on site. What is the next appropriate step?

• A. Capture these interfaces, windows, and assumptions in the activity/milestone list and basis of schedule.
• B. Use date constraints to hold fabrication and startup to the milestone.
• C. Build construction logic first and add vendor details after award.
• D. Track only delivery in the schedule and leave submittals and startup in logs.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: Before detailed schedule development, long-lead procurement and commissioning facts should be translated into explicit planning inputs. Vendor submittals, fabrication windows, delivery prerequisites, and startup interfaces belong in the activity or milestone definition and basis of schedule so the later model is traceable and logic-driven.

In PSP practice, vendor and commissioning information like this is not something to “fill in later.” Once the WBS and milestone framework are set, the next step is to document the required submittal-review cycle, release-to-fabrication point, fabrication window, delivery dependency on site access, and commissioning prerequisites such as permanent power and vendor support. Those items should be reflected in the activity or milestone list and the basis of schedule so the eventual schedule model can apply proper logic, calendars, and interface assumptions.

• Define the key review, fabrication, delivery, and startup events.
• Capture access windows and other calendar limitations.
• Record the commissioning handoffs and required prerequisites.
• Document the assumptions before building the detailed logic network.

Waiting to add these later, collapsing them into one delivery date, or forcing dates with constraints weakens schedule quality and forecast credibility.

These are planning inputs that must be defined and documented before the logic-driven schedule model is developed.

Question 57

Topic: Conduct Scheduling Duties

As of the June 14, 2026 data date, a critical-path activity has this update:

Activity: Cable Pull Area B
Physical progress rule: installed cable length
Physical complete: 65%
Remaining duration: 4 workdays

Which additional evidence best supports confidence that this current forecast is credible?

• A. The baseline finish still remains ahead of the required energization date.
• B. Charged labor hours are 64% of budgeted hours, close to the 65% update.
• C. 13,000 of 20,000 ft are installed, recent output is 1,800 ft/day, and crew/access are confirmed for the next four workdays.
• D. The superintendent expects weather and rework interruptions to end next week.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: The strongest support for a forecast is objective evidence that the reported remaining duration is achievable. For a quantity-based activity, installed quantity, recent productivity, and confirmed crew/access directly test whether 4 workdays is realistic as of the data date.

In a schedule update, the best evidence is current, objective, and directly linked to the remaining work. Here, progress is measured by installed cable length, so the most credible support for the 4-workday forecast is quantity installed, recent production rate, and confirmation that the needed crew and access will be available.

• Objective quantity confirms the 65% status.
• Recent output shows whether the remaining quantity can be finished in 4 workdays.
• Confirmed crew and access test whether that production rate is actually achievable.

Cost alignment is only an indirect indicator, baseline margin does not validate the forecast itself, and an optimistic opinion is not reliable update evidence.

It directly ties remaining duration to objective progress, demonstrated productivity, and confirmed execution conditions.

Question 58

Topic: Conduct Scheduling Duties

At the July 15, 2026 data date, the accepted current schedule shows A130 Install switchgear starting July 18 on the driving path to interface milestone M-240 Energize substation, with 2 workdays total float to M-240. All listed work uses a Monday-Friday calendar. A new owner access restriction blocks the switchgear room for 4 workdays beginning on A130’s forecast start, and the scheduler says M-240 will slip 2 workdays. Which evidence best validates that conclusion?

• A. Matching the owner restriction dates to field records confirms the event occurred.
• B. Reviewing the baseline path confirms A130 was critical before the event.
• C. Comparing the 4-workday restriction with 2 workdays of float shows a 2-day overrun.
• D. Inserting a 4-workday fragnet into the accepted current schedule recalculates M-240 2 workdays later.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The best validation is a time-impact style recalculation in the accepted current schedule at the data date. That check tests the restriction against the live logic, calendar, and remaining float to confirm whether the interface milestone forecast really moves by 2 workdays.

When a new event may affect a critical or near-critical path, the strongest validation is a recalculation in the accepted current schedule as of the data date. Here, the access restriction begins on A130’s forecast start and the path to M-240 has only 2 workdays of total float. A 4-workday fragnet tied to the affected sequence, using the same working calendar, shows whether the event actually consumes float and pushes the interface milestone 2 workdays. Event occurrence records help confirm facts, but they do not prove schedule impact. Baseline criticality is historical, and simple subtraction cannot confirm overlap, logic interaction, or whether another path becomes driving. The key evidence is modeled impact in the current network.

A modeled fragnet in the current accepted schedule is the strongest validation because it tests the event against current logic, calendar, float, and milestone forecast.

Question 59

Topic: Conduct Planning Duties

An owner is preparing the baseline schedule for a refinery turnaround. The project has a fixed outage window, contractual milestones tied to liquidated damages, separate engineering and field calendars, and monthly integrated cost/schedule analysis at the control-account level. Scope packages are defined, but planning assumptions, progress-measurement rules, and update/forecast conventions are not yet documented. What is the best action for the PSP planner before baseline approval?

• A. Begin monthly variance reporting from the preliminary activity list and refine the model afterward.
• B. Develop and align a basis of schedule that ties objectives, assumptions, calendars, control accounts, and status/forecast rules to the schedule model.
• C. Have the scheduler finalize network logic first and address reporting needs later.
• D. Baseline the schedule now and document assumptions during the first update.

Best answer: B

What this tests: Conduct Planning Duties

Explanation: The PSP planning role is to connect project objectives and planning assumptions to the schedule model before it becomes the baseline for control. In this scenario, missing basis-of-schedule and update rules would weaken later monitoring, forecasting, and integrated cost/schedule analysis.

Within AACE Total Cost Management, planning is not separate from later schedule control; it establishes the basis that makes the schedule usable for development, statusing, forecasting, and analysis. Here, the fixed outage, contractual milestones, different calendars, and control-account reporting all affect how the schedule must be built and how progress will later be measured.

• Confirm alignment of scope, WBS/control accounts, and key milestones.
• Document assumptions, calendars, inclusions, exclusions, and logic basis.
• Define progress-measurement, update, and forecast conventions before baselining.
• Approve the baseline only after the schedule model reflects that documented basis.

Finishing logic or issuing reports first may seem faster, but it produces a schedule that is harder to monitor consistently and less credible for integrated analysis.

This creates the documented planning foundation needed for credible schedule development, monitoring, updating, forecasting, and integrated analysis.

Question 60

Topic: Conduct Planning Duties

A contractor is requesting baseline approval for a wastewater plant schedule. Monthly variance reporting begins next period, engineering uses a 5-day calendar while construction uses a 6-day calendar, and an owner-approved bypass change was added before the mechanical completion milestone. The approval package includes only a PDF bar chart and milestone dates; it does not preserve the baseline schedule model, basis of schedule, or approval record for the incorporated change. What is the best action?

• A. Approve the package now and capture missing assumptions in the first update report.
• B. Freeze contract milestones now and explain activity-level differences in monthly narratives.
• C. Treat the first current forecast as the reference for future schedule comparisons.
• D. Complete the package with model, basis, calendars, and approved-change evidence before approval.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: The baseline must be more than frozen dates; it needs traceable approval evidence. Preserving the approved model, basis assumptions, calendars, and incorporated change allows later updates to compare actual and forecast performance against the same approved reference.

A baseline is only useful for control if later users can reconstruct what was approved and why. In this scenario, future reports must compare status and forecast against an approved reference across different calendars and an incorporated owner change. A PDF bar chart and milestone list do not preserve the schedule model logic, baseline data date, calendar assumptions, or evidence that the bypass change was part of the approved baseline. The better action is to complete the baseline package before approval so variance analysis, update validation, forecast comparison, and schedule-impact communication remain supportable.

• Preserve the approved schedule model or baseline snapshot.
• Document key assumptions, calendars, constraints, and milestone definitions in the basis of schedule.
• Include the formal approval record and approved-change evidence tied to the baseline freeze.

Using later narratives or forecasts as substitutes would weaken schedule control and obscure true variance.

A usable baseline must preserve the approved model, assumptions, calendars, and incorporated changes so later comparisons remain traceable and credible.

Question 61

Topic: Conduct Planning Duties

A contractor is preparing the baseline schedule for a substation upgrade. The owner requires weekly variance analysis and a monthly executive schedule report. The draft update plan currently includes:

• status collection every Friday
• responsibility by discipline lead
• percent complete as the only required field for in-progress activities

No rules are defined for actual start/finish dates, remaining duration, objective measurement, source evidence, or milestone ownership. What is the next appropriate step?

• A. Define objective update rules for actual dates, physical progress, remaining duration, evidence, and milestone ownership before baselining.
• B. Baseline now and decide which status fields are missing after the first report.
• C. Report only contractual milestone dates because executive reporting does not need detailed activity status.
• D. Have leads enter expected finish dates manually instead of collecting detailed status inputs.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: Percent complete alone is not enough for reliable schedule control. Before approving the baseline, the team should define objective progress-measurement rules and mandatory status inputs so monitoring, variance analysis, and reporting are consistent from the first update.

In PSP practice, status-readiness is part of planning quality. A schedule can be logic-complete and still be weak for control if the update process does not define what data must be collected and how progress will be measured objectively. Percent complete by itself usually does not establish actual start or finish dates, support a defensible remaining duration, or provide evidence for forecast changes.

A sound next step is to define the update basis before baselining, including:

• required status fields for each update
• objective progress rules by activity type
• evidence sources and responsible owners
• milestone status responsibility

That gives the project consistent inputs for monitoring, variance analysis, forecasting, and stakeholder reporting. Baseline approval should follow, not precede, that readiness check.

Those inputs are needed for traceable status, credible forecasts, and meaningful variance reporting from the first update cycle.

Question 62

Topic: Conduct Scheduling Duties

The integrated project schedule has been updated through the data date of August 15, 2026, and the turnover milestone is now forecast 12 workdays late. Stakeholders want to compare four recovery ideas: resequence cable pull after partial energization, add one electrical crew, work Saturdays for 5 weeks, or defer a non-critical reporting package. What is the next best scheduling step?

• A. Add finish constraints to hold the turnover milestone, then test which option removes the negative float.
• B. Apply the most promising recovery option in the live schedule first, then review the new forecast with stakeholders.
• C. Rebaseline the turnover milestone before analysis so each option can be measured against a current target date.
• D. Create separate what-if copies of the current statused schedule and model each option with documented assumptions before comparing milestone impacts.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: When stakeholders want to compare recovery strategies, the scheduler should test them in separate what-if versions of the current statused schedule model. That preserves the approved baseline and the official forecast while producing traceable comparisons of logic, resource, calendar, or scope changes.

The core concept is controlled what-if analysis from the current schedule update, not from the baseline and not in the live working forecast. Because the schedule has already been statused through August 15, 2026, the next step is to copy that current model and test each recovery idea separately with clear assumptions so stakeholders can compare finish-date movement and side effects.

• Start from the current statused schedule model.
• Create separate scenarios for sequence, resource, calendar, or scope changes.
• Change one option set at a time and document assumptions.
• Compare resulting milestone dates, float changes, and feasibility before recommending action.

The closest distractor is editing the live schedule first, but that bypasses disciplined comparison and can overwrite the official forecast before any option is approved.

What-if analysis should be performed on controlled copies of the current statused schedule so each option’s effect can be compared without altering the approved baseline or live forecast.

Question 63

Topic: Conduct Scheduling Duties

Data date: May 28, 2026. Before a turnover review, the project manager asks whether to escalate an owner notice and launch recovery for package handoff M-340. The only summary currently in the meeting package is the milestone table below; it does not show driving activities, total float to the required date, or the basis for remaining durations on predecessor interface work.

Exhibit: Milestone table

What is the next appropriate step?

• A. Direct recovery on all predecessor milestones to regain baseline.
• B. Report no impact because the required date is still met.
• C. Escalate immediately because the handoff baseline has slipped.
• D. Trace the handoff’s driving path and validate predecessor status.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The milestone table is a useful warning signal, but it is not enough by itself to justify escalation or recovery. Before advising stakeholders, the scheduler should verify what is actually driving the handoff milestone, how much float remains to the required date, and whether the predecessor interface updates are credible.

A milestone table summarizes dates; it does not explain why a milestone moved or whether action is warranted. Here, the handoff forecast is later than baseline but still before the required date, and the table omits the key evidence needed for a decision: driving path, total float, and update quality on predecessor interface work. The next step is to analyze the updated integrated schedule and confirm whether the forecasted handoff date is both logic-driven and reliable.

• Identify which predecessor activities are driving M-340.
• Check total float to the June 23 required date.
• Validate actuals and remaining durations on the interface work.

Immediate escalation treats variance as proof of impact, while blanket recovery may target work that is not actually controlling the handoff.

Stakeholder decisions need evidence beyond milestone dates, especially the driving path, float, and credibility of the underlying update.

Question 64

Topic: Conduct Scheduling Duties

A process-plant project is preparing a baseline for approval. The approved basis of schedule states that construction and commissioning will be controlled through three system turnovers, and monthly status reports must show variance by turnover package. The proposed model instead uses one plantwide Mechanical Complete milestone feeding one commissioning path for the whole facility, although it still meets the final contractual completion date. Which evidence best validates withholding baseline approval?

• A. A logic check shows each non-start/end activity has predecessors and successors.
• B. A critical-path report shows the contract completion milestone still has float.
• C. A traceability review shows the model omits turnover milestones and handoff logic.
• D. A resource review shows monthly staffing aligns with the craft plan.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: The strongest validation is direct traceability between the basis of schedule and the schedule model. If the project will execute and report by system turnover, a baseline without turnover milestones and handoff logic will be difficult to update, analyze, and control later even if the current finish date is acceptable.

Baseline approval should confirm more than an acceptable finish date. The schedule model must support how the project will actually execute, status progress, analyze variance, and communicate impacts. In this case, the basis of schedule defines three turnover packages as the control and reporting structure. If the model collapses that strategy into one plantwide handoff, the team will not be able to measure slippage, identify driving paths, or explain impacts by turnover package in a credible way.

A traceability review is the best evidence because it directly compares the approved planning basis with the modeled milestones and logic. Float, clean logic, and reasonable staffing are useful quality checks, but they do not solve a model structure that conflicts with the execution strategy.

It directly proves the schedule model does not reflect the approved execution and control basis, creating later status and variance problems.

Question 65

Topic: Conduct Scheduling Duties

Data date is August 31, 2026. In a first-pass monthly update for a refinery turnaround schedule, the contractual milestone Unit Restart shows the following. Here, SPI = EV/PV, and values below 1.0 indicate behind plan.

The current driving path to Unit Restart has 0 total float; a parallel path has 12 workdays float. What is the next most appropriate step?

• A. Record the slippage as a schedule risk and wait for the next update cycle.
• B. Rebaseline the milestone to September 30 so future reports match the current plan.
• C. Validate the driving-path status and remaining durations, then develop targeted recovery options.
• D. Compress the parallel path with 12 workdays float to improve schedule performance quickly.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: The metrics show a deteriorating schedule condition, not a reporting artifact. Because the slipped contractual milestone is on the current driving path with zero float, the next step is to validate the update data on that path and analyze feasible recovery actions.

In schedule control, variance and trend data tell you whether focused analysis is needed. Here, the forecast for the contractual milestone moved from 4 workdays late to 8 workdays late versus baseline, and SPI dropped from 0.94 to 0.89, showing worsening performance. Because the milestone sits on the current driving path with 0 total float, the slippage is an active schedule issue affecting the forecast, not just a possible future risk.

The proper next step is to confirm the status and remaining-duration inputs on the driving activities, then evaluate recovery options on the work actually controlling the milestone. Rebaselining would hide variance without fixing it, and compressing a path that still has 12 workdays float does not protect the contractual date. The key is to analyze the driving cause before choosing corrective action.

Worsening SPI and milestone variance on a zero-float driving path require validation and recovery analysis before any baseline change or broad action.

Question 66

Topic: Conduct Scheduling Duties

Before approving a refinery turnaround baseline, you review two hydrotest activities for Units 1 and 2. Each is 6 days on the same 24-hour outage calendar, both are scheduled in parallel, and both are assigned to the same named hydrotest crew. Each activity has appropriate technical predecessors and successors, the basis of schedule states that only one hydrotest crew will be available during the outage, and no date constraints are applied. What is the best professional action before approving the baseline?

• A. Flag a communication evidence issue and approve after documenting the overlap.
• B. Flag a calendar assumption issue and change the hydrotests to a 5-day calendar.
• C. Flag a resource realism issue and re-sequence or resource-load the hydrotests.
• D. Flag a logic issue and add a finish-to-start tie only to stop overlap.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: This is primarily a resource realism problem. The baseline allows both hydrotests to run at the same time, but the basis of schedule says only one crew is available, so the model is not executable as planned.

Baseline validation checks whether the approved schedule can actually be performed as modeled. In this scenario, the decisive fact is the mismatch between parallel hydrotest work and the documented availability of only one hydrotest crew. That makes the concern resource realism, not logic, because the activities already have appropriate technical relationships; not calendar assumptions, because the stated outage calendar may still be correct; and not communication evidence, because a narrative cannot cure an infeasible plan.

The proper response is to make the baseline reflect real execution conditions by re-sequencing the work or resource-loading it against actual crew limits. Adding artificial logic just to stop overlap can hide the underlying resource assumption instead of validating it. The key takeaway is that a baseline must be both logic-driven and resource-feasible.

The schedule is logically connected and unconstrained, but the planned overlap conflicts with the documented single-crew assumption.

Question 67

Topic: Conduct Scheduling Duties

At the July 1, 2026 data date on a utility expansion project, the contractual Mechanical Completion milestone has a required date of August 15, 2026, a forecast finish of August 22, 2026, and 5 workdays of negative float on the driving path. The access restriction causing the slip has already occurred. The contract says total float is a shared project resource, and baseline dates may change only through approved change control. What is the best action for the scheduler?

• A. Escalate the required-date miss with negative-float evidence, the shared-float clause, and recovery/change options
• B. Tell the team the contractor controls float because it built the schedule
• C. Replace the baseline date with August 22 in the current update
• D. Log the delay as a risk and wait for next period’s update

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: Negative float against a contractual required date is an active schedule issue, not just a modeling condition. The scheduler should communicate the miss and its basis immediately, respect the contract’s shared-float rule, and support recovery planning or formal change control rather than hide or delay the problem.

Negative float means the current forecast is later than a required or constrained date. Here, the July 1, 2026 update already shows Mechanical Completion forecast after its contractual required date, so the schedule condition is a present issue that needs stakeholder attention. Because the contract defines float as a shared project resource, the scheduler should not declare that one party owns or may reserve float unilaterally. The professional response is to report the data date, affected milestone, amount and cause of negative float, and the decision needed, then support management with recovery options and, if justified, a formal change request. Replacing the baseline with the forecast would erase performance visibility, and waiting would misclassify an active delay as a future uncertainty.

It addresses an active contractual schedule issue with current evidence, respects shared float, and supports recovery or formal change control without hiding variance.

Question 68

Topic: Conduct Scheduling Duties

A refinery turnaround tracks schedule performance in weighted progress units, not dollars. At the April 30, 2026 data date, the exchanger package shows:

Use \( SPI = \frac{EV}{PV} \).

Which interpretation is most accurate?

• A. The package is ahead of schedule, with SPI = 1.11, so no recovery review is needed.
• B. The package is 10% under budget, so cost control action is required.
• C. The package is behind schedule, with SPI = 0.90, so recovery review is triggered.
• D. The package will finish exactly 10% late, so it should be rebaselined now.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: Compute SPI from the supplied schedule progress units: \(225/250 = 0.90\). An SPI below 1.00 means less work was earned than planned by the data date, and the stated trigger of 0.95 means this package should enter recovery review.

SPI compares earned progress with planned progress at the data date. Here the project uses weighted schedule units, so the interpretation is about schedule performance, not cost.

• EV = 225 units
• PV = 250 units
• \(SPI = 225/250 = 0.90\)

An SPI of 0.90 means the package has achieved 90% of the progress that was planned by April 30, 2026, so it is behind schedule. Because the project basis says any package with SPI below 0.95 requires recovery review, this result crosses the trigger. The key takeaway is that SPI indicates relative progress performance at the status date; it does not, by itself, prove an exact finish-date delay or justify rebaselining.

Using \(225/250 = 0.90\), the package has earned only 90% of planned progress by the data date, which is behind schedule and below the 0.95 trigger.

Question 69

Topic: Conduct Scheduling Duties

You are reviewing a contractor delay-impact note during the June 30, 2026 schedule update. The project uses both 5-day engineering and 6-day construction calendars. The note claims that late owner approval caused an 8-workday delay to Ready for Startup, but it provides only this excerpt:

Cause: IFC drawing approval finished June 18
Claimed impact: Ready for Startup moved July 24 -> August 3
Support: 'Approval delay directly pushed startup'
Missing: referenced baseline/update, data date,
         logic path, applicable calendar

What is the next appropriate step?

• A. Accept the 8-workday claim from the milestone slippage shown.
• B. Request the baseline/update, verify data date and calendar, then trace driving logic.
• C. Insert an 8-day lag between approval and startup in the current schedule.
• D. Recommend rebaselining the startup milestone before reporting June status.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The claim is unsupported because it gives dates without the schedule context needed to test impact. A proper review must first identify the approved baseline or update, confirm the data date and calendar, and verify that the delayed activity actually drives the milestone.

In delay-impact analysis, a late activity date does not automatically prove schedule impact. The review must be anchored to the correct schedule artifact and timing facts: which approved baseline or current update is being compared, what the data date is, which calendar applies, and how the delayed activity connects through driving logic to the affected milestone. Without those facts, the reported movement could be float consumption, a non-driving path, a calendar mismatch, or a comparison between different schedule versions.

The proper next step is to obtain and validate the missing schedule basis, then test or trace the impact in the model. Accepting the claim, forcing in a lag, or rebaselining would bypass schedule-control discipline and could turn an unsupported narrative into a reported fact.

A delay claim is not supportable until it is tied to the correct schedule version, status date, calendar, and driving path.

Question 70

Topic: Conduct Scheduling Duties

Data date: September 12, 2026. A shutdown contract requires Unit Backfeed by October 3, 2026. The approved baseline gave the cable-pull path 6 workdays of total float. After an owner-directed outage-window change, the current update forecasts Unit Backfeed on October 7, 2026, with -3 workdays total float on the same driving path. The contractor says the owner simply consumed “contractor float” and that no recovery meeting is needed. Which evidence best validates the scheduler’s decision to escalate this as a contractual and recovery-planning issue?

• A. Review the approved change log for the outage-window shift.
• B. Review the baseline float report for the cable-pull path.
• C. Review update completeness for actual starts and finishes.
• D. Review the float-ownership clause and current driving-path report.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The decision should be validated with evidence that addresses both parts of the issue: float ownership and current contractual impact. The strongest support is the governing float language plus current CPM evidence that the required milestone is now on a negative-float driving path.

When float use is disputed, a scheduler should validate two things before escalating: what the governing documents say about float ownership, and whether the current schedule update shows an actual threat to a required milestone. Here, the update already forecasts Unit Backfeed late and shows negative total float on the driving path, so this is no longer just a routine variance discussion. Reviewing the float-ownership clause establishes whether the contractor can claim exclusive use of float, while the current driving-path report confirms that the path now affects a contractual date and therefore needs recovery planning. A change log or historical baseline float value may explain background, but neither one proves the present contractual exposure by itself. The key distinction is that current negative float to a required milestone turns a float dispute into a control and recovery issue.

It validates both the disputed right to use float and the current negative-float impact to the required milestone.

Question 71

Topic: Conduct Planning Duties

The integrated schedule for a process-plant upgrade is under baseline review. The basis of schedule says any package on the path to Startup must have a confirmed execution calendar, an identified resource source with availability for the planned start window, and subcontractor concurrence on the duration basis.

Exhibit: Planning evidence

Which analysis is most defensible?

• A. The schedule is ready for baseline because all three packages have durations and logical ties.
• B. MCC installation is sufficiently validated because the prior-project duration is acceptable until the subcontractor mobilizes.
• C. None of the packages are baseline-ready until every subcontractor provides activity-level labor loading for each trade.
• D. Steel erection and loop checks are sufficiently validated, but MCC installation needs further validation before baseline approval.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: Baseline readiness depends on credible support for planned durations and dates, not just the presence of logic and durations. Steel erection and loop checks have confirmed resource source, availability, and calendar assumptions, while MCC installation still relies on an unconfirmed historical duration and unvalidated access basis.

For planning-duty baseline review, the key test is whether driving work is supported well enough to make the baseline credible. That does not always require detailed labor loading at the lowest level, but it does require evidence that the planned duration can actually be achieved.

Steel erection is supported by defined crews, confirmed availability, and the correct execution calendar. Loop checks are also supported because the OEM resource source, availability, and calendar are identified. MCC installation is different: its duration was copied from prior work, and the electrical subcontractor has not confirmed crew availability or the room-access sequence that may control productivity. That package still needs validation before the baseline is approved.

A historical duration can inform planning, but it cannot replace current resource and subcontractor confirmation for a driving package.

Confirmed resources, calendars, and concurrence support steel erection and loop checks, but MCC installation still lacks validated subcontractor and access assumptions.

Question 72

Topic: Conduct Planning Duties

An owner is deciding whether to accept a contractor’s first baseline schedule for a process-unit revamp. The proposed completion date meets the contract milestone, but the PSP reviewer wants evidence that the plan is truly ready for baseline approval. Which review result best validates baseline readiness?

• A. Logic validation confirms no open ends, one longest path, and only contractual date constraints.
• B. Management approval confirms the proposed finish date and reporting format are acceptable.
• C. Milestone audit confirms every contract and interface milestone appears in the proposed baseline.
• D. Cross-functional readiness review confirms WBS traceability, constructable sequence, realistic crew loading, and documented assumptions/exclusions.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: Baseline acceptance should be supported by evidence that the schedule is complete, traceable, buildable, resource-feasible, and based on documented assumptions. A cross-functional readiness review covering those points is stronger than milestone compliance, logic cleanliness, or management sign-off alone.

Before approving a baseline, the key question is not whether the finish date looks acceptable; it is whether the underlying planning basis is credible and controllable. The strongest validation is an integrated readiness review showing that scope elements are fully traced into scheduled activities and milestones, the planned sequence has been checked for field constructability, labor demand fits agreed resource availability, and the basis of schedule documents the assumptions, calendars, exclusions, and interfaces used to build the model. Those checks provide objective evidence that the baseline can support later monitoring, updating, and forecasting.

A clean logic report, a complete milestone list, or management sign-off may all support approval, but each is only partial evidence if used alone.

This is the strongest evidence because it directly tests completeness, traceability, constructability, resource realism, and the documented basis needed before baseline acceptance.

Question 73

Topic: Conduct Scheduling Duties

At the July 31, 2026 data date, a scheduler is drafting the weekly executive summary.

Exhibit: update facts

Which summary statement best separates fact, issue, assumption/risk, forecast, variance, and recommendation?

• A. As of July 31, the vendor’s August 18 shipment notice is the only variance, while the October 14 finish is just an assumption until more progress is recorded. Because no change is approved, no recommendation should be made.
• B. As of July 31, the vendor’s revised August 18 shipment date is a fact and the resulting critical-path delay is an active issue; the schedule now forecasts mechanical completion on October 14, 14 days later than the September 30 baseline. Recovering up to 5 workdays assumes weekend access approval, so that recovery remains a risk until approved, and management should decide whether to authorize the recovery plan.
• C. As of July 31, mechanical completion will be October 14 because weekend access will recover 5 days and the transformer delay remains only a risk. The baseline should be revised now so reports match the likely finish.
• D. As of July 31, the project is 14 days behind, so October 14 should be reported as the new committed date. The vendor notice and pending weekend approval are both facts already built into the recovery plan.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The best statement separates what is known now from what is still contingent. It treats the vendor notice as fact, the critical-path delay as an issue, the October 14 date as a forecast with a 14-day variance to baseline, and the weekend recovery as conditional rather than certain.

Good schedule reporting is decision-ready: it distinguishes observed facts, current issues, uncertain future conditions, forecast dates, and recommended actions. In this update, the vendor’s revised shipment date is a confirmed fact. Because that delayed shipment already affects the critical path, it is an active issue, not just a risk. The October 14 mechanical completion date is the current forecast, and its variance is 14 days later than the September 30 baseline. The possible 5-day recovery is not committed work because it depends on pending weekend access approval; that dependency is an assumption, and the chance that approval is not granted is a remaining schedule risk. A strong executive summary then states the needed management action clearly rather than hiding the variance or rewriting the baseline.

It correctly distinguishes confirmed status from contingent recovery, reports the baseline variance as a forecast, and ends with a decision-oriented recommendation.

Question 74

Topic: Conduct Scheduling Duties

Exhibit:

• Data date: July 10, 2026
• Prior forecast for Ready for Startup: August 27, 2026
• Current forecast for Ready for Startup: September 3, 2026
• Standard project calendar: Monday-Friday
• Pipe pressure test: in progress; 1 workday late
• Approved change CR-12: adds Owner witness test, 3 workdays remaining, FS after pressure test
• Owner witness test resource: sole owner representative available only Monday and Wednesday
• Turnover package approval: 2 workdays remaining, FS after witness test
• Milestone constraint: finish-no-later-than August 28, 2026

What is the best diagnostic or correction?

• A. Wait to model CR-12 until the baseline is formally revised.
• B. Reduce pressure-test remaining duration to absorb the delay.
• C. Remove the finish-no-later-than date before reporting the update.
• D. Trace the forecast through CR-12 and the owner’s Monday/Wednesday calendar.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: Forecast movement should be explained from the current driving path, not from the most visible late activity. Here, the pressure test is only 1 workday late, while the approved witness test adds new remaining work on a restricted availability pattern that can account for the larger slip.

To interpret milestone movement, start with the current forecast logic and remaining work at the data date. A 1-workday delay on Pipe pressure test does not reasonably explain a milestone moving from August 27 to September 3. The more likely driver is approved change CR-12, which inserted Owner witness test as an FS successor and tied it to a scarce resource available only Monday and Wednesday. That restricted resource calendar stretches 3 workdays across more elapsed time, and the following 2-day approval activity pushes the milestone further.

The finish-no-later-than August 28 date should remain because it is a contractual control date; it should reveal variance or negative float, not be deleted to make the update look better. Approved changes also belong in the current forecast immediately. Simply shortening remaining duration on the pressure test would make the forecast less credible.

CR-12 adds driving remaining work on a restricted owner calendar, which explains more movement than the one-day pressure-test slip.

Question 75

Topic: Conduct Scheduling Duties

A scheduler is finalizing the baseline for WBS 3.2, whose deliverable is Fire alarm system installed, tested, and accepted. Field supervisors say progress cannot be statused consistently. The quality review confirms that logic is complete, calendars are correct, and no date constraints are driving the work.

Exhibit: Activity excerpt

Which correction best addresses the real issue?

• A. Split all activities into one-day tasks before baseline approval
• B. Keep the list and distinguish duplicates with new activity codes
• C. Retain the list but update only remaining duration each period
• D. Create unique, measurable deliverable activities and move support work to LOE

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The problem is not logic, calendars, or constraints; it is poor activity definition. Several activities are duplicated, too broad, or nonmeasurable, so the schedule should be rebuilt into discrete deliverable-based tasks, with ongoing support effort handled separately if needed.

This is an activity-definition and WBS-traceability problem. A good schedule activity should represent a discrete, measurable piece of work or a clear milestone tied to a deliverable. In the excerpt, Manage fire alarm work and Support turnover as needed are ongoing effort statements, Install devices appears twice without clear distinction, and Fire alarm is too broad to status objectively.

The best correction is to rewrite the work into unique activities linked to specific deliverables or completion events, and to handle true ongoing support as level of effort (LOE) or in an appropriate support area. That gives the team objective status points and preserves schedule-model clarity. Simply changing codes, update technique, or granularity does not fix vague, duplicated, or poorly traceable activities.

It fixes the root problem by replacing vague and duplicated work statements with discrete activities traceable to the WBS deliverable.

Questions 76-100

Question 76

Topic: Conduct Planning Duties

A contractor submits an integrated schedule model for baseline approval. The file includes an approved WBS, activity list, logic ties, durations, and contractual milestones. The package does not include a basis-of-schedule narrative, calendar assignments, progress-measurement and status-cutoff rules for future updates, or the rationale for imposed date constraints.

The owner wants to use this model for baseline approval, monthly status updates, variance analysis, and executive reporting. Which analysis is most accurate?

• A. Ready; logic ties and milestones are enough for baseline control.
• B. Ready now; update rules can be standardized after first reporting.
• C. Not ready; missing schedule basis prevents credible control and reporting.
• D. Hold approval; every activity needs daily crew-level loading.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: The key gap is missing planning basis, not missing network mechanics. A schedule can calculate dates, but without documented calendars, assumptions, constraint rationale, and update rules, it cannot support defensible baseline approval or consistent later analysis.

A schedule model can credibly support control only when the planning basis behind its dates is documented and traceable. In this scenario, the network structure exists, but the package omits core basis-of-schedule elements that explain how dates were built and how future status will be applied. Without that information, teams may update progress inconsistently, reported variance cannot be tied back to an approved basis, and stakeholder communication will lack supportable schedule logic.

Useful minimum planning information includes:

• calendar and work-period rules
• progress-measurement and status-cutoff conventions
• key assumptions, exclusions, and imposed-constraint rationale

A model that calculates critical path is not automatically ready to become the approved control baseline.

A workable network is not enough; baseline approval also requires documented basis-of-schedule information to support consistent updates and defensible variance analysis.

Question 77

Topic: Conduct Scheduling Duties

Data date September 30, 2026. In a refinery turnaround update, the baseline finish for the contractual Unit Back Online milestone is October 28, 2026, and the current forecast for that milestone is still October 28, unchanged for the last two updates. The report shows overall SPI = 0.91 and a 10-day adverse variance on the critical work package, while the trend note says, “Recovery underway; no milestone impact expected.” Field review found four current driving-path valve-replacement activities reported 85%-95% complete, but each kept the same remaining duration as the prior update and none had objective quantity-installed backup, even though a two-day access loss has already occurred.

Which evidence best validates the scheduler’s conclusion that the unchanged milestone forecast is not yet defensible?

• A. Review showing the driving-path valve work lacks objective progress backup and revised remaining durations
• B. Confirmation that the contractual milestone currently has zero total float
• C. Comparison showing non-driving support work gained float this update
• D. Trend chart showing overall SPI declined from 0.93 to 0.91

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: When milestone movement, variance, and narrative conflict, the best validation comes from the quality of the status data on the current driving path. High reported progress with no objective backup and unchanged remaining durations after a known disruption makes the unchanged milestone forecast unreliable.

A milestone forecast is only as credible as the update data supporting the activities currently driving it. Here, the SPI and adverse variance suggest schedule pressure, the trend note claims recovery, and the milestone date has not moved. The most defensible validation check is whether the driving-path activities were updated with objective progress evidence and realistic remaining durations after the access loss.

• Verify the current driving path to the milestone.
• Check that reported physical progress is supported by field evidence.
• Confirm remaining durations were revised to reflect actual conditions and the disruption.

A declining SPI or zero float can indicate concern, but neither proves the unchanged milestone forecast is valid. If the driving work is statused with stale or unsupported data, the unchanged forecast should not be accepted as credible.

Forecast credibility depends on valid status and remaining-duration data on the current driving path, so unsupported updates there are the strongest evidence against the unchanged date.

Question 78

Topic: Conduct Planning Duties

A scheduler submits a draft basis of schedule for baseline approval on a process-unit upgrade. The reviewer must understand how the main owner-facing dates and their sequence were developed. The current excerpt states:

Key dates:
- IFC piping issue: June 10
- Equipment on site: August 25
- Mechanical completion: November 30
Assumptions:
- Normal contractor productivity
- One workfront per area
- Commissioning follows construction

The schedule model uses a 5-day engineering calendar and a 6-day construction calendar. The equipment purchase order is not yet awarded, and IFC piping depends on a client model review that is still pending approval. Which revision should be prioritized before baseline approval?

• A. Attach a full CPM network printout from the current schedule model.
• B. Approve the baseline now and explain the date rationale in the first update.
• C. Add a milestone-basis table linking each key date to its source, driving sequence, calendar, and pending approval assumptions.
• D. Add detailed craft-loading and earned-value weights for all construction activities.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: A basis of schedule should explain why key dates are credible, not just list them. The best improvement is the one that ties each date to its source, logic basis, calendar, and unresolved approvals so a reviewer can judge traceability and uncertainty before baseline approval.

The core issue is evidence quality in the basis of schedule. A reviewer needs to see how milestone dates were derived, what sequence drives them, which calendar applies, and whether any unapproved inputs or uncertain assumptions affect those dates. A compact milestone-basis table does that directly: it connects each key date to a control reference or planning assumption, shows the logic basis, and makes pending approvals visible.

That is better than adding large amounts of schedule output or resource detail because the learning objective is not to show everything in the model; it is to document the rationale behind the key dates and sequences. A full network printout is output, not explanation, and delaying the rationale until after approval weakens baseline control. The best choice is the targeted addition that improves traceability before the baseline is approved.

This adds the minimum traceable evidence a reviewer needs to understand how dates and sequences were developed before approving the baseline.

Question 79

Topic: Conduct Scheduling Duties

At the September 5, 2026 data date, a contractor is preparing the weekly owner turnover review for Substation A. All dates are calendar dates. The owner requires 48-hour notice if the energization turnover milestone will miss its required date.

Exhibit: Turnover milestone facts

Which action should the scheduler prioritize for the review?

• A. Discuss only the 2-day loop-check delay for now, and wait until punch closeout finishes before stating milestone impact.
• B. Escalate using the approved September 18 forecast, show the worsening trend and the +6/+3 day baseline and required-date impacts, and keep weekend work contingent.
• C. Report a likely September 16 outcome, assume weekend recovery will be approved, and delay escalation until staffing is confirmed.
• D. Reset the baseline milestone to September 18 so reporting aligns with current conditions before the owner review.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The best response is to report the approved current forecast against both the baseline and the owner’s required date. Here the milestone has worsened from September 14 to September 18, which is 6 days late to baseline and 3 days late to the required date, so it should be escalated as an active issue.

In milestone control, three references matter: the approved baseline for variance, the current approved forecast for expected completion, and the required date for commitment impact. This update shows deterioration from a September 14 prior forecast to a September 18 current forecast, which is 6 days late to baseline and 3 days late to the owner’s required date. Because the weekend crew is neither approved nor committed, it is a recovery scenario, not the official forecast. The scheduler should therefore report the September 18 date as current status, escalate the turnover as an active issue, and present weekend work separately for approval.

The closest alternative assumes a recovery date that the project has not yet authorized or staffed.

It preserves the approved control references, quantifies the commitment breach, and keeps an unapproved recovery idea separate from official status.

Question 80

Topic: Conduct Scheduling Duties

A highway rehabilitation project is being updated at the June 15, 2026 data date. The approved basis of schedule states that only one paving crew is available, only one lane-closure permit can be active at a time, and Segment 2 work starts only after Segment 1 is accepted by the owner. The contract milestone is Open all lanes by September 30, 2026. In the current schedule model, Segment 2 paving is linked to Segment 1 paving with an SS + 2 days relationship so the milestone still forecasts September 30. The field superintendent confirms concurrent paving is impossible. What is the best correction?

• A. Keep the overlapping logic and rely on resource leveling during execution to separate the segments.
• B. Reduce paving durations until the milestone meets September 30 without changing the current sequence.
• C. Change Segment 2 paving to follow Segment 1 owner acceptance, keep September 30 as the required milestone date, then recalculate and report the impact.
• D. Add a finish-no-later-than constraint to Segment 2 completion so the contractual date remains in the forecast.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: When the schedule model conflicts with the approved basis of schedule and confirmed field sequence, the logic must be corrected first. The contractual date should remain a control requirement for measuring forecast impact, not a reason to keep impossible overlap in the network.

The core issue is schedule-model credibility. The approved planning basis and field confirmation both say the work is resource- and permit-constrained: only one segment can be paved at a time, and Segment 2 cannot start until Segment 1 is accepted. That makes the current SS + 2 days link invalid, even if it helps the model hit September 30.

The best action is to replace the relationship with the true sequence, rerun the schedule, and then communicate any float loss, negative float, or recovery need against the contract milestone. A contractual date is a control point for monitoring performance; it should not be protected by artificial overlap, unsupported duration cuts, or forced dates that hide the real forecast.

A realistic forecast is more valuable than an on-paper date produced by bad logic.

This restores a credible logic sequence from the approved execution basis and uses the contract date to measure impact rather than to force an unrealistic forecast.

Question 81

Topic: Conduct Scheduling Duties

At the August 14, 2026 data date, the project uses a 5-day workweek with no holidays. For this question, use forecast movement = current forecast finish - prior forecast finish and baseline variance = current forecast finish - baseline finish. All finish values below are schedule-model outputs in workdays (wd) after the data date.

Update notes:

• System integration test is on the driving path; its remaining duration increased from 6 wd to 11 wd.
• Operator training slipped 3 wd on a parallel path but still has 4 wd total float.

Which explanation is best for stakeholders who need decision-ready schedule information?

• A. Completion moved 9 workdays later than the prior forecast because both delayed activities now drive the finish, so recovery should be split equally.
• B. Completion moved 5 workdays later because operator training used all float and became the finish driver, so recovery should focus there.
• C. Completion moved 4 workdays later than the prior forecast, so the next report should replace the baseline with the current forecast.
• D. Completion moved 5 workdays later than the prior forecast and 9 later than baseline; the driving-path integration test caused it, while operator training only consumed float.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The current forecast is 39 wd after the data date versus 34 wd in the prior forecast and 30 wd in the baseline. That means the finish moved 5 wd later than the prior forecast and 9 wd later than baseline, and the only stated driver is the integration test because it is on the driving path while operator training still has float.

Decision-ready schedule communication should quantify the movement, identify the driver, and separate finish impact from float consumption. Here, the current forecast is 39 workdays after the data date, compared with 34 in the prior forecast and 30 in the approved baseline.

The update note says System integration test is on the driving path and its remaining duration increased from 6 wd to 11 wd, which explains the 5-workday finish movement. Operator training slipped 3 wd, but it still has 4 wd of total float, so it consumed float without moving project completion. The best explanation therefore states the amount of movement and attributes it to the driving-path change, not to the parallel-path slip or a baseline reset.

It correctly calculates both movements and ties the finish slip to the only stated driving-path change.

Question 82

Topic: Conduct Planning Duties

An infrastructure project has an approved baseline schedule B0. The schedule management plan states that discipline reviewers may comment on draft updates, but only the project sponsor and project controls manager may approve a new baseline after approved change control. Monthly updates must report the current forecast against B0, and every issued native model must have a unique revision ID tied to the transmittal and change log.

At the June 30 data date, the lead scheduler incorporates reviewer comments into the update file, renames it Final, sends stakeholders a PDF with only the revised finish dates, and states that the “revised baseline is approved.” No change approval exists, and the native file cannot be tied to a revision history.

Which correction best addresses the real governance problem?

• A. Publish only the revised dates so stakeholders focus on the current plan instead of variance.
• B. Keep B0 as the approved baseline, issue the June 30 dates as forecast, and assign controlled revision IDs linked to approvals and change records.
• C. Treat reviewer concurrence as sufficient and note that the June 30 file supersedes B0.
• D. Keep the PDF as the record copy and leave the native model outside formal revision control.

Best answer: B

What this tests: Conduct Planning Duties

Explanation: The issue is governance discipline, not schedule logic. Reviewer comments do not authorize a baseline change, forecast dates must be communicated separately from the approved baseline, and the issued model must be traceable through formal version control.

Schedule governance should clearly separate review authority, baseline approval, forecast communication, and version control. In this scenario, B0 remains the only approved baseline because no approved change control exists and the named approvers have not authorized a new baseline. The June 30 file should therefore be issued as a status update and forecast against B0, not described as an approved revised baseline. The native schedule model also needs a controlled revision ID tied to the transmittal, approval record, and change log so later audits, updates, and impact analysis can identify exactly what was reviewed, issued, and approved. Treating reviewer input as approval is the closest trap, but technical review authority is not the same as baseline approval authority.

This preserves formal baseline authority, separates forecast reporting from baseline control, and restores model-version traceability.

Question 83

Topic: Conduct Scheduling Duties

A substation schedule update is being reviewed.

Exhibit:

Data date: June 15, 2026
Calendar: 5-day workweek
Required milestone: Ready for Energization by July 24, 2026
Current forecast: July 31, 2026
Total float to milestone: -5d

Current model logic:
- Pull MV cable for Areas 1-5 (single activity)
  -> FS to Terminate and test panels for Areas 1-5 (single activity)
  -> FS to Ready for Energization

Field status:
- Areas 1-3 are already released from cable pulling.
- Termination can start in any released area.

The scheduler proposes adding a 5-day lead on the finish-to-start link to show overlap. Which diagnostic or correction best addresses the real issue?

• A. Crash panel termination before changing the logic.
• B. Rebaseline the milestone to the current forecast.
• C. Add a 5-day lead to the finish-to-start link.
• D. Model area-by-area handoffs and recalculate the driving path.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The issue is not just a late milestone; it is that the dependency structure does not reflect how work is actually handed off. Correcting the logic to match area-by-area release gives a credible forecast, more accurate float consumption, and better recovery targeting.

The core concept is dependency credibility. A single finish-to-start link between two combined activities forces all cable pulling to finish before any termination can start, even though three areas are already available and the work can proceed progressively. That modeling choice can create an artificial critical path, consume float unnecessarily, and overstate the milestone delay.

The better correction is to model the real handoffs, typically by splitting the work into area-based or turnover-package activities, and then recalculate the schedule. Once the logic matches the field execution plan, the scheduler can see which path is truly driving, which work is near-critical, and where recovery effort will actually help. Adding arbitrary lead only masks the modeling problem, while rebaselining or crashing first can drive the wrong control action.

The real problem is overly coarse FS logic that blocks valid progressive turnover and can misstate the true critical and near-critical paths.

Question 84

Topic: Conduct Scheduling Duties

At the August 15, 2026 data date, the integrated schedule shows the contractual milestone Mechanical Completion - Area B forecast for November 7 against a required date of October 31. The project manager asks the scheduler to change the existing FS logic between Cable Pull Complete and Terminate & Megger to SS+5 and add a Finish On or Before October 31 constraint so the monthly report shows on time. Field leads say overlap is only possible if cable work is replanned into releasable sections, but the current model has one lump-sum cable activity and no approved recovery resources. What is the best action?

• A. Change to SS+5 now because overlap appears feasible in the field.
• B. Keep the late forecast and test recovery separately until section-based logic is defined and supported.
• C. Reduce remaining duration now and document recovery support next month.
• D. Add the required-date constraint now and remove it after reporting.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The requested edits are date-driven, not evidence-driven. Because overlap requires a different activity breakdown and there are no approved recovery assumptions, the live control schedule should keep the logic-based late forecast and evaluate recovery in a separate what-if analysis.

A schedule model should be changed only when the revision makes the forecast more realistic. In this case, the proposed SS+5 relationship is not yet supported by the current activity structure, because the work is still modeled as one lump-sum cable activity rather than releasable sections. Adding a hard milestone constraint would be even worse, because it would hide the real forecast variance instead of representing executable logic.

• Keep the current control schedule logic-driven.
• Test any recovery idea in a separate scenario or what-if analysis.
• Revise the live model only after section-based activities, logic, and assumptions are documented and supportable.

The tempting alternative is to add overlap immediately, but a possibility in principle is not enough to justify a forecast change.

This preserves a logic-driven forecast and avoids forcing dates until the model reflects a documented, executable overlap plan.

Question 85

Topic: Conduct Planning Duties

During baseline review for a refinery turnaround, the Unit B turnover milestone moves from October 14 to October 20 after the integrated schedule is recalculated. No affected work has started; the data date is still July 1. The scheduler suspects the shift is caused by piping tie-in activities using a 7D-24H calendar while the approved basis of schedule requires all outage work to use the OUTAGE-6D calendar. Which evidence best validates treating this as a planning issue rather than a routine reporting variance?

• A. A status log confirming the affected activities still have no actual starts as of July 1.
• B. A calendar audit showing tie-in activities use 7D-24H despite the basis-of-schedule requirement for OUTAGE-6D.
• C. A milestone report showing turnover moved six days later than the preliminary target.
• D. A subcontractor recovery note proposing weekend work to regain the six days.

Best answer: B

What this tests: Conduct Planning Duties

Explanation: The strongest validation is evidence that the assigned activity calendars conflict with the approved basis of schedule. When the milestone shift comes from an incorrect or inconsistent calendar assumption before execution starts, it is a planning-quality issue, not a routine reporting variance.

Calendar selection is a planning parameter documented in the basis of schedule. In this scenario, no affected work has started, and the suspected cause is a mismatch between the activity calendar used in the model and the approved outage calendar. The best validation is a calendar-assignment audit that traces the affected activities back to that documented rule. That shows the date movement is caused by inconsistent schedule setup, so it should be resolved through planning and model quality control rather than reported as execution variance. A variance report only shows the effect, a no-start status does not prove the source, and a recovery note assumes the slippage is an execution problem before the planning basis has been checked. Validate the calendar input first before treating the movement as performance variance.

This directly links the date movement to an inconsistent planning input in the schedule model, not to execution performance.

Question 86

Topic: Conduct Scheduling Duties

The monthly owner report is due today. As of the June 30 data date, the contractual mechanical completion milestone still forecasts October 15, but that date depends on a second-shift recovery plan that has not been approved and for which electricians have not been confirmed. In addition, the current critical-path activity was reported 40% complete in the field, yet no actual start or revised remaining duration was loaded into the update. The draft executive summary says, “Project remains on track to meet October 15; the recent delay has been recovered.” What is the best action?

• A. Omit the milestone forecast and report only overall progress until next period.
• B. Issue the summary as written because the forecast still meets October 15.
• C. Revise the summary to describe October 15 as conditional pending critical-path status validation and approved recovery resources.
• D. Declare the milestone delayed now because the second shift is not yet approved.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: The draft report claims confidence that the facts do not support. A critical-path forecast should not be presented as fully recovered when key status data are missing and the recovery plan depends on unapproved, unconfirmed resources.

Decision-ready schedule reporting must distinguish a calculated forecast from a well-supported forecast. In this case, the October 15 date may still appear in the schedule, but confidence is overstated because the activity driving the milestone has incomplete update data and the recovery plan relies on unresolved assumptions about approval and staffing. The best professional response is to communicate the date as conditional, disclose the data-quality concern, and note that recovery feasibility still requires validation.

• Verify the actual start and remaining duration for the driving activity.
• Confirm whether the second shift is approved and staffed.
• Report the milestone confidence level only after those points are resolved.

A firm “delay recovered” message is weaker than a transparent conditional forecast tied to evidence.

It avoids overstating confidence by separating the calculated forecast from unresolved status data and unverified recovery feasibility.

Question 87

Topic: Conduct Planning Duties

During baseline planning for a plant retrofit, the scheduler must define the progress rule for the work package Install and test 40 pumps. The package is planned for 20 workdays on a 5-day calendar with one crew providing 4 crew-days per workday. Historical work content is 1.5 crew-days to install each pump and 0.5 crew-day to test each pump. At a sample update after 8 workdays, 18 pumps are installed and 10 are tested. For a quantity-based rule, percent complete = earned crew-days / total crew-days, and remaining duration = remaining crew-days / 4. Which approach best supports objective status updates, physical progress validation, remaining-duration estimates, and forecast credibility?

• A. Use a 50/50 rule: 50% once started
• B. Use crew-day weighting: 32/80 = 40%, 12 workdays remaining
• C. Use equal install/test milestone points: 28/80 = 35% complete
• D. Use elapsed duration: 8/20 = 40% complete

Best answer: B

What this tests: Conduct Planning Duties

Explanation: For discrete work, the progress rule should tie status to measurable output and actual effort. Weighting installation and testing by crew-days does that, so field counts can validate percent complete and remaining work can be translated into a credible forecast.

The strongest planning choice is a weighted physical-progress rule based on measurable quantities and their work content. Here, installation uses three times the effort of testing, so a rule based only on elapsed time, coarse start/finish milestones, or equal milestone weights will distort real progress. Defining this rule in the basis of schedule makes future updates more objective and forecast-ready.

• Total work content = 40 × (1.5 + 0.5) = 80 crew-days.
• Earned work at the sample update = 18 × 1.5 + 10 × 0.5 = 32 crew-days.
• Physical progress = 32 / 80 = 40%.
• Remaining duration = (80 - 32) / 4 = 12 workdays.

A time-based rule may coincidentally show the same percentage at one update, but it does not prove physical accomplishment or support the same forecast credibility.

Crew-day weighting matches the 1.5-to-0.5 work split, so verified counts convert into objective progress and a defensible remaining-duration forecast.

Question 88

Topic: Conduct Planning Duties

At a pre-execution gate review for a refinery tank replacement, the integrated schedule covers all approved scope, has documented calendars and logic assumptions, and meets the required turnover milestone with 12 workdays of total float. Internal schedule-quality comments are closed, and no work has started as of the June 1, 2027 data date. A vendor warns that a pending regulator comment could add 10 workdays to fabrication release, but no directive or approved change request exists. The owner needs a control schedule before notice to proceed. What is the best approval decision now?

• A. Accept a later forecast and use it as the control reference.
• B. Validate a schedule update before approving any schedule.
• C. Approve the baseline schedule and log the vendor warning as a risk.
• D. Approve a milestone-extension change request from the warning.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: A baseline schedule can be approved when approved scope, logic, calendars, and review evidence are complete enough to establish the control reference. Here, no work has started and no change is approved, so the vendor warning remains a risk to monitor rather than a forecast to accept, an update to validate, or a change to approve.

The key distinction is the type of approval being made. A baseline schedule is approved when the model for the approved scope is complete, quality-reviewed, and ready to become the control reference for future measurement. In the stem, those readiness conditions are met: scope is approved, logic and calendars are documented, comments are closed, and the required milestone is achievable.

The vendor note does not change that approval decision because it describes a possible future impact, not an actual status condition and not an approved change. Since no work has started, there is no schedule update to validate with actual dates or remaining duration. And without an authorized change, there is no basis to extend milestone commitments.

The right action is to approve the baseline and separately track the uncertainty through risk management and later impact analysis if it occurs.

The schedule is ready to serve as the approved control reference, while the vendor warning is still an untriggered risk rather than status or an approved change.

Question 89

Topic: Conduct Planning Duties

An owner hands a baseline substation schedule to a new scheduler for monthly updates and later delay analysis. The schedule model contains the items below, but the basis-of-schedule document says only, Logic and durations reviewed with the team.

- Pour transformer foundation -> Set transformer: FS + 14 workdays
- Civil work calendar: 6 days/week
- Milestone: Utility outage window
- Energization milestone constraint: Must Finish On October 31, 2026

Which correction best addresses the real issue?

• A. Run schedule diagnostics and hand off the model once logic and float checks pass.
• B. Replace the lag and outage milestone with more detailed activities so the model explains itself.
• C. Expand the basis of schedule with the rationale, source, and ownership for each lag, calendar, milestone, and constraint.
• D. Remove the Must Finish On constraint so the new scheduler can rely only on calculated dates.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: The real issue is insufficient planning evidence, not simply model detail or schedule-health metrics. Another scheduler needs documented reasons for the lag, special calendar, outage milestone, and date constraint before updating or analyzing the schedule with confidence.

In PSP practice, the basis of schedule is the artifact that explains why the schedule model was built the way it was. For a clean handoff, another scheduling professional must be able to trace non-obvious modeling choices such as lags, special calendars, interface milestones, and date constraints back to their source and planning basis. Here, the note reviewed with the team is too vague; it does not say whether the 14-workday lag is curing time or site-access delay, whether the 6-day calendar is contractual or assumed overtime, or whether the October 31 date is a contract requirement, outage commitment, or management target.

• Document the modeling decision.
• Identify the source and owner.
• State the assumption or external requirement.
• Preserve traceability for future updates and analysis.

Adding detail or running diagnostics may help model quality, but neither replaces documented planning evidence.

The handoff problem is missing traceable planning evidence, so the basis of schedule must explain why those modeling choices were used.

Question 90

Topic: Conduct Planning Duties

A utility substation upgrade is ready for baseline review. The draft basis of schedule already includes the WBS, contract milestones, and default calendars, but the critical path depends on a vendor lead time, an owner-controlled outage window, and one shared crane. Management wants future monthly updates to explain any forecast movement credibly. The planner can add only one section before approval. Which addition should be prioritized?

• A. Executive dashboard with baseline milestones, variance colors, and report cadence
• B. Vendor lead-time source, outage-window basis, shared-crane limit, exclusions, and status rules
• C. Recovery scenario using a second crane and weekend shifts before approval
• D. Critical-path printout with early/late dates, float values, and logic report

Best answer: B

What this tests: Conduct Planning Duties

Explanation: A basis of schedule should preserve the rationale behind baseline dates, especially on critical-path work. Documenting the vendor-duration source, outage-window basis, resource limit, exclusions, and status rules gives reviewers a defensible baseline and gives later updates a traceable explanation for forecast movement.

The key purpose of a basis of schedule is to explain why the schedule was built the way it was, not just to restate dates or show model outputs. In this case, the most valuable addition is the documented source of the vendor lead time, the rationale for the owner-controlled outage window, the shared-crane resource assumption, any exclusions, and the rules for statusing remaining work. Those items support baseline review because they show whether the critical-path dates are credible, and they support future updates because they let the scheduler explain whether slippage came from performance, a changed assumption, a resource limit, or an external interface. A dashboard or float printout may help reporting, but neither captures the underlying schedule rationale. A recovery scenario should remain separate until it is approved.

This documents the assumptions, constraints, resource limits, exclusions, and update basis needed to defend the baseline and explain later forecast changes.

Question 91

Topic: Conduct Planning Duties

An owner is preparing the baseline for a process-unit expansion. Project objectives include partial turnover on September 1, 2027, and final startup on November 15, 2027; the cost team will measure performance through WBS-based control accounts, but several long-lead durations still rely on vendor budget quotes and progress-measurement rules are not yet defined. In a Total Cost Management context, which action should the PSP planning lead prioritize?

• A. Issue a milestone dashboard now and defer integration details until execution.
• B. Finish detailed CPM logic now and capture assumptions later in update narratives.
• C. Document a basis of schedule linking objectives, WBS/control accounts, calendars, assumptions, logic, and progress rules before baseline approval.
• D. Baseline sponsor target dates now so performance reporting can begin immediately.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: The best priority is to establish a basis of schedule that connects project objectives to the schedule model and control structure before baseline approval. In TCM, that planning foundation supports not only schedule development, but also later status updates, forecasting, and integrated cost-schedule analysis.

PSP planning should create the bridge between what the project must achieve and how the schedule will be built, controlled, and analyzed later. In this scenario, the milestone objectives are known, but key planning inputs are still incomplete: some durations are based on preliminary vendor quotes, progress rules are undefined, and cost performance will be tracked through WBS-based control accounts. The planning lead should therefore prioritize a basis of schedule that documents assumptions, calendars, milestone logic, exclusions, and alignment to the control structure before the baseline is approved.

• Confirm the logic basis and planning assumptions.
• Define how progress and remaining work will be measured.
• Align schedule coding with the cost-control structure.

That gives the scheduling team a credible model and gives project controls a valid reference for future monitoring and forecasting. A faster baseline or cleaner report would not provide the same control integrity.

This creates the approved planning foundation needed for credible schedule development and later monitoring, updating, forecasting, and integrated analysis.

Question 92

Topic: Conduct Scheduling Duties

A contractor submits an EPC baseline schedule for approval. The validation check shows:

Most constrained internal activities were forced to match management handoff targets rather than external commitments. Before baseline approval, which correction best addresses the real schedule-quality issue and protects later variance analysis?

• A. Review each hard constraint, keep only externally required dates, replace the rest with logic-driven relationships or milestones, and recalculate the schedule.
• B. Approve the baseline because the schedule has no open ends and currently meets the required milestones.
• C. Retain the internal constraints and use monthly variance reports to monitor whether those handoff dates hold.
• D. Increase activity detail and progress codes for each handoff area before approving the baseline.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The main problem is not missing logic ends; it is excessive hard constraints on internal work. Because the schedule moves 21 workdays later when those constraints are removed, the baseline is being date-forced and should be corrected to a logic-driven model before approval.

A baseline schedule should be approved only after its dates are shown to come from valid logic, calendars, and justified constraints. Here, the zero open ends are a good sign, but they do not offset the larger problem: 143 internal activities are being forced to target dates, and a test run shows those constraints are masking a 21-workday finish impact.

Before approval, the scheduler should:

• review each hard constraint for external justification
• keep only true contractual, regulatory, or access-date constraints
• replace internal target dates with proper logic or milestone structure
• recalculate float and the driving path

That approach protects future variance analysis, because baseline comparisons will then reflect real schedule performance instead of manually imposed dates. Simply meeting milestones on paper is not enough if the dates were forced.

This removes artificial date forcing so float, driving path, and later variance are based on defensible schedule logic.

Question 93

Topic: Conduct Planning Duties

During final baseline-readiness review for a water-treatment expansion, the team notes:

Which analysis is best?

• A. Baseline approval should be withheld until the dashboard format is finalized.
• B. Baseline approval should be withheld because required completion scope and logic are missing.
• C. Baseline approval can proceed because mechanical completion is close to final completion.
• D. Baseline approval can proceed because the missing test work can be added in a later update.

Best answer: B

What this tests: Conduct Planning Duties

Explanation: A baseline is not ready for approval if the schedule model omits work required to achieve a contractual milestone. Here, final completion depends on startup, turnover, and a 14-day test, so a model ending at mechanical completion is incomplete and cannot support valid baseline control.

The core issue is baseline completeness, not reporting administration. A credible baseline schedule must include the full scope and logic needed to achieve each contractual milestone. Because final completion is earned only after a successful 14-day performance test, the model cannot stop at mechanical completion; omitting startup, turnover, and test activities means the contractual finish date, driving path, and float to that milestone are not actually represented. Adding that missing scope after approval would not be a routine progress update—it would change the approved baseline content itself. By contrast, revising the dashboard format is a communication task that can be completed without changing schedule logic or scope. Mechanical completion may be important, but it is not an acceptable substitute for the contract-defined completion event.

A baseline cannot be approved when work required to achieve the contract completion milestone is absent from the schedule model.

Question 94

Topic: Conduct Scheduling Duties

Data date: August 1, 2026. All activities use a 5-day calendar. The current logic-driven update shows Path A at 0 days total float and Path B at 2 days total float. A single E&I specialist crew supports key activities on both paths during August, and the basis of schedule assumed full crew availability. The owner has now confirmed that the crew will be unavailable for 4 workdays, August 18–21, on another outage. A superintendent proposes weekend overtime on Path A only. Which action should the scheduler prioritize?

• A. Keep the forecast unchanged until the crew absence starts and track the situation only as a risk.
• B. Model the confirmed crew outage, test whether Path B becomes driving, and recommend only resource-feasible recovery against the baseline.
• C. Start weekend overtime on Path A because the current zero-float path remains the main priority.
• D. Rebaseline now to the reduced crew availability, then decide whether any recovery is needed.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: A confirmed reduction in a shared specialist crew can consume near-critical float and change the driving path. The best choice is to update the forecast with that known resource loss, then evaluate recovery options that are actually feasible, while keeping the approved baseline intact for performance measurement.

Resource availability affects schedule feasibility, not just activity dates. Here, the schedule has only a 2-day gap between the current critical path and the near-critical path, and both rely on the same specialist crew. A confirmed 4-workday loss of that crew can consume Path B’s float, shift the driving path, or make a Path A-only overtime plan ineffective. The scheduler should first incorporate the known outage into the forecast, recalculate the resource-feasible result, and then compare recovery options that can actually be staffed.

• Keep the approved baseline as the control reference.
• Recheck which path is driving after the outage is modeled.
• Recommend overtime or added resources only if they improve the forecasted finish.

The key takeaway is that recovery should follow a credible resource-based forecast, not the original logic-only critical path.

Known resource loss must be modeled in the forecast before selecting recovery, because it may shift the driving path while the baseline remains the control reference.

Question 95

Topic: Conduct Scheduling Duties

Data date: June 14, 2026. All activities use the same 5-day calendar. The owner will fund overtime on only one path this month. The approved control schedule is measured against the contractual milestone Ready for Startup.

Exhibit: TF = total float

Which work should the scheduler recommend prioritizing first to best protect the approved contractual startup date?

• A. Software patch, SAT, and operator training
• B. Drain change and retest
• C. Fireproofing, insulation, and paint touch-up
• D. MCC install, cable pull, and loop checks

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The best priority is the path with verified zero total float that directly drives the contractual milestone in the approved control schedule. That makes the MCC install-cable pull-loop checks chain the strongest recovery focus when only one overtime package is available.

The key concept is to prioritize the current driving or critical path in the approved schedule control reference, not simply the path that looks busy or urgent. Here, the MCC install, cable pull, and loop checks chain has 0d total float, directly links to Ready for Startup, has verified status, and already has approved overtime available.

• A path with positive float is not the first recovery priority because it can slip without immediately moving the milestone.
• A near-critical path may deserve monitoring, but it is still secondary to a verified zero-float path.
• A pending change modeled only in a what-if fragnet is not the approved basis for first-priority recovery action.

The closest distractor is the software path, but its remaining uncertainty and 1d float still make it less urgent than the verified zero-float path.

This is the verified zero-float path in the approved control schedule, so it is the current driving path to the contractual milestone.

Question 96

Topic: Conduct Scheduling Duties

Data date is July 15, 2026. In an EPC facility startup schedule, the contractual owner-ready milestone is required by August 29, 2026. During update review, the scheduler finds that commissioning has no predecessor because a logic link was deleted, piping rework is shown 80% complete with 2 days remaining although field verification is about 40% complete, and the forecast assumes weekend crews even though no weekend work is approved. The milestone still forecasts August 29 because it carries a Must Finish On August 29 constraint. What is the best action?

• A. Keep the update unchanged and manually state a later finish in the report.
• B. Publish the August 29 forecast because the contractual date still appears met.
• C. Remove only the Must Finish On constraint, then request a rebaseline if the date slips.
• D. Reconcile status to field evidence, restore logic, replace unsupported resource/calendar assumptions, and rerun the forecast before reporting it.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: A forecast is credible only when it is logic-driven and supported by valid status and approved resource assumptions. Here, deleted logic, unsupported progress, unapproved weekend crews, and a hard milestone constraint can all distort the finish date, so the model should be corrected and recalculated before it is used.

A reliable forecast must come from a logic-driven schedule model with supportable status and realistic resource assumptions. In this scenario, the August 29 date is not trustworthy because the update contains an open end created by deleted logic, progress and remaining duration that conflict with field evidence, and weekend crews that are not approved. The Must Finish On constraint can further mask true finish movement by forcing the milestone date instead of letting the network calculate it.

• Restore the missing dependency and check for other dangling logic.
• Update progress and remaining duration from objective status evidence.
• Replace unapproved recovery calendars or resources with approved assumptions, then rerun the forecast.

The right control action is to repair the schedule basis first, before any report or what-if analysis.

The forecast cannot be trusted until missing logic, unsupported status, unapproved resource calendars, and the artificial milestone constraint are addressed.

Question 97

Topic: Conduct Scheduling Duties

During the July 15, 2026 update of a power project, the contractual energization milestone now forecasts September 8, 2026 and shows 6 workdays of negative float against its required August 29, 2026 date. The baseline critical path ran through cable terminations, but after statusing the month, the critical path shifted to testing. The scheduler deleted the finish-to-start link from cable terminations to testing because testing had already started in the field before terminations were fully complete. What is the best diagnostic check?

• A. Cut remaining durations to remove negative float.
• B. Trace driving logic for deleted ties, out-of-sequence status, and dangling activities.
• C. Add a finish constraint to force the prior path.
• D. Replace the required date with the current forecast.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The unexpected path appeared after a logical relationship was removed to allow status entry. The best first step is to trace the driving path and validate whether out-of-sequence progress or dangling logic distorted the forecast and negative float.

When a finish forecast or critical path changes unexpectedly, first test the integrity of the affected schedule logic before changing dates or durations. Here, testing started out of sequence, and the finish-to-start link from cable terminations was deleted to accommodate that status. That can create a dangling or open-ended path, making the calculated critical path and negative float unreliable. The strongest diagnostic is to trace the milestone’s current driving predecessors backward and confirm that incomplete work, actual starts, and predecessor/successor ties still represent the real execution sequence.

• Start at the late milestone and identify its current driving path.
• Check whether any links were removed or left open during statusing.
• Verify actual starts and remaining duration on the out-of-sequence work.
• Recalculate only after restoring valid logic or documenting the proper modeling approach.

Changing required dates, forcing constraints, or shortening durations may hide the symptom, but they do not diagnose the model-quality problem.

Deleting a relationship to enter progress can create a false driving path, so the first check is the affected logic and status for dangling or out-of-sequence conditions.

Question 98

Topic: Conduct Scheduling Duties

An EPC contractor has completed a proposed baseline schedule for a compressor-station project. The project controls manager must decide whether it is ready for baseline approval, knowing the baseline will later be used for milestone variance analysis. Which review result is the strongest evidence that approval is justified?

• A. Discipline leads say the planned durations look reasonable based on similar past projects.
• B. A schedule quality review confirms WBS traceability, no unexplained open ends, calendars and constraints match the basis of schedule, and resource assumptions are documented.
• C. A CPM report shows one critical path and positive float on all near-critical activities.
• D. A milestone check shows all contract dates are met after adding finish constraints to major deliverables.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The best evidence is an objective schedule-quality review that validates scope coverage, logic integrity, calendars, constraints, and documented assumptions. Those checks protect later variance analysis because baseline dates come from a credible schedule model, not from forced dates or subjective confidence.

A baseline should be approved only after the schedule model has been validated as a reliable control document. For later variance analysis to be defensible, baseline dates must come from complete scope coverage, sound logic, correct calendars, justified constraints, and documented assumptions, not from optimism or manually imposed milestone dates.

• Trace WBS or control-account scope to activities and milestones.
• Check logic quality, especially unexplained open ends and artificial constraints.
• Verify calendars, resource assumptions, and basis-of-schedule notes align with the model.

A report showing only positive float or stakeholder confidence may look encouraging, but it does not validate the baseline’s integrity.

This review result shows the baseline is traceable, logic-driven, and documented well enough to support credible future variance analysis.

Question 99

Topic: Conduct Scheduling Duties

A power-plant outage team is archiving closeout records. The review found that owner drawing approval for three exchanger packages was planned at 7 working days, but actual approvals averaged 15 working days; each approval activity fed fabrication start with zero total float, and monthly reports did not highlight the approvals until the fabrication milestone slipped. Which draft lesson learned is specific enough to improve future planning, schedule development, monitoring, forecasting, and communication on similar work?

• A. For future outages, improve engineering-procurement communication in monthly updates.
• B. For future outages, note that owner approvals need closer monitoring.
• C. For future outages, extend all procurement durations to add protection.
• D. For packages needing owner approval before fabrication, estimate approval durations from recent actual cycle times, document the basis, then reforecast and report any approval activity once it becomes driving.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The best lesson learned is evidence-based and actionable. It ties the observed cause—underestimated approval duration on driving work—to specific future practices for estimating, basis documentation, forecasting, and reporting before milestone slippage appears.

A useful schedule lesson learned does more than describe a problem. It should capture the observed condition, the schedule consequence, and the specific practice change future teams can apply during planning, schedule development, updates, forecasting, and stakeholder communication.

Here, the closeout evidence shows a repeated mismatch between assumed and actual owner approval duration on work with zero float that directly drove fabrication. The strongest entry turns that into a repeatable rule: use actual cycle-time evidence for similar approvals, document the assumption in the basis of schedule, and reforecast/report the activity when it becomes driving. That makes the lesson traceable and reusable.

Broad reminders to watch work more closely or communicate better are too vague, while lengthening all procurement durations is overbroad because the evidence points to a specific approval interface.

It converts the closeout finding into a reusable scheduling rule with a documented basis, a forecasting trigger, and a reporting action.

Question 100

Topic: Conduct Scheduling Duties

At closeout for a power plant outage project, the team is archiving schedule records for future claims review and lessons learned. The project finished 18 days late after two owner-directed scope changes and several logic revisions during execution. The archive contains the approved baseline schedule, basis of schedule, final as-built milestone dates, approved change orders, and monthly PDF schedule reports, but it does not contain the native statused monthly schedule files, update narratives, or records explaining inserted fragnets and logic changes. Which analysis is best?

• A. The missing contemporaneous update files and logic-change records most weaken later schedule-impact review and contract administration.
• B. The missing records mainly reduce future planning quality because baseline and final slippage are enough to analyze schedule impact.
• C. The missing records mainly reduce lessons-learned value because approved change orders and final dates are enough for delay review.
• D. The missing records can be recreated after closeout from PDF reports and staff recollection with little effect on claims support.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The key gap is the loss of contemporaneous schedule evidence. Baseline documents and final dates show where the project started and ended, but statused update files and narratives are what support defensible delay analysis, contract administration, and credible lessons learned about how the schedule changed over time.

For schedule closeout, preserving only the original plan and the final outcome is not enough. A later schedule-impact review needs the time-phased record of progress, remaining duration, logic revisions, and forecast movement at each data date. In this scenario, the baseline, change orders, and final as-built dates show that changes occurred and that the project finished late, but they do not show when a change became driving, whether float was consumed before the delay, or how inserted fragnets altered the path to completion. Native statused schedule files and update narratives are the strongest contemporaneous evidence for that analysis, and they also improve future planning and organizational learning.

• Baseline records the approved reference.
• Statused updates show evolving forecast and path changes.
• Narratives explain why progress and logic were changed.

A reconstructed history after closeout is much weaker than preserved contemporaneous records.

Without statused updates and logic-change support, the team cannot reliably reconstruct how the driving path changed over time or attribute delay impacts defensibly.

Questions 101-119

Question 101

Topic: Conduct Scheduling Duties

At the June 30 data date, the forecast for Mechanical Completion moved from July 24 to August 1. On the current driving path, two installation activities were updated to 80% complete, but neither has an actual start and both still show the same remaining duration they had before the update; no approved change has been logged. Which evidence best validates classifying this reported delay as a progress-data issue?

• A. An owner notice imposes a new access blackout on the work area after July 8.
• B. A logic trace shows a new finish-to-start dependency added on the driving path during this update.
• C. Field logs show both activities started before June 30 and have less remaining work than entered in the update.
• D. A resource report shows the shared installation crew is overallocated for the next two weeks.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: This is an update-validation question. When percent complete is reported without actual starts and without revised remaining duration, the strongest validation for a progress-data issue is source evidence showing the field status was entered incorrectly as of the data date.

The key concept is update-cycle discipline: actual starts, actual finishes, percent complete, and remaining duration must be consistent with the data date. Here, the schedule shows advanced progress on driving activities but no actual starts and no reduction in remaining duration, which is a classic data-quality warning. If field logs confirm those activities already started before June 30 and have less work left than the update shows, the reported milestone slip is best classified as a progress-data issue.

A logic review, resource-loading result, or external restriction could each explain a real delay, but they would validate different root causes. The best validation is the evidence that directly tests whether the entered status is wrong at the data date.

Source records proving missing actual starts and overstated remaining duration confirm the slip is caused by bad status data rather than a real change to the schedule drivers.

Question 102

Topic: Conduct Scheduling Duties

Data date: May 30, 2026. The accepted update forecasts the Ready-for-Startup milestone for September 25, 2026, and activity Install main switchgear is on the driving path with 0 days total float. On June 2, the supplier issued a notice that factory rework will delay switchgear delivery by 12 calendar days. No baseline change has been approved. Before briefing leadership on June 3, which evidence best supports a defensible schedule-impact communication about the startup milestone?

• A. A time-impact analysis using a fragnet in the May 30 update
• B. A baseline-to-current-date comparison for startup
• C. The procurement cost variance with a late-material note
• D. The supplier notice showing the 12-day delivery delay

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: A defensible schedule-impact message should be based on the current accepted, statused schedule model. Inserting a fragnet for the delivery issue into the May 30 update shows whether the event consumes float or moves the startup forecast, which is the evidence leadership needs.

For schedule-impact communication, the key evidence is model-based impact, not just proof that a delay occurred. A supplier’s 12-day delay is only the event duration; it does not automatically equal a 12-day milestone slip. The strongest support is a time-impact analysis performed in the latest accepted update at the stated data date, using a fragnet for the added rework and shifted delivery, then comparing the milestone forecast before and after the insertion. That connects the issue to the current driving path, available float, and forecasted startup date. A baseline comparison or cost variance may be useful in broader reporting, but neither demonstrates the specific schedule effect of this new event. The best communication to leadership is evidence-backed and traceable to the live schedule logic.

It tests the delivery issue against the current accepted schedule logic and shows the before-and-after forecast effect on the milestone.

Question 103

Topic: Conduct Planning Duties

You are developing the baseline shutdown schedule for a turbine replacement. Activity logic is drafted, but three planning inputs are still unresolved: the contract requires mechanical completion by October 15, operations has not approved whether execution will use a 24-hour outage calendar or one 10-hour shift, and the turbine vendor has not confirmed the delivery date needed for the installation interface. Each unresolved item would materially change activity dates and float. The project manager wants the schedule issued tomorrow for baseline review. What is the next appropriate step?

• A. Escalate the unresolved inputs for decision before baseline review.
• B. Apply a finish-no-later-than constraint to preserve October 15.
• C. Proceed to baseline review and reconcile the gaps in the first update.
• D. Issue the draft schedule using a 24-hour calendar assumption.

Best answer: A

What this tests: Conduct Planning Duties

Explanation: The planner should escalate before baseline review because the unresolved contract, calendar, and interface inputs materially affect schedule logic and dates. Until those facts are resolved or formally directed, the schedule model and proposed baseline are not credible.

When unresolved planning facts materially affect durations, calendars, logic, or contractual milestones, the correct next step is escalation rather than forced progress. In this scenario, the execution calendar changes production rates, the vendor commitment changes the interface handoff, and the contract completion date must be tested against realistic logic instead of imposed artificially.

A sound planning response is to raise the issue to the project manager or other decision maker, state the missing inputs, and explain how each one affects schedule development and baseline readiness. That protects the basis of schedule and gives management a clear decision path. Using optimistic assumptions, forcing a date with a constraint, or waiting until the first update would move an unresolved planning problem into schedule control and weaken forecast credibility.

Escalation is required because unresolved contractual, calendar, and interface facts would materially change the baseline logic and dates.

Question 104

Topic: Conduct Planning Duties

A wastewater treatment project is moving from scope definition into baseline schedule development. The owner has approved civil foundations and long-lead pump procurement to proceed, but process piping outside Area A is still only concept-level. Monthly control reporting must roll up by plant area and responsible contractor, and the key contractual milestones are Design Complete, First Energization, and Substantial Completion. Which decomposition approach best supports schedule development and later control?

• A. Fully decompose all expected work now, including uncertain piping scope, into detailed activities so the baseline will not need later revision.
• B. Build the schedule around the three contractual milestones and let each discipline manage detailed work outside the integrated schedule.
• C. Create control accounts at plant area and contractor responsibility points, decompose approved near-term scope into activities with milestone logic, and keep less-defined future piping as planning packages.
• D. Organize the WBS only by contractor and keep each contract as one summary activity until all design is complete.

Best answer: C

What this tests: Conduct Planning Duties

Explanation: The best choice aligns decomposition with both control needs and current scope maturity. Approved near-term deliverables should become activities and milestones, while less-defined future work should remain in planning packages until enough detail exists for credible scheduling.

The core planning duty is to translate scope and deliverables into a structure that supports both schedule development and later control. In this case, the project needs reporting by plant area and responsible contractor, so control accounts should align to those control points. Approved near-term work such as foundations and long-lead procurement is defined enough to break into activities and measurable milestones with logic. By contrast, concept-level piping outside Area A is not yet mature enough for reliable detailed activities, durations, or relationships, so planning packages are the better placeholder.

• Use the WBS and control accounts to reflect deliverables and accountability.
• Convert approved, near-term scope into activities and milestones.
• Hold immature future scope in planning packages until detail is available.

That approach preserves traceability and forecast credibility, unlike either overly summary or overly detailed decomposition.

It matches the control structure to reporting needs, turns approved deliverables into schedulable work, and avoids false precision by holding uncertain scope in planning packages.

Question 105

Topic: Conduct Scheduling Duties

At the July 31 data date, an EPC schedule shows environmental permit approval on August 20 driving the critical path. Similar recent permits have sometimes triggered an agency request for a supplemental study; if that request occurs here, approval would slip 15 workdays. No request has been issued yet, and the contractual foundation-start milestone has only 5 workdays of total float. What is the next appropriate step?

• A. Record a risk with a clear trigger and planned contingency
• B. Escalate it as an issue and begin recovery actions
• C. Insert the possible 15-workday delay into the update now
• D. Rebaseline the permit path to a later finish

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: This is future uncertainty, not an active delay. The right next step is to document the schedule risk, define the trigger that would convert it into an issue, and prepare a contingent response because the possible impact exceeds the available float.

In schedule control, an uncertain future event remains a risk until objective evidence shows it has occurred. Here, the agency has not issued the supplemental-study request, so there is no actual permit delay to status into the July 31 update. The scheduler should capture the risk, define the trigger, and prepare the response because the possible impact is greater than the available float.

• Trigger: the agency requests the supplemental study.
• Exposure: up to 15 workdays against only 5 workdays of total float.
• Response planning: prepare actions such as permit-expedite support or logical resequencing if the trigger occurs.

Once the trigger happens, the impact can be reflected in the forecast and managed as an active issue.

Because the delay is only a possible future event, it should be managed as a schedule risk with a defined trigger and contingent response.

Question 106

Topic: Conduct Scheduling Duties

At the July 18, 2026 data date, the integrated outage schedule shows:

Contract Completion required: August 29, 2026
Current forecast: September 4, 2026
Driving-path total float: -4 workdays
Requested activity path total float: +1 workday
Basis note: Total float is a shared project resource

A subcontractor asks to delay the +1-float activity by 3 workdays for crew leveling, stating it “owns” that float. What is the next appropriate step?

• A. Approve the slip because the subcontractor owns that float.
• B. Inform stakeholders that float is shared and assess recovery before approval.
• C. Rebaseline the completion milestone before reviewing the request.
• D. Add constraints to preserve the required finish date.

Best answer: B

What this tests: Conduct Scheduling Duties

Explanation: The schedule already forecasts a miss of the contractual completion date, so negative float is now an active control and communication issue. Because the basis says float is shared, the subcontractor cannot claim exclusive use of it; the next step is to notify stakeholders and evaluate recovery before approving more float consumption.

Negative total float to a required contract milestone means the forecast finish is later than the required date, so the matter is no longer just a local activity adjustment. It has become a stakeholder, contractual, and recovery-planning issue. When the basis or contract states that total float is a shared project resource, no subcontractor may treat float on its path as privately owned for convenience. The proper next step is to communicate the current exposure using the data date and forecast, then analyze recovery options on the driving path before approving any additional delay. Rebaselining or forcing dates with constraints would hide the problem rather than manage it, and approving the slip based on float ownership would conflict with the stated schedule basis.

Treat negative float as a control signal that requires action and communication.

Negative float against a required milestone and a shared-float clause require stakeholder communication and recovery analysis before any approval.

Question 107

Topic: Conduct Scheduling Duties

Before notice to proceed, a contractor submits a Level 3 baseline for an industrial plant expansion. The project controls manager wants evidence that this baseline can later support monthly status updates, baseline-versus-forecast comparisons, approved change control, and schedule-impact discussions. Which evidence best validates that decision?

• A. An archived approved baseline package with the frozen schedule file, approval record, basis of schedule, and validation of scope traceability, logic, calendars, constraints, and resource assumptions.
• B. A milestone register signed by owner and contractor for all contract dates.
• C. A health-check report showing no open ends, limited constraints, and one continuous critical path.
• D. A resource-loaded histogram confirming planned crew demand fits the staffing plan.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: The best evidence is the archived approved baseline package because it preserves both the exact control schedule and the documented basis for its dates. That is what lets future updates, forecast comparisons, change evaluations, and impact discussions be traced back to the same approved reference.

A baseline can function as a control reference only if the exact approved model can be reproduced and defended later. The strongest evidence is a complete approved baseline package: the frozen schedule file, the approval record, the basis of schedule, and documented validation showing the model traces to scope and milestones and that logic, calendars, constraints, and major resource assumptions were checked. That combination supports consistent status updates, meaningful forecast-to-baseline variance analysis, disciplined change control, and credible schedule-impact discussions. A health check, a signed milestone list, or a resource histogram may each confirm one aspect of quality, but none alone proves what was approved or why the approved dates were accepted.

It preserves the exact approved control schedule and the supporting validation needed for later variance, change, and impact analysis.

Question 108

Topic: Conduct Scheduling Duties

During the June update for a transmission project, the reporting cut-off and data date are June 30, and the project director needs the June dashboard today. No baseline change has been approved.

Exhibit:

Activity: E-210 Cable Pull
Calendar: Mon-Fri; July 1 and July 2 are workdays
Baseline finish: July 1
Verified actual start: June 24
Verified physical progress at end of June 30: 60%
Remaining duration at end of June 30: 2 workdays
July 3 field comment: "about 80% complete"

Which action is the best schedule-control response?

• A. Shift the data date to July 3 and use the 80% field comment.
• B. Keep June 30 but enter 80% complete from the July 3 comment.
• C. Hold the activity at the July 1 baseline finish until it completes.
• D. Use verified June 30 status, forecast July 2, and note July 3 separately.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: A defensible schedule update uses actual progress and remaining duration as of the stated data date, not newer information from after the cut-off. Here, the verified June 30 status supports a July 2 forecast, which is 1 workday later than the July 1 baseline, while the July 3 comment should be treated separately.

The data date is the boundary for reliable schedule status. For a June 30 update, the scheduler should load only evidence valid at June 30, then let the schedule model calculate the forecast from that point. In this case, the valid June 30 status is an actual start of June 24, 60% verified progress, and 2 workdays remaining at end of day June 30. On the stated calendar, that supports a forecast finish of July 2, which is 1 workday late versus the July 1 baseline. The July 3 statement that the work is “about 80% complete” may be useful as a note to management, but it is post-cut-off information and should not overwrite the June 30 update unless the reporting cycle is formally changed. Using later anecdotal progress would make the update look fresher, but less controlled and less reliable.

This uses only data-date-valid evidence, preserves the baseline as the control reference, and yields a defensible July 2 forecast.

Question 109

Topic: Conduct Scheduling Duties

At the June 30 data date, a refinery turnaround scheduler plans to report that the turnover milestone moved from the approved baseline date of July 24 to a forecast date of August 2 after a late exchanger delivery and out-of-sequence piping progress. Before issuing the owner update, which evidence best validates that the reported slippage and recovery discussion are transparent and professionally defensible?

• A. Meeting minutes showing discipline leads believe the lost time can still be recovered
• B. A reissued baseline aligning the milestone date to the August 2 forecast
• C. A dashboard showing the new date without tracing the changed remaining durations
• D. An update audit linking actuals and remaining durations to field logs and delivery records, plus a recalculated driving-path review

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The strongest validation is traceable update evidence tied to the current schedule logic. When actual dates and remaining durations are supported by field and delivery records, and the model is recalculated from the data date to confirm the driving path, the reported milestone slip is credible and defensible.

Professional schedule reporting should be based on verifiable status inputs and logic-driven forecast results, not opinion, cosmetics, or pressure to soften bad news. In this case, the late delivery and out-of-sequence progress affect both update quality and path analysis, so the best validation is an audit that traces actual dates and remaining durations to source records and then confirms the current driving path after recalculation at the June 30 data date.

A defensible check should show:

• where the status came from
• how the changed status affected the forecast
• which path now drives the turnover milestone

Consensus notes may help communication, but they do not validate the forecast. Reissuing the baseline hides variance, and a dashboard without traceability only republishes unsupported dates.

Source-verified status data and a current driving-path recalculation objectively support both the forecast slip and any recovery discussion.

Question 110

Topic: Conduct Planning Duties

A utility substation project is entering schedule preparation. No logic-driven schedule model has been built, and no baseline exists. The project controls manager asks the PSP to reconcile the WBS with contract milestones, define discipline calendars, confirm site-access and outage assumptions, and document inclusions and exclusions in the basis of schedule before activity logic is developed. What type of work is primarily being requested?

• A. Schedule-model development
• B. Schedule control
• C. Planning-duty work
• D. Professional schedule communication

Best answer: C

What this tests: Conduct Planning Duties

Explanation: This situation is about creating the inputs needed for a credible schedule, not building or updating the schedule itself. Reconciling scope, milestones, calendars, and assumptions is core planning-duty work that supports the later handoff into schedule-model development.

The key distinction is where the project is in the scheduling lifecycle. Here, the team is still defining the planning basis: aligning the WBS, confirming contractual and access constraints, setting calendars, and documenting assumptions, inclusions, and exclusions in the basis of schedule. Those are planning duties because they prepare the information needed to build a valid schedule model later.

This is not schedule-model development yet, because the stem stops before sequencing activities, assigning logic, or calculating dates. It is not schedule control, because there is no approved baseline or status update to compare against. It is not professional schedule communication, because the request is to prepare planning inputs rather than report schedule facts, impacts, or recommendations to stakeholders.

A good PSP recognizes this as pre-model planning work that enables a clean handoff into detailed scheduling.

These tasks establish the planning basis, assumptions, calendars, and milestone framework needed before the logic-driven schedule model is developed.

Question 111

Topic: Conduct Planning Duties

At the start of a refinery outage project, the project manager asks for an integrated Level 3 schedule by next week. Engineering has not agreed the WBS below control-account level, procurement lead times are still assumptions from a prior outage, contractor and turnaround calendars differ, and unit-turnover interface milestones are not yet defined. No work has started, no baseline exists, and leaders want the most useful next step for a credible scheduling handoff. Which action should the scheduler prioritize first?

• A. Build the network now and refine provisional inputs during updates.
• B. Set a preliminary baseline and begin variance-control reporting.
• C. Issue an executive note and leave assumptions informal for now.
• D. Define WBS detail, milestones, calendars, and basis-of-schedule assumptions first.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: This situation is primarily asking for planning-duty work, not schedule control or reporting. The missing information consists of core planning inputs—scope decomposition, milestones, calendars, and assumptions—that must be defined before the schedule model can be built and handed off for analysis.

The key distinction is between planning inputs and schedule outputs. Here, the project has not started, there is no approved baseline, and several foundational items that drive activity definition, logic, and dates are still unresolved. That means the scheduler should first complete planning-duty work: confirm the WBS detail, agree interface milestones, align calendars, and document the basis-of-schedule assumptions.

• Planning duties create the foundation for a credible model.
• Schedule-model development should follow agreed inputs, not placeholders.
• Schedule control requires an approved baseline and status data.
• Communication is useful, but it cannot replace missing planning definition.

The closest distractor is starting the model immediately, but that would embed uncertainty instead of resolving it before development.

These unresolved items are planning inputs that must be established before a credible integrated schedule model can be developed.

Question 112

Topic: Conduct Scheduling Duties

A scheduler is updating a construction schedule.

• Data date: August 12, 2026
• Calendar for the driving path: Monday-Friday, no holidays
• Approved baseline milestone date for M-120 Substantial Completion: August 28, 2026
• Contract required date for M-120: August 28, 2026
• Current forecast for M-120: August 26, 2026
• Verified field issue: the current driving activity needs 3 additional workdays; successor logic is unchanged

What is the next appropriate scheduling step?

• A. Keep the milestone forecast at August 28 because the existing float absorbs the added duration.
• B. Treat the added duration only as a schedule risk and wait for the next status cycle.
• C. Replace the approved baseline milestone date with August 31 in this update.
• D. Recalculate M-120 to August 31, showing 1 workday negative float, before choosing recovery actions.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The milestone is currently forecast 2 workdays ahead of its August 28 required date. Adding 3 workdays on the driving path consumes that float and slips the forecast to August 31, so the next step is to recalculate the update, show negative float, and then consider recovery.

In a schedule update, once a verified issue changes remaining duration on the driving path, the scheduler should first recalculate the forecast impact. Here, M-120 is forecast for August 26 against an August 28 required date, so it has 2 workdays of float. The verified issue adds 3 workdays to the driving path, which moves the milestone 3 workdays later to August 31 on a Monday-Friday calendar.

• Start with 2 workdays of available float.
• Add 3 workdays of delay on the driving path.
• Net result: 1 workday late versus the required date.

That means the update should show 1 workday of negative float before any recovery option is selected or communicated.

The milestone was 2 workdays ahead of the required date, so a 3-workday increase on the driving path pushes it to August 31 and creates 1 workday of negative float.

Question 113

Topic: Conduct Scheduling Duties

At the July 31 data date on a refinery turnaround, the schedule model shows A120 Issue IFC Package as a finish-to-start predecessor to B340 Install Piping Spools. Field records show B340 actually started on July 24 using a partial package, while A120 is still in progress with 4 workdays remaining. The project manager asks the scheduler to enter an actual finish on A120 dated July 23 so the update will “look logical.” Which review result best validates that this is out-of-sequence progress requiring schedule-model review instead of manual date forcing?

• A. A logic trace showing B340 started from a partial turnover while A120 still had remaining duration and no approved logic revision exists.
• B. A baseline comparison showing project finish would stay unchanged if A120 were given an actual finish on July 23.
• C. A resource check showing the piping crew was fully staffed when B340 actually started.
• D. A float report showing turnaround completion still has 6 days of total float after the update.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: Out-of-sequence progress exists because the successor actually started before its finish-to-start predecessor finished. The best validation is evidence that ties the actual field sequence to the logic trace and shows the current relationship no longer represents how the work was executed.

When a successor starts before its modeled predecessor finishes, the scheduler should verify whether the update reflects true field execution or a bad status entry. The strongest validation is a logic review tied to source evidence: B340 has an actual start, A120 still has remaining duration, and there is no approved relationship change documenting the partial turnover.

That combination shows a schedule-model integrity problem. Manually inserting an earlier actual finish on A120 would hide the real sequence and damage forecast credibility. The proper response is to review how the remaining work and partial release should be modeled, not to force dates so the network appears clean.

Float, unchanged project finish, or crew availability may matter for impact analysis, but they do not prove the current logic is valid.

This evidence directly shows the executed sequence no longer matches the modeled finish-to-start logic, so the model must be reviewed instead of forcing dates.

Question 114

Topic: Conduct Scheduling Duties

As of the May 15, 2026 data date, the project uses a Monday-Friday calendar. The contractual milestone Ready for Start-up was baselined for June 2, 2026 and now forecasts June 10, 2026, a 6-workday slip. The slip is traced to delayed availability of the vendor specialist for integrated control-system testing.

Exhibit: update excerpt

The team needs a recovery recommendation for tomorrow’s executive status meeting. Which action should the scheduler prioritize?

• A. Add a finish constraint to hold the June 2 date
• B. Add the extra insulation crew to show immediate progress
• C. Rebaseline the milestone to the June 10 forecast
• D. Model compression of control-system testing and confirm shift approval

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: The best recovery action is the one that attacks the driving path to the slipped milestone. Here, integrated control-system testing and its successor have zero float, so a targeted what-if on that path gives executives a credible decision tied to resources, approvals, and the approved baseline.

Recovery should focus first on the activity chain that is currently driving the late milestone. In this update, integrated control-system testing has zero total float, directly drives Ready for Start-up, and has a plausible compression lever: a second shift, if approved in time. That makes a targeted what-if analysis on that activity the strongest recommendation because it addresses schedule impact, checks feasibility with the vendor and witness availability, and gives management a clear approval decision while still measuring against the June 2 baseline.

Accelerating pipe insulation or area paving may improve visible progress, but those activities have float and are not driving the milestone now. Rebaselining or adding a date constraint changes reporting, not the real forecast. The closest distractor is accelerating insulation, but available resources on non-driving work do not recover a driving-path delay.

It targets the driving activity, checks resource and approval feasibility, and preserves the baseline for an evidence-based recovery decision.

Question 115

Topic: Conduct Scheduling Duties

Data date: July 18, 2026. After the monthly update, the forecast for milestone Ready for Energization moved 6 workdays later. The scheduler confirmed that no logic relationships, remaining durations, or date constraints changed.

Both activities are driving predecessors to the milestone. Basis of schedule: one relay-test crew is available on a 5-day calendar; no overtime or second crew is approved.

Which diagnostic or correction best addresses the real issue?

• A. Add a finish-no-later-than constraint on the milestone.
• B. Rebaseline the milestone to the new forecast date.
• C. Remove a predecessor so both tests can run in parallel.
• D. Check crew availability, calendars, and leveling assumptions for the relay-test crew.

Best answer: D

What this tests: Conduct Scheduling Duties

Explanation: This is a resource-driven forecast problem. Both driving activities become ready on the same date, both require the same single qualified crew, and the basis of schedule does not allow extra capacity. That makes resource availability the best explanation for the milestone movement and the key recovery limitation.

When forecast dates move but logic, remaining duration, and constraints are unchanged, resource data are the next diagnostic check. Here, both driving activities are ready on July 21, both require the only relay-test crew, and the basis of schedule allows just one crew on a normal 5-day calendar. The milestone can therefore slip even with unchanged logic because finite resource capacity forces the work to be sequenced.

• Verify the shared crew assignment.
• Confirm the crew calendar and any leveling rules used in the forecast.
• Assess recovery only after checking whether added capacity is actually approved.

Changing logic, forcing dates, or resetting the baseline would hide the real cause instead of diagnosing it.

Unchanged logic, durations, and constraints point to the single limited crew as the cause of the later forecast and the main limit on recovery.

Question 116

Topic: Conduct Planning Duties

An EPC team is preparing an initial baseline schedule for a substation expansion. Before approval, the owner asks for one artifact that documents the assumed 20-week transformer lead time, the 6-day construction calendar, the exclusion of utility relocation by others, and the rationale for the energization milestone. Work has not started, so there is no update narrative, and no changes have been approved. Which action is best?

• A. Approve the schedule baseline as the formal record of those dates.
• B. Open a change log entry for the assumptions and exclusions.
• C. Use the schedule model as the formal record of date development.
• D. Prepare a basis of schedule documenting assumptions, exclusions, calendars, and rationale.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: The owner is asking for the documented reasoning behind how the initial schedule was built, not just the dates it produced. That belongs in the basis of schedule, which captures assumptions, exclusions, calendars, and milestone rationale before baseline approval.

The key distinction is artifact purpose. A basis of schedule explains why the schedule was built the way it was, including assumptions, calendars, inclusions, exclusions, constraints, and rationale for major dates. In this scenario, the project has not started and no change has been approved, so the team needs the planning-basis document that supports baseline approval.

• The schedule baseline is the approved reference set of dates used later for variance measurement.
• The schedule model is the logic-driven network that calculates and forecasts dates.
• A schedule report or update narrative communicates status and forecast after progress updates.
• A change log records requested or approved changes and their impacts.

The closest distractor is the schedule model, but calculation logic does not replace a clear documented basis of schedule.

A basis of schedule is the planning document that records the assumptions, exclusions, calendars, and date rationale supporting the initial schedule.

Question 117

Topic: Conduct Scheduling Duties

On an industrial upgrade, stakeholders need the next schedule update to show both the contractual target and a credible forecast. The data date is August 14, 2026. The turnover milestone is contractually required by October 31, 2026, but the current model applies Must Finish On October 31, 2026 to that milestone. A 7-workday concrete cure is modeled as FS+7d, owner inspection can occur only on Monday/Thursday, and no acceleration or calendar change has been approved. Which action should the scheduler prioritize?

• A. Remove Must Finish On, keep October 31 as a required date, and model curing/inspection with explicit activities and correct calendars.
• B. Keep Must Finish On, retain the lag, and use negative float to show the contractual pressure.
• C. Add soft start constraints to downstream work so the network stays aligned with October 31.
• D. Shift critical work to a 7-day calendar now and test recovery after the next update.

Best answer: A

What this tests: Conduct Scheduling Duties

Explanation: A required milestone date should remain a comparison point, not a hard constraint that forces the forecast. Here, the best action is to preserve the contract date for reporting while letting logic, explicit activities, and the correct calendars determine the true finish.

Hard constraints, soft constraints, logic, lags, and calendars serve different purposes in a schedule model. The October 31 turnover date is a required contractual milestone, so it should remain visible for control and reporting, but a Must Finish On hard constraint can force the date and reduce transparency of the true forecast and driving path. In this case, the waiting period and inspection timing are better modeled through explicit activities and the correct calendars than through a forced milestone date or a generic lag. Soft constraints can be valid for real external limits, such as access or permit windows, but they should not be added just to make the network appear to meet a required date.

• Keep the contractual date as a required/reporting reference.
• Let logic determine the forecast finish.
• Use explicit activities and proper calendars for curing and inspection.

Keeping the milestone forced to the contract date may still show negative float, but it gives a weaker basis for diagnosis and decision-making.

This keeps the contractual date visible as a control reference while letting logic and calendars produce a credible forecast.

Question 118

Topic: Conduct Scheduling Duties

At the August 14, 2026 data date, the scheduler is updating activity A1400 - Cable pull and terminations.

Exhibit:

Which response should the scheduler prioritize in the update and stakeholder status report?

• A. Replace the baseline finish with the August 26 forecast for reporting.
• B. Reduce remaining duration to match 88% complete before issuing the update.
• C. Keep the baseline, report the August 26 forecast as late, and request recovery review.
• D. Report the activity as essentially on plan because it is 88% complete.

Best answer: C

What this tests: Conduct Scheduling Duties

Explanation: Percent complete is a progress indicator, not proof of schedule performance. Here, the supported forecast finish is later than the baseline finish on a driving path, so the activity should be reported as behind schedule against the approved baseline.

In schedule control, an activity can show a high physical percent complete and still be behind schedule if the remaining work and logic drive a late forecast. The key comparison is not 88% versus 100%; it is approved baseline finish versus current forecast finish, supported by credible remaining-duration evidence.

• The baseline finish is August 12, 2026.
• The forecast finish is August 26, 2026.
• The unfinished scope is constrained by a fixed outage window and still requires 4 workdays of closeout.
• The activity drives the energization milestone with 0 total float.

That means the activity is late in schedule terms, even though most of the quantity is complete. The right control response is to preserve the baseline, report the variance clearly, and trigger recovery review rather than forcing the remaining duration or hiding the slippage.

The supported forecast finish is later than the approved baseline on a driving path, so the activity is behind schedule despite 88% complete.

Question 119

Topic: Conduct Planning Duties

During planning for a utility plant expansion, the proposed schedule update process will collect actual starts, actual finishes, and remaining duration from discipline leads each week. Before baseline approval, the owner asks for weekly reports showing installed quantities by system and traceable physical percent complete by work package, but no field forms, coding, or source data currently support that request. What is the next appropriate step?

• A. Defer the new reporting request until after the first update cycle.
• B. Add summary activities by system and leave the planned field update process unchanged.
• C. Baseline the schedule now and infer physical progress from remaining duration until better data exist.
• D. Reconcile the report request with feasible measurement rules and required data collection before baseline approval.

Best answer: D

What this tests: Conduct Planning Duties

Explanation: The best planning response is to align reporting expectations with the update process before baseline approval. If stakeholders want quantity-based or traceable physical progress reporting, the team must define how those data will be measured, coded, sourced, and reported rather than improvise later.

This is a planning-readiness issue, not just a reporting preference. A report that requires installed quantities and traceable physical percent complete cannot be produced credibly if the planned update process only captures actual dates and remaining duration. The next step is to reconcile the stakeholder request with the status collection process: confirm the needed report, define objective measurement rules, identify source data, assign collection responsibility, set coding needed for roll-up, and document the approach before baseline approval. If the organization cannot support that level of detail, the report requirement should be adjusted before baselining. Adding summary activities or estimating progress manually may make the schedule look more reportable, but they do not create reliable source data. The key point is that reporting commitments must be supported by a planned, objective data collection method.

The reporting commitment should be matched to objective, supportable status inputs before the schedule is baselined.

Continue with full practice

Use the AACE PSP Practice Test page for the full PM Mastery route, mixed-topic practice, timed mock exams, explanations, and web/mobile app access.

Focused topic pages

• AACE PSP: Conduct Planning Duties
• AACE PSP: Conduct Scheduling Duties
• AACE PSP: Communication Competency

Free review resource

Read the AACE PSP guide on PMExams.com for concept review, then return here for PM Mastery practice.