Every major rail post-mortem reads the same way. Funding arrived later than planned. Environmental review took longer than expected. Utilities turned up where the drawings said they would not. Contracts did not integrate cleanly. Testing and commissioning ran long. Each finding is true, and each is presented as something that happened to the project. 

I have spent 30 years building and reviewing construction schedules, including on transit programs, and I would put it differently. Most of those causes were in the program schedule years before they became headlines. They were not hidden. They were shown in a way nobody was asked to read. 

The schedule showed it. The report did not. 

A transit program schedule is not short of information. The problem is what gets reported from it. Monthly reports to boards and funding partners usually show the revenue service date, a percent complete and a list of risks. The revenue service date holds until, suddenly, it doesn't. 

Underneath that date, the schedule is often telling a different story month after month. Float is being consumed on the paths that lead to funding milestones. Utility relocation activities are slipping in small increments that never individually make the report. Integration testing is modeled as a few long bars, so every upstream slip disappears into them until the final months, when the date moves all at once. 

None of this requires new software or a new method. It requires asking the schedule different questions. 

Report float by funding milestone 

Public rail is paced by money as much as by construction. Full Funding Grant Agreements, annual appropriations and local funding commitments arrive on their own calendars. Yet, program reporting rarely tracks schedule float against them. 

Each month, report the float remaining on the path to every funding milestone, not just to revenue service. A path that loses 10 days a month for six months is telling the board something important long before the service date moves. The decision to re-sequence, re-scope or seek bridge funding is cheap at month two and expensive at month 18. 

Model integration testing at the density it actually has 

On a new line or a major upgrade, systems integration testing is where the separate contracts finally have to work together: train control, communications, traction power, stations, fare systems, vehicles. It is hundreds of interdependent steps, each waiting on the readiness of systems built by different contractors. 

Program schedules routinely show it as a handful of bars with comfortable durations. When upstream work slips, those bars absorb it silently. Then the testing period arrives, the real sequence asserts itself, and the opening moves by a season. 

Model testing at the density it actually has, tied to the readiness of every contributing system, and the schedule will warn you a year early instead of a month late. 

Treat reviews and outages as risks, not milestones 

Environmental review, historic consultation, track outages and utility agreements are often shown as single milestones with fixed dates. They are not milestones. They are processes that can reopen, slip or be lost entirely. A lost weekend outage can cost a month or more because the next available window may be that far away. 

Show them as activities with owners, durations and the conditions that could reopen them. A schedule that shows the National Environmental Policy Act as a dot on a line has not priced reality. 

What it would take 

Nothing here is exotic. It is a monthly schedule review that reads float by milestone, models integration at real density and treats external processes as risks, reported plainly to the people who fund and govern the program. 

Public rail will never be fast, but the 20-year project is not usually a surprise to its own schedule. It is a surprise to everyone who was only ever shown the date.