Reading a Schedule Spec: Section 01 32 16

Section 01 32 16, Construction Progress Schedule, is the CSI MasterFormat Division 01 section where the owner tells the contractor what the schedule has to be: what software, how detailed, when it's due, how it's updated, and how time extensions get requested. It's often a few pages that nobody reads until the first baseline gets rejected. This post walks through what's usually in one, what each part means in practice, and the clauses worth reading twice. It ends with a checklist for bid time and kickoff.

Every spec is different. Some are a single page; some public agency specs run longer than the general conditions. Treat this as a map of the usual territory, then read yours.

Where it fits

The schedule spec sits in Division 01 under 01 32 00, Construction Progress Documentation, alongside related sections for things like photographic documentation. It works together with the general conditions (for example, AIA A201 or an owner's own), the supplementary conditions, and other Division 01 sections on submittals, payment procedures, and closeout. When they conflict, the contract's order-of-precedence clause decides. Check the general conditions for time extension and claim procedures too, since the schedule spec usually describes the schedule mechanics and the general conditions set the notice rules.

What's usually in it

Most schedule specs follow the CSI three-part format, though many put almost everything in Part 1.

Definitions

Terms like activity, critical path, float, data date, baseline, and update. Read these. A spec that defines the critical path as "the longest path" behaves differently in review from one that defines it as "activities with zero or negative total float," especially once a schedule has multiple calendars or constraints.

Software and file format

Often names a specific product, such as Primavera P6, or "P6 or equal," and requires native files with every submission (for P6, usually an .xer export). If the spec names a tool you don't use, find out before bid whether a compatible native file is acceptable.

Scheduler qualifications

Some specs require a dedicated scheduler with a minimum number of years of experience or a professional certification, and require the resume to be submitted for approval. If you plan to have the PM do the schedule, this clause matters.

Submittal sequence and timing

Typically:

1. A preliminary or initial schedule covering the first few months of work, due shortly after notice to proceed.
2. A detailed baseline schedule covering the whole project, due within a stated number of days after NTP.
3. Monthly updates, often due with or before the pay application.
4. Revisions, recovery schedules, and time impact analyses as triggered.

Note the owner's review period too. If the owner has 21 days to review a baseline, and the baseline is due 30 days after NTP, you may be working on an unaccepted schedule for close to two months.

Content and detail requirements

This is the longest part, and the part reviewers enforce. Common requirements:

• Maximum activity durations for construction work, with longer durations allowed for procurement and fabrication.
• A minimum or maximum number of activities, or a level-of-detail statement.
• Activities for submittals, owner reviews, procurement, fabrication, delivery, inspections, testing, commissioning, and closeout, not just field work.
• Activity codes for area, phase, responsible party, and CSI division or trade.
• Every activity has a predecessor and successor, except the start and finish.
• Limits on lags, leads, and negative lags.
• Limits or prohibitions on constraints, especially on mandatory constraints.
• Contract milestones shown and tied to logic.
• Calendars defined, including holidays and anticipated weather days.

Many of these line up with the checks in The DCMA 14-Point Assessment, Explained for Construction. Run those checks on your own schedule before the owner does.

Cost and resource loading

Some specs require the schedule to be cost loaded so it can serve as the schedule of values or support payment. Some require manpower loading for major trades. Both add real work at baseline and every update.

Updates

How often (usually monthly), what data date to use, what the update must include (actual dates, remaining durations, percent complete), and what the narrative must cover. A typical narrative requirement asks for the critical path, changes to logic and durations, delays and their causes, and corrective actions. Some specs prohibit logic changes in an update without separate approval. Others require a log of every change.

Float

Often a sentence or two stating that float is shared, not for the exclusive use of either party, and that time extensions will be granted only for delays to contract completion. Sometimes a prohibition on sequestering float through preferential logic or extended durations. Read it closely; it governs every future time request. See Who Owns the Float?.

Recovery schedules

A trigger, usually a forecast completion that slips past the contract date by some number of days, that obliges the contractor to submit a recovery schedule showing how it will get back on track, often at its own cost.

Time extension requests

How to ask for time: usually a time impact analysis with a fragnet, inserted into the current update, submitted within a stated period after the event. The general conditions set notice deadlines; the schedule spec sets the format. See Time Impact Analysis, Step by Step.

Payment ties

Some specs let the owner withhold part or all of a progress payment if the baseline isn't accepted or the update isn't submitted. This is the clause that gets everyone's attention, usually in month two.

Clauses worth reading twice

Reading it at bid time

The schedule spec has a cost. A cost-loaded, resource-loaded schedule with a dedicated qualified scheduler, monthly narratives, and TIAs for every change is a different line item from a summary Gantt maintained by the PM. Price it. If the spec names software you don't own, price that too, or ask a question during bidding.

Reading it at kickoff

• Put every schedule deadline from the spec on a calendar: preliminary, baseline, update due dates, review periods.
• Build the activity code structure the spec requires before you build activities. Retrofitting codes is miserable.
• Set the project calendars and weather days the spec requires.
• Agree with the owner's reviewer on any ambiguity now: the critical path definition, which constraints are acceptable, how updates are submitted.
• Share the spec requirements with the people who'll feed the schedule: PM, superintendent, major subs.

If you're on the owner's side, the companion to this post is What Owners Should Check in a Baseline Schedule Submittal.

Checklist

• Find the critical path definition, the float clause, and the time extension procedure.
• Note software, native file format, and scheduler qualification requirements.
• List every submittal deadline and owner review period.
• Note detail rules: max durations, constraints, lags, required activity types, codes.
• Check for cost loading, resource loading, and payment withholding.
• Check how weather days are defined and carried.
• Price it at bid time; set it up at kickoff.