A Neutral can help define the interface question without becoming project management or redistributing contractual responsibility informally.
The project may have one outcome and several parties responsible for getting there.
Consortium interface strain arises where partners, packages or contractors depend on each other but do not agree where one responsibility ends and another begins. The project still needs coordinated delivery while the interface question is being resolved.
Design, access, testing or supply responsibility may overlap.
Programme logic can turn interface questions into delay disputes.
The parties remain operationally dependent while positions harden.
Interface disputes grow quickly because each party's evidence is usually built from its own package.
Independent evaluation, facilitation, Standing Neutral or specialist determination can create a common professional route around the interface while delivery continues.
Consortium strain becomes expensive when interface questions turn into competing project histories.
The route should isolate the current dependency before every delay and variation is added to it.
Interfaces are unclear or change through coordination.
Workfronts, access or predecessor activities block progress.
No party can demonstrate completion alone.
Each participant attributes critical impact elsewhere.
Variations create new interface obligations without a shared reset.
The interface itself should become visible as a defined project question.
That helps the Neutral work on the dependency without taking over the package managers' responsibilities.
Standing Neutral can provide a known route before every interface issue becomes a formal claim.
Neutral Evaluation can test a defined technical-commercial issue while project authority remains with the participants.
Design, planning and package responsibility remain with the project teams.
Choose the route from the urgency of the interface and the authority the project needs.
Continuing capability, facilitation, assessment and specialist decision answer different project questions.
Standing Neutral
Use a Standing Neutral where repeated interface questions benefit from continuing independent capability.
An interface mandate should solve the dependency without reallocating the whole contract.
Keep the project record, responsibility boundaries and required output explicit.
Design, access, sequence, testing, supply or another defined dependency.
Identify the actual participants and interfaces.
Protect project continuity where possible.
Drawings, programme, RFIs, test records and change material.
Engineering and management decisions stay with the responsible parties.
Assessment, process plan or specialist decision.
Consortium interface often sits inside wider project and supply situations.
Move into the route that best describes the immediate dependency.
When interface pressure is one part of wider delivery strain.
SUPPLY Supplier / customer strainWhen performance and delivery sit across a commercial supply relationship.
PPP Public-private project interfaceWhen the project also involves public authority and concession context.
SECTOR Construction & InfrastructureFor wider project-sector context.
BOARD Dispute Board PracticeFor contract-linked project dispute mechanisms.
Find the professional for the interface function, then add project and technical depth.
Relevant project type, engineering context, contract environment and jurisdiction should refine fit after the Neutral role is clear.
Do not search by prestige before the mandate is clear.
Sector, jurisdiction and specialist depth should refine fit.
Use the Global Register, then run matter-specific conflict and availability checks.
Consortium strain often begins at the interfaces between organisations rather than inside one organisation.
The Neutral process should make shared obligations, package boundaries and decision routes clearer without becoming project management.
Design, procurement, construction, technology, commissioning or operating packages may depend on one another in ways the contracts describe imperfectly.
A consortium may need decisions while delay responsibility remains disputed.
Steering committees, project boards and lead-member structures should retain the authority they actually possess.
Interface questions may require engineering or technical expertise that should not be assumed from general Neutral standing.
The project may still depend on daily cooperation even when formal positions have hardened.
Clarify the interface before debating blame.
Many consortium problems become more manageable when the immediate interdependency is solved before final responsibility is allocated.
Clarify the interface before debating blame.
Many consortium problems become more manageable when the immediate interdependency is solved before final responsibility is allocated.
Map the affected packages and dependencies
Identify what each member needs from the others for the project to continue.
Separate live mitigation from final liability
The consortium may need an interim operating solution while preserving later contractual positions.
Choose Standing Neutral, evaluation or determination
Recurring interface pressure may support Standing Neutral use, while one technical question may need evaluation or expert determination.
Keep technical authority explicit
Do not ask a process Neutral to certify engineering, design or compliance unless that separate specialist mandate is validly created.
Preserve consortium governance
Joint boards and contractual management structures should continue exercising their own authority.
The Neutral should improve the process without acquiring authority that belongs elsewhere.
The boundary should be visible before the process begins, especially where commercial urgency creates pressure to delegate too much.
A defined consortium-interface process.
- Standing Neutral support.
- Neutral Evaluation of a bounded interface question.
- Expert Determination where specialist authority is appropriate.
- Facilitation or mediation between consortium members.
- A clearer route between live mitigation and later liability.
Project or technical management.
- Not the consortium leader.
- Not project management.
- Not the engineer or certifier unless separately appointed.
- Not a substitute for contractual governance.
- Not responsible for delivery performance.
Current public professional records
Only currently published professional records are shown.
Gregory Hunt
Arbitrator & Mediator
Published record: Gregg held Executive Director roles within all organisations and was CEDR’s first Global Group Director of Dispute Resolution. ?In April 2016 Gregg formed Hunt ADR Limited which is registered with…

Vinod kumar
Arbitrator & Mediator
Published record: Vinod also advises clients in commercial transactions involving commercial contracts, real estate and infrastructure development, labour and industrial relationship, human resource policy, environmental compliances etc. Vinod is one of the…

Nityesh P. Peetumber
Arbitrator & Mediator
Published record: Selected Cases as a Junior Commonwealth of Australia v State of Tasmania (the Tasmanian Dams case) (1983) 158 CLR 1, as junior to R J Ellicott QC and AM Gleeson…

James Miller
Arbitrator & Mediator
Published record: Judge Miller presided over one of Colorado\\\'s busiest trial courts for nearly twelve years, where he was praised by attorneys, litigants and jurors for his sense of fairness, his preparation,…
A consortium interface becomes manageable when the dependency is defined tightly enough for independent work.
Keep delivery moving, keep responsibility visible and choose the Neutral role from what the interface actually needs.