A maintenance-of-traffic phase change gets treated on most transportation schedules as a traffic control decision, approved by the agency, implemented by the contractor, documented and moved on from. What that framing misses is that every MOT phase carries its own logic constraints on which construction activities can happen, in what sequence, and that changing a phase can quietly shift float from one party to another without either side explicitly agreeing to it.

Why MOT Phasing Is a Schedule Logic Issue, Not Just a Traffic Control Issue

Each maintenance-of-traffic phase defines which lanes, shoulders, and work areas are available to the contractor at a given point in the project, which in turn constrains which construction activities can physically happen during that phase. A phase that provides access to one side of a roadway restricts work on the other side until the next phase begins. That means the MOT phasing plan isn’t just a safety and traffic management document. It’s effectively a second schedule logic layer sitting on top of the construction schedule, and the predecessor relationships in that layer are just as real as the ones in the CPM schedule itself, even though they often aren’t modeled as formal logic ties.

How Float Ownership Gets Affected Without Anyone Deciding It Should

A phase change requested by the agency can either consume or create float, depending on direction. If an agency requests an MOT phase adjustment that delays contractor access to a work area, that delay consumes float on every activity depending on that access, and depending on how the contract addresses agency-directed changes, that consumed float may belong to the contractor by default unless the schedule explicitly shows the agency action as the cause.

A phase change requested by the contractor for its own convenience shifts float the other way. If a contractor requests a phasing adjustment to improve its own sequencing or productivity, and the agency approves it, any float gained from that adjustment arguably belongs to the project as a whole, or to the agency, not automatically to the contractor, depending on how the original schedule allocated risk. This distinction rarely gets explicitly documented at the time the phase change is approved, which sets up exactly the kind of ambiguity that produces a dispute later, once a schedule slip elsewhere makes float ownership suddenly matter.

MOT phase changes late in a project carry outsized float risk because there’s less schedule left to absorb the ambiguity. A phasing adjustment made early in a long-duration project, with substantial float remaining across multiple paths, is a much lower stakes event than the same adjustment made late, when float has already been consumed elsewhere and a phase change’s effect on the critical path is immediate and unambiguous.

What Belongs in the Schedule to Protect Against This

Every MOT phase transition should appear as an explicit milestone in the CPM schedule, with clear predecessor and successor logic showing which construction activities depend on which phase being active. When a phase change is requested, whether by the agency or the contractor, the schedule update accompanying that change should explicitly document who requested it and why, creating a contemporaneous record of float impact rather than leaving the question to be reconstructed later from correspondence and memory. And float ownership language in the contract itself, if it exists, should be applied consistently to MOT-driven schedule changes, not treated as a separate category exempt from whatever float ownership framework governs the rest of the schedule.

---

Frequently Asked Questions

Why does a maintenance-of-traffic phase change affect schedule float? Because each MOT phase constrains which construction activities can physically occur, functioning as a second logic layer on top of the CPM schedule. A phase change that delays or accelerates contractor access to a work area consumes or creates float on every activity depending on that access, even though this effect is often not formally modeled in the schedule.

Who owns the float when an agency requests an MOT phase adjustment? It depends on the specific contract’s float ownership provisions, but the key issue is that this should be explicitly documented at the time of the phase change, showing the agency’s request as the cause of any resulting schedule impact, rather than left ambiguous and reconstructed later during a dispute.

Does it matter who requests an MOT phase change? Yes. A phase change requested by the agency and one requested by the contractor for its own sequencing convenience have different implications for who should benefit from or absorb any resulting float impact, and this distinction is frequently not documented clearly enough at the time to avoid later disagreement.

How should MOT phase transitions be reflected in the CPM schedule? As explicit milestones with clear predecessor and successor logic tied to the construction activities that depend on each phase, so that any phase change and its float impact can be traced and documented contemporaneously rather than reconstructed after a dispute arises.