Caltrans, DSA, and DGS each administer construction differently, and treating their schedule requirements as interchangeable is one of the fastest ways to get a CPM submission rejected on a California public-agency project. A schedule built to satisfy one agency's conventions can fail another's review outright, even when the underlying project controls discipline is identical.
This guide covers what each agency actually requires, where their expectations overlap, and the schedule-quality failures that most often trigger rejection comments on California public works and vertical construction projects.
Caltrans: Standard Specifications Section 8-1.02
Caltrans progress schedule requirements are set out primarily in Standard Specifications Section 8-1.02 (Progress Schedule), supplemented by project-specific special provisions that can tighten or expand the base requirement. Depending on contract value and project type, Caltrans may require:
- A CPM baseline schedule submitted within a specified number of days after contract approval, built in a Caltrans-accepted software format (Primavera P6 is standard on most contracts of meaningful size).
- Specific activity coding conventions tied to Caltrans' cost/pay item structure, so schedule activities can be cross-referenced to progress payments.
- Monthly (or, on some contracts, more frequent) updates with a written narrative addressing critical path changes, float consumption, and the cause of any completion-date slippage.
- A defined process for schedule revisions, often requiring a formal request and Caltrans acceptance before a revised baseline supersedes the prior one.
Caltrans resident engineers and construction staff review schedules primarily against the contract's own specification language rather than a universal template — the special provisions on a specific contract can override or add to the standard specification, so the first step on any Caltrans project is reading the project-specific schedule specification in full before building the baseline.
DSA: inspection-driven, not schedule-approval-driven
The Division of the State Architect (DSA) has a different role than Caltrans. DSA is primarily a plan-review and inspection authority for K-12 schools and community college construction under the Field Act, focused on structural and life-safety code compliance during construction, not on approving or rejecting CPM schedules as a contractual deliverable.
That doesn't mean DSA is irrelevant to the schedule. DSA inspection milestones, close-out inspection sequencing, and the project inspector's (IOR) sign-off points all have to be reflected accurately in the CPM logic, because:
- DSA closeout certification is frequently a prerequisite for beneficial occupancy or substantial completion, so it belongs on the critical path, not treated as an afterthought activity.
- Structural inspection hold points (rebar placement, structural steel connections, etc.) can create real logic constraints on sequencing that a schedule built without DSA experience will miss.
- Change orders driven by DSA-required corrections need to be reflected in schedule updates with the same rigor as any other change, since DSA-driven delays are a recurring source of EOT claims on school construction.
DGS: General Conditions-driven, contract by contract
The Department of General Services (DGS) administers a wide range of state facility construction, and its CPM scheduling requirements typically live in the General Conditions and project-specific specifications rather than a single statewide standard the way Caltrans' Section 8-1.02 functions. Common DGS-administered requirements include:
- Baseline schedule submittal within a fixed window after notice to proceed (commonly 15-30 calendar days, but always confirm against the specific contract).
- Monthly update submissions tied to the payment application cycle, often requiring the schedule update to accompany or precede the pay app for approval.
- Schedule of values reconciliation, so cost and resource loading in the CPM schedule ties out to the payment schedule DGS is tracking separately.
Because DGS requirements vary by contract, the discipline that matters most is treating every DGS project's specification as its own document, rather than assuming last year's DGS project used the same rules.
Where the three agencies' expectations overlap
Despite their differences, Caltrans, DSA-inspected, and DGS-administered projects share a common thread in what actually gets a schedule accepted on first review:
- Traceable logic — every activity connected with real, defensible relationships, not artificial constraints used to force a finish date.
- Calendars that match the contract — working days, holidays, and any weather allowance consistent with the specification, not a generic 5-day calendar applied without adjustment.
- A narrative that explains the critical path — reviewers on all three agency types reject updates that show a changed finish date with no explanation of why.
- Coding structure that matches the specification — whether it's Caltrans pay-item coding, a DGS-specified WBS, or simply consistent activity ID conventions, agency reviewers check this early and reject submissions that don't match.
Why first-submission rejections happen
In HADVEN's experience preparing and reviewing schedules for California public agencies, the same handful of issues account for most rejection comments regardless of which agency is reviewing:
- Missing or open-ended logic that leaves activities untestable against the finish date.
- Activity coding that doesn't match the specification's required structure, making cost/schedule cross-referencing impossible for the reviewer.
- Calendars that don't reflect the actual contract working days, holidays, or weather shutdown periods.
- A narrative that describes progress in general terms instead of naming the specific activities driving the critical path and explaining float consumption since the prior update.
- Constraints used to force an on-time finish date rather than letting the logic calculate it honestly.
Every one of these is preventable with a schedule built to the specification from day one, and reviewed against agency-specific conventions before submission — which is the service HADVEN provides through California CPM scheduling and independent schedule quality review.