How to Handle a Dispute With a Freelancer

Almost every freelance dispute has the same shape. Something small goes slightly wrong. Nobody mentions it, because mentioning it feels awkward and disproportionate. It happens again. By the time anyone raises it, both parties are annoyed, both have a story in which they are the reasonable one, and the conversation that would have taken two minutes in week one takes two weeks in month two.

The single most effective thing you can do about disputes is to have the awkward conversation early, when it is still cheap and still about the work rather than about the relationship. Everything else in this guide is what to do when that has not worked.

Catch it early: the warning signs

Projects rarely fail suddenly. They drift, and the drift is visible if you know what to watch for.

Communication slows before delivery does. Replies that used to come the same day start taking three. This is the earliest and most reliable signal, and it usually means the freelancer is behind and does not yet want to say so.

Updates get vaguer. “Making good progress” replaces “the homepage is built, working on the contact form”. Specific updates are cheap to give when work is happening.

The first deliverable arrives late and thin. A first draft that is noticeably less finished than you expected is worth addressing immediately, not politely absorbing.

Scope conversations start appearing. Unprompted mentions that something “was not really included” often precede a request for more money, or a delivery that omits it.

Seeing one of these is not a reason to panic or to escalate. It is a reason to ask a direct, friendly, specific question — “how are we doing against Thursday?” — while the answer can still change the outcome.

Work out which problem you actually have

Before you do anything, be precise with yourself about what has gone wrong, because these problems need genuinely different responses and conflating them is how people end up in unwinnable positions.

• Non-deliveryNothing arrived, or the freelancer has gone quiet. The most clear-cut case, and the strongest position to be in.
• QualityWork arrived but is not good enough. The hardest to argue, because “good enough” is subjective unless the brief made it objective.
• Scope disagreementSomething you expected is missing. Turns entirely on what the brief and listing actually said — not on what each of you assumed.
• LatenessThe work is coming but not on time. Ask whether the delay causes you real harm before deciding how hard to push.
• CommunicationThe work may be fine but the process is not. Often fixable with one direct conversation about cadence.

Be honest about the quality case in particular. If you did not specify what “good” meant, and what you received is a competent execution of what you asked for, you have a preference problem rather than a delivery problem. That is still worth discussing — many freelancers will happily revise — but it is a weaker position than a missed deliverable, and going in as though it were the stronger one tends to make people defensive.

Also check whether you are actually within the agreed revision rounds. A great many “disputes” are simply a revision request that was framed as a complaint.

Get your evidence in order first

Spend fifteen minutes on this before you write anything. It changes both the tone of your message and, if it goes further, the outcome.

What you want is a short, factual chronology: what was ordered, what was agreed, what was promised and when, what actually arrived and when, and precisely which agreed item is missing or wrong. Pull the specifics out of the order, the listing description, your requirements submission and the message thread — not from memory.

Two things people consistently get wrong here. First, they gather evidence of annoyance rather than evidence of breach: fifteen screenshots of slow replies matter far less than one line from the listing that says a deliverable was included. Second, they leave it too late — if any of the discussion has happened outside the platform, bring the substance back into the platform thread now, in writing, while it is still uncontested.

Keep files, drafts and delivered assets exactly as received. If a formal dispute is opened on Zinn Hub, both parties can attach evidence to it — up to ten files per dispute, up to 25 MB each — and having the originals to hand makes that straightforward.

Raise it directly, and raise it well

This is the step that resolves most problems, and it is the step people most often skip in favour of escalating, which almost always makes things slower rather than faster.

A good first message does four things and nothing else:

• States the specific gap. “The brief listed five page templates and three were delivered” — not “I am disappointed with this”.
• Quotes the source. The listing, the brief, the requirements you submitted, or the message where it was agreed.
• Names the outcome you want. The two missing templates delivered, a revision, a partial refund, or a cancellation. Be concrete.
• Gives a reasonable window. A date by which you would like a reply or a fix.

Keep it unemotional and keep it on the platform. Nothing weakens a strong case faster than an angry message, because it shifts the conversation from what was delivered to how everyone behaved. And a freelancer who feels attacked will defend rather than fix, even when they were going to fix it anyway.

Give a genuine chance to respond. Freelancers get ill, lose internet access and have emergencies like anyone else, and a proportion of “they have vanished” cases turn out to be a few days of silence with a reasonable explanation behind them.

Negotiating an outcome that sticks

If the direct message produces a conversation rather than a fix, you are negotiating. It helps to know what the realistic outcomes are before you start, because asking for something that was never going to happen wastes the goodwill you need.

In rough order of how easily they are agreed: a revision or correction; a deadline extension with something in return; a partial refund proportionate to what was not delivered; completion of part of the work with a partial refund for the rest; a full refund and cancellation.

The proportionate partial is the outcome that resolves most genuine disagreements, and it is worth understanding why. If four fifths of the work is delivered and usable, a demand for a full refund reads as an attempt to get four fifths of a job for nothing, and the freelancer will dig in. A request for a fifth back is hard to argue with and usually accepted quickly. Ask for what is fair rather than for the maximum, and you will get an answer faster.

Whatever you agree, write it down in the platform thread in one message: what will be delivered, by when, and what happens to the money. Verbal or scattered agreements are the reason the same dispute gets had twice.

Cancelling an order on Zinn Hub

If a direct conversation has not worked, the next step on Zinn Hub is a cancellation request. It is deliberately a negotiation rather than a decision: either party can open one, and it is opened for a percentage of the order value, so a partial outcome is available from the start.

