Board, founder, investor and committee process.
Neutral Chairing, facilitation, evaluation, special review and recurring governance capability.
APPOINTMENT / ENTERPRISE NEUTRAL SYSTEM
Move from appointing a Neutral occasionally to knowing when independent capability belongs inside the enterprise.
An Enterprise Neutral System is the organisational architecture for using Neutral capability across recurring governance, commercial, project, workplace, transaction and cross-border situations. It defines use cases, role taxonomy, intake, appointment, panels or standing capability, conflicts, mandate templates, information controls, reporting, review and institutional learning. The system should make access easier without turning the enterprise into a hidden dispute-resolution institution or converting every problem into a Neutral process.
MATURITY PATH
Ad hoc.
Repeatable.
Governed.
Measured.
Embedded.
1
ONE-OFF APPOINTMENTS
2
STANDARD INTAKE + TOOLS
3
GOVERNANCE + ROLE TAXONOMY
4
DATA + REVIEW
5
INTEGRATED PROFESSIONAL SYSTEM
ENTERPRISE USE LAYERS
The enterprise should know where independent capability adds value before choosing a professional.
Supplier, customer, JV and alliance strain.
Evaluation, mediation and facilitation can clarify issues before formal dispute routes consume the relationship.
Long-duration project continuity.
Standing Neutral and Dispute Board systems can create independent capability before live project strain hardens.
Independent channels and sensitive process.
Ombuds or independent review can improve process while management, HR, governing bodies and formal investigators retain authority.
Valuation, earn-out and post-acquisition questions.
Expert Determination or Neutral Evaluation can give defined questions the appropriate independent function.
Relationships across markets.
Corridor and jurisdiction context can inform discovery without replacing governing law, local advice or matter-specific fit.
INDEPENDENT CAPABILITY SHOULD HAVE A HOME INSIDE THE ENTERPRISE
Somebody should own the system without owning the Neutral's professional judgement.
Legal, governance, risk, HR, procurement or another function may administer access, while each Neutral engagement preserves independent professional responsibility.
ENTERPRISE SYSTEM DESIGNER
Assess the current operating architecture and generate the next-stage design.
Defined Neutral role taxonomy
Can users distinguish evaluation, mediation, chairing, standing and determination?
Confidential requirement intake
Can the enterprise describe the need before naming a professional?
Appointment and conflict workflow
Are standing, profile evidence and clearance recorded?
Role-specific mandate library
Are authority and information boundaries standardised?
Governance and escalation
Who owns access, exceptions and systemic review?
Data and learning
Are use cases, outcomes and recurring questions reviewed safely?
ENTERPRISE DESIGN TESTS
A system can become efficient and still become professionally unsafe if its controls are wrong.
The enterprise creates a preferred Neutral panel and stops checking matter-specific fit.
A panel can reduce search friction but should not replace role, sector, jurisdiction, conflicts, availability and mandate assessment for each matter.
Procurement treats Neutral selection like ordinary vendor selection.
Commercial controls can remain relevant, but professional independence, conflicts, role competence and appointment terms require a distinct layer.
The system measures success only by settlement rate.
Different Neutral roles produce different outputs. Evaluation, chairing, Ombuds work and Standing Neutral use need outcome measures that fit the professional function.
The enterprise mines confidential engagements for internal learning without a governance rule.
Institutional learning should be anonymised and governed separately from the professional engagement, with privacy and confidentiality preserved.
ENTERPRISE SYSTEM MINIMUM
Six capabilities distinguish a repeatable system from a collection of one-off appointments.
INTAKE
Requirement first, procedure second.
ROLE
Consistent professional taxonomy.
DISCOVERY
Evidence-linked professional search.
APPOINTMENT
Standing, conflicts, availability and acceptance controls.
GOVERNANCE
Clear ownership without interference in Neutral judgement.
LEARNING
Safe review of systemic use and recurring questions.
PROFESSIONAL DISCOVERY
Current public professional records
Only currently published professional records are shown.
PUBLIC PROFESSIONAL RECORD / Nouakchott, Mauritania
Cheikhany Jules
Arbitrator & Mediator
mediationarbitrationBanking and Finance
Published record: Key Legal and Development Consulting Roles: Drafting of the Mauritanian Commercial Code – Ministry of Economic Development / World Bank (1999–2000) Legal Framework for Notaries – Ministry of Justice /…
PUBLIC PROFESSIONAL RECORD / Paris, France
Ana Gerdau de Borja
Arbitrator & Mediator
mediationarbitrationAviationBanking and FinanceEducation
Published record: Ana Gerdau de Borja Mercereau is a lawyer specializing in international arbitration, mediation and dispute boards. Admitted to the Brazilian Bar in 2006 and to the Portuguese Bar in 2008,…
PUBLIC PROFESSIONAL RECORD / Nairobi, Kenya
Philip Gicheru Gichaaga
Mediator
mediation
Published record: Philip Gichaaga is a certified neutral with a professional focus on mediation and conflict resolution.
PUBLIC PROFESSIONAL RECORD / Arizona City, United States
Charles Wang
Arbitrator & Mediator
mediationarbitrationBanking and Finance
Published record: Assistant Vice President for China Affairs; Professor of Practice, Director of China Law Program Professor Charles Wang is Assistant Vice President for China Affairs at the University of Arizona and…
ENTERPRISE SYSTEM ROUTES
Move from enterprise design into the component that needs to be built next.
ENTERPRISE
Independent capability becomes useful at scale when the operating system is clear.
USE CASE
Different organisational pressures should route into different Neutral functions.
GOVERN
The enterprise can govern access without governing the Neutral's professional judgement.
ENTERPRISE INFRASTRUCTURE
Build repeatable access to independent capability without turning Neutrals into ordinary vendors.
A repeatable appointment architecture is useful only if it clarifies internal administration without absorbing the professional function itself.
USE CASES
Where does independent capability add recurring value?
Boards, joint ventures, long projects, supplier relationships, sensitive channels and cross-border questions may each justify different enterprise routes.
OWNERSHIP
Who owns the system internally?
Legal, governance or another authorised function can own the architecture without owning the Neutral's professional judgement.
ACCESS
How do teams reach the right route?
The system should help users move from a real requirement into role matching, discovery, clearance and mandate design without defaulting to a generic preferred list.
MEASUREMENT
How will the enterprise know the system is healthy?
Quality measures should test speed, clarity, professional fit, boundary discipline and learning rather than only settlements or disputes avoided.
OPERATING MODEL
A durable system routes recurring pressure through defined roles and appointment controls.
The strongest appointment systems make role, authority, information and review points explicit before a live matter tests them.
OPERATING PATH
Build capability around repeatable decisions, not around a static panel.
An enterprise system becomes useful when it helps different teams make the same core appointment decisions consistently without flattening every matter into the same process.
01
Map recurring enterprise pressures
Identify the situations that repeatedly need independent capability and separate board, project, commercial, institutional and cross-border needs.
02
Create role-selection pathways
Translate each pressure into possible Neutral functions before professionals are compared.
03
Connect to the canonical professional record
Use published practice, sector, jurisdiction and corridor evidence rather than internal biographies or unverified lists.
04
Build staged conflicts and mandate controls
Make sensitive intake, clearance, authority and acceptance standard parts of the enterprise pathway.
05
Create programme governance and exceptions
Define system owner, case owner, approvals, data rules and when teams may depart from the normal route.
06
Review the system as professional infrastructure
Use aggregate learning to improve the architecture while preserving the independence and confidentiality of each engagement.
PROCUREMENT BOUNDARY
Standardise access, records and safeguards—not professional judgment.
The system should govern access, records and process while protecting professional independence and retained institutional authority.
THE SYSTEM CAN GOVERN
Repeatable capability across the organisation.
- Shared intake and role logic.
- Evidence-led discovery.
- Staged conflict clearance.
- Mandate and acceptance controls.
- Governance, records and safe learning.
THE SYSTEM MUST NOT CONTROL
Ordinary vendor procurement logic.
- Do not treat Neutrals as interchangeable vendors.
- Do not use a preferred panel as a substitute for fit.
- Do not measure quality only by settlement or management preference.
- Do not mine confidential engagements for unrestricted internal learning.
- Do not let enterprise efficiency erase matter-specific independence review.
PROFESSIONAL EVIDENCE
Use the public register as evidence infrastructure, not as an internal recommendation list.
The enterprise system should widen disciplined access to the profession, not create an institutional recommendation list.
ENTERPRISE SYSTEM PRINCIPLE