Caltrans CPM scheduling requirements: Standard Specifications §8-1.02C
The California Department of Transportation states its critical path method requirement in the body of its own Standard Specifications, at §8-1.02C, "Level 2 Critical Path Method Schedule", with the defined terms it depends on in §1-1.07B, the Glossary of the same book. §8-1.02C(1) binds the section to a contract whose Bid Item List carries a bid item for a Level 2 CPM schedule, so it is a term of that contract rather than a standard adopted by reference.
This page describes the 2025 Edition, and a new edition takes effect during 2026. Caltrans issued an implementation memo dated 20 July 2026: the 2026 Standard Specifications must be used on projects submitted on or after 19 October 2026, and the memo states that the 2025 Standards will not be supported after 16 October 2026. The 2026 PDF was not public when this page was written and has not been read here. Every clause number, band and threshold below is from the 2025 Edition. Do not carry a 2025 number into a 2026 project without reading the 2026 book.
On quotation. Caltrans is the one state specification described on this site whose title page asserts copyright — "© Copyright 2025 California Department of Transportation. All rights reserved." Section numbers, thresholds and rule titles are stated here in this project's own words with the citation attached, and nothing beyond a short anchoring phrase is reproduced.
What §8-1.02C requires
| Requirement | What the 2025 Edition states | Clause |
|---|---|---|
| Scheduling software | Primavera P6 for Windows is named directly, at its latest version, with an "or equal" allowance the Engineer decides. | §8-1.02C(3) |
| Baseline schedule | The baseline schedule's data date is the Contract approval date, and the start milestone falls on that date. A general time-scaled logic diagram is due within 5 business days of Contract approval, and a preconstruction scheduling conference is held within 10 days of it. A separate day count for the baseline submission itself was not established from the material read here. | §8-1.02C(2)(11), (5), (6) |
| Update frequency | Monthly, with the update meeting on or before the first day of each month, beginning 30 days after the baseline schedule is accepted. | §8-1.02C(7) |
| Narrative | Required, under twelve enumerated headings. | §8-1.02C(4) |
| Recovery or revised schedule trigger | No clause named "recovery schedule" appears in §8-1.02C. | Not stated in this provision |
| Time impact analysis | Due within 5 business days of a proposed change that affects the critical or near-critical path, and within 10 days of a written request. The method inserts the change into the accepted schedule whose data date is closest to and before the event, and compares scheduled completion dates. | §8-1.02C(8)(b) |
| Float ownership | Department-owned float is modelled as the predecessor activity to the scheduled completion date; §1-1.07B defines it as time saved on the critical path by Department action. Early completion time is the Contractor's, and may be shown on any schedule. | §8-1.02C(2)(12), §1-1.07B |
The bands, which are what make this specification unusual
Most scheduling specifications state prohibitions: no open ends, no negative lag, no unauthorized constraints. §8-1.02C states bands, with a number at each end, and a schedule can sit outside one from either direction.
- Activity count. At least 50 and not more than 500 activities, unless otherwise authorized (§8-1.02C(2)(5)). A 30-activity schedule for a large job and a 900-activity schedule are both outside it.
- Activity duration. At least 1 working day and not more than 20 working days for each activity, unless otherwise authorized (§8-1.02C(2)(10)). Read with §1-1.07B's definition of a milestone as an event activity of zero duration, the low end does not reach milestones.
- Criticality share. Not more than 50 percent of baseline activities may be critical or near critical, unless otherwise authorized (§8-1.02C(6)). This is a cap and not a band — the specification states a maximum and no minimum.
The criticality cap is decidable without any industry default, because Caltrans defines both halves of it in its own Glossary. §1-1.07B defines the critical path as the longest continuous chain with the least total float, and a near critical path as a chain whose total float exceeds the critical path's but is not more than 10 working days. The number is Caltrans's, in Caltrans's own units. This project's rule pack computes that pair and nothing else; where an activity's total float cannot be computed, the pack reports the share as undecided rather than dropping the activity, because dropping it would lower the share.
Department-owned float, and what a file can show about it
§8-1.02C(2)(12) requires Department-owned float to appear as the predecessor activity to the scheduled completion date, and §1-1.07B adds that it is the last activity shown before scheduled completion. The arithmetic of a forward and backward pass does not change for this: a predecessor activity is an ordinary node and the passes compute it as they compute anything else. What the clause fixes is whose the resulting float is, which is an entitlement question about a computed number and one the reviewing authority determines.
Nothing in a P6 export identifies which activity is the Department's float. It is a modelling convention, so the rule that checks the clause asks for the activity identifier as a supplied contract fact and reports the clause as not evaluated when it is not given, rather than guessing at a name.
The software clause is the least checkable line in the section
§8-1.02C(3) looks like the most quotable requirement and is the hardest to decide from a file. "Latest" is a fact about a release calendar and a submission date, not about a schedule; "or equal" is a determination the clause reserves to the Engineer against stated capabilities; and an export declares the tool that wrote it, which is evidence that P6 was used and not evidence that its version was current. This project reports what wrote the file and does not decide the clause.
Reviewer-side guidance is published separately
Caltrans publishes Construction Manual Chapter 3, Section 8, "Prosecution and Progress" (March 2022), which is written for the Department's own reviewers rather than for the Contractor. It is guidance to staff, not a term of the contract, and it is a separate document from the specification described above.
What this page does not tell you
- It does not tell you which clauses govern your project. §8-1.02C applies where the Bid Item List carries the Level 2 CPM schedule bid item. The incorporated contract documents for a specific project — the special provisions, the bid item list, any revised standard specifications — have to be read. An agency name alone does not establish which clauses apply.
- The 2026 Edition has not been read. Clause numbers and thresholds may move. Projects submitted on or after 19 October 2026 are governed by a book this page does not describe.
- Several clauses were not established here. No recovery-schedule clause was found in §8-1.02C, and a baseline submission deadline distinct from the data date requirement was not established. Those are absences in what was read, not findings that the requirement does not exist elsewhere in the contract.
- This project computes and reports; it does not decide submissions. It states what the imported schedule contains and checks it against the clauses cited, and it refuses to decide excusability, entitlement, or whether a schedule is adequate. The reviewing authority determines acceptance.
Related pages
- How state DOT scheduling specifications compare — the five agencies on this site side by side.
- UFGS scheduling requirements — the federal specification and how a contract term ranks against a standard.
- Glossary — total float, near critical, data date, and the other terms used above.
- What the engine does and limitations.
- The conformance rule catalogue and the standards map, which records how this specification was read and what was refused.
Source: web/pages/caltrans-scheduling.md. Source commit date: 2026-09-11.