Online Work & Freelancing
Unpaid Test Work for Freelancers: When to Say Yes or Offer a Paid Pilot
Unpaid Test Work for Freelancers: When to Say Yes, Set a Boundary, or Offer a Paid Pilot

☰ Table of Contents
When a prospective client asks for a quick unpaid test, it can sound like a small price for a real opportunity. But for freelancers, the difference between a fair skills check and free production work is often hidden in one detail: will the client use the result in their business? A short, fictional exercise can show how you think. A finished landing page, researched list, logo concept, or edited video can become usable work, even when it is called an audition.
This guide offers a practical way to assess unpaid test work, set a boundary without losing a good client, and propose a paid pilot that keeps risk manageable for both sides. It is especially useful for US, Canadian, and European freelancers dealing with remote hiring processes.
Why the unpaid test feels harmless
Hiring has uncertainty. A client may have received polished portfolios that were not actually made by the applicant, or may be hiring for a role that requires judgment beyond a résumé. Asking for a small demonstration can be reasonable. Freelancers also want to avoid investing hours in a client who turns out to be disorganized.
The trouble is that “small” has no shared definition. A five-minute critique of a public page is not the same as a custom homepage mockup. The former demonstrates reasoning; the latter may be delivered straight to a developer. Before agreeing, identify what the exercise produces, how long it takes, and whether the output could be used without you.
When a skills check becomes free production
Use three questions before you start. First, is the task based on the client’s real business, customers, or confidential materials? Second, could they use the output with little or no additional work? Third, does it ask for a deliverable you normally charge for? Two or more “yes” answers are a strong sign that the request is production work, not just an assessment.
Scope matters as much as time. A 20-minute sample can still reveal a valuable concept, while a two-hour fictional exercise might be a fair skills test if it is not usable. Ask for a written brief and clarify ownership. A test should not quietly grant the client unlimited rights to concepts, files, or code.

A better way to prove your skills
Offer evidence that is relevant without creating a ready-to-ship asset. You can walk through a comparable portfolio project, annotate a public example, explain your first three decisions, or complete a short exercise using fictional inputs. For design or writing, a low-fidelity direction is often enough to show taste and process; reserve polished production files for paid work.
Ask what the client needs to learn from the test. If the concern is communication, a short discovery call or a small paid collaboration may be more informative than an isolated deliverable. If they want to see how you handle feedback, define one feedback round and a capped scope.
A practical paid-pilot menu
A paid pilot reduces the client’s risk while respecting your work. Give them a smaller first engagement with a clear outcome, fixed price, and decision point. The figures below are examples, not universal market rates; adjust them for your specialty, experience, and local market.
| Request | Safer alternative | Boundary to set |
|---|---|---|
| “Design a homepage as a test” | Paid wireframe or 60-minute design audit | One page, one direction, no production files before payment |
| “Write a sample article for our site” | Paid outline plus opening section | Fictional or limited excerpt; publication rights only after payment |
| “Build a feature to see how you code” | Small sandbox task or code walkthrough | Use dummy data; no deployment or reuse in the live product |
| “Research 50 leads” | Paid sample of 5 records with method notes | Agree on fields, source rules, and usage first |

How to respond without sounding defensive
Keep the reply warm, specific, and oriented toward solving the client’s concern. Avoid accusing them of trying to get free work; many hiring managers simply reuse a process they have seen elsewhere. State what you can provide and offer a practical alternative.
For a genuine low-stakes test, put the time limit in writing and ask that the output remain for evaluation only. If the client later wants to use it, agree on a fee and transfer rights after payment.
Red flags and reasonable exceptions
Be cautious when a client refuses to define the task, asks several candidates for bespoke concepts, requests source files before choosing someone, or says the test will be “great exposure.” Pressure to start immediately without written terms is another warning. Walk away if the client claims ownership of unpaid work or keeps expanding the assignment.
There are legitimate exceptions. A short, standardized exercise may be normal in some hiring processes, especially for an employee role. A brief critique of a public sample can be useful when the time is capped and no custom asset is produced. You can choose to participate, but make the tradeoff consciously rather than treating unpaid work as the only route to a contract.

Frequently asked questions
Should freelancers ever do unpaid test work?
Sometimes, if the task is brief, clearly limited, not usable as client production, and worth the opportunity to you. You do not need to accept every test to be considered professional.
How long should a skills test take?
There is no universal limit, but a short exercise should be genuinely short. Ask for a time cap and stop when it is reached. A multi-hour deliverable deserves a paid-pilot discussion.
What if the client says every candidate must complete it?
Ask whether the exercise is fictional, how it will be evaluated, and whether the client retains or uses submissions. Then decide based on the scope and your own pipeline.
Can a client use work from an unpaid test?
Do not assume they can or cannot. State in writing that the material is for evaluation only and that any use or transfer of rights requires a separate paid agreement. Local law and contract terms vary.
What should I charge for a paid pilot?
Price a small, useful outcome rather than discounting your normal project blindly. Define the deliverable, revision count, schedule, and how the pilot fee will be treated if the client expands the work.
How can I decline without burning the relationship?
Thank them, explain the distinction between evaluation and production, and offer a portfolio walkthrough or a compact paid pilot. A respectful boundary is often a positive signal to a serious client.
Before your next proposal, pair this approach with a clear freelance scope of work and a written revision policy. Browse more practical advice in Online Work & Freelancing.

