Dispute policy

A recorded process for unresolved testing disagreements.

Effective July 22, 2026

The process protects both sides by comparing the published job, assignment, submission history, and communication—not by relying on an unverified summary.

Issues covered

Before opening a dispute

When safe and practical, explain the issue in the assignment conversation and propose a specific resolution. A client should use a revision request for correctable omissions. A tester should respond with the relevant submission version and requirement.

Opening and responding

  1. Open the dispute from the relevant job, assignment, or submission and choose the closest dispute type.
  2. State the requested resolution and identify the exact requirement, evidence, message, deadline, or ledger event involved.
  3. The other party may respond and attach relevant evidence. Do not include unrelated personal data or duplicate confidential files.
  4. Continue to preserve the record. Deleting a message or local file does not guarantee removal of evidence already retained for the case.

Review

A moderator or administrator may request clarification, limit new transitions while the case is open, and compare the evidence with the requirements in effect when the assignment was accepted. Reviewers should disclose conflicts and must not resolve their own dispute.

Possible outcomes

Appeals

An appeal must identify a material factual error, process error, or evidence that could not reasonably have been supplied earlier. Repeating the original position without new grounds does not require a new outcome.

For duplicate or undelivered purchase payments, use the refund process. For threats, fraud, or out-of-scope system access, also follow the safety guidance.