# Conflict resolution

Lemon.io treats developers and clients as equal partners. If something goes wrong on a project, the Client & Developer Experience team steps in to resolve the issue fairly.

Common situations and how they are handled:

* **Communication issues** — if a client flags a communication concern, Lemon.io reaches out to both sides, identifies what is actually happening, and mediates. Many “communication issues” turn out to be scope confusion or missing context.
* **Technical disputes** — neutral third-party technical consultants from the Lemon.io community can be brought in to objectively assess the work.
* **Client ends the engagement early** — if a client ends an engagement before completion, hours already worked are paid in full. 
* **A client has requested a replacement** — Lemon.io then investigates what happened. If the issue was on the client’s side (unclear requirements, lack of access, changing scope), this is documented and used to improve the next match for both parties.

**Guaranteed payment is a core promise to developers.** Lemon.io does not allow clients to withhold or delay payment due to dissatisfaction. All disputes go through the Client & Developer Experience team, not directly between you and the client.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.lemon.io/for-developers/conflict-resolution.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.