Saudi Binladin Group All articles
Program Delivery

When the Crossing Owns the Clock: A Pre-Bid Package for Class I Rail Coordination

Saudi Binladin Group
When the Crossing Owns the Clock: A Pre-Bid Package for Class I Rail Coordination

Photo: California Public Utilities Commission, No restrictions, via Wikimedia Commons

The Second Approval Authority

A highway widening, a utility corridor, a transit connection, or an industrial park expansion can clear every local and state review and still stall at a single set of railroad tracks. Class I railroads are private operating businesses with their own engineering standards, insurance requirements, flagging rules, and capital priorities. When a public works project intersects their right-of-way, the railroad becomes a de facto approval authority. The problem is that bid documents often treat that authority as a permitting formality rather than a delivery constraint.

The result is a shadow schedule: operating agreements negotiated after award, flagging crews requested when the contractor is already mobilized, force-account work measured in railroad-defined units, and insurer approvals that surface weeks before a planned closure. None of these steps is mysterious. They are simply absent from the bid package. For program delivery teams, the remedy is not a better excuse after the hold occurs; it is a named pre-bid schedule and cost package that makes railroad coordination visible before proposals are due.

What the Shadow Schedule Contains

Class I coordination generally runs through four workstreams. Each has its own long-lead milestones and its own failure mode.

Operating and construction agreements. A railroad will typically require a formal agreement covering right-of-entry, scope, standards, indemnification, and insurance before any work near its tracks. Drafting and execution can take months, and the railroad's legal and engineering reviews are sequential, not parallel. Bidders who assume a standard template will be signed within weeks are pricing an assumption, not a schedule.

Flagging and track protection. Many projects require railroad-provided flaggers, watchmen, or both. These resources are allocated from railroad rosters and compete with the railroad's own capital program. A flagging request submitted after award may be honored, but the date may not match the contractor's planned closure window. Protection costs also vary by track type, traffic density, and work method.

Force-account work. Railroad-owned utilities, signal systems, and track modifications are often performed by the railroad on a force-account basis. The contractor cannot competitively bid this work, cannot control its productivity, and may not receive a firm estimate until design is further advanced. Force-account exposure belongs in the bid as a quantified allowance, not as a note in the assumptions.

Insurance and risk approvals. Railroads impose specific insurance limits, additional-insured requirements, and safety protocols. The contractor's insurance program may satisfy them, but the approval process still takes time. A certificate of insurance is not the same as a railroad approval.

Build the Responsibility Matrix First

Before estimating cost, the pre-bid team should map who owns each coordination step. A responsibility matrix with clear owners prevents the most common failure: the assumption that someone else is chasing the railroad. The matrix should distinguish between the project owner, the contractor, the railroad, and third-party utility owners. For each row—agreement execution, design submittal, flagging request, force-account authorization, insurance approval, track outage request—the matrix should identify the responsible party, the required input, the review duration, and the evidence of completion.

This matrix is not a contractual delegation of risk. It is a planning instrument. Its purpose is to expose dependencies that a bid schedule normally hides. When the matrix shows that a railroad design review cannot begin until a utility relocation is complete, the bid team can see the sequence rather than discovering it during construction.

Set a Milestone Ladder, Not a Single Date

Railroad coordination is often reduced to one milestone—'railroad approval'—which is too coarse to schedule. A more useful approach is a ladder of intermediate milestones, each with a realistic duration:

Each rung should be tied to a predecessor and a decision gate. The ladder should also identify which rungs can run in parallel and which cannot. For example, insurance approval may proceed while the agreement is in legal review, but flagging reservations may not be confirmed until the construction method is approved. Presenting this ladder in the bid documents gives every proposer the same coordination model and makes schedule comparisons meaningful.

Price the Coordination, Not Just the Construction

The cost package should mirror the milestone ladder. Direct costs include railroad review fees, flagging labor, track-protection equipment, force-account allowances, insurance premiums attributable to railroad requirements, and any railroad-mandated construction materials or methods. Indirect costs include the schedule contingency required to absorb railroad review duration and the management effort to track submittals and approvals.

A common mistake is to bury these costs in general conditions or a percentage markup. That approach obscures the true cost of railroad coordination and makes it difficult to evaluate trade-offs later. A separate coordination cost section—visible in the bid breakdown—allows the owner to compare proposals on a like-for-like basis and gives the contractor a defensible basis for change management if railroad requirements evolve.

Contingency With a Trigger, Not a Guess

Contingency for railroad coordination should be tied to specific triggers rather than applied as a blanket percentage. Useful triggers include the number of separate railroad jurisdictions, the presence of railroad-owned utilities, the need for track outages, the complexity of the agreement, and the maturity of the project design at bid time. A project with one crossing, no railroad utilities, and a standard agreement carries a different risk profile than a multi-track corridor with signal work and a required closure window.

The contingency should also have an owner and a release condition. If the railroad approval milestone is achieved earlier than planned, the contingency can be released or reallocated. If it slips, the trigger is documented and the schedule impact is measured against the ladder rather than argued after the fact.

Make It Part of the Bid Evaluation

Finally, the pre-bid package should influence how proposals are evaluated. If the owner asks for a railroad coordination plan, the evaluation should reward specificity: named milestones, a responsibility matrix, a cost breakdown, and a contingency logic. A generic statement of intent to coordinate with the railroad is not a plan. A schedule that shows the railroad review as a single bar is not a schedule.

For US infrastructure programs in 2026, the pressure to deliver quickly is real, but speed at the bid stage cannot substitute for coordination discipline. The crossing will still own the clock unless the bid documents own the crossing. Treating Class I coordination as a named pre-bid package is the difference between a railroad hold that is managed and one that becomes the project's defining delay.

All Articles

Related Articles

The Empty Shelf at Handover: Making Spares Readiness a Commissioning Gate

The Empty Shelf at Handover: Making Spares Readiness a Commissioning Gate

The Fifth Transformer: Making Interchangeability a Pre-Bid Design Standard

The Fifth Transformer: Making Interchangeability a Pre-Bid Design Standard

The Hold-Point Ledger: Planning Special Inspections as a Finite Delivery Resource

The Hold-Point Ledger: Planning Special Inspections as a Finite Delivery Resource