Who maintains the architecture?
Owns role taxonomy, intake routes, approved tools, reporting rhythm and access policy without deciding professional merits.
ENTERPRISE GOVERNANCE
Own access.
Protect independence.
Control data.
Review exceptions.
Learn safely.
SYSTEM OWNER
INTERNAL
NEUTRAL JUDGEMENT
INDEPENDENT
APPOINTMENT
MATTER-SPECIFIC
INSTITUTIONAL LEARNING
SEPARATE
APPOINTMENT / ENTERPRISE NEUTRAL GOVERNANCE
Govern the system without governing the Neutral's professional judgement.
Enterprise Neutral Governance defines who owns access to Neutral capability, who may approve exceptions, how conflicts and panel use are controlled, what data the enterprise may keep, how confidential engagements are separated from organisational learning and how the system is reviewed over time. The governance layer should make appointment repeatable without converting internal legal, risk, HR or procurement teams into arbiters of the Neutral's independent professional conclusions.
GOVERNANCE RESPONSIBILITIES
The enterprise needs clear ownership around the Neutral system and clear limits inside the Neutral engagement.
Who manages each appointment?
Preserves requirement, evidence, conflicts, mandate, acceptance and record while respecting the Neutral's independence.
Who handles exceptions?
Material disclosures, objections and waiver questions should follow the actual governing framework rather than informal convenience.
What may the enterprise retain?
Appointment metadata, confidential merits, process notes, outputs and anonymised learning may require different access and retention rules.
How is quality assessed?
Review mandate compliance, responsiveness, process discipline and professional evidence without pressuring a Neutral toward preferred substantive outcomes.
What may return to enterprise policy?
Recurring use cases and anonymised process lessons can improve the system if confidentiality and professional boundaries remain intact.
ADMINISTRATION AND INDEPENDENCE NEED DIFFERENT OWNERSHIP
The enterprise can administer access, fees, records and system design. It should not control what an independent professional concludes inside a valid mandate.
That separation becomes more important as Neutral capability moves from occasional use into a repeatable organisational system.
GOVERNANCE DESIGNER
Assign ownership for the system while keeping the engagement independent.
Role taxonomy
Who approves recognised enterprise use cases and Neutral role definitions?
Conflict exception
Who decides whether an open disclosure requires consent, further review or replacement?
Confidential data access
Who may see appointment metadata versus substantive matter material?
Panel / shortlist policy
Who governs panel composition without forcing every matter to use the panel?
System review
Who reviews recurring use, exceptions and process learning?
GOVERNANCE FAILURE TESTS
Repeatability can create new risks that one-off appointments never had.
The enterprise panel becomes mandatory even when the matter needs a different professional.
Panels should reduce search friction, not override matter-specific fit, conflicts, jurisdiction, role or availability.
Procurement performance scores include whether the Neutral produced an outcome management liked.
Measure professionalism, process, mandate compliance and service quality without penalising independent judgement.
Confidential case notes are mined for institutional analytics.
Separate administrative metadata and properly governed anonymised learning from confidential merits or private communications.
The system owner approves role changes inside live matters.
Role change belongs to the mandate, parties, authorised body and professional conflict analysis, not merely to system administration.
ENTERPRISE GOVERNANCE MINIMUM
Six controls make the system governable without making the Neutral controllable.
OWNERSHIP
System administration has a named home.
INDEPENDENCE
Professional judgement has a non-interference rule.
EXCEPTIONS
Conflicts and policy exceptions have an authorised route.
DATA
Access and retention follow information type.
REVIEW
System performance is periodically assessed.
LEARNING
Anonymised institutional learning remains separately governed.
PROFESSIONAL DISCOVERY
Current public professional records
Only currently published professional records are shown.
PUBLIC PROFESSIONAL RECORD / Gujrat, India
Pradip Jain
Arbitrator & Mediator
mediationarbitrationConstructionEngineering and Infrastructure Disputes
Published record: Worked as General Manager (Engineering) & Superintending Engineer in Sardar Sarovar Narmada Nigam Ltd. for Resettlement of PAPS (Project Affected Persons) of Madhya Pradesh, Maharashtra and Gujarat as per Government…
PUBLIC PROFESSIONAL RECORD / Cologne, Germany
Dr. Oliver Heinrich
Arbitrator & Mediator
mediationarbitrationevaluationBanking and FinanceInformationCommunications and Technology
Published record: Prior to working as an attorney, Oliver was project manager for the European Satellite Navigation System Galileo at the German Aerospace Centre (Deutsches Zentrum für Luft- und Raumfahrt e.V.). As…
PUBLIC PROFESSIONAL RECORD / Arlington, United States
Joshua Erlich
Arbitrator & Mediator
mediationarbitrationrestorativeBanking and Finance
Published record: Mr. Erlich is primarily a litigator, where his emphasis is on constitutional, employment, and civil rights issues. His most common cases involve violations of Title VII of the Civil Rights…
PUBLIC PROFESSIONAL RECORD / Mexico City, Mexico
Eduardo Perez Motta
Arbitrator & Mediator
mediationarbitrationBanking and FinanceTechnology / IP
Published record: He was previously head of the Brussels office that led the negotiation of the FTA between Mexico and the European Union. He was Coordinator of Advisors to the Secretary of…
GOVERNANCE ROUTES
Use governance to connect enterprise design, appointment and live process.
OWN
The enterprise needs a home for the system, not an owner of the Neutral's judgement.
REVIEW
System learning should improve process without exposing confidential professional work.
SEPARATE
Administrative authority and independent professional authority should remain distinct.
GOVERNANCE ARCHITECTURE
Govern the infrastructure around Neutral work without governing professional judgment.
A repeatable appointment architecture is useful only if it clarifies internal administration without absorbing the professional function itself.
SYSTEM OWNER
Who maintains the enterprise architecture?
A named internal owner can maintain policy, access routes, records and review cycles without directing professional judgement inside live matters.
CASE OWNER
Who administers each appointment?
A matter-level owner can coordinate intake, conflicts, contracting and records while keeping substantive independence outside internal management.
EXCEPTIONS
Who decides when the standard route does not fit?
A governance committee or authorised body should handle exceptions transparently rather than allowing ad hoc overrides.
LEARNING
What can the enterprise safely learn?
Aggregate learning should come from process, volume and non-identifying patterns rather than mining confidential merits material or judging whether a Neutral pleased management.
EXCEPTION / REVIEW PATH
Make ownership, exceptions and review routes explicit before the difficult case arrives.
The strongest appointment systems make role, authority, information and review points explicit before a live matter tests them.
OPERATING PATH
Govern access, records and policy without governing the Neutral's conclusion.
Enterprise governance is strongest when internal administration is disciplined and professional independence is visibly protected.
01
Name the system owner and its limits
Define who maintains policy, templates, training and reporting while stating that live professional judgement remains independent.
02
Separate system ownership from case ownership
The person governing the programme should not automatically control information, scope or outcome in every live appointment.
03
Create an exceptions route
Non-standard appointments, unusual roles, new conflict issues and sensitive matters should have a visible escalation path.
04
Control enterprise data retention
Keep appointment metadata and governance records proportionate while preventing uncontrolled retention or analytics on confidential case material.
05
Measure process quality rather than preferred outcomes
Review timeliness, usability, role clarity, conflicts discipline and stakeholder experience rather than settlement rate or management agreement.
06
Feed safe learning back into policy
Use de-identified patterns, recurring process friction and control failures to improve the system without compromising individual engagements.
INDEPENDENCE BOUNDARY
Administration can be standardised; independence cannot be centrally controlled.
The system should govern access, records and process while protecting professional independence and retained institutional authority.
THE SYSTEM CAN GOVERN
Administration, access and institutional learning.
- System ownership and governance review.
- Appointment routing and record control.
- Exception handling.
- Role-based access and retention rules.
- Aggregate process learning under clear safeguards.
THE SYSTEM MUST NOT CONTROL
Professional judgement and live mandate independence.
- Do not score Neutrals by whether management liked the outcome.
- Do not let procurement override matter-specific professional fit.
- Do not mine confidential case material for analytics without authority.
- Do not allow system owners to alter live mandates unilaterally.
- Do not turn preferred panels into mandatory appointment pools.
PROFESSIONAL DISCOVERY
Enterprise governance should widen access to verified evidence, not create a favoured list.
Enterprise governance can manage access and process. It should never turn directory placement or panel inclusion into automatic appointment.
ENTERPRISE GOVERNANCE PRINCIPLE