Fictional practice case. Enable JavaScript for interactive classification and scoring, or work through the evidence and model explanation below.
The scenario
- project
- Riverbend Community Hospital (fictional)
- reporting Period
- Original baseline, Revision 1
- data Date
- Notice to Proceed — 6 January 2026
- contractual Finish
- 30 September 2027
- protocol
- For this training case, missing contractual scope or network logic that can mask the completion forecast requires correction before the baseline may become the controlled execution plan.
Evidence register
contract-milestones / Contract milestones
Prior: Contract milestone schedule identifies 12 required dates.
Current: All 12 milestones use matching IDs, descriptions, and dates.
Support: The signed compliance matrix maps each milestone to the native activity ID.
turnover-scope / Commissioning and turnover
Prior: Specification requires testing, training, documentation, and phased turnover.
Current: One zero-duration “Commissioning complete” milestone represents the entire scope.
Support: No detailed turnover sequence or approved deferred-planning package accompanies the file.
open-ends / Network continuity
Prior: Only authorized project start and finish boundaries may remain open.
Current: Forty-six detailed activities have no predecessor or no successor.
Support: The schedule basis does not list approved exceptions or external interfaces for these activities.
calendars / Calendar governance
Prior: The basis identifies four purpose-specific calendars.
Current: The native file contains the same four calendars and holiday exceptions.
Support: Workweek, holiday, weather, and shift assumptions reconcile to the approved calendar register.
long-durations / Long-duration work
Prior: Durations above 30 working days require a measurable basis.
Current: Six activities exceed 30 working days.
Support: Each activity has a quantity, crew, production-rate calculation, and monthly measurement rule.
mandatory-finish / Completion constraint
Prior: Contract completion is represented as the required finish milestone.
Current: The milestone also carries a Mandatory Finish constraint.
Support: Neither the schedule basis nor the compliance matrix authorizes the logic override.
path-narrative / Longest-path narrative
Prior: The narrative identifies structural steel as the controlling sequence.
Current: The calculated longest path begins with the constrained design-release chain.
Support: No sensitivity report or explanation reconciles the narrative with the native calculation.
owner-equipment / Owner-furnished MRI equipment
Prior: The responsibility matrix requires release, manufacture, delivery, shielding inspection, and installation interfaces.
Current: The schedule begins at MRI installation and omits the upstream owner and vendor activities.
Support: No separate interface schedule or approved milestone carries the omitted work.
Model review
The contractual milestone set reconciles.
Every required milestone has a traceable native activity with the stated contractual date.
This is a supported completeness control. The reviewer should retain the mapping as part of the acceptance record and continue testing the network behind the dates.
Turnover scope is collapsed into a single milestone.
Testing, training, documentation, and phased turnover cannot be evaluated as activities or logic.
A zero-duration finish point does not model the required work. Missing completion scope can make the forecast and longest path incomplete.
Unexplained open ends break network continuity.
Forty-six detailed activities cannot transmit delay through a complete predecessor-successor chain.
Open ends outside authorized boundaries weaken CPM behavior and can suppress the effect of delayed work. Each needs logic or a documented, approved exception.
The calendar model matches the documented basis.
The four native calendars reconcile to their workweeks, exceptions, and stated purposes.
Different calendars are not inherently deficient. Here they are visible, purpose-specific, and supported by the controlled calendar register.
Long durations have measurable production support.
The six activities above the review threshold include quantities, crews, rates, and progress rules.
A threshold is a screening device, not an automatic rejection rule. The provided basis makes these durations reviewable and measurable.
An unauthorized Mandatory Finish overrides the forecast.
The completion milestone is pinned even though the controlling network should calculate its forecast date.
A mandatory constraint can override logic and distort float. The reviewer needs explicit authority and a documented purpose, or the constraint should be removed.
The narrative does not describe the calculated longest path.
The stated structural-steel path differs from the native path driven by constrained design release.
A baseline narrative must explain the schedule that was actually calculated. The conflict also signals that the constraint may be masking the intended execution sequence.
A material owner-vendor interface is omitted.
MRI installation appears without the release, manufacture, delivery, and inspection work that enables it.
A comprehensive baseline must represent material interfaces regardless of which party performs the work. Omitting the chain hides responsibility and timing risk.
Model disposition and closeout
Revise and resubmit
The resubmission should add the required commissioning and turnover sequence, connect or document every open end, represent the MRI interface chain, remove or authorize the Mandatory Finish constraint, and reconcile the narrative with the recalculated longest path. The acceptance record should preserve the native file, schedule basis, compliance matrix, review comments, responses, and a comparison proving that unrelated model changes were not introduced.