When a worker submits a microtask result, the client has one main job: check whether the worker completed the conditions that were visible before the work started.
You do not need to look for a reason to reject a submission, but you should not accept everything without checking it either.
Start with the original instructions
Open the task instructions and proof requirements first, then review the worker's submission.
This keeps the decision based on what the worker was actually asked to do.
Check the required action
Compare the report with each required step: the target page, requested action, assigned data, screenshot, link, file, or written proof.
Do not add new requirements during review
If the task did not ask for a device model, a second screenshot, or an extra comment, the worker should not be rejected for not providing it.
Review the result against the published requirements.
Check the proof
The worker may submit text, a link, a file, or a screenshot depending on the task. Make sure the proof actually confirms the requested result.
If a unique text was assigned
Check whether the worker used the value assigned by the system, especially for codes, links, test data, and other individual values.
See Unique Texts in Microtasks.
When should you accept a result?
If all required steps are complete, the proof is valid, and the result matches the instructions, accept it.
After acceptance, the worker receives payment for the completed microtask.
What if there is a small fixable issue?
If the work is basically correct but one item is missing, a correction is often more appropriate than an immediate rejection.
Be specific. For example: “Please add a screenshot of the final screen showing that the form was submitted successfully.”
When is rejection reasonable?
- A different action was completed.
- The proof does not confirm the result.
- The wrong data was used.
- A required step was skipped.
- The submitted proof clearly belongs to another task.
Give a clear rejection reason
Do not write only “wrong” or “not accepted.” Explain what requirement was not met.
A useful reason is: “The task required a screenshot after successful registration. The attached image only shows the form before submission.”
Review results within the available review period
Microtasks have a review period, so it is better not to leave submitted work waiting without a decision for too long.
Use the same criteria for every worker
For a high-volume task, define a short checklist:
- The required action is complete.
- The proof confirms it.
- The correct assigned data was used.
- The report is complete.
Do not compare workers with each other
Compare each submission with the task requirements, not with the most detailed report another worker happened to send.
If many workers make the same mistake
Review your instructions. If several unrelated people misunderstand the same step, that step may need clearer wording.
Three questions before accepting
- Was the required action completed?
- Is there proof that confirms it?
- Am I asking for anything that was not in the original instructions?
Useful guides
For clearer task setup, see How to Create a Microtask on DitWork.
If you need more of the same results, see How to Add More Completions to an Active Microtask.
The main point
Accept work when it meets the requirements that were visible before the worker started. If an issue can be corrected, explain exactly what is missing. If the work does not meet the task, give a specific rejection reason.
Browse tasks in the microtasks section.
