> For the complete documentation index, see [llms.txt](https://novacont.gitbook.io/nova-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://novacont.gitbook.io/nova-docs/novacont-lite/dispute-resolution.md).

# Dispute Resolution

Disputes in NovaCont Lite are not routed to NovaJury. They are reviewed manually by the NovaCont admin and support team. This means the process is currently centralized. As the user base grows, a NovaJury-style decentralized model may be considered but this is a possibility, not a commitment.

### How the Process Works

{% stepper %}
{% step %}

### Raise the Dispute

The client or provider taps **Open Dispute Chat** while the contract is in the "Accepted" or "Delivered" state. This sends a "RaiseDispute" message on-chain and moves the contract into the "Disputed" state.
{% endstep %}

{% step %}

### Contact the Support Team

The user shares the details of the dispute through the support team's account.
{% endstep %}

{% step %}

### Admin Review

An authorized reviewer examines the evidence provided and decides how the funds should be split between the client and the provider (clientShareBps).
{% endstep %}

{% step %}

### Decision & Reasoning

The reviewer records their decision on-chain via a "ResolveDispute" message, together with a **reason**. This reason is queryable by anyone from the contract data — every decision is documented transparently.
{% endstep %}
{% endstepper %}

> Disputes typically receive a response within 1–4 business days, depending on volume.