Appointment, number of members, expertise and independence should match the contractual architecture.
PRACTICE / DISPUTE BOARD PRACTICE
Independent project process built into the contract.
Dispute Board Practice sits inside project and contract architecture. A board may be standing or formed for a defined dispute, and its functions, procedure and effect come from the governing contract, rules and appointment terms.
PROJECT-LINKED NEUTRAL PRACTICE
The board is useful because it belongs to the project architecture, not because it sits outside the project looking in.
Strong Dispute Board Practice combines project familiarity, Neutral discipline and strict attention to the authority created by the contract.
CONTRACT
The board's authority begins in the agreed framework
Composition, referral, procedure and effect should be read from the governing arrangement.
PROJECT
The work happens while delivery continues
The board needs to understand the live project without becoming part of project management.
DECISION
Outcome and effect depend on the board mandate
Recommendation, decision, interim effect and later review should never be guessed from the label alone.
PROJECT PROCESS UNDER PRESSURE
A Dispute Board should reduce the distance between the live project and the process used to address its disputes.
Construction disputes grow quickly when facts, programme, site conditions and project relationships change faster than the formal process can respond. Board architecture can create a nearer professional route, provided the board remains independent and follows its contractual function.
THE DISPUTE BOARD FUNCTION
Understand the project. Respect the contract. Stay outside management.
The board may receive referrals, hear parties, inspect context where authorised, evaluate technical-commercial material and issue the form of outcome the governing arrangement requires.
A standing board may gain useful familiarity without taking part in management.
The dispute or issue before the board should be identified within the contract's procedure.
Submissions, meetings, site context and evidence should follow the board's authority.
The board must not overstate the effect of a recommendation or decision.
THE BOARD INSIDE A LIVE PROJECT
The process must understand the site without becoming the site team.
Dispute Board Practice is unusually close to project reality. That proximity is useful only when professional independence and contractual boundaries remain visible.
LIVE PROJECT
Facts keep moving while the board process is running.
PROJECT ARCHITECTURE
The contract and project structure determine how the board fits.
Regular project context can reduce the time needed to understand later referrals.
The function remains contract-linked even where the board is not standing from project start.
Board members are not contract administrators or project managers unless another role is expressly and compatibly created.
FROM CONTRACT TO BOARD OUTCOME
The board process should follow the architecture the parties actually agreed.
Dispute Board Practice is strongest when constitution, referral, procedure and outcome all map cleanly back to the governing project framework.
DISPUTE BOARD PATH
Contract first. Referral second. Board process third.
The board should not invent jurisdiction or remedy because the project would benefit from it.
Appoint members, clear conflicts and confirm the governing terms.
Use only the familiarity and information the arrangement permits.
Identify the dispute, relief and procedural route under the contract.
Run a fair and proportionate board process.
Apply contractual, technical and professional judgment within authority.
Recommendation or decision should carry only the effect the framework provides.
PROFESSIONAL BOUNDARIES
A Dispute Board is part of project dispute architecture, not a substitute project manager or arbitral tribunal by default.
Its legitimacy comes from doing the contractual job precisely.
WHAT THE ROLE DOES
Provides the board function created by the project framework.
Receives matters through the agreed referral route
Can use project familiarity where authorised
Applies relevant technical and commercial understanding
Runs an independent board process
Issues the authorised recommendation or decision
The particular board type and rules matter.
WHAT IT DOES NOT DO BY DEFAULT
Does not acquire powers simply because the project is difficult.
No general management authority
No automatic arbitral jurisdiction
No authority outside the contract or board terms
No guarantee that every issue belongs before the board
No assumption that all board outcomes have the same effect
Read the actual board framework before describing what the process can do.
WHERE DISPUTE BOARD PRACTICE IS MOST NATURAL
The practice follows project architecture rather than a generic dispute category.
Construction and infrastructure are the clearest settings, but board-style arrangements can also appear in other major long-term projects.
Complex delivery, variations, delay and technical interfaces.
Long project lives and multiple commercial interfaces.
Engineering, procurement, construction and performance questions.
Project structures where responsibilities and packages overlap.
Projects where parties, advisers and professional expectations span markets.
FIND THE PROFESSIONAL
Find board capability by project and board function, not by generic dispute experience alone.
Dispute Board appointments should consider board experience, project context, technical or commercial depth, independence, jurisdictional setting and capacity for the required timetable.
Look for understanding of standing and ad hoc board procedure where relevant.
The professional should understand the type of project behind the referral.
Board proximity to the project makes ongoing disclosure discipline important.
Members must be able to manage submissions, hearings and multi-member deliberation where applicable.
Select someone able to work within the actual board rules and outcome structure.
DISPUTE BOARD PRACTICE
The best Dispute Board is close enough to understand the project and disciplined enough never to forget that its authority comes from the contract.
Constitute carefully, use project context proportionately, follow the referral process and describe the board's outcome only as the governing arrangement allows.