Microtaches.com

Manual validation on microtasks: passing quality control on the first try

L'équipe Microtaches · Updated 2026-06-20 · Astuces worker

On Microtaches, many missions go through human validation before your Ops are credited. Here's exactly what a moderator looks for, the mistakes that get tasks rejected, and how to push your validation rate up.

Manual vs automatic validation: what changes for you

What a human reviewer actually looks at

A moderator doesn't judge your intent — they judge what they see. Concretely, they check five things, usually in under a minute:

  • Brief compliance. What did the brief ask, exactly? Did you do that, or something else?
  • Proof quality. Is the link valid, the screenshot legible, the ID complete, the answer non-empty?
  • Target / group respect. If the mission targeted a specific profile (country, language, sector), does your submission match?
  • Language and tone. Correct English if required, tone aligned with the brief.
  • Authenticity. No detectable copy-paste, no generic answer recycled from another mission, no raw unedited AI.

7 mistakes that get a microtask rejected

  1. Blurry or cropped screenshot. The URL isn't readable, the date isn't visible, you have to guess. Auto-reject.
  2. Wrong field filled. You pasted a link in the wrong slot, or filled a field with content meant for another.
  3. Detected copy-paste. Same answer as ten other workers, or obvious recycling from a previous mission.
  4. Off-target. The mission targeted a specific platform, country, or topic — you answered next to it.
  5. Late submission. The mission window had passed when you posted your proof.
  6. Empty security-question answers. Blank fields, or answers under 5 characters: the submission is blocked server-side.
  7. Missing proof. You did the work but forgot to attach the direct link or screenshot that proves it.

What happens if your task is rejected

How long does manual validation take?

It depends on the mission type and the day's volume, but the order of magnitude is stable:

  • High-volume missions (comments, micro-checks): usually a few hours.
  • Complex briefs (writing, research, cross-checks): up to 24-48h.
  • Off-hours missions (weekends, late evenings): review may wait for the next moderation slot.

While you wait, your task shows under My tasks with the status In review. Once validated, the status flips to Completed and your Ops are credited automatically — no action needed on your side.

How to dispute a rejection (without shooting yourself in the foot)

A rejection isn't a death sentence, but tone and message quality change everything. What works:

  • A short, factual message: "Task X rejected, I believe the proof shows Y, here's the link and the screenshot."
  • Attached proof: full screenshot, exact URL, timestamp if possible.
  • One message per task, not a flood of follow-ups within the hour.
  • Honest acknowledgement of what might have been missing, plus a fix proposal if the mission allows.

What doesn't work: insulting the moderator, contesting multiple tasks in bulk without detail, or claiming "I did it right" without any extra proof. In all those cases the rejection sticks and your credibility with support drops.

Building a strong validation rate over time

Your validation rate is a long-term asset. A worker above 90% sees their mission catalog grow; one around 50% quickly ends up with a thinner one. A few simple habits make the difference:

  • Read the full mission description (the worker version, not just the title) before accepting.
  • Be extra careful on your first few tasks in a new category: the system learns whether to trust you.
  • Decline rather than letting tasks expire. If a mission doesn't fit, decline it.
  • Prepare your proof before submitting. Clean screenshot, full URL, re-read fields, non-empty answers.
  • Avoid stacking 3 tasks in parallel if you know you won't have time to do them properly (the platform limit is 3 concurrent tasks).
  • Take a break after two rejections in a row. Often it's a fatigue or brief-misreading signal, not a platform issue.

Ops, payment, and when the credit happens

Ops for a manually-validated mission are credited after a moderator validates, not at submission. While the task is in In review, the amount is not yet on your balance.

To understand how Ops then convert into gift cards or a bank transfer, see our guide converting your Ops to euros or gift cards. For the tax side, see declaring micro-task income or, if you're already self-employed, combining micro-entrepreneur status with micro-tasks.

A concrete example: a LinkedIn comment mission

LinkedIn comment missions are a typical case of strict manual validation. A moderator checks: that the comment is published from your personal account, that it isn't a copy-paste, that it matches the requested tone, that it carries the disclosure when the mission requires it, and that it's still online. One missing box = rejected.

This isn't gratuitous rigidity: it's what makes the missions serious and properly paid, instead of diluted in a sea of mediocre submissions.

Ready to aim for a validation rate above 90%?

Free signup, clear missions, human validation, paid in gift cards or SEPA bank transfer.

Create my Microtaches account
How long until a task is validated?
It depends on the mission and the time of submission. Most missions are reviewed within a few hours. Complex briefs can take up to 48 hours. Until then, the task stays in 'In review' under My tasks.
What if my task expires while in review?
If you submitted before the deadline, your task stays eligible for review; it is not marked as expired. Expiration only applies to accepted tasks that weren't submitted within the window.
Can a rejection block my account?
A single rejection has no effect on account access. Restrictions or blocks come from a pattern of rejections, fraud attempts (fake accounts, automation, mass copy-paste), or abusive behaviour with support.
Can I redo a rejected task?
It depends on the mission. Some allow a redo with a cooldown (e.g. a few hours before retry). Others don't, and the attempt is final. The information is visible directly on the task card.
Are Ops credited before or after validation?
After. While your task is 'In review', the Ops aren't on your balance yet. As soon as the moderator approves, the credit happens automatically — nothing to request.
How do I know what a moderator actually checks?
Each mission lists its concrete validation criteria in the worker description. That description is what counts, not just the mission title. Take 30 seconds to read it fully before clicking Accept.
Is my validation rate visible somewhere?
Your task history (validated, rejected, expired) is available under My tasks. Even if it isn't shown as an explicit percentage, the platform tunes the volume of missions offered to you based on it.