TxDOT CPM scheduling requirements: Item 8, Prosecution and Progress, Section 5
The Texas Department of Transportation carries its scheduling requirement inside its prosecution-and-progress item rather than in a section of its own. Item 8, "Prosecution and Progress", Section 5, Project Schedules, of the 2024 Standard Specifications for Construction and Maintenance of Highways, Streets, and Bridges runs from 5.1 to 5.5.4 and covers the scheduler, the schedule itself, its format, the two schedule types, and a four-step time impact analysis.
Section 5 opens by saying what the schedule is for: it conveys the Contractor's intended work plan to the Department. It also states that the work of preparing and maintaining it is not measured or paid for directly but is subsidiary to the other items — so unlike several agencies compared on this site, Texas does not make the schedule a bid item.
One note on this document before the requirements. TxDOT's title page carries a copyright notice reserving all rights in the book. Of the sixteen documents read for this site, it is the only one that does. Everything below is a characterisation of what the clauses require, written in this project's own words and cited to the clause, and nothing is reproduced from the book.
What Item 8 Section 5 requires
| Requirement | What the 2024 Standard Specifications state | Clause |
|---|---|---|
| Scheduling software | Primavera P6 named, and named as sufficient rather than mandatory. A CPM submittal is the scheduling software's native file in a format the Engineer finds acceptable; in every case a Primavera Project Planner and P6 .xer export will be accepted. No other product is excluded and none is compelled |
5.5.2 |
| Schedule type | Set by the plans: bar chart or CPM. The bar chart tier is due seven calendar days before the preconstruction meeting; the CPM tier carries the preliminary, baseline and progress schedules below | 5.2, 5.5.1, 5.5.2 |
| First schedule due | CPM tier: a preliminary schedule seven calendar days before the preconstruction meeting, unless a later date is agreed, running from the authorisation date to begin work and reaching 90 calendar days out from the work start date | 5.5.2.1 |
| Baseline deadline | Submitted for review inside 45 calendar days of the work start date, unless the Engineer extends it, and an acceptable baseline must be in place before the 90th calendar day from that date | 5.5.2.2 |
| Agency review | 15 calendar days for the Engineer to evaluate the baseline and say whether it has been accepted; where comments are issued, a revised schedule or the Contractor's reasons for not revising follow within 10 calendar days. On monthly updates the Engineer responds in 5 calendar days and the resubmission window is 5 | 5.5.2.2.1, 5.5.2.3 |
| Update frequency | Monthly. The cut-off for recording progress is the last day of each month and the updated schedule is due no later than the 20th calendar day of the month after | 5.5.2.3 |
| Narrative | Required. A brief bulleted statement covering the major items that have affected the schedule, and every schedule revision listed with its purpose and its effect on the critical path and the completion date. Where the plans call for it, a Project Schedule Summary Report on a Department form takes the narrative's place | 5.5.2.3, 5.5.2.3.1 |
| Recovery or revised schedule trigger | No recovery-schedule clause. The schedule is revised when construction phasing or sequencing changes, or on any other change that deviates from the original schedule; the revision is built from the latest update preceding it | 5.5.2.3 |
| Time impact analysis | Yes, in four prescribed steps, provided when directed. Step 4 is due 15 calendar days at the latest once the impact has stopped having an effect, or once the full effect is known. A separate notice of potential time impact comes first | 5.5.3, 5.5.4 |
| Float ownership | Total float is defined in whole days as the delay an activity can absorb before the completion date moves, and is stated to be a shared commodity between the Department and the Contractor | 5.4 |
| Activity durations | Not to exceed 20 working days unless agreed with the Engineer. Durations are stated in whole working days, and each work activity carries an estimated production rate per working day unless otherwise agreed | 5.2, 5.4 |
| Relationships | On a CPM schedule, a predecessor and a successor for each activity | 5.3 |
| Critical path | Identified clearly as the longest continuous path. Where two plots are requested, one shows only the critical path determined by the longest path and expressly not by float | 5.3, 5.5.2.2 |
| Calendars | Seasonal weather conditions are built into the calendars for work influenced by temperature or precipitation — earthwork, concrete paving, structures, asphalt and drainage are the examples given — along with holidays, weekends and other non-work days named in the contract | 5.3 |
| Title block | Each submittal carries a legend for abbreviations, plus the run date, data date, project start date and project completion date | 5.3 |
The critical path is defined by path length, not by float
Two clauses in Section 5 say the same thing from different directions, and together they settle a question most specifications leave open.
5.3 requires a CPM schedule to identify the critical path unambiguously, as the longest continuous path. 5.5.2.2 then asks, where two plots are requested, for one of them to show only the critical path as determined by the longest path — and adds that it is not based on critical float.
That second phrase is doing real work. In a network with multiple calendars, or with constrained milestones, the activities at the lowest total float and the activities on the longest continuous path are not always the same set: a schedule can carry many zero-float activities forming no continuous chain to completion, and a longest path whose float is not zero at all. Texas picks one of the two definitions and says so twice.
This project reports both quantities and labels which is which — the longest path as the file's own scheduler recorded it, and total float per activity — and reports any disagreement rather than resolving it, because which governs is a fact about the contract documents. Total float and free float covers the distinction, and schedule calendars the reason multiple calendars can separate them.
Seasonal weather built into calendars, not into contingency
5.3 requires seasonal weather conditions to be incorporated using calendars, for the classes of work that temperature or precipitation can influence, and names five: earthwork, concrete paving, structures, asphalt and drainage. Non-work periods — holidays, weekends and any others the contract identifies — go into the calendars too.
Placing weather in the calendar rather than in an activity or a duration
allowance is a structural choice, and it is one the file records. A calendar
carries its work and non-work days in the export; a weather allowance buried in a
duration does not. So "was a seasonal calendar applied to the paving work" is
answerable from an .xer file and "was weather allowed for" generally is not —
which is why this page separates requirements a file can settle from requirements
it cannot. Calendars in an XER file describes what the export
carries; whether the calendar applied is the right one for the work is determined
by the reviewing authority.
A time impact analysis in four steps, with the last one on a clock
5.5.4 prescribes the shape of the analysis rather than citing an external method, which makes Texas unusual in a different way from the agencies that name AACE recommended practices. The four steps are: establish the project's status immediately before the impact; predict the impact's effect on the update used in step one; track the effects while the impact is occurring; and establish the project's status once the effect has ended, with the mitigating actions or circumstances used to keep the project going through the impact period identified.
The impact is then measured by comparing step one against step two, where that prediction was requested, and against step four once the impact is complete. Steps 1, 3 and 4 must be complete before a time extension or a milestone adjustment will be considered, unless the Engineer approves otherwise — so the prospective step is the optional one, and the two status snapshots and the contemporaneous tracking are not.
Step 4 carries a deadline: 15 calendar days at the outside, counting from the point at which the impact stopped having any effect — or from the point at which the information on that effect became fully known. And a separate obligation runs earlier: 5.5.3 requires a notice of potential time impact where a time extension or milestone adjustment may be justified, or when directed, and states that failing to give it forfeits the right to request one — except where the Contractor could not reasonably have known of the impact at the time.
5.5.4 also gives the Engineer a ground for rejecting the analysis: where the review finds schedule revisions that were made but not identified in a narrative. That ties the narrative obligation at 5.5.2.3 directly to the analysis, a connection most documents compared on this site leave implicit.
How delay analysis methods differ sets the four-step shape beside the named external methods; nothing on this page states whether a delay is excusable or compensable, which the contract and the reviewing authority decide.
What this page does not tell you
- It does not tell you which clauses govern your project. Whether the plans call for a bar chart or a CPM schedule is decided by the plans, and the incorporated contract documents — the edition named, plus every special provision — are what apply. An agency's name alone does not establish which clauses bind.
- Only Item 8 Section 5 was read for the scheduling requirement. Provisions elsewhere in the 2024 book that bear on contract time, liquidated damages or claims are outside what this page establishes.
- There is no rule pack behind this page. It rests on a reading of the specification text, with each requirement cited to the clause it came from. Nothing in this engine checks a schedule against these clauses today.
- This project computes and reports; it does not decide submissions. It states what an imported schedule contains and reports it against the clauses cited. Whether a schedule is acceptable, and whether more contract time is due, are determined by the reviewing authority.
Related pages
- How state DOT scheduling specifications compare.
- Neighbouring readings: CDOT · WSDOT · PennDOT.
- Float ownership across specifications and total float and free float.
- The XER format and calendars in an XER file.
- Glossary — longest path, total float, data date, fragnet.
- What the engine does and its limitations.
- The conformance rule catalogue and the standards map.
Source: web/pages/txdot-scheduling.md. Source commit date: 2026-09-11.