A dispute board creates value only if both parties believe its members understand the project and can be trusted to deal with them fairly.
The Robert Hunt source is especially useful because it treats the Dispute Resolution Board as a contractual institution rather than a generic advisory group.
Its design is deliberate.
The source describes nomination and appointment of independent members, selection of a chair, a three-party agreement, periodic visits, defined procedures, project information, hearings, remuneration and rules governing how recommendations or decisions operate.
That architecture matters because credibility is not automatic.
It has to be designed.
The Strategic Context
A standing neutral has two competing needs.
It must become familiar enough with the project to understand emerging issues quickly.
It must remain independent enough that neither party believes familiarity has become alignment.
This is a difficult balance.
Too little engagement and the board becomes an expensive panel that must relearn the project when a dispute arises.
Too much informal involvement and members can drift into consulting, advocacy or prejudgment.
The strongest design makes the boundary explicit.
What Leaders Commonly Misread
The first mistake is allowing party nomination to become party representation.
The source states that once appointed, members should not act as advocates for the party that nominated them.
The second is selecting prestigious names without checking availability, relevant experience or understanding of the dispute-board process.
The third is assuming technical expertise alone is sufficient.
Members also need judgement, fairness, process discipline and the ability to resolve disputes cost-effectively.
The fourth is leaving procedures vague.
If the contract does not explain how referrals, site visits, communications, hearings and decisions work, the board can become another disputed interface.
The fifth is treating neutrality as an ethical aspiration rather than an operating rule.
Reframing the Issue
ERANORTH's source-derived Dispute Board Trust Architecture has six components.
Independence
Members act for the board, not for a nominating party.
Competence
The board understands the technical, commercial and dispute context.
Equal information
Neither side should obtain private procedural advantage.
Familiarity
The board stays current with the project.
Procedural clarity
Referral, hearing, decision and escalation rules are known.
Legitimacy
The parties understand the legal or contractual effect of the board's output.
Trust emerges when all six operate together.
Strategic Analysis: Natural Justice Is an Operational Discipline
The source emphasises ordinary principles of natural justice and recommends that communications to the board be shared with both parties. It also discourages private meetings between board members and one party.
That is not merely legal formality.
It protects perception.
A board can make a technically excellent recommendation and still lose legitimacy if one party believes the process was unequal.
For senior leaders, perceived fairness matters because acceptance depends partly on confidence in the process.
The source also recommends that members visit the project regardless of whether disputes have arisen.
That creates familiarity without requiring private advisory relationships.
The board learns through common information.
Member Selection
The source recommends substantial industry and management experience for construction DRB members and strong knowledge of dispute management.
The exact years of experience suggested in the historical paper should not be converted into a universal rule. [FACT CHECK REQUIRED]
The more useful executive criteria are:
- relevant technical understanding;
- contract-management literacy;
- dispute-resolution competence;
- independence;
- availability;
- judgement;
- communication;
- ability to maintain boundaries.
For the chair, process leadership may be especially important.
Strategic Analysis: Governance Should Be Designed for Turnover
Long projects outlast individuals.
Project directors change. Contractor managers move. Board members may become unavailable.
A credible dispute-board mechanism should therefore survive personnel turnover.
Appointment and replacement processes, document continuity, conflict checks and orientation should be clear from the beginning.
Otherwise, the mechanism may work only while the original relationships remain intact.
This matters because later project phases can generate the most consequential disputes, particularly around completion, delay and final account.
Institutional design should therefore be stronger than personal chemistry.
Decision Framework
Before appointing a board, test five questions.
1. Does the membership fit the project's risk profile?
Complex tunnelling, digital systems and hospital construction may require different expertise.
2. Are conflicts and independence addressed?
Both actual and perceived conflicts matter.
3. Is the information protocol clear?
Define project reports, meeting minutes, site visits and communications.
4. Is the referral process usable?
The board should be accessible before positions harden.
5. Is the legal effect understood?
Advisory, temporarily binding or otherwise? Current dispute-board forms vary. [FACT CHECK REQUIRED]
From Strategy to Execution
Immediate action: define DRB governance in the contract, including appointment, information, visit frequency, referral and communication.
Medium-term capability building: create orientation material so project teams understand when and how to engage the board.
Long-term strategic positioning: retain data on referrals, acceptance, time to resolution and project outcomes.
Use evidence to improve future board design.
Signals to Monitor
Watch for members engaging privately with one party, infrequent visits, project reports not reaching the board, unclear remuneration, late referrals, the chair dominating technical matters outside expertise, or parties treating the board as a tactical step before arbitration.
Another warning sign is site teams not knowing what issues are appropriate to bring forward.
Questions for the Leadership Team
- Do both parties trust the appointment process?
- Is the board's expertise aligned with project risk?
- How will members stay informed without becoming consultants?
- Are communications transparent?
- What procedural rules apply to referrals and hearings?
- What legal effect does the board's output have?
- What would cause either party to stop trusting the mechanism?
Closing Perspective
A dispute board is credible when its independence and familiarity reinforce each other rather than compete.
That requires careful member selection, equal information, procedural discipline and clear contractual architecture.
Trust is not a soft outcome.
It is the operating asset that makes early dispute resolution possible.
Related article: A Standing Neutral Changes the Economics of Disputes
Related article: When Dispute Boards Fail: Bias, Overreach and Loss of Legitimacy
About EraNorth Insights
EraNorth Insights publishes practical analysis on strategy, projects, operations, transformation and decision intelligence for professional and organisational use. About EraNorth.