MEP Procurement Float: Check the Network Before Pricing a Delay

An equipment delivery slips by seven working days. Does the MEP completion milestone also slip by seven? The answer depends on the activities that must finish before installation can start. If the work area would not have been ready anyway, some delivery movement may consume schedule float before it affects completion.
This article builds an original, deliberately small network for a packaged HVAC unit. It demonstrates schedule arithmetic and an internal cost sensitivity. It does not establish delay responsibility, ownership of float, contractual entitlement or a payment claim. All durations, costs and the calendar exception are hypothetical.
1. Define the milestone and both incoming paths
The milestone is “unit installation and planned checks complete.” It is a package milestone, not the whole building’s completion. Assume all necessary work is represented below, sufficient separate resources are available, and every relationship is finish-to-start with no lag. A successor begins on the next working day after its predecessor finishes.
Procurement path: A, complete technical release, 4 working days; B, manufacture after release, 8; C, transport and receive, 5. Procurement total = 17 working days.
Readiness path: D, complete the work area and installation access, 22 working days, starting alongside A.
Converging work: E, install the unit, 3 working days, only after both C and D finish; F, complete the defined checks, 2 working days after E.
The forward calculation is max(4 + 8 + 5, 22) + 3 + 2 = 27 working days. The readiness path controls this baseline. Adding both incoming paths, 17 + 22 + 3 + 2, would incorrectly treat parallel work as sequential.
A real readiness activity should be broken into the actual tasks and interfaces where needed. It must not be a convenient placeholder that hides a late support, access release or another predecessor. The short example is only useful because its assumptions are stated.
2. Calculate float to the chosen finish
Use elapsed working-time boundaries with project start at 0. Procurement finishes at 17; readiness at 22; installation at 25; checks at 27. A backward pass from 27 places the latest procurement finish at 22, giving 22 − 17 = 5 working days of total float on the procurement path.
The PMI paper on basic CPM calculations explains forward and backward passes and distinguishes total float from free float. In this unconstrained example, total float measures how far an activity can move without moving the package finish; free float measures how far it can move without moving its immediate successor’s early start.
A, B and C each show 5 days of total float. They share the same five-day allowance; adding their displayed values does not create 15 days. A and B each have zero free float because their successors are planned to follow immediately. C has 5 days of free float because installation is waiting for D.
For a numerical backward check, C’s latest finish is 22 and latest start is 17. B’s latest finish is therefore 17 and latest start 9. A’s latest finish is 9 and latest start 5. Their early starts are 12, 4 and 0 respectively, so each latest-start minus early-start difference is 5.
3. Put the calculation on an explicit working calendar
Let work start on Monday, 2 November 2026. For this example only, all activities use Monday–Friday working and one invented nonworking date, Monday, 16 November. That date is a project-calendar assumption, not a statement about a national holiday. No other calendar exceptions apply.
A finishes Thursday, 5 November, working day 4.
B finishes Wednesday, 18 November, working day 12.
C finishes Wednesday, 25 November, working day 17.
D finishes Wednesday, 2 December, working day 22.
E finishes Monday, 7 December, working day 25; F finishes Wednesday, 9 December, working day 27.
The latest C finish is 2 December. The gap from 25 November is seven calendar days but five working days. Those numbers describe the same interval on this calendar; substituting one for the other changes the forecast.
For an Excel check, put the working start date in B2 and the exception date in H2. Because the start date is already a working day and counts as day 1, the finish formula is WORKDAY.INTL(B2,27−1,1,H2). Microsoft’s WORKDAY.INTL documentation defines the weekend and holiday exclusions. Format the result as a date. Adding 27 instead of 26 would incorrectly exclude the starting workday from this duration count.
Without the invented exception, the 27th working day is 8 December. Omitting one calendar entry changes the milestone by a day without any change to activity durations. Actual factory, transport and site calendars may differ; this common-calendar example must then be replaced by a date-based network using each activity’s applicable calendar.
4. Spend shared float only once
Now extend A by 3 working days and B by 4, with no other changes or recovery. Procurement becomes 7 + 12 + 5 = 24 working days. The revised milestone is max(24,22) + 3 + 2 = 29 working days. The finish moves from 9 December to Friday, 11 December: two working days later.
The combined seven-day extension consumes five days of shared float and then moves the finish by two days. Reviewing A and B independently against the original five-day float would miss that combined result. At the revised position, procurement controls the package finish and the unchanged readiness path has two working days of float.

Original simplified network. Durations are hypothetical working days on one common calendar. The illustrated milestone covers this package only; available independent resources and finish-to-start links without lag are assumed.
For one internal cost sensitivity, assume only 750 CU of incremental package support is needed for each additional working day, with no weekend charges, remobilization or other effects. The modeled extension cost is 2 × 750 = 1,500 CU. Charging 7 × 750 = 5,250 CU would price all procurement movement as completion extension under a model that supports only two additional days.
That limited calculation does not make delay within float costless. Storage, changed transport, reserved crews or rescheduled visits may have distinct costs even when the finish is unchanged. Identify each actual consequence separately, with evidence, and avoid counting the same resource twice.
5. Validate the network before using the number
The GAO Schedule Assessment Guide warns that missing logic, inappropriate calendars, constraints and stale activity status can distort float. It also explains why multiple calendars complicate identifying the driving path from a zero-float flag alone. Review the actual sequence driving the milestone, not just the software’s color coding.
Use the current status date, actual finishes and realistic remaining durations; preserve the comparison schedule.
Check that delivery, receiving, access and downstream checks are connected to the correct milestone.
Confirm supplier lead-time start events, calendar exceptions and any resource conflicts.
Test all related changes together and record float consumed and remaining on the same path.
Keep an explicit management buffer separate from calculated float, and route recovery decisions through the project’s approval process.
Use the resulting milestone constraint to set an HVAC RFI response-needed date, keeping supplier lead-time start conditions and the calendar basis visible.
For the technical questions feeding procurement, Nexora’s paid HVAC RFI Pack provides a register, printable form, tracker, dashboard and question library to keep decisions and follow-up visible. Its described deadline calculations use calendar days. Keep the working-day network and float calculation in the project schedule, and carry the resulting response-needed dates into the RFI review.



Comments