Once a request is open, the other party has 72 hours to do one of four things: accept it, counter-offer a different percentage, decline it, or escalate the matter to a formal dispute. If they do nothing at all within that window, the cancellation is automatically granted at the requested percentage — so silence does not work as a defence.

Counter-offers are capped at three rounds. That is a deliberate design choice: it stops a cancellation becoming an indefinite haggle, and once the rounds are exhausted the route forward is escalation to a dispute rather than another counter.

Both parties are notified at each step, and everything is visible on your resolutions page in the dashboard. This stage settles a large share of cases, because a specific percentage is a much easier thing to agree on than an abstract argument about whether a job was done properly.

Raising a formal dispute

A dispute is the escalation route. It can be opened directly by either party on an order, or reached by escalating a cancellation that has not settled.

You open it by selecting a reason and writing a description of the problem. The reason categories are Quality issue, Non-delivery, Payment issue, Communication breakdown, Scope disagreement and Other. Choose the one that genuinely fits — the category shapes how the case is reviewed, and a scope disagreement filed as non-delivery reads badly once the delivered work is examined.

From there the case moves through defined states while it is worked: open, awaiting response, awaiting evidence, investigating, under review, awaiting an admin ruling, and finally resolved, dismissed or closed. You can see the current state at any time. Both parties can post messages to a dispute thread and attach evidence files, so the case builds a single record rather than living in two inboxes.

There is also a route that closes cases quickly and without a ruling: a Zinner can self-resolve a dispute by issuing a full refund. It happens more often than people expect, particularly where the freelancer accepts something went wrong and would rather resolve it than argue.

If it does need a ruling, a Zinn Hub administrator reviews the evidence from both sides and decides. Take that seriously when you write your case: the reviewer was not there, and what they can see is the order, the brief, the delivered work and the thread. A clear chronology with the relevant lines quoted is worth far more than volume.

What the outcomes look like

A ruling is not binary. The resolution categories cover the realistic range, which is worth knowing before you decide how to frame your case.

• Vendor at faultFull or partial refund to the buyer, depending on how much of the agreed work was not delivered.
• Buyer at faultNo refund, with the payment released to the Zinner — or a partial refund where the position is mixed.
• Mutual, no faultA full refund, a partial refund, or no refund with the project treated as completed.
• DismissedThe dispute is found to be invalid.
• Self-resolvedThe Zinner issued a full refund before a ruling was needed.

Notice how many of those are partial. That is the reality of most disputes: both parties usually contributed something to the situation, and outcomes reflect it. Going in expecting a total victory is the most common cause of disappointment with a process that was actually working properly.

Where the money goes

This is the detail buyers most often want confirmed up front, so it is worth stating plainly.

Refunds on Zinn Hub are credited to your Zinn Wallet, in full, in USD. There is no refund-to-card flow, and there is no facility to return money to the original payment method. Wallet credit can be spent on the platform — on the same job with a different Zinner, or on anything else — and it holds its value in USD, which is the only currency anything is charged in.

It is also worth understanding what protection you have while an order is open, because it depends on how your Zinner takes payment. Choose a Platform Protected Zinner and your payment is held by Zinn Hub until the order completes — and that hold covers the whole order as a single amount, not a series of stages. Zinn Hub does not operate milestone or staged payments, so you should not plan a project around releasing money in instalments. Where a Zinner is instead connected to their own payment account, you pay them directly at checkout, which is faster for them and a different risk profile for you. You can narrow the Zinners directory by payment mode, and it is worth asking which one applies before you order anything substantial.

The refund policy sets out the full position, and our terms and conditions govern the rest.

Why a chargeback is the worst first move

When people feel ignored, the instinct is to go around the platform and ask their card issuer to reverse the payment. It feels decisive. It is almost always the worst available option, for four reasons.

It is slower. A card dispute is a formal process between institutions, measured in weeks or months. A platform cancellation has a 72-hour clock on it.

It removes your best evidence. The platform holds the order, the brief, the delivered files and the full message thread. A card issuer sees a payment and two assertions, and will typically decide on documentation neither party controls.

It ends the negotiation. The moment a chargeback lands, the freelancer stops trying to resolve anything and starts defending themselves. Any chance of the work being finished is gone.

It can put your own account at risk. Going outside the platform’s resolution process, rather than using it, is not a neutral act on any marketplace.

Use the internal route first. It exists precisely for this, it is faster, and it is the only route where “the work gets finished properly” is still one of the possible outcomes.

Making the next hire dispute-proof

Almost every dispute traces back to a decision made before the order was placed. The three that matter most:

Write a brief that can be checked. A deliverable list with numbers and formats turns “is this good enough?” into “is this what we agreed?” — a far easier question for everyone, including a reviewer. Our guide on writing a project brief covers how.

Read the proposal properly. The warning signs are usually visible before you spend anything. Our guide on red flags in a freelancer proposal covers what to look for, and how to vet a freelancer covers the checks after that.

Test before you commit. A Micro Zinn at $5, $10, $15 or $20 tells you how someone communicates and delivers before a four-figure decision does. It is the cheapest dispute-avoidance measure available, and our guide on testing a freelancer before you commit explains how to run one properly.

And keep the relationship on the platform. Every protection described in this guide depends on there being an order and a record. Move the conversation or the payment elsewhere and none of it applies — there is nothing to cancel, nothing to dispute and nothing to refund.