Design the board to stay close enough to the project to help, and independent enough not to become project management.

The protocol should state what routine access the board receives. Periodic progress reports, site visits and high-level programme information may be useful. Unlimited access to internal management systems may be unnecessary and can make the board appear embedded in project control.

Site visits should have a defined purpose. Members may observe progress, understand interfaces and meet relevant project participants while avoiding directions to contractors, design teams or management. Questions can clarify; instructions belong to authorised project roles.

Informal assistance should be distinguished from formal referral. Some boards are expected to help the parties surface issues early. That can be valuable if the contract allows it, but participants should know whether a conversation is informal, whether views are non-binding and whether a member's later formal role is affected.

Formal referrals should define the issue, contractual basis, timetable, information process and required output. A broad referral that asks the board to fix the project invites authority beyond the contract.

Board composition should match likely project questions. One member may bring legal or contractual depth, another engineering or technical competence, and another project or commercial experience. The protocol should not assume every member is equally expert in every dimension.

Conflicts are continuing. Major projects introduce new subcontractors, experts, lenders, insurers, advisers and project companies over time. Board members should update disclosures where new relationships become relevant.

Remuneration should support standing availability. A retainer, visit fee and referral fee structure may be appropriate depending on the project, but payment should not make one project participant appear to control the board.

Confidentiality and record handling should fit the contract and jurisdiction. Board communications may later be relevant to formal proceedings, so legal effect should not be assumed from professional practice alone.

The relationship to arbitration, litigation or other dispute mechanisms should be explicit. The protocol should identify whether board steps are mandatory, whether decisions have interim effect and how urgent relief or limitation issues are handled under the governing law.

Closure should be planned for project completion, termination or replacement. Members should know what records remain, whether final disclosures are needed and whether any later arbitral or advisory role is restricted.

Periodic information should be curated. The board may receive progress summaries, major programme changes, significant notices, risk themes and other agreed material rather than every project document. A defined information set helps members understand the project while reducing the chance that they become another layer of project administration.

Regular meetings or site visits should have a simple agenda. Project status, emerging interfaces, unresolved issues and any requested informal assistance can be discussed without asking the board to approve design, certify payment or direct resources. Minutes or short attendance notes can record the mode of engagement and prevent later disagreement about whether the board expressed a formal view.

Where the board has several members, internal governance matters too. The protocol should identify the chair's coordination role, quorum, how members communicate, how conflicts affecting one member are handled and whether a replacement can join without destabilising project familiarity.

Referral procedure should be scalable. A small defined issue may need written submissions and a short meeting. A technically complex referral may justify expert material or site review. The board should be able to tailor procedure within the authority granted rather than forcing every referral into the same timetable.

The protocol should also address simultaneous project and dispute pressures. A formal referral should not automatically stop work unless the contract says so. The project team needs to know what obligations continue while the board considers the issue.

Finally, the parties should review whether the board remains the right composition as the project changes. Construction may move into commissioning, operations or a new technical phase. Replacement or additional expertise may be needed, but change should preserve independence and avoid strategic reshaping of the board after positions have hardened.