Introduction to Disputes
After you submit your coding for a task, a QA analyst reviews your work. If the QA analyst identifies an error, they will edit the code and send it back to you for review.
As the data entry analyst, you will receive a notification that a code has been changed. You can then review the QA analyst's edit and either agree with the change or disagree with it.
If you disagree, this creates a dispute. The original QA analyst can then review your reasoning and either accept your original coding or maintain their correction.
Your final payment for the task is determined by the final agreed-upon coding after the dispute process is resolved.
How to Complete Dispute Tasks
You will be sent the Quality Control Report of your Data Entry Task
Review the mistakes found in your work.
When you spot a correctly identified mistake: learn from your error and ensure you never make it again
4. When you spot an incorrectly identified mistake:
Describe in detail why your original labeling was correct and the error listed in the report is wrong
Change back to your original label in the game's data entry screen.
5. When done, upload the completed report. If there are no incorrectly identified mistakes, please still fill in the report and leave the second sheet blank.
Important to Remember
Q: Are there any mistakes I should ignore?
A: Yes, the following do not count as mistakes as they don't affect the accuracy of the system:
Duration -- Start/end times should only be changed if there is a discrepancy of more than 10 seconds.
Except rucks, which should be accurate to within 1 second
Kick meters -- Only change if there is an error of more than 15 meters
Ensure you change the label within the coding window as well as note down the change in your spreadsheet - it will not count if you don't do both
Do not change any colors or font on the spreadsheet - send it back in the same format as the 'example texts'
Q: What should I do if I disagree with a QA correction?
A: Review the QA analyst's change carefully. If you believe your original coding was correct, select "Disagree" and the dispute will be reviewed. Make sure you are confident in your reasoning before raising a dispute.
Q: How long does a dispute take to resolve?
a: Disputes are typically resolved within 1–2 days depending on workload. Your payment for the affected task will be finalised once the dispute is settled.
Q: Can I dispute multiple codes on the same task?
A: Yes. Each code change from QA can be individually agreed with or disputed.