Compressed Schedule for a Multi-Building Campus Backbone
You are the RCDD project lead for a 1,450-cable Cat 6A and OM4 backbone upgrade across four campus buildings. The client's funding expires in 90 calendar days, and the contract carries $2,500/day liquidated damages. The general contractor has given you a 40-day window for horizontal cabling in Building A, but the electrical contractor will not finish pathway and junction-box work there until day 22. Your crew of six installers averages 55 cable pulls per day when pathways are ready. The client just approved a change adding 180 cables in Building C, with no additional time. Your PM asks whether to accept the schedule as-is or request a time extension.
1. Calculate whether the remaining work fits the 90-day window and identify the critical constraint. What do you recommend to the PM?
Read the worked answer
Workload math. 1,450 + 180 change = 1,630 cables. At 55 pulls/day with six installers, that is 1,630 ÷ 55 ≈ 29.6 crew-days of installation - well inside 90 days on its own.
The real constraint is sequencing, not labor. Building A cannot start until day 22, leaving only 18 days of its 40-day window. If Building A holds roughly a quarter of the original 1,450 (≈360 cables), that is 360 ÷ 55 ≈ 6.5 crew-days - feasible, but only if pathways are truly released on day 22. The change adds 180 cables in Building C, which may share the same crew. Total crew-days rise to ~30, still under the 90-day envelope, but float is thin once testing, labeling, and certification are added.
Recommendation. Accept the change but formally document the day-22 dependency as a client/GC risk, request a written pathway-release commitment, and reserve testing float. Do not request a time extension yet - the data does not support it. Instead, negotiate a schedule contingency: if Building A pathways slip past day 25, the extension clause triggers. This protects the $2,500/day exposure without appearing to pad the schedule.
2. The electrical contractor slips Building A pathway release to day 35. What is the contractual and schedule impact, and how do you document it?
Read the worked answer
Impact. Building A now has 5 days (day 35 to 40) instead of 18. At 55 pulls/day, only ~275 cables can be installed - if Building A holds 360, roughly 85 cables cannot be completed in the GC window. That pushes horizontal cabling into the testing/closeout phase and threatens the 90-day funding deadline.
Contractual position. The delay is caused by another trade, not your crew. Under typical ICT subcontract language, this is a compensable or at least non-excusable-to-you delay. You should issue a written notice of delay within the contract's notice period (often 48–72 hours), citing the day-35 release, the original day-22 commitment, and the calculated cable shortfall.
Documentation. Record daily site reports, the GC's written pathway commitment, photos of incomplete pathways, and a revised schedule showing the 85-cable slip. Request a time extension of at least 5 days and reserve the right to claim extended general conditions. Do not accelerate with overtime until the client confirms who bears the cost - unpaid acceleration erodes margin and sets a precedent.