Program Governance

Keep Delivering While the Dispute Exists

How contract governance should escalate disagreement, preserve rights and maintain delivery continuity instead of allowing issues to consume the project.

EraNorth Insights · 30 Aug 2026 · 7 min read

The commercial disagreement may be real, but the project still has to decide what happens tomorrow morning.

The supplied AS 4000—1997 historically contains a dispute process involving notice, conference and arbitration, while also stating that the parties should continue to perform the contract subject to specified exceptions. The Week 11 forum likewise recommends understanding the supplier's position, agreeing corrective actions where possible and following the contract's dispute-resolution process.

These sources point to an executive principle often lost once positions harden:

A dispute-resolution system should protect delivery as well as legal rights.

The Strategic Context

Disputes consume scarce organisational capacity.

They draw attention from executives, project managers, technical specialists and commercial teams.

They can slow decisions, damage trust and create defensive behaviour.

But many disputes arise while the project is still live.

The organisation therefore faces two problems at once:

  1. resolve the contested entitlement; and
  2. preserve delivery of the underlying project.

If every disagreement suspends performance, the commercial mechanism can become a project-failure mechanism.

If parties ignore disputes to preserve relationships, unresolved exposure accumulates.

Strong governance must do both.

What Leaders Commonly Misread

The first mistake is assuming escalation means relationship failure.

A defined escalation path can protect relationships by moving a problem to people with enough authority and distance to resolve it.

The second is leaving unresolved issues at project-team level for too long.

Operational teams may not have authority to settle a material commercial matter.

The third is escalating everything immediately to lawyers.

Legal advice may be essential, but excessive legalisation can narrow the space for practical settlement.

The fourth is allowing the existence of a dispute to blur ongoing obligations.

The parties still need clarity about which work continues, what is paid, what remains contested and what evidence is preserved.

The fifth is treating dispute-resolution clauses as boilerplate chosen during drafting rather than part of delivery architecture.

Reframing the Issue

Dispute governance should be built around two parallel tracks.

Track 1: Delivery continuity

What work continues?

What interim directions are required?

What payments are undisputed?

What safety or operational actions cannot wait?

Track 2: Commercial resolution

What is disputed?

Who has authority to negotiate?

What contractual process applies?

What evidence is needed?

What escalation or formal forum comes next?

Separating the tracks prevents the dispute from swallowing the entire contract.

Strategic Analysis

The supplied AS 4000—1997 historically uses a staged process: notice of dispute, conference and then arbitration if unresolved, while preserving certain rights to seek urgent or payment-related relief.

Current dispute mechanisms vary substantially by contract, jurisdiction and legislation and must be verified. [FACT CHECK REQUIRED]

The strategic value lies in staged escalation.

Different disputes require different levels of intervention.

A measurement disagreement may be solved by technical review.

A scope-entitlement issue may need senior commercial negotiation.

A large delay claim may require expert analysis.

A payment dispute may interact with statutory adjudication rights.

A safety-related injunction cannot wait for a long negotiation process.

The governance system should therefore match resolution pathway to issue type and urgency.

Authority Matters

A common failure is sending people to settlement meetings who cannot settle.

The supplied standard historically requires representatives at dispute conferences to have authority to agree resolution or methods of resolution.

That is a useful governance principle.

Escalation should increase decision authority, not simply increase meeting seniority.

Leadership should know:

  • negotiation limits;
  • settlement authority;
  • precedent implications;
  • accounting impact;
  • broader portfolio effects.

A settlement that looks sensible on one project can create expectations elsewhere if the underlying issue is systemic.

Strategic Analysis: Resolution Speed Has Economic Value

The cost of a dispute is not limited to legal fees or the eventual settlement.

Unresolved disputes can slow decisions, increase management effort, weaken supplier cooperation, delay subcontractors, distort forecasting and consume executive attention. Resolution speed therefore has economic value.

This does not mean leadership should settle weak claims simply to make them disappear. It means the cost of prolonged uncertainty should be included in the decision.

A hypothetical engineering project has a disputed $500,000 variation affecting work on the critical path. If the dispute remains unresolved, the contractor may proceed cautiously, preserve resources for the claim and avoid additional discretionary cooperation. If a commercially reasonable interim arrangement allows work to continue while entitlement is assessed, the project may protect a far larger benefit.

The correct approach depends on contract, evidence and risk.

Governance should also prevent the dispute from infecting unrelated work. Undisputed invoices should not become bargaining chips unless the contract and law permit the relevant action. Technical cooperation should not collapse because one commercial issue remains open.

This separation requires leadership discipline. The parties need to preserve rights while deliberately containing the dispute.

The best dispute system is not the one with the most formal stages. It is the one that resolves material uncertainty at the lowest appropriate level before the cost of conflict exceeds the value being argued about.

Decision Framework

Use a Dispute Continuity Matrix.

Issue definition

What exactly is contested?

Undisputed position

What do both parties agree should continue?

Delivery risk

What happens if the dispute remains unresolved for 30, 60 or 90 days?

Resolution level

Operational, senior commercial, executive, expert, mediation, adjudication, arbitration or court?

Authority

Who can settle?

Evidence

What facts or analysis are still missing?

Precedent

Would the resolution affect other contracts or claims?

This makes escalation deliberate.

From Strategy to Execution

Immediate action: define the dispute, preserve undisputed performance and assign a resolution owner.

Medium-term capability building: create escalation protocols with clear authority thresholds and access to technical, commercial and legal expertise.

Long-term strategic positioning: track dispute causes, duration and settlement patterns across the portfolio. Repeated disputes about the same clause or interface are design feedback.

The strongest dispute strategy reduces recurrence.

Signals to Monitor

Watch for disputes remaining unresolved at monthly meetings, senior leaders learning of issues only after positions harden, payment of undisputed amounts being delayed because other matters are contested, project staff withholding cooperation, duplicated legal and technical analysis, or settlement discussions without authorised decision-makers.

Another warning sign is when the project stops distinguishing the claim from the relationship.

Questions for the Leadership Team

  1. What is actually disputed?
  2. What work and payment can continue regardless?
  3. Who has authority to resolve the issue?
  4. What evidence is missing?
  5. What happens if resolution takes another three months?
  6. Does the contract provide a suitable escalation path?
  7. What recurring system problem does this dispute reveal?

Closing Perspective

Dispute governance is successful when it protects both the commercial position and the project outcome.

The objective is not to avoid every disagreement.

It is to ensure disagreement does not become organisational paralysis.

Related article: Claims Begin with Evidence, Not Lawyers

Related article: Litigation Is a Delivery System: Forum Choice, Case Management and the Economics of Commercial Disputes

Related article: Contractor Failure Is a Continuity Problem Before It Is a Legal Problem


About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.