> ## Documentation Index
> Fetch the complete documentation index at: https://docs.fundwork.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Resolving Disputes on Fundwork | Trust & Safety Guide

> Learn what to do if a dispute arises on Fundwork — how to document your case, protect your records, and get support when an engagement goes wrong.

Even with clear agreements and good-faith effort on both sides, disputes occasionally arise. A client may feel that deliverables don't meet the agreed criteria; a worker may find that an approved payment is being withheld. Knowing what to do — and what to document — before things escalate puts you in the strongest possible position.

<Note>
  Fundwork is currently in **alpha**. A formal dispute resolution process is under development. Specific timelines, escalation paths, and resolution procedures will be published before public launch. During alpha, contact Fundwork support directly if you need assistance with a dispute.
</Note>

## Common Dispute Scenarios

<CardGroup cols={2}>
  <Card title="Client refuses to pay for approved work" icon="circle-dollar-to-slot">
    A worker has delivered work that meets the agreed criteria, but the client is withholding payment or has gone silent.
  </Card>

  <Card title="Worker doesn't deliver" icon="clock">
    A client has released a milestone payment or is waiting on deliverables, but the worker has missed deadlines or stopped responding.
  </Card>

  <Card title="Scope disagreement" icon="arrows-left-right">
    Both parties have different understandings of what was agreed — usually because the original brief was ambiguous or scope changed without written confirmation.
  </Card>

  <Card title="Quality dispute" icon="star-half-stroke">
    Work was delivered on time, but the client believes it doesn't meet the quality or specifications agreed upon.
  </Card>
</CardGroup>

## What to Do When a Dispute Arises

Follow these steps to protect your position and give support the clearest possible picture of what happened.

<Steps>
  <Step title="Document your communications">
    Gather all messages, notes, and confirmations related to the engagement. If you've communicated inside Fundwork's messaging system, that record is already timestamped and accessible. Export or screenshot anything you may need to reference.
  </Step>

  <Step title="Collect your deliverable records">
    Keep copies of all files, links, commits, designs, or other work products you submitted or received. On-chain payment receipts generated by Fundwork are immutable records — note the transaction details for any payments already made.
  </Step>

  <Step title="Attempt direct resolution first">
    Before escalating, try to resolve the issue directly with the other party. Clearly and calmly describe your position, reference the original agreed deliverables, and propose a specific resolution. Many disputes stem from miscommunication and can be resolved quickly when both parties engage in good faith.
  </Step>

  <Step title="Contact Fundwork support">
    If direct resolution fails, contact Fundwork support. Provide your documentation: the relevant **.base.eth names**, a timeline of the engagement, the on-chain payment receipt details (if applicable), and a clear description of the disagreement and your proposed resolution.
  </Step>
</Steps>

## How to Protect Yourself Before a Dispute Happens

The best dispute is one that never starts. Put these habits in place from the beginning of every engagement.

<Tip>
  Define deliverables, acceptance criteria, and revision limits in writing before work begins. Agree on them explicitly — don't assume.
</Tip>

<Tip>
  Use milestones on any engagement larger than a single small task. Releasing payment incrementally limits risk for both parties and creates natural checkpoints to surface disagreements early.
</Tip>

<Tip>
  Confirm all scope changes in writing and get acknowledgement from the other party before any additional work is performed.
</Tip>

<Tip>
  Keep all substantive project communication inside Fundwork's platform so that a complete, timestamped record exists if it's ever needed.
</Tip>

<Warning>
  Never move payments or work off-platform. Off-platform transactions fall entirely outside Fundwork's oversight. If a dispute arises from an off-platform arrangement, Fundwork support cannot assist you.
</Warning>