The short answer
When a client asks for sample work before hiring you, judge it by scope and payment, not by whether it happened at all. A request to adapt one of your existing portfolio pieces to their brief, or a short paid test contract, is a normal part of hiring on Upwork. A request for original, deliverable-quality work with no payment and no contract - a logo concept, a written draft, a working code snippet - is a free-work harvest, whether or not the client calls it a 'test.'
The fastest gut check: could the client take what you produce and use it, ship it, or publish it without ever hiring you? If yes, it is not a screening step. It is unpaid production work wearing a screening step's name.
Paid test vs free spec work: the line that matters
Upwork's own protection only covers work inside a started contract. Everything before that point - proposals, messages, any task a client asks you to complete before hiring - has no payment protection at all. That single fact is why the scope of an unpaid request matters so much more than whether the client asked nicely.
How to tell a reasonable screening step from a free-work request
| Signal | Reasonable screening | Free-work harvest |
|---|---|---|
| Time required | A few minutes to review your existing samples or answer specific questions | An hour or more producing something new |
| Payment | Either no deliverable is produced, or it is a paid micro-contract | Unpaid, and the client resists every paid alternative you offer |
| Usability | Nothing they could ship or publish on its own | A logo, a draft, a working script - something they could use directly |
| Specificity | General questions about your process or past work | A brief for their actual project, disguised as a 'test' |
| Pattern | One client, one reasonable ask | A job post that reads like it is collecting free drafts from many applicants at once |
When a small free sample is actually reasonable
Not every unpaid ask deserves pushback. A client who wants to see how you approach their specific problem, without asking for finished, usable work, is doing normal due diligence.
- They ask you to walk through your process for a task like theirs, in writing or on a call, without producing the deliverable itself.
- They ask you to point to an existing piece in your portfolio that is closest to their project and explain how you would adapt it.
- They ask a specific, answerable question about your past work - how you handled a similar client, what tools you used, how long a comparable job took you.
- The total time asked of you is genuinely a few minutes, not an hour of new production work.
None of this requires you to create anything new. It uses what you have already built. That is the difference between a client evaluating your existing work and a client extracting new work from you for free.
The scripts that push back without losing the job
Most of the time, a direct but polite redirect gets you either a paid contract or a clear signal to walk away. You rarely need to accuse anyone of anything.
- Offer the portfolio first: 'I don't do unpaid sample work, but I have a piece in my portfolio that's very close to what you're describing - here's the link, happy to walk you through how I'd adapt it for your project.'
- Offer a paid micro-contract: 'I'm glad to do a small paid test so you can see my process on your actual project - a short fixed-price contract for [specific, bounded scope] works well for that. Want me to send a proposal for it?'
- Offer a scoped call instead of deliverable work: 'Rather than a written sample, I'd rather get on a 15-minute call and walk through exactly how I'd approach this - that usually tells a client more than one sample piece does anyway.'
- If they push back on paying for the test, ask directly: 'Just so I understand, is the plan to hire the freelancer whose sample you like best, or is there a contract starting regardless of the sample?' A client with a real hire in mind can usually answer this without hesitating.
When to walk away
Walk away when a client insists on unpaid, deliverable-scale work and refuses every paid alternative you offer. That refusal tells you what the relationship will look like after you are hired - a client unwilling to pay a small amount to screen you properly is not going to become easier to work with once real money and real deadlines are involved.
- The job post itself asks every applicant for a project-specific sample before anyone is hired - a strong signal the sample requests are the actual goal, not the hire.
- The client refuses a paid micro-contract, a scoped call, or your existing portfolio as an alternative, and insists specifically on new, unpaid, usable work.
- The requested sample is scoped almost exactly to a real deliverable they need - the 'test' looks identical to the actual job.
- The client's profile has no payment verification, no hire history, or a pattern of posting jobs and hiring rarely - see the full breakdown in how to avoid Upwork scams and bad clients.
None of these alone is proof of bad intent. Together, they are enough reason to decline and move your Connects to a client who does not need convincing to pay for a small test.
The honest summary
A request for sample work is not automatically a red flag, and it is not automatically fine either. Judge it on scope: does it use what you have already built, or does it ask you to produce something new and usable for free? Offer a paid micro-contract or your existing portfolio first. If a client insists on unpaid, deliverable-scale work and rejects every alternative, that insistence is the real answer, and it usually arrives faster than you would expect once you actually ask the direct question.
Short, practical drops on proposals, niches, client scripts, and rates. No spam, unsubscribe anytime.
Frequently asked questions
Is it normal for an Upwork client to ask for sample work before hiring?
It is normal for a client to want to see evidence of your skill before hiring, but that evidence should come from your existing portfolio, a short paid test contract, or a conversation about your process - not new, unpaid, deliverable-quality work made specifically for their project.
Should I ever do free sample work for an Upwork client?
Only if the ask is genuinely small - a few minutes reviewing your existing samples or answering specific questions, not new production work. If what they are asking for would take real time and produce something they could use without hiring you, offer a paid micro-contract instead.
How do I turn a free sample request into paid work?
Offer a short, fixed-price contract scoped to exactly what they wanted to see in the sample. Most legitimate clients accept this without pushback, because it gives them the same information plus an actual working relationship, and it puts you inside Upwork's payment protection instead of outside it.
What if the whole job post asks every applicant for a free sample?
Treat it as a strong signal, not certain proof. A job post that asks every applicant to submit project-specific work before anyone is hired is a known pattern for collecting free drafts from a large pool of freelancers. Check the client's hire history and payment verification before applying, and consider whether your Connects are better spent elsewhere.
Does Upwork protect me if I do unpaid work before a contract starts?
No. Upwork's payment protection only applies to work completed inside a started contract. Anything you produce before a contract exists, including a sample or test task, has no protection and no recourse if the client uses it and does not hire you.
Last reviewed by David Iya on September 2, 2026
