Direct answer

Not as a full free project. Offer a tiny paid first stage on a record, or a capped sample that can never be used as the deliverable.

A new client likes your work, wants to move ahead, and asks for one thing first: a small test project, unpaid, to see how you work before they commit. Sometimes that request is an honest hiring step from a firm that has been burned before. Sometimes it is the whole job, sliced thin and renamed, and the hiring never arrives. The two look identical in the asking email, and the difference only shows in what the client accepts when you answer. A real test has three marks: it is small compared with the job behind it, it tests skill rather than producing a usable asset, and the client is willing to put a small amount of money and a decision date behind it. This page gives you the check, the three answers you can give, the shape of the tiny paid pilot that protects both sides, and the exact reply to send, so you can say yes to being tested without donating the work itself.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 21, 2026. First published November 21, 2026. The records quoted below are real and public, read back from the live service on November 21, 2026.

Step 1. Run the three-mark check before you answer: size, usability, commitment

Hold the request up against three marks. Size: a test should be a small fraction of the engagement behind it, an afternoon or a day at most, not the first full deliverable of the project wearing a test label. If the test would take a week, it is not a test, it is stage one with the invoice removed. Usability: a test proves skill, so its output should show how you work without handing over something the client can ship, publish, or build on. The moment the test output is directly usable as a finished deliverable, the client no longer needs to hire anyone to get its value, and many never do. Commitment: a client running a genuine hiring process can name what happens next, who decides, by what date, and what the paid work looks like if the test goes well. A request that is vague on all three is not a process, it is a hope, and hopes do not pay for test projects. Score the request honestly: three marks present, proceed to the paid pilot in step 3. Marks missing, use the capped sample in step 2 or decline with the reply in step 5.

Step 2. If it stays free, cap it so it can never be used as the deliverable

There is one honest free shape, and it is narrow: a sample, not a project. A sample is small enough to finish in a short sitting, it shows your method and your standard, and it is delivered in a form that cannot be lifted into use: an excerpt rather than the whole piece, a low resolution or watermarked version of visual work, a walkthrough of an approach rather than the finished asset, or work on a dummy brief the client supplies instead of their live one. State the cap in your reply before you start, in friendly terms: happy to show you how I work, here is the sample I can do, and the full version is stage one of the engagement. A client who only wanted to see your skill accepts this instantly, because a sample answers their real question completely. A client who pushes back on the cap, who needs the real thing, at full quality, on the live brief, has told you which of the two requests this was, and they have told you before it cost you anything. Believe them.

Step 3. Offer the better door: a tiny paid first stage, priced, dated, on a record

The answer that serves both sides is a pilot: the test, run as a real first stage of the job. Shape it tightly. Scope: one small, complete piece of the real work, chosen so its quality is easy to judge, the first section, the first screen, the first report, not a fragment that only makes sense inside the whole. Price: a small fixed fee, real money, low enough that approving it needs no committee and high enough that it is a purchase rather than a token. Date: a stated delivery date and a stated decision date, the day the client says yes or no to the main engagement. Credit: if you like, offer to credit the pilot fee against the main job when they proceed, which costs you nothing with a client who hires you and keeps the pilot honest with one who does not. Run the pilot on a job record from the first message, so the brief, the fee, the delivered pilot, and the client's decision all sit in one place both sides can open. A pilot shaped this way tests everything a free test claims to test, skill, communication, reliability, and adds the one thing a free test never tests: whether this client pays, promptly and without drama, which is the fact you most need before the main job.

Step 4. Put the pilot on a record, so the test and the decision are both visible

A test project fails as evidence when it lives in an email thread: the brief in one message, the files in another, the verdict, if it comes, in a call nobody wrote down. On a record, the pilot is a small job with the same states as a large one, steps saved as they complete, then a decision recorded by the client. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show the decision states a pilot moves through:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the accepted record as a test that ended in a recorded yes: status accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release state ok_to_release, 4 steps checked. The client did not just feel the work was good, they recorded the decision, with a decider and a date, which is exactly the artifact a hiring test should produce. The pending record shows the state you also need to be able to show: 5 steps checked, release state hold, work delivered and waiting on its decision, visible as waiting rather than lost. Run your pilot this way and either outcome is clean: a yes on the record starts the main job from the same page, and a no, or a silence that passes the decision date, closes the test with the delivered pilot and its fee already settled.

Step 5. Send the reply in this shape: yes to a test, no to a free project

