BountyShift

Disputes

When you dispute a rejected report, the run record opens identically to both sides. The decision rests on what it shows.

How it opens

The dispute button beside the rejected report is all it takes. You do not upload anything extra; you mark the case you disagree on and the record says the rest. The job stops occupying a slot the moment a dispute opens.

  • Window: seven days from the rejection notice
  • Settled within three working days
  • You keep taking new work while it runs
  • The number of disputes is not recorded against you — only their outcomes

What the decision looks at

Was the case run

Does the record hold a start and end stamp, and was it run in the environment the job asked for.

Is the evidence enough

Is there a screenshot, a log and a reproduction step for the bug reported.

Does the reason hold

Does the company's stated reason match what the record shows.

What the outcome does

If the dispute goes your way the fee is released, your acceptance rate is untouched and the rejection comes off your record. If it does not, the reasoning goes on your record — one case does not drop your level, a pattern does. Where one company keeps rejecting on the same unfounded ground, we track it and it becomes a warning on their side.

See what the record holds

Knowing what a dispute rests on makes it easier to get the job right first time.

What BountyShift is

BountyShift is a marketplace for software testing work. Companies send their new builds here to be tested, and the work is done entirely remotely — from home, on your own computer or phone. There are five kinds of job: website, mobile app, desktop software, embedded device and game testing. Every job's fee is known before you take it and is fixed; it does not change with how many faults you find, and a job where you find nothing is still paid. Payments run weekly, and no commission is taken from testers.