Stacy Witbeck https://www.swhhsr.com/Areas/CMS/assets/img/STW-logo.png California CSLB #414305,2800 Harbor Bay Parkway
Alameda, CA 94502
510.748.1870

November 18, 2026

We Were All Working in the Same Tunnel

Lessons in partnering, problem solving and working across contract lines.

By Matt Johnson, Area Manager, Northern California 

Every construction project has a contract that defines the roles, responsibilities, and formal procedures for issue resolution. But the success of a project may be better defined by how the project team deals with the issues and unanticipated conditions that were never contemplated when the contract was drafted. I've come to see partnering as a core value in my management approach, because the real test is what happens – how we behave – when an actual problem arises.

On a project in Seattle, the Northgate Link Extension N180 Trackwork for Sound Transit, we were working under a traditional low-bid, lump-sum contract with clearly defined responsibilities. Although there wasn't a formal pre-construction phase built into the delivery model, we utilized the time before on-site access was granted to be intentional about building the foundation for a collaborative relationship which we would lean on for years to come. 


Formal partnering sessions started more than a year before breaking ground and continued quarterly with the client and key stakeholders, with an independent moderator facilitating the sessions. That gave us the forum to establish how decisions would be made, what needed to be resolved before work was released, and how we would manage the complex materials, installation sequences, and handoffs ahead. 

That early work also established how we would handle issues once construction was underway. 

Project-First Approach to Issue Resolution 

We established an Issue Resolution Ladder that paired counterparts at each level of the project: foreman to inspector, superintendent to lead inspector, project manager to resident engineer or construction manager, and project executive to project director. The people closest to the work had the first opportunity to address an issue because they usually had the best information about what was happening. If they couldn't resolve it quickly, there was a defined next level. We also strived to resolve issues at the lowest level, but team members didn’t, and shouldn’t, hesitate to elevate an issue when needed to avoid wasting time.


Routine field problems can consume a surprising amount of time once they move through several levels of an organization. More people have to get up to speed, documentation grows, and decisions move farther away from the people who understand the actual conditions. On N180, issues were resolved at the project level without having to move into executive dispute resolution. That approach worked well within the N180 team, while the overlapping contracts required a similar way to work through problems across project boundaries.

Alignment Across Contract Lines

With five concurrent contracts working within the same alignment, coordination couldn't stop with the N180 team. Sound Transit facilitated monthly Coordinated Installation Plan (CIP) meetings with the contractor teams to work through handoffs, site access, and schedule constraints. Each contractor had its own milestones, changes, delays, and restrictions, so the CIP gave the team a regular place to see where one contract's work would affect another before those interfaces reached the field.

Tunnel ventilation was a good example. Several contractors were working underground at the same time, and while each had its own work area, everyone was dealing with the same air. The contractors developed a coordinated ventilation plan that pushed and pulled fresh air through the tunnel sections and station boxes, with air quality monitored daily as the work progressed. 


The same issue applied to access, sequence, and handoffs. A constraint on one contract could affect the contractor coming behind it, so understanding those interfaces became part of planning the work. Those interfaces deserve as much planning as the work in the middle, and that principle extended to the subcontractors and suppliers performing specialized work. Major subcontractors participated in daily game-plan meetings, safety briefings, and issue-resolution discussions because the people performing specialized work often had information the rest of the project team needed while access, sequence, and safety were still being planned. 

The more specialized the work, the shorter the information path should be between the people making decisions and the people producing and installing it. 

Relationships That Outlast the Project

I've worked well with plenty of people I disagreed with regularly because we could put the facts on the table, work through the issue, make a decision, and continue with the job. The construction industry feels smaller the longer you’re in it, and people show up again and again on projects.

People move between contractors, agencies, and projects, and the person sitting across from you today may be somebody you're working with again five or ten years from now. They probably won't remember every detail, but they'll remember whether you raised problems early, whether the information you gave them was accurate, and whether you could handle an issue without making the job more complicated than it already was. 

They will remember how you behaved. 


  

Read more about the Northgate Link Extension N180 Trackwork project