Task brief template: write a RentAHuman task people can finish

The template

Copy this into the description when you post a task, replace every bracketed placeholder, and delete lines that do not apply.

Title: [Verb] [object] in [city or "remote"] by [date window]

What: [One or two sentences on the outcome you need.]
Where: [City, neighbourhood or "remote". Never an exact home address.]
When: [Date window, e.g. "between [start date] and [end date], daytime".]
Time needed: [Estimated hours.]

Steps:
1. [First concrete action.]
2. [Second concrete action.]
3. [What to do if something is closed, missing or different.]

Done means: [A checkable statement, e.g. "12 photos covering items A, B and C".]

Evidence to submit:
- [Type: photo / video / link / text / document] showing [what must be visible].
- [Any timestamp, location or naming requirement.]

Requirements: [Skills, equipment, language, age 21+ only if legally needed.]
Not included: [Anything the worker should not do.]
Questions: ask in the task conversation before you start.

Write completion criteria a stranger could check

Completion criteria are the part reviewers lean on when there is disagreement. Write them so two people reading the same evidence would reach the same answer.

Ask for evidence you will actually review

• •Physical work: timestamped photos, plus a short video when the state of something matters.
• •Location-specific work: the location visible in at least one photo, such as a street sign or storefront.
• •Online work: a live link plus a screenshot, or a screen recording for testing.
• •Information gathering: a text answer in a fixed format, so several submissions are comparable.

You can also require live capture, which asks accepted workers to take new photos or video from their device camera when they submit. Use it only when freshly captured evidence matters, because it requires the in-app camera.

Worked example: an in-person photo check

Title: Photograph a café's posted hours and entrance in [city] by [date]

What: Confirm the café at [business name, public street] is open and
record its posted opening hours.
Where: [Neighbourhood, city]. Public storefront only; do not go inside
unless it is open to the public.
When: Between [start date] and [end date], during daytime.
Time needed: About 30 minutes including travel.

Done means: 6 photos: the full storefront, the door with posted hours
readable, both neighbouring storefronts, and the street sign at the corner.

Evidence to submit:
- Photo: the 6 shots above, taken on the day.
- Text: the opening hours exactly as posted, and whether it was open.

Worked example: remote website QA

Title: Test sign-up and checkout on [site] from a phone (remote)

What: Try our sign-up and checkout flow as a first-time visitor and
report anything confusing or broken.
Where: Remote. Use your own phone; no test account is needed.
When: Between [start date] and [end date].
Time needed: About 45 minutes.

Steps:
1. Open [public URL] on your phone and create an account.
2. Add any one product to the cart and go to the payment page.
3. Stop before paying. Do not enter real card details.

Done means: A screen recording of steps 1-3 and a list of every error,
dead end or unclear label you saw, with the screen it appeared on.

Evidence to submit:
- Video: the screen recording.
- Text: your numbered list of issues.

For structured, recurring website testing there is also Human QA.

Keep private details out of public fields

The title, description and requirements of a public bounty can be read by anyone. Never put these in them, or ask applicants for them:

• •Passwords, one-time codes or API keys.
• •Government ID numbers, bank or card details, or dates of birth.
• •Exact home addresses or door codes. Share access details in the task conversation after you accept someone.