When you host a task, the brief is the only thing workers see before they start. A vague brief gets vague work. A clear brief gets submissions you can approve in seconds. Here is how to write a task description that gets great results, plus a template you can copy.
1. Start with a one-line goal
Tell workers why the task exists. "We want honest first impressions of our new delivery app" helps workers make good decisions when something is not covered in the steps.
2. Write numbered steps
Break the task into short, numbered steps. One action per step. Workers follow numbered steps far more accurately than a paragraph.
3. Say exactly what proof you need
- "A full-screen screenshot showing your username and the shared post."
- "The direct link to your post, not your profile."
- "A 30 to 45 second vertical video showing the product clearly."
The more precise your proof requirement, the faster your reviews.
4. Set a fair reward
Price the task for the time and effort it really takes. Simple follows and joins take a minute. Videos, testing and research take longer and deserve more. Fair rewards attract careful workers, and careful workers save you review time.
5. Add an example
An example of a good submission removes guesswork. If you can, describe what an ideal screenshot or video looks like.
6. State what will be rejected
Be clear and fair: "Submissions from private accounts cannot be approved", "Videos with background music over your voice will be rejected." Workers appreciate knowing the rules in advance.
7. Keep it honest
Ask for genuine opinions and real engagement. Do not ask workers to post fake reviews or misleading claims, and ask them to disclose paid posts. Honest tasks protect your brand and the workers' accounts.
A task brief template you can copy
Goal: We want real people to try our new [product] and share an honest first impression.
Steps: 1. Download [app] from [store]. 2. Create an account. 3. Place a test order using code [CODE]. 4. Record a 30 to 45 second vertical video saying what you liked and what confused you.
Proof: Upload the video and a screenshot of your order confirmation showing your username.
Will be rejected: videos under 20 seconds, videos where the app is not visible, reused videos.
Weak brief vs strong brief
| Weak | Strong |
|---|---|
| "Promote our page" | "Follow @brand on Instagram and share our latest post to your story" |
| "Send proof" | "Upload a full screenshot of your story showing your username" |
| "Make a nice video" | "Record a 30 to 45 second vertical video showing the product and saying one thing you liked" |
| "Test our app" | "Sign up, add any item to your cart, and tell us where you got stuck" |
Choosing how many people you need
- Testing: 10 to 20 people usually reveal most usability problems.
- Video content: order more than you need, since you will choose the best.
- Research: enough for a pattern, often a few dozen people who match your customer.
- Awareness: scale gradually and measure what each batch brings.
Mistakes to avoid
- Asking for several different things in one task. Split them.
- Hiding a key requirement in the middle of a paragraph.
- Changing the rules after people have started.
- Setting a reward far below the real effort, which attracts rushed work.
After your task goes live
- Check the first few submissions early and update the brief if people misunderstand something.
- Leave a short note when you reject, so workers can fix and resubmit.
- Review promptly. Read how to review submissions fairly.
Ready to post? Create a business account and host your first task. New to the idea? Start with what crowdsourcing is.