The reply, word for word in shape: Thanks, I am glad you want to see the work up close before committing, that is sensible. I do not run full projects unpaid, because a finished piece handed over free stops being a test. Here is what I can do. Option one, a paid pilot: [the small piece], fixed fee of [amount], delivered by [date], on a shared record you can open as it progresses, and if you go ahead I will credit the fee against the main job. Option two, a free sample: [the capped excerpt or walkthrough], which shows my approach and standard but is not a usable deliverable. Either way I would need your decision by [date] so I can hold the slot. Notice what the shape never does: it never apologises for charging, never lectures the client about bad actors, and never leaves the free full project on the table as a third option to be negotiated back to. Clients running a real process pick the pilot, because it is plainly the better test. Clients who walk away from both options were not running one.

Honest limits

This page is general information about handling a test request, not legal or career advice: some industries and some large employers run standard unpaid assessments as a fixed hiring step, and whether to enter those processes at all is a judgement about that market and your alternatives, not a rule this page can set. A paid pilot tests willingness to pay a small fee; it cannot prove a client will pay a large final balance easily, which is why the main job still wants staged payments and acceptance stage by stage. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove the work is good, which is the client's judgement to record as acceptance, and it is that recorded decision, not the receipt alone, that makes a test settle anything.

Step 6. Read the answer as the real test result, and set your standing rule

The deepest information in this exchange is not in the pilot, it is in which option the client chooses. A client who pays a small fee promptly, judges the pilot on its merits, and decides by the agreed date has passed every part of the test that matters for the main engagement, and has done it before you risked real time. A client who insists the only acceptable test is the full project, free, usable, and open ended has also given you a complete result, about how scope, money, and decisions will behave on the main job, at the cost of one email instead of one project. Set the standing rule now and put it in your standard terms: test work is run as a small paid first stage on a record, free samples are capped excerpts that cannot be used as deliverables, and decisions land by a stated date. With the rule written once, the next request is answered in minutes, warmly, from the page, instead of being re-argued from your bank balance each time it arrives.

Frequently asked questions

A new client wants me to do a free test project before they hire me. Should I do it?

Not as a full free project. Run the three-mark check first: a genuine test is small compared with the job behind it, it tests skill rather than producing a usable deliverable, and the client can name who decides, by what date, and what the paid work looks like next. Then offer the two honest shapes. A tiny paid first stage, one small complete piece of the real work at a small fixed fee, delivered and decided by stated dates, on a job record both sides can open, with the fee credited against the main job if they proceed. Or a free sample that is capped so it can never be used as the deliverable, an excerpt, a walkthrough, or a low resolution version. A client who refuses both shapes has answered the test themselves.

How can I tell a real hiring test from free work in disguise?

Ask what the test produces and what happens after it. A real test produces evidence about you, your skill, your communication, your reliability, and its output is judged against a decision with a named decider and a date. Free work in disguise produces an asset, something the client can ship, publish, or build on without hiring anyone, and its aftermath is vague, no decider, no date, no described next stage. The fastest tell is the reaction to a capped sample or a small pilot fee: a client running a process accepts either at once, because both answer their real question, while a client after the asset argues for the full piece, at full quality, on the live brief, still free.

What should a paid pilot include, and what should it cost?

One small, complete piece of the real work, chosen so its quality is easy to judge on its own: the first section, the first screen, the first report. Price it as a small fixed fee, real money that needs no committee to approve, and state the delivery date and the decision date in the same note. Run it on a job record so the brief, the steps, and the client's decision sit in one place. Crediting the pilot fee against the main job when the client proceeds is a strong goodwill move: it costs you nothing with a client who hires you, and the pilot still paid for itself with one who does not.

What if the client says every other freelancer agreed to the free test?

Treat it as information, not pressure. It may even be true, and it changes nothing about the arithmetic: a usable project handed over free costs you the same whoever else donated theirs. The calm reply is that your test policy is a paid pilot or a capped sample, it is the same for every client, and it exists so the test stays a test, small, judged, and decided by a date. Do not criticise the freelancers who agreed and do not accuse the client of anything. A client with a genuine vacancy fills it with the best pilot result, not with the longest free queue, and a client selecting mainly on willingness to work free is selecting for the trait that predicts the rest of the engagement.

How does a job record help with a test project?

It turns the test into a small real job with visible states: the brief and fee agreed in writing, the pilot steps saved as they complete, and the client's decision recorded with a decider and a date instead of drifting in a thread. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, so a pilot is judged from the same page the main job will run on. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, run the pilot on one record, so the test, the fee, and the hiring decision all sit where both sides can check them: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related