Creating a microtask is only the beginning. After that, the task moves through a clear lifecycle until an accepted worker result is paid.
Creation -> moderation -> budget -> publication -> worker starts -> report submitted -> review -> approval -> payment.
1. Creation
You define the action, instructions, proof requirements, completion time, reward, result quantity, and other eligibility settings.
2. Moderation
The task has a moderation status. Review is especially important for tasks with additional safety conditions, software installation, or other sensitive parameters.
If the task is acceptable, it can continue. If a problem is found, it may be stopped or blocked until the issue is resolved.
3. Task budget
On DitWork, the main account balance and the budget of a specific microtask are separate. New completions need funds available in the task budget.
See Microtask Budget.
4. Publication and availability
Once the necessary conditions are met, the task can become active and visible to eligible workers. Country, device, profile requirements, schedule, repeat rules, and other settings may affect who can see it.
5. A worker starts the task
When a worker starts, a specific completion is reserved for that person for the configured time. The assigned target, reward, and any unique text or code are associated with that completion.
6. Work and report submission
The worker follows the instructions and submits the required proof, such as text, a link, screenshot, file, or several items.
7. Review
After submission, the result waits for review. The client compares the proof with the task requirements and checks whether the requested result was actually delivered.
8. Approval
If the requirements are satisfied, the result is approved and the final payout is recorded.
For payment models, see Fixed Price or Payment Range.
9. Payment
After approval, DitWork credits the worker for the completed microtask and sends a notification that the result was accepted and payment was added to the balance.
What if the worker does not submit in time?
A started completion is reserved only for a limited period. If no result is submitted in time, the reservation can expire according to the task rules.
What if the task budget runs out?
New completions can stop until funding is restored. Long-running tasks can also use task budget auto-refill settings.
What if all required results are collected?
Once the target quantity is reached, additional workers are no longer needed. If you want more results later, the quantity can be increased.
See How to Add More Completions.
A complete example
- Create the microtask.
- Complete moderation.
- Fund the task budget.
- The task becomes available.
- A worker starts and reserves a slot.
- The worker completes the instructions.
- The worker submits proof.
- The client reviews it.
- The result is approved.
- DitWork credits the payment.
Prepare the task before launch
Read How to Create a Microtask on DitWork and How to Make a Microtask More Attractive to Workers.
Create a new task at Create a microtask.
The main point
After launch, each DitWork completion moves from reservation to submission, review, approval, and payment. A well-prepared task makes every later stage easier for both the client and the worker.













