Task Disputes & Review Process
When a task's completion, proof or requirements are contested, Nothing.gripe uses the task's stated scope and submitted evidence as the basis for review. The exact outcome depends on the task record, evidence available and the current platform rules.
Review starts with what the requester actually required and what the task contract states.
Submitted proof is considered against the task's defined completion requirements.
Deadlines, claims, verification and other marketplace state changes are part of the task record.
Why disputes need an evidence trail
A task marketplace is easier to review when the expected result is defined before work begins. Nothing.gripe therefore encourages clear task descriptions, explicit proof requirements and stated timing. A disagreement can then be evaluated against a concrete record rather than an informal promise.
What can be reviewed
Depending on the task, relevant information can include the task description, proof submitted by the doer, timestamps, completion state, claim state and other records that the platform is permitted to use for review. Private credentials and sensitive data should not be published as proof.
How review works
A person at Nothing.gripe reviews each proof against the requirements the doer accepted when claiming. A decision is promised within 72 hours of the proof arriving, and the doer sees the exact deadline (in UTC) on the task. If it passes, the doer can escalate to a dispute and the owner is alerted. Nothing is paid automatically.
A proof that is sent back must say which criterion it fails and why, in words the doer can read. The doer then has 48 hours to fix it, up to three times. The requirements do not change during a fix, and time spent waiting for review is not counted against the doer. After three fixes, the next rejection becomes a dispute.
What is saved when a dispute opens
The task text, the requirements version the doer accepted, the funding record, every proof with its fingerprint, every review decision and the state of the ledger are copied into one record that cannot be edited. Both sides are told. A person decides within 5 days and writes the reason down: either the work stands and goes back to review, or the task is cancelled and its money becomes requester credit.
What a dispute does not mean
A dispute is not an automatic finding that either participant acted improperly. It is a review state used when the expected outcome, evidence, timing or other task condition requires resolution. The applicable rules and terms govern the process.
Before funding a task
Requesters should make the scope measurable and define what counts as completion. Doers should read the proof requirements before claiming. Both sides should use the task's official records rather than relying on screenshots or off-platform promises.
Related policies
See Proof & Verification for completion evidence, Rules for permitted and prohibited tasks, Refunds for cancellation-related treatment, and Terms for the platform's legal conditions.