Guide

How to Write a Task Description That Gets Quality Responses

A task post is a filter, not a diary entry. The better it filters, the fewer back-and-forth messages you need before someone actually shows up.

The five things a good task post answers before anyone has to ask

• What exactly needs to happen, in the order it happens
• Where, and what access looks like (gate code, parking, stairs, apartment number)
• When — a specific window, not "flexible" or "ASAP"
• Who supplies what — tools, materials, ladder, cleaning supplies
• What "done" looks like, in a sentence someone could check against

Miss any one of these and you'll get messages asking for it — or worse, someone who shows up having assumed the answer, and assumed wrong. See our companion checklist on the information people forget to include for a fuller pass on this.

Before and after: the same job, two ways

Before: "Need help assembling some furniture this weekend, flexible on time, reasonable price."

After: "Assemble one IKEA bed frame and one 6-drawer dresser, both still boxed, hardware included. Third-floor walk-up, no elevator. Saturday between 10am–2pm. I'll provide the space; bring your own tools. Budget $120–150 for both. Boxes need to be broken down and left by the door when done."

The second version gets fewer replies in volume but a far higher share of them from people who can actually do the job on your terms — which is the metric that matters. For the pricing logic behind that $120–150 range, see our furniture assembly cost guide.

Say what "done" looks like, specifically

"Clean the apartment" and "clean the apartment including inside the oven, inside the fridge, and baseboards, ready for a move-out inspection" are different jobs at different prices, even though they could describe the same three hours of work. Defining the finish line in the post — not after the person arrives — is the single most effective way to prevent an argument about scope later. We cover this in more depth in how to avoid scope creep on a one-time job.

Put the boring logistics up top, not buried

Parking, pets on site, stairs, whether kids will be home, whether the water or power will be off — these details feel unimportant to you because you live with them, but they change how someone bids and whether they can even take the job. Bury them at the bottom of a long post and most people won't reach them before deciding to skip it.

One line that filters out mismatched applicants

Add a single sentence that only makes sense to someone who actually read the post — "please mention which day this week you're free" or "confirm you have your own ladder." Generic, copy-pasted replies will skip it; the responses that answer it directly are worth opening first.

Keep it to one screen

Long posts read like a legal document and get skimmed, not read. Aim for one screen's worth of text: a two-line summary, a short bulleted scope, the logistics, and the budget. If the job genuinely needs more explanation than that, it's probably a multi-day project rather than a single task — worth checking against our guide to scoping task size before you post it as one listing.

Why a clear post also gets you better prices

A clear, specific post naturally attracts fewer but better-fitted responses, and better-fitted responses tend to quote more accurately, since the responder actually knows what they're pricing. A vague post, by contrast, often collects a wide spread of guesses — some too low to be real, some padded to cover the unknowns — because nobody replying actually knows what they're bidding on.

Photos are worth more than another paragraph

For almost any physical task, one or two photos do more work than an extra paragraph of description — a photo of the actual furniture box, the specific mess in the yard, or the room that needs cleaning removes ambiguity that words alone tend to leave in. It also lets a tasker self-select more accurately: someone who sees the real scope up front and still replies is a more reliable signal than someone replying to a text-only description they'll only fully understand once they arrive. If your platform supports attaching images to a post, use it for anything where "what this actually looks like" matters more than a written description can capture.

Common vague phrases and what to say instead

• Instead of "flexible timing," write the actual window: "Saturday or Sunday, 9am–1pm either day"
• Instead of "a few pieces of furniture," name them: "one 3-drawer dresser and one desk, both flat-pack, hardware included"
• Instead of "reasonable price," write a number or range: "$100–130 for both, final price confirmed on arrival if boxes are missing hardware"
• Instead of "clean up the yard," describe the debris: "clear dry leaves and bag them from a roughly 3,000 sq ft backyard, no hauling needed"
• Instead of "help with an errand," list the stops in order with addresses and any deadline attached to each

None of these rewrites take more than a minute longer to write, and each one removes an entire round of back-and-forth messaging that a vague version would have required before anyone could actually quote the job.