Skip to content

Raising and following a creator dispute

What the Dispute Centre shows, which grounds each party may raise, why performance is not one of them, and why the content of dispute evidence is never displayed.

Updated

The Dispute Centre lists what is contested on a booking, how much that currently pauses, and what has been determined. A dispute pauses only the amount it names, and only while its state freezes that amount. A resolved dispute still records what was contested, so the contested figure and the paused figure are shown side by side and never as one number.

The content of dispute evidence is not shown here. Every piece is recorded as private; the page lists only its kind, the party that submitted it and the time. Nothing on this screen can be quoted into a public profile or a review.

BEFORE YOU START

  • The "view" permission for a workspace with a booking in it. Determining a dispute additionally needs "administer".
  • A settlement booking. A dispute is raised against a booking and, where relevant, one specific deliverable on it.
  • A ground your party is entitled to raise. A business cannot raise a ground that only a creator may raise, and the reverse.

STEPS

  1. Open the Dispute Centre from the sidebar, under Engage.
  2. Read the table. Each dispute shows its ground, its state, the amount contested and the amount paused right now.
  3. Open a dispute's detail card for the claim, the direct-resolution deadline and the determination.
  4. Read the evidence table on that card. It lists what was submitted and by whom, never the material itself.
  5. Read the review-eligibility line. It says what kind of review, if any, the engagement can produce.
  6. Check the grounds table at the foot of the page before raising a dispute, to see which party may raise each ground and which contest money by default.

WHAT YOU SHOULD SEE

Contested and paused as two separate columns. On an open dispute they will usually match; on a resolved one the paused figure falls to zero while the contested figure stays, because the record of what was claimed does not disappear when the claim is settled.

Every evidence row marked private. A row that is not marked private is a defect and is shown in red rather than hidden, so somebody can act on it.

WHAT THIS WILL NOT DO

  • It will not accept poor performance as a ground. A creator guarantees the contracted work and its publication, not the behaviour of a platform algorithm. Low views, low reach and low sales become disputable only where the creator made a false claim, failed an express contractual requirement, expressly guaranteed that outcome, or manipulation is proven. Each of those has its own ground.
  • It will not show you the content of any piece of evidence, including your own organisation's.
  • It will not move money. A determination records an outcome; a payment, refund or reversal is recorded separately against the settlement.
  • It will not let a dispute freeze more than the booking's outstanding amount, and it will not produce a negative.
  • It will not offer a ground to a party who may not raise it.

IF IT DOES NOT WORK

  • "No dispute raised" records the absence of a complaint, not the absence of a problem.
  • A determination that is refused for exceeding the contested amount is working correctly: what is awarded to the creator and what is refunded to the business together cannot exceed what was contested.
  • A dispute that shows as no longer paused after an appeal has not lost its freeze. An appeal re-freezes the contested amount, and the state chip will read "appealed".
  • A dispute against a booking whose money has already released will contest only what remains. A release and a dispute cannot both succeed against the same amount.

COMMON QUESTIONS

Can I see the evidence somebody submitted?

Not here. Every piece is recorded as private and this page lists only its kind, the party and the time, so that nothing on it can be quoted into a public profile or a review.

Why can I not raise a dispute because a post underperformed?

Because a creator guarantees the contracted work and its publication, not the behaviour of a platform algorithm. Where a false claim, a missed contractual requirement, an express guarantee or manipulation is involved, each has its own ground.

  • Reading a creator settlement

    The business ledger and the creator ledger, what "released" actually records on this build, and why a dispute pauses only the amount it names.

  • Reading delivery evidence

    What the evidence record for a published deliverable holds, how the acceptance verdict is derived, and why no post on this build has ever been confirmed as still live.

  • Checking what is proved about a creator

    Reading the ten separate verification dimensions, why there is no single verified badge, and why an ownership challenge cannot be checked on any platform on this build.