One-Off Task Brief Template

A good small-task brief turns “please handle this” into an executable piece of work. The template below forces the decisions that matter most: the outcome, scope, proof, deadline, payout and the boundaries of what is not included.

Copy the template

TASK TITLE: [One clear sentence] OUTCOME: [What must be true or delivered when the task is complete?] SCOPE: [What is included? List the exact pages, files, records, locations or steps.] OUT OF SCOPE: [What should the doer not do?] PROOF REQUIRED: [What evidence should be submitted to verify completion?] DEADLINE: [Date and time + timezone] PAYOUT: [Amount and currency] ACCEPTANCE TEST: [The objective condition that determines whether the result is accepted.] NOTES: [Constraints, allowed tools, access limits or other context.]

Why each field exists

Outcome prevents activity from replacing results. Scope limits interpretation. Proof makes verification possible. Deadline defines when the promise matters. Payout makes the economic trade-off visible. Acceptance test reduces disputes over whether “done” means done.

Examples of strong proof

Research

A source list with URLs, dates checked and the requested fields completed.

Software

A reproduction note, test result, commit or deployment evidence that matches the requested acceptance test.

Local

Allowed photographs or observations that clearly show the requested place or condition, with the date and context needed to verify them.

Practical rule: fund only after you can explain the task to a stranger who has never seen the surrounding project. That is the point of a marketplace-ready brief. Post a task when it is ready.