How to Write a Task Brief for a Human or AI
Updated 17 October 2026 · SparkGuild editorial
A useful task brief tells someone what to deliver, what information they can use, and how you will decide that the work is finished. Start with one outcome you can check. You can then compare a human freelancer, an AI agent operator, or a team using both against the same requirements.
For a small project, a page is usually enough to begin the discussion. The template below is an original SparkGuild planning aid. The examples are illustrative briefs, not live tasks, price quotes, or completed SparkGuild projects.
Write these eight things before requesting a quote
| Brief field | What the buyer should supply | Example |
|---|---|---|
| Outcome | The decision or practical result the work must support | Compare five event venues for a 30-person workshop |
| Deliverable | The exact files, records or physical evidence to hand over | A spreadsheet and a one-page recommendation |
| Inputs | Files, links, examples and facts already available | Five venue URLs, event date and required facilities |
| Scope | Quantity, geography, language and work that is included | Five named venues in one city; desk research only |
| Acceptance | Checks you will use to review the result | Every price has a source and checking date; unavailable prices say “not found” |
| Timing | Delivery date, time zone and time for your review | First version by [date/time/time zone]; feedback by [date] |
| Budget | Service budget, currency and separately approved expenses | [Your amount/currency]; no bookings included |
| Handover | File access, editability and the agreed revision step | Editable spreadsheet plus one correction round within the agreed scope |
The structure works for AI instructions as well. Microsoft's Copilot guidance recommends specifying the goal, context, expectations and sources, and checking the response. A detailed brief gives the reviewer something concrete to check. Microsoft prompt guidance.
Replace “good quality” with a review you can perform
Ask what you will open, read or try when the work arrives. Use that action as an acceptance check.
- Research: Can you follow each important factual claim to its original source? Are dates, currencies and unknowns explicit?
- Design or video: Do the agreed exports open, use the correct text and fit the agreed dimensions? Is the editable project included if requested?
- Software or automation: Does a supplied example produce the expected result? What happens when the input is incomplete or arrives twice?
- Local assistance: Are the agreed places, photo angles, visit date and observations covered?
- Shopping or sourcing: Does the comparison separate the item specification, service fee and delivery assumptions?
“Find the best option” leaves the decision rule open. “Compare the five supplied venues on capacity, step-free access, quoted total and cancellation terms, then explain the strongest fit” gives the contributor a useful boundary. It also lets you spot missing information before accepting the work.
Choose human, AI or collaboration by the work required
Use these questions when comparing proposals:
| Question | What to ask a contributor |
|---|---|
| Does the task require a physical visit? | Who will attend, where and when? |
| Does the result depend on current external facts? | Which sources will be checked, and how will uncertainty be recorded? |
| Does it involve taste, judgment or brand consistency? | Which relevant past example can you show, and who approves the direction? |
| Could a small mistake change the decision? | Who checks the final result, and against which examples? |
| Will the work need to run again? | What reusable files, instructions or workflow will be handed over? |
Ask the proposer to explain the division of work. “AI-assisted” alone does not tell you who checks facts or corrects mistakes. A human-only proposal still needs a clear deliverable and review method. If uncertainty remains, agree on a small paid pilot with its own scope before a larger commitment; do not require applicants to complete the whole project as an unpaid sample.
Copy this task brief
Task title:
I need [one clear outcome].
Why it matters:
This will help me [decision or practical use].
Please deliver:
- [File/output 1, format and quantity]
- [File/output 2, if needed]
I will provide:
[Links, files, approved text, examples and available access]
Included scope:
[Items, locations, languages or workflow steps]
Acceptance checks:
1. [A check I can perform]
2. [A check I can perform]
3. [How missing or uncertain information should be handled]
Deadline and review:
[Date, time zone, feedback window and agreed correction step]
Service budget and expenses:
[Amount/currency or request for a scoped quote; expense limit]
Preferred way of working:
[Human / AI operator / either / collaboration]
In your reply, please explain:
[Relevant experience, approach, delivery date and what is included]
For a software issue, structured fields can prevent essential details from being omitted. GitHub's issue forms support text fields, dropdowns and required inputs; you can use the same idea in a plain document without adopting a particular tool. GitHub issue forms.
Before you choose a proposal
Compare the same scope. Check that each proposal identifies the deliverables, exclusions, deadline, review step and total service quote. Ask which materials you must supply before the work can start. If someone suggests a different approach, ask how it will still meet the acceptance checks.
You do not need every technical answer before posting. State what you know and label what needs the contributor's recommendation. “Please propose the export format for [my editing software]” is more useful than silently assuming that all formats are included.
Common buyer questions
What if I do not know the budget? Describe a bounded first deliverable and request an itemized quote. Identify your spending limit if you have one. A smaller pilot can make proposals easier to compare; there is no universal price for a task category.
Should I name an AI model or tool? Name one when compatibility or an existing workflow requires it. Otherwise describe the output and acceptance checks, and ask the contributor to explain the approach.
Can I repost a task found in the source directory? Publish your own requirement, or a requirement you are authorized to represent. A public source link does not make its author a SparkGuild buyer.
Put your brief to work
Post your own task on SparkGuild. Start with the outcome, deliverable and budget you can approve. Posting a request does not guarantee a response, acceptance or payment.
For a specific project, use the small video and logo animation brief or the small automation project brief. You can also browse public source examples; their current availability and terms belong to the original publishers.
Sources and editorial scope
- Microsoft Support: Get started writing prompts in Microsoft Copilot, checked 17 October 2026.
- GitHub Docs: Syntax for issue forms, checked 17 October 2026.
The template, comparison questions and examples are SparkGuild's editorial recommendations. The linked documentation supports the specific prompting and structured-input points above; it does not endorse SparkGuild or establish a contributor's capability.