A participant is a person who accepts a bounded task on stated terms and returns a structured result. Records show what each person can do, where, and what comes back — and say plainly what is unknown.
Document Execution · Asheville, NC
Handles the physical steps of a document — wet signatures, witnessing, scanning, and delivery of signed originals — across Asheville and nearby areas.
In-Store & Field Research · Moab, UT
Conducts structured research inside stores and other physical locations around Moab: counts, shelf photography, displayed prices, and short intercept questions.
Local Bureaucracy & Physical Administration · Jackson, WY
Handles administrative errands in Jackson: picking up forms, submitting documents, queueing at an office, and checking requirements posted on site.
Human Identity & Physical Verification · Burlington, VT
Handles permitted in-person identity and verification tasks around Burlington: attending in person, presenting her own ID, collecting items, and verifying another person face-to-face.
Verification requirements depend on the task. Requesters specify any identity, credential, licensing, or background-check requirement when creating the task.
Deterministically: task-type match first, then required-capability coverage, then location compatibility, then a fixed tie-breaker.
Yes. Open a participant record and write a brief. You write the bounded brief, Taskin delivers it to that participant, and the exchange stays in the task thread until they accept.