Guide
How a sample becomes a full task
Why a short sample is often the first step, and how an agreed sample turns into a published worker task.
A sample shows the rule, not the whole file
A large file is hard to quote from a one-line description. A sample of ten to twenty rows, a few pages, or a short recording lets an administrator see the real columns, the real gaps, and the real labels. The sample should be representative. If most of the file is messy and the sample is the clean part, the later task will not match the quote.
Say what "done" means for one row or one page. For a product check, that might be: compare these five fields to the reference, leave a blank when the reference is silent, and flag a row when two sources disagree. For a transcript, it might be: type the words that are clear, and mark a timestamp when a phrase is not clear. Those rules are what a worker would later see.
The enquiry is not yet a task
Sending the enquiry form stores the business name, the contact details, the selected service, and the description. An administrator can add notes, a quotation, the agreed scope, and a follow-up date. None of that publishes a task. Workers cannot open the enquiry, and they cannot see the sample unless a task is later written and published for workers who are eligible.
A quotation is a proposal for a defined scope. It is not an order until you accept that scope. If the sample shows that the work is broader than the first description, the quotation can be revised or the work can be declined. The service pages do not list a price because the sample is what makes a price possible.
A published task has its own instructions
When the scope is agreed, an administrator can create a task. The task has a title, a summary, instructions, eligibility, quality criteria, a reward, a currency, a quantity, and sometimes a deadline. Publishing it is a separate action from saving a draft. Workers see the task only after it is published, the deadline has not passed, and a place is still open.
The instructions on the task should be specific enough that two careful workers would make the same decision on the same row. If a row needs a business decision, the instruction should say to flag it rather than guess. Quality criteria say what will be checked when the work is submitted, such as whether flags were used, whether invented values were avoided, and whether the file matches the column list.
Review looks at the submitted result
A worker accepts one assignment on that task, does the work, and submits the result. Images and files can be attached when the instructions ask for them, within the size limits shown on the form. An administrator approves or rejects the submission. A rejection can include feedback. A second submission is possible only when the task allows it.
Approval records the task reward as an unpaid earning. It does not send the money. A later payment record is written by a person. If no task has been published, none of these steps occur, and the worker dashboard says that no task is available.