Short answer: The construction progress schedule specification (Section 01 32 16 in most project manuals) tells the general contractor when the schedule is due, what software and file format it must use, how short the activities must be, what the owner will not accept in the logic, who owns the float, how the schedule carries cost, what each monthly update must include, and how a time extension is requested. On the six public specifications reviewed here, a preliminary schedule is due 7 to 20 days after notice to proceed, the baseline 30 to 45 days after, activities are capped at 15 or 20 working days, and payment waits on an accepted schedule.
The section number moves around: 01 32 16, 01 32 00, 01 32 13 or, on federal work, UFGS 01 32 01.00 10, but the title is almost always some form of construction progress schedule. The clauses are the same family, and the reviewer reads the submittal against them in order. The quotations below come from the US Army Corps of Engineers UFGS 01 32 01.00 10, West Virginia University 013200, Yale University 01 32 00, Bakersfield City School District 01 32 13, Iowa DOT Special Provision SP-230037 and the San Jacinto River Authority 01 32 16.
1. Submittal timing
Nearly every spec asks for a short-range preliminary schedule, then the full baseline.
- Preliminary. WVU: within 7 days after notice to proceed (1.4.C). Bakersfield: within 10 days of NTP, before the first progress payment request. UFGS: 15 calendar days (3.4.1). Yale: 20 days (1.5.B.1).
- Baseline. WVU and SJRA: 30 days (1.4.D; 1.6.A.3). UFGS: 42 calendar days (3.4.2). Iowa DOT: accepted, not just submitted, within 45 calendar days, and no contract work starts before acceptance (230037.06.A, 230037.01.B).
The GC needs subcontractor durations and the procurement list in hand before NTP, because 30 days is not long to build and check a full network. The reviewer checks the transmittal date first. What the review itself covers is in what the owner's reviewer will check.
2. Software and file format
The named software is usually Primavera P6. Yale requires "Primavera P6 Professional Project Management Software version 8.3 or newer" and a uniquely named XER for every submittal (1.5.A). Iowa DOT requires P6 8.2 or later plus a PDF plot by WBS, a plot of the longest path, the XER and a narrative (230037.06.F). UFGS requires the XER "in a version of P6 importable by the Government system" and the SDEF coding structure from ER 1-1-11 (2.1.2.1, 3.3.7). Not every owner names P6: WVU asks for XML (1.4.C) and the SJRA spec names Microsoft Project 2007 (1.7.A.1). A schedule in the wrong tool is rejected without a technical review.
3. Activity duration caps
Every spec in the set caps activity length so progress can be measured each month: 15 days at Yale (1.6.B.1) and Bakersfield; 20 working days at WVU (2.2.F), Iowa DOT (230037.03.I.4) and SJRA (1.11.B.2.c); 20 workdays or 30 calendar days for non-procurement activities under UFGS (3.3.2). Procurement and owner review periods are excepted; construction activities over the cap need written approval. The reviewer sorts the activity table by original duration and reads down from the top.
4. Constraints, lags and open ends
This clause group rejects more otherwise complete schedules than any other:
- UFGS: "Mandatory constraints that ignore or affect network logic are prohibited." "Leads (negative lags) are prohibited." Start-to-finish ties are prohibited, and lags must be "reasonable as determined by the Government and not used in place of realistic original durations" (3.3.8, 3.3.16).
- Yale: "Mandatory Start and Mandatory Finish constraints shall not be allowed." Other date constraints must be justified, and every start-to-start tie must carry a finish-to-finish tie (1.5.B.1.a.3, 1.5.B.1.a.5).
- Iowa DOT: negative lag, positive lag, open-ended activities and non-contractual constraints are prohibited, and every remaining lag and constraint must be listed and justified in the narrative (230037.03.F, 230037.03.O). SJRA goes further: no lags at all, "specific activities with specific durations in-lieu-of leads and lags" (1.7.B.1.c.1).
The reviewer checks the schedule log for open ends, the constraint column, and the relationship report for lags. "Justify every constraint" means a table in the narrative, not a sentence saying they are reasonable.
5. Float ownership
Float belongs to the project. UFGS: float "belongs to the Project and is available for Contractor and Government use" (3.10). WVU: float "is not for exclusive use or benefit of either the Owner or the Contractor" (1.3.F.1). Bakersfield: "Neither the District nor Contractor owns Project Float." Iowa DOT adds that float suppression techniques are grounds for rejection (230037.03.R). A baseline that hides float with constraints or padded durations is a spec violation and a weak record for any later claim. UFGS 3.8.6 states the test: "No time extension will be granted unless the delay consumes all available Project Float."
6. Calendars and weather days
Specs differ more here than anywhere else. UFGS: "The preferred methodology is the use of a weather calendar" (3.3.9). Iowa DOT: weather contingency days shown as non-workdays, justified in the baseline narrative, and the calendar updated monthly with actual days lost (230037.03.D, 230037.03.M). SJRA: no multiple calendars, and durations must already include normal weather per a rain-day baseline in the general conditions (1.7.B.1.e, 1.11.D). Match the calendar method to the spec rather than a house standard; the reviewer opens the calendar in P6 and compares it to the clause.
7. Cost loading
Most public owners require the schedule to carry the contract value, and the activities must add up to the contract sum. Yale: "The sum of costs for all activities must equal the total Contract Sum unless otherwise approved by Owner" (1.3.B). WVU: cost-loaded activities roll up to the schedule of values line items (2.2.T.2). Iowa DOT: one resource per bid item, within plus or minus 1 percent of the contract sum (230037.04). UFGS: loading must be "reasonable and without front-end loading" (3.2.1). WVU also requires closeout activities to total 5 percent of the Contract Sum (2.2.T.3). The reviewer sums the loaded values against the contract amount and reads the cash flow curve for front-loading.
8. Monthly updates
Monthly is the floor, and the update is tied to the pay application. UFGS: "monthly at a minimum," with the submittal not later than four workdays after the update meeting (3.4.3, 3.6.2). Iowa DOT: data date equal to the pay request date, submitted within 5 working days, with a recovery statement when there is slippage (230037.06.B). Bakersfield: an update with each progress payment application. WVU: percent complete or remaining duration on every activity (3.1.B). Each update carries actual dates, progress on in-progress work, every logic or duration change explained, the current longest path, and a narrative. The reviewer checks that the data date matches the pay period, that no actual dates moved since last month, and that changes were disclosed. The full list is in monthly schedule updates that keep pay applications moving.
9. The narrative
Every spec in the set except WVU requires a narrative with each submittal. UFGS: "Identify and discuss all schedule changes by activity ID and activity name" (3.5.2). Iowa DOT lists sequencing, production rates, the longest path, changes, delays, cost comparisons and a certification signed by the project manager and the scheduler (230037.06.F). A narrative that reads the same every month tells the reviewer nobody read the schedule before sending it. The monthly narrative report is where the GC gets credit for managing the job.
10. Time extensions and time impact analysis
The specs set a notice period, a method, and a deadline. UFGS: justification of delay "within 10 days of a delay occurring" and a time impact analysis based on AACE 52R-06 (3.8, 3.8.3). Iowa DOT: notice within 5 days and a written TIA within 15 calendar days of the engineer's request (230037.06.D, 230037.06.E). Yale: each TIA runs on the most recently accepted update, and no delay goes into the schedule without an executed change order (1.5.C.1, 1.5.C.2). Bakersfield: 14 calendar days for a time impact evaluation on changed work, and missing it "will result in Contractor waiving its right to a time extension." The GC calendars those periods on day one; the clause does not care whether the delay was real if the notice was late. The method is laid out under time impact analysis and delay claim support.
11. Late or rejected schedule
UFGS: the contracting officer "may withhold 10 percent of pay request amount from each payment period," and a contractor without an approved schedule "will be deemed not to have provided an estimate upon which a progress payment can be made" (3.2.3, 3.4). WVU: invoices are withheld until the schedule is submitted, then held until the university approves it (3.1.C.2.a). SJRA: progress payments are not processed unless an acceptable updated schedule accompanies the pay request (1.12.D.1). Yale: a missing schedule lets the owner hire a third-party scheduler at the contractor's cost (1.5.B.1.b). Read together, the first pay application is gated by the baseline and every later one by the update.
Reading the spec before the quote
The practical sequence: list each clause above with the owner's paragraph number against it, confirm the software and format, collect subcontractor durations and the procurement list before NTP, and build the baseline to that clause table so the reviewer finds every item where the spec says it should be. The gain is a baseline accepted on the first review, a first pay application released on time, and a record that already meets the owner's rules when a time extension is needed.
Send the scheduling specification and the drawings, and CPM Pros will send back a written quote with a firm price and delivery date, typically within 3 business days.