Who's Responsible When Coordination Errors Reach the Field?

A duct conflicts with a beam. A dimension is wrong. A penetration wasn't detailed. When coordination errors reach the field, the first question is always: "Who's responsible?" The answer is rarely simple—and the finger-pointing can cost more than the fix itself. Here's what you need to know about liability for coordination errors.

The Liability Landscape

Construction projects involve multiple parties, each with their own contracts and scopes. When something goes wrong, determining responsibility depends on:

• Contract language
• Standard of care expectations
• Industry practice
• Who knew (or should have known) about the issue
• Who had the ability and responsibility to prevent it

The challenge: coordination errors often fall into gray zones where multiple parties share some responsibility but none accepts full liability.

Parties and Their Obligations

The Architect (Prime Design Professional)

Under standard AIA contracts, the architect typically has overall responsibility for coordinating the work of consultants. This includes:

• Ensuring drawings from different disciplines are coordinated
• Maintaining design intent across all documents
• Reviewing consultant work for conflicts with architectural design

However: The architect isn't expected to independently verify every technical decision of each consultant. They coordinate, but each consultant remains responsible for their discipline's technical accuracy.

Consulting Engineers

Each engineering discipline is responsible for:

• Technical accuracy of their design
• Code compliance within their scope
• Coordinating with adjacent disciplines where their systems interface
• Flagging conflicts they identify during design

The gray zone: What happens at discipline interfaces? If the structural engineer's beam location conflicts with the mechanical engineer's duct routing, who should have caught it?

The General Contractor

In most contracts, the GC is expected to:

• Review documents for constructability
• Identify conflicts and inconsistencies
• Issue RFIs for unclear conditions
• Coordinate trade work in the field

Importantly: The contractor isn't responsible for design errors—but they may be responsible for building something they knew (or should have known) was wrong. The duty to identify and report issues creates shared responsibility.

The Owner

Owners typically aren't liable for design coordination errors—they hire professionals for that. However, owner-directed changes that create conflicts can shift responsibility.

Common Scenarios and Typical Outcomes

Scenario 1: MEP vs. Structural Conflict

Scenario 2: Dimensional Discrepancy

Protecting Your Firm

1. Clear Contract Language

The best protection starts with contracts that clearly define coordination responsibilities:

• Who is responsible for what interfaces?
• What is the standard for "coordination"?
• What review processes are expected?
• How are conflicts resolved?

2. Document Your Process

If disputes arise, you want evidence of due diligence:

• Records of coordination meetings
• Documentation of QA/QC reviews
• Written communication about identified issues
• Evidence of technology used for review (including AI)

3. Prevention Is Better Than Defense

The best protection against coordination liability is catching issues before they reach the field. Every error found during design is one that won't become a claim.

• Structured coordination milestones: Explicit checkpoints where coordination is verified
• Cross-discipline review: Each discipline reviews interfaces with adjacent disciplines
• AI-augmented review: Technology that catches what human review misses
• Clear accountability: Someone owns coordination verification and signs off

When Claims Happen

Despite best efforts, some coordination errors will reach the field. When they do:

Don't Point Fingers Immediately

The instinct to blame someone else often escalates disputes. Focus first on solving the field problem, then address responsibility.

Document Everything

Capture the condition, the proposed resolution, the cost impact, and the communications about it. This documentation is essential if the dispute continues.

Involve Insurance Early

If the issue may become a claim, notify your professional liability insurer. They can provide guidance and may need to be involved in resolution discussions.

Focus on Resolution

Often, the cheapest resolution is a negotiated split of responsibility rather than litigation. Consider the cost of fighting vs. the cost of settling.

The Evolving Standard of Care

An important consideration: as AI tools become common, the "standard of care" for coordination may evolve. If sophisticated review tools are widely available and affordable, not using them could eventually be seen as falling below professional standards.

This doesn't mean AI review is currently required—but early adopters are establishing a higher bar that may become the expectation.

Recommendations

For Design Professionals

• Clarify coordination responsibilities in contracts before starting work
• Implement documented QA/QC processes, including AI review where appropriate
• Communicate proactively about interface issues rather than assuming others will catch them
• Maintain records of coordination efforts as evidence of due diligence

For Contractors

• Review documents thoroughly before bidding and issue RFIs for identified conflicts
• Don't build something you know is wrong—the "I was just following the drawings" defense has limits
• Document any document issues you identify and the responses you receive
• Consider pre-construction AI review to identify risk before you own the problem

For Owners

• Consider independent plan review before construction to verify coordination
• Ensure contracts clearly define coordination responsibilities
• Don't direct changes that create conflicts without design team review

Conclusion

Coordination errors are everyone's problem and no one's responsibility—until they become expensive claims. The liability landscape is complex, with multiple parties often sharing fault for issues that fell through the gaps.

The best protection isn't better contract language or liability insurance (though both help). It's prevention—catching issues before they reach the field where they become disputes. AI-augmented review is one tool that can significantly reduce the chance that coordination errors become your problem.