Dispute Resolution
En resumen
Dispute Resolution gives the petanque ecosystem a single, fair, well-documented path for handling conflicts — between clubs, between players and federations, between national bodies, or up the chain to FIPJP — with structured submissions, neutral mediation, reasoned decisions, transparent appeals and a searchable precedent database. The subsystem keeps every party informed, every deadline visible, and every ruling defensible long after the case is closed.
Cómo funciona
Anyone with standing can open a formal dispute. The submission form asks for parties involved, the relevant facts, supporting documents, and a classification: financial, sporting, administrative or conduct-related. The classification drives the routing rules — a sporting dispute about a refereeing decision goes one way, a financial dispute about licence fees goes another.
The escalation pathway is configured per tenant but follows a familiar shape: club first, then region or district, then national federation, then the continental body, and finally FIPJP for cases that cross borders or set new precedent. At each level the dispute is owned by a named handler with clear deadlines for acknowledgement, response and decision. Parties can see exactly where their case sits and what happens next.
Mediation is the default first attempt before formal adjudication. The system assigns a neutral mediator, opens a private workspace for the parties, sets a timeline, and records whether mediation succeeded, partially succeeded or failed. If mediation fails, the case is moved to the appropriate decision body. Decisions are documented with full rationale, citing the rules applied and the evidence weighed, and published — redacted where necessary — to the precedent database, which is searchable by classification, level and outcome.
Appeals are a first-class concept. Each decision lists the appeal window, the appeal body, and the grounds on which an appeal can be lodged. The same audit trail captures every step from initial submission to final decision, so a dispute decided at FIPJP level can be reconstructed years later in detail.
Capacidades clave
- Formal dispute submission for any party combination with structured classification
- Configurable escalation pathway from club to FIPJP with per-level handlers and deadlines
- Mediation workflow with assigned mediator and tracked outcome
- Decision documentation with rationale and rules cited
- Searchable precedent database, redacted where needed
- Defined appeal process with windows, bodies and grounds
- Full audit trail from submission to final decision
En la práctica
Two clubs disagree over the eligibility of a transferred player at a regional final. The losing club opens a dispute, classifies it as sporting, attaches the licence document and match sheet, and submits. The regional handler acknowledges within 48 hours and proposes mediation; both clubs accept and a neutral mediator from a different region opens a shared workspace.
Mediation reaches a partial agreement on procedure but not on the result. The case escalates to the national disputes panel, which issues a documented decision citing two prior precedent cases pulled directly from the database. The losing club lodges an appeal within the published window; the appeal is scheduled, the parties prepare, and the audit trail follows the case all the way through.
Funcionalidades de este subsistema
8| ID | Status | Funcionalidades |
|---|---|---|
| F17.04.01 | Entregado | Formal dispute submission (club vs club, player vs federation, etc.) ✅ PL-F1704a |
| F17.04.02 | Entregado | Dispute classification (financial, sporting, administrative, conduct) ✅ PL-F1704a |
| F17.04.03 | Entregado | Escalation pathway (club > region > national > continental > FIPJP) ✅ PL-F1704a |
| F17.04.04 | Entregado | Mediation workflow (assigned mediator, timeline, resolution) ✅ PL-F1704a |
| F17.04.05 | Entregado | Decision documentation with rationale ✅ PL-F1704b |
| F17.04.06 | Entregado | Precedent case database (searchable by type) ✅ PL-F1704b |
| F17.04.07 | Entregado | Appeal process with defined timelines ✅ PL-F1704b |
| F17.04.08 | Entregado | Full audit trail on dispute proceedings ✅ PL-F1704b |
Partes interesadas que necesitan este subsistema
Aparece en 6 análisis de partes interesadas