Order Intake Form: AI Freelance Briefs Before You Start Work
A Fiverr or Upwork intake form for AI freelance jobs: required brief fields, a revision cap, and a reject rule for incomplete briefs—before you draft.

Who this guide is for
You can already get a usable first pass out of an AI tool. The waste happens before that pass: a one-line “make it good,” no files, no word cap, then three unpaid rewrites.
This page is the intake form—the questions and attachments you collect before you draft. Chinese operator write-ups often treat 平台接单 as a pipeline; the English job is smaller: a complete brief in the official thread. It is not a hustle list, not an hour log, and not this author’s personal order diary.
AI for making money on this URL means a paid, scoped file—not a prompt race. For which jobs to accept, how to count hours, and how platforms take a cut, use the commercial order queue. This URL stays on fields.
If you have not chosen client delivery yet, start with seven realistic AI side hustle paths.
Job | What you are designing | Not this page |
|---|---|---|
Intake form (here) | Required questions, files, reject rules | Fee tables and weekly hour math |
Queue discipline | Accept/refuse, escrow, caps, hour log | Field-by-field brief schema |
Idea shopping | A menu of AI hustles | Any operating SOP |
Fiverr names this step Requirements. Upwork usually collects the same facts as questions on the job post plus whatever you refuse to start without in messages. Do not open both marketplaces on night one.
Form vs one-line DMs
A message that says “need an article tomorrow” is not a brief. A form is a brief you can dispute against.
Dimension | Complete intake | One-line DM |
|---|---|---|
When you start | After required fields and files | Immediately, then guess |
What you can prove | Answers sitting on the order | A chat fragment |
Revisions | Counted against a written cap | “Until it feels right” |
AI | Preference asked up front | Surprise after delivery |
Protection | Official thread + escrow | WhatsApp “to save fees” |
Escrow still matters. Moving the intake to a side chat throws away the trail you will need if the buyer later says you ignored the brief.
The fields you actually need
Fiverr’s Help Center describes Requirements as the place to ask for what you need before you start, and to mark questions required so the order cannot proceed empty. It also warns that too many questions frustrate buyers. See Creating a Gig. The Community blog on clear Gig requirements adds the same idea: start from your workflow, not a 20-field interrogation.
Copy this set. Cut anything that would not change the file you ship.
Field | Required? | What “done” looks like |
|---|---|---|
Deliverable | Yes | Format + size (e.g. 800 words, Google Doc; 10 slides, 16:9) |
Goal | Yes | What the file is for (sales page, internal wiki, five captions) |
Inputs | Yes | Client-owned text, URLs, or uploads you are allowed to use |
Constraints | Yes | Must-include / must-avoid claims, tone, banned sources |
Deadline | Yes | Date after files arrive—not “ASAP” with empty attachments |
Usage / rights | Yes | Where it will run; exclusive vs not; what is out of scope |
AI preference | Yes | Allowed to assist / not allowed. Honor an explicit non-AI request. |
References | Optional | Two examples of “this shape, not that shape” |
How they found you | Optional | Fiverr’s Help notes this as an optional extra, not a start blocker |
Do not start if deliverable, inputs, or deadline is blank. That is the whole product.
Fiverr’s AI guidelines allow AI as assistance, not as an unmodified dump. You stay accountable for the file. If the client forbids AI, say so in the form and follow it. Asking after delivery is how disputes start.
On Upwork, the client may already have screening questions. Cover letter guidance treats those answers as part of the proposal. Your intake job is the inverse: you still do not start work until the same start-blocking facts exist in the contract thread—even if the public job post was vague.

First seven days (one gig, one form)
- Lane lock (30 min) — One deliverable type (for example wiki summaries or 800-word refresh articles). Not both.
- Field list (45 min) — The table above, in the marketplace’s requirement or question UI. Required vs optional marked.
- Package text (30 min) — Restate what is not included (source files, extra languages, unlimited rewrites) in the same place buyers complete requirements.
- Incomplete-brief rule (15 min) — Written: wait / decline / paid “brief cleanup” extra. Pick one default.
- QA against the form (30 min) — Checklist: every required answer has a matching sentence or heading in the draft.
- Pilot (one order) — Do not add a second gig until this form has been used once without you asking the same questions again in chat.
- Kill rule (10 min) — If a buyer refuses the form twice, stop. Guessing is not a service.
Score the brief before you accept
This is a yes/no gate, not a personality test.
Signal | Accept | Wait or reject |
|---|---|---|
Completeness | Goal, inputs, constraints, deadline filled | “Help me” plus no files |
Scope fit | Matches the package you sold | Custom “build the whole knowledge base” |
Source quality | Client-owned or clearly licensed | Pirated PDF, scraped dump |
Revision cap | Stated on the gig and in the form | “Until I’m happy” |
Channel | Official order | PayPal-only side deal |
AI | Preference answered | Silence, then anger after delivery |
Three complete briefs beat twenty empty ones.
What to send when the form is empty
Do not start the draft “to be nice.” Paste a short reply in the official thread:
I can start as soon as the required fields and files are in this order: deliverable size, goal, inputs I’m allowed to use, constraints, deadline from file receipt, and whether AI assistance is allowed. If any of those stay blank, I cannot open the gig.
If they still send a vibe: wait, decline, or sell a brief-cleanup extra (you turn their paragraph into the form, then the original package starts). That extra is a product, not a free translation.
Failure modes
- Field sprawl — fifteen optional questions; buyers bounce before they pay.
- Start-on-vibe — you draft from a DM; the Requirements answers arrive different.
- Hidden AI — you never asked; they wanted non-AI.
- Rights fog — they wanted exclusive perpetual use on a micro package.
- Off-platform intake — the only complete brief lives in WhatsApp.
- Second gig too early — two forms, two fee tables, zero completed schema.
After a month of complete briefs, add one adjacent package that reuses the same fields. Do not invent a new interrogation.
Rules that are not optional
Stay inside marketplace terms. Keep confidential files off public samples. Do not promise rankings or revenue. Track payouts for tax in your jurisdiction—this is not tax advice.
Fiverr: Requirements + AI guidelines as linked above. Community standards still apply. On any other platform, read that site’s current order-start and AI rules before you copy this list.
FAQ
Can I run this with few reviews? Yes. A short required-field list and redacted sample outputs matter more than a long badge row. Reviews do not replace a blank brief.
Fiverr or Upwork? One lane first. Fiverr: put start-blocking questions in Requirements and mark them required. Upwork: treat job questions plus your start rule in the contract thread. Do not run both forms in week one.
Does AI fill the whole deliverable? It can draft. You still match the form, check facts, and skip unmodified dumps. If they forbade AI, you do not use it.
What if they refuse the form? Wait, decline, or sell brief cleanup. Starting anyway trains them to skip it next time.
When do I add a second service? After this form has survived real orders without you re-asking the same questions in chat—not after one busy weekend. For hours and fees, go back to the order queue.
Thirty-day checklist
Week 1: One gig, required-field list, incomplete-brief rule. Week 2: Two orders that started only after the form was complete—or two documented waits. Week 3: Cut one question that never changed the file. Week 4: One redacted sample that shows the form → file shape. No second marketplace.
Related on MMHow
A working intake form is short, required where it blocks start, answered before the model opens, and boring enough to reuse.
Last reviewed
Last reviewed: 31 August 2026. Unattributed order counts and monthly gross bands were removed. Official Fiverr Requirements and AI guideline pages were added. The title no longer shares a duplicated keyword suffix. This page is an editorial SOP, not a personal income log.
Continue Reading
Comments
No comments yet. Be the first to share your thoughts.
