Post a small task, pay per worker who completes it, and approve the evidence they submit.
You describe a task and how many workers you need
|
v
You approve the steps and the evidence you require
|
v
Your job is submitted for review
|
v
Workers claim it, complete it and submit proof
|
v
You approve or reject each proof
|
v
Approved proofs are paid from the amount you
funded when you created the job
You control the approval step. Nothing is paid out for work you have not approved.
| Field | Required | Notes |
|---|---|---|
| Title | Yes | Up to 255 characters. |
| Category | Yes | From the categories your operator has configured. A sub-category can also be set. |
| Steps | Yes | At least one instruction. Be specific — this is the only thing the worker sees. |
| Proof requirements | Yes | At least one item. What the worker must supply as evidence — a screenshot, a link, some text. Be clear, because this determines what you can judge. |
| Workers needed | Yes | How many completions you are paying for. |
| Worker earnings | Yes | What each worker is paid, at least 0.01. Your total is this figure multiplied by the number of workers, plus the operator's fee and any per-country charges. |
| Speed | Yes | How urgently you want it completed. Influences where it is shown. |
| Minimum quality score | Yes | 0–100. Workers below this threshold are not offered the job. |
| Target countries | Optional | Where you want workers from. |
| Excluded countries | Optional | Countries to exclude from the same pool. |
| Daily limit | Optional | Caps how many slots open per day. |
| Minimum account age | Optional | Excludes recently created accounts. |
| Featured | Optional | Gives your job priority for a fixed promotional period, at an additional fee set by your operator. |
pending until your operator reviews it.
Workers submit proof and you decide. On each submission you can record a rating and a comment, then approve or reject.
Your operator filters the worker pool before your job reaches anyone. You cannot see or override these:
The practical effect is that a job can receive fewer, or later, submissions than the numbers suggest. Slow uptake is usually a targeting or price problem rather than a fault.
| Symptom | Cause and fix |
|---|---|
| No workers are picking up my job | Usually the pay rate, the country list, or the quality threshold excluding the available pool. Loosen the minimum quality score or widen the countries. |
| My job is stuck at pending | Normal. Micro Jobs always require review. Your operator has to approve it. |
| Submissions are poor quality | Your proof requirements are too loose, or the minimum quality score is too low. Both are within your control. |
| My job completed with fewer workers than requested | It will not — it stays open until the count is reached. If it closed early, raise it with your operator. |
| The total charged differs from what I expected | The figure is per worker, not per job, and includes the operator's fee plus any per-country charges and the featured fee. |
| A rejected job was not refunded | Known bug on this build — Micro Job rejections do not currently return funds. Contact your operator. |
| A worker disputed my rejection | Re-review the submission and record your decision with a comment. |