If you completed a microtask, submitted your proof, and the client did not accept it, do not start with an argument. Start by checking exactly what happened.
Sometimes the problem is simple: the wrong screenshot, a skipped step, an incorrect link, or a requirement that was missed. Sometimes the rejection reason does not match the original instructions.
Read the rejection reason first
DitWork stores the review decision and the rejection reason when a submitted result is rejected.
Compare the reason with the original instructions
- the required action;
- the expected result;
- the required proof;
- any assigned unique text, code, or link;
- other mandatory conditions.
If you really missed something
If the client is right and the issue can be fixed, correct it instead of arguing. When correction or resubmission is available, send the proper proof and review the whole report before submitting again.
A simple example
The task required registration and a screenshot after successful registration. You registered correctly but attached the screen before completion. If correction is available, submit the final screen.
If the client asks for something that was never in the task
Workers are expected to follow the published requirements. A new requirement introduced after the work is completed should not automatically become a reason to reject the original result.
Keep your proof until the result is final
- screenshots;
- links;
- completion time;
- your assigned code or unique text;
- other supporting files.
Proof should show the result
If the task asks for successful form submission, show the success state. If it asks for registration, show the account state after registration.
If you received a unique text or code
Make sure you used the exact value assigned to you. See Unique Texts in Microtasks.
Waiting for review is not the same as rejection
A submitted result may simply still be under review. Microtasks have a review period, so do not treat the lack of an instant decision as a rejection.
Do not send many identical messages
One calm message is enough: “Hello. I completed the task according to the instructions. Could you please specify which requirement was not met? I will check it and correct the report if necessary.”
If the reason does not match the task
Collect the task number or link, the original requirement, your proof, the rejection reason, and a short explanation.
If the issue cannot be resolved normally, contact DitWork Support.
What to send to support
Keep it concise: task number, what the task required, what you completed, what proof you submitted, the rejection reason, and why you believe it does not match the original instructions.
Never fake proof
If you did not complete the action, editing screenshots or using someone else's result will only make the situation worse.
If the client was right
- Read all instructions before starting.
- Check the proof requirements.
- Save assigned data immediately.
- Take required screenshots while completing the task.
- Review the report before submission.
If the client does not respond
Keep your evidence. If the decision remains disputed and cannot be resolved, provide the task details and proof to support.
What happens after acceptance
When a result is accepted, DitWork records the accepted status and credits the worker for the completed microtask.
Quick procedure after a rejection
- Read the rejection reason.
- Open the original instructions.
- Compare the reason with the requirements.
- Check your report and proof.
- Correct a real mistake if correction is available.
- Keep evidence if the reason does not match the task.
- Contact support when necessary.
Understand the client's side too
See How to Review a Microtask Result and Accept the Work.
The main point
One rejected result is not a reason to panic. Find the exact reason and compare it with the original task.
If you made a mistake, correct it. If the work follows the published requirements and the rejection is based on something else, keep your proof and contact support if needed.
Find new tasks in the microtasks section.
