Full payment
If the recording meets the current standard, the reviewer can approve it at the full eligible amount.
Contributor update · August 3, 2026
We are gradually opening a one-time re-review option for eligible older rejected recordings. A human listens again and can approve full payment, award partial payment when part of the recording is useful, or keep the rejection with a specific reason.
The rollout
We are releasing re-review gradually—not all at once. That lets us watch the size and speed of the human queue, check decision quality, and expand without slowing down ordinary recording reviews.
Account selection is stable and automatic. Increasing the rollout adds more accounts; it does not repeatedly move people in and out. If you are not included yet, there is nothing you need to do to join.
Where to look: open Earnings and find your recordings. The button appears directly on a recording after it has been checked and found eligible.
What happens
Open Earnings and look at your older rejected recordings. If re-review is available for your account and that recording is eligible, you will see a Request re-review button.
The recording moves into a dedicated queue. You do not need to upload it again, contact support, or repeat the automated audio check.
A human reviewer listens to the stored recording and applies the current policy. Earlier automated checks may provide context, but they do not replace this listening review.
The result and its reason appear with the recording in Earnings. We will also notify you when the re-review is complete.
Possible outcomes
The goal is a fairer decision: recognize usable work when it is there, while keeping unusable recordings out of paid datasets.
If the recording meets the current standard, the reviewer can approve it at the full eligible amount.
If a meaningful part is usable, the reviewer can approve a percentage of the standard payment instead of rejecting all of the work.
If the recording is not usable under the current policy, the rejection stays in place and the reviewer provides a specific reason.
Eligible requests go to a reviewer who listens. An old score or missing analysis does not become the new decision.
A reviewer can recognize meaningful usable work without having to choose only between full payment and zero.
The first decision and its reason remain in the audit history while the new outcome is recorded separately.
The review uses the recording already stored securely with your submission.
The program is being released to accounts in stages so we can keep the human queue moving and monitor decisions carefully. Being outside the current stage does not say anything about your account or your recordings. Accounts with more than 100 historical candidates currently see re-review availability on their newest 100; Earnings shows a notice when that limit applies. You do not need to contact support; check Earnings as availability expands.
No. The program covers eligible historical rejections, not every rejected recording. A button will not appear when a recording is outside the historical program or has narrow, conclusive evidence such as being an exact duplicate. The eligibility check is intentionally designed to send uncertain cases to a person rather than exclude them automatically.
No. Existing automated checks are supporting context for the reviewer. We do not require an automated QA rerun before an eligible request can enter the human queue, and a human listens before the second decision is made.
No. A request guarantees a new human listening review, not a particular result. The second decision can be full payment, partial payment, or an unchanged rejection.
No. Each recording has one re-review lifecycle. This keeps the decision history clear and lets the queue serve more contributors fairly.
We are not promising a fixed turnaround time while the program is expanding. Requests stay in the dedicated queue until a reviewer completes them, and your recording's status remains visible in Earnings.