Direct answer

Cancelled is not free, and a file dump is not a handover. Send the work listed, priced, and labelled by state.

The project is dead and the client wants everything, including the half-finished parts, sent over today. Two mistakes wait in that request. The first is sending a dump: a folder of mixed finals, drafts, and working files with no statement of what is finished, what is part-done, and what was never checked, which hands the client material they can misuse and hands you the blame when the unfinished parts fail. The second is sending it before the money question is settled, because once the files move, your leverage and the record of what the cancellation covered both move with them. This page gives you the order: sort the work into three piles by state, price the handover against the agreement and the delivery record, send a listed handover the client can accept, and write the clause that settles this before the next job starts.

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

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

Step 1. Sort the half-finished work into three piles, by state, before you send anything

Pile one is finished work: stages that were completed and, ideally, accepted before the cancellation. These are deliverables in the ordinary sense, and the client who has paid for them, or pays the cancellation invoice, receives them as finals. Pile two is the part-done stage, the stage that was in progress when the cancellation landed. This pile is the dangerous one. It is not a deliverable yet: it may contain placeholders, unchecked figures, and steps that were never run. It can still be worth sending, because the client or their next hire may build on it, but only labelled as what it is: where it stops, what remains undone, and what was never checked. Pile three is the raw working material underneath both: drafts, notes, working files, and intermediate versions. Raw material is not a deliverable by default; it is the means of production, and it moves only if the agreement says so or as a separately priced item. Write the three piles down as an inventory before anything is sent. The inventory is the handover, and everything else on this page hangs off it.

Step 2. Price the handover before the files move, not after

A cancellation does not erase the value of work already done. The amount the handover rides on has three parts, each checked against the agreement rather than invented in the moment. First, the finished stages at their agreed prices, including any stage the client already accepted. Second, the part-done stage, billed for the work actually in it: completed steps at the stage rate or the hours recorded, not the full stage price for a stage that never finished, and not zero for work the client now wants to keep. Third, any cancellation amount the agreement itself sets, a kill fee or notice amount agreed at signing, credited with deposits already paid. If the agreement is silent on cancellation, the first two parts still stand on the record of work done; the third is a negotiation, and it is far easier before the files move than after. Send the cancellation invoice with the inventory attached, and make the sequence plain in one line: on payment, the listed work transfers. That sequence protects both sides: the client knows exactly what payment buys, and you are never chasing money for files already gone.

Step 3. Send a handover the client can check and accept, with the gaps named on it

The difference between a dump and a handover is the record that travels with the files. 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 layer a cancelled job should close on:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Build the cancellation handover the same way: one link carrying the inventory, each finished stage with its record, the part-done stage with its stopping point and its not-checked list stated in words, and the next steps a successor would need, written for a stranger. The accepted record above is the state you want the cancelled job to reach: the client has seen exactly what the handover contains and has accepted that set, gaps included, as the closing delivery. The pending record is the state to avoid leaving behind: work checked, no decision recorded, which is how a cancelled job turns into a later argument about what was sent and what it was worth. If the client will not accept, send the handover anyway and let the pending state sit on the record as the dated fact of their silence; do not chase the argument into a fresh file dump.

Step 4. Hold the two lines that keep a cancellation clean: rights and raw files

Two things are routinely smuggled into a cancellation handover, and both belong in writing before the transfer. The first is rights: unfinished work transfers for use only as the agreement provides, and the ordinary line is that use rights in the part-done material pass on payment of the cancellation invoice, not on receipt of the files. If the client wants to hand your half-finished stage to another freelancer to complete, that is a reasonable thing to allow once paid, and saying so plainly costs you nothing. The second is pile three. If the client wants the raw working files as well, price them as their own line, with the same rule as any raw-file delivery: finals are the deliverable, raws are a separate item with their own terms. What you never do is include raws silently in the dump, because a silent inclusion reads later as though they were always part of the deal. One short written summary closes the job: the inventory, the amount, the payment-then-transfer sequence, the rights line, and the raw-file line. Five lines, sent before the files, settle nearly every cancellation fight before it starts.

Honest limits

This page is general information about handling a cancellation, not legal advice, and it does not read your agreement for you: a signed contract with its own cancellation and ownership clauses governs over anything here, and a large or disputed cancellation is worth a lawyer hour. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove half-finished work is correct, complete, or safe to build on, which is exactly why the part-done pile carries its gaps in words. Zambo never holds funds and cannot make a client pay a cancellation invoice; the record makes the amount checkable, and the payment-then-transfer sequence keeps the leverage where it belongs.

Step 5. Write the cancellation clause into the next agreement, while this one is fresh

Every cancelled job teaches the same clause, and it is five short lines long. Cancellation by either side is in writing, with a stated notice date. Work done to that date is invoiced from the record, finished stages at their prices and the stage in progress for the steps completed. A cancellation amount, if you charge one, is a stated figure or percentage agreed at signing. The listed work, finished and part-done with its gaps named, transfers on payment, and raw working files are a separate priced item. Client feedback and acceptance windows keep running to the notice date, so a stage accepted before cancellation stays accepted. With that clause in place, the next cancellation is an administration task: sort, price, hand over, close. Without it, it is this page, improvised under pressure, again.

Frequently asked questions

My client cancelled the project and wants all the half-finished work handed over. What do I send?

Send a listed handover, not a file dump, and send it on payment. Sort the work into three piles first: finished stages, which transfer as finals; the part-done stage, labelled with exactly where it stops and what was never checked; and the raw working files, which move only if the agreement says so or as a separately priced item. Attach the inventory to a cancellation invoice covering the finished stages at their agreed prices, the part-done stage for the work actually in it, and any cancellation amount the agreement sets, credited with deposits paid. The handover itself should carry the record of each stage and name its gaps, so the client accepts a stated set of work, in a stated state, instead of receiving a folder nobody can later describe.

Does the client have a right to my unfinished work if they have not paid for it?

Not by default, and the agreement decides most of it. The ordinary position is that work transfers for use on payment: a client who cancels owes for the work done to the cancellation date, and the listed work, finished and part-done, moves when that invoice is paid. If your agreement promises delivery of work in progress on cancellation, or was silent while you sent drafts freely all along, the argument gets harder, which is why the payment-then-transfer sequence and the raw-file line belong in writing at signing. Until payment, you can share a view of the inventory and the record so the client can check what exists, without handing over usable files.

How do I price a stage that was only half finished when the client cancelled?

Price the work that is actually in it, from the record, not the full stage price and not zero. If the stage was priced as a block, count its completed steps or milestones and charge that share; if you work hourly, the recorded hours to the cancellation date are the figure. Then add any cancellation amount the agreement itself sets, and credit every deposit and part payment already made, shown as its own line so the client can follow the arithmetic. The part-done stage is also labelled as unfinished when it transfers: the price buys the work in its stated state, gaps named, not a finished deliverable at a discount.

What if the client wants to give my half-finished work to another freelancer to finish?

That is usually the best ending for both sides, and the handover is what makes it work. Once the cancellation invoice is paid, the part-done stage transfers with its inventory, its stopping point, and its not-checked list, so the successor starts from a stated state instead of guessing which parts of a folder are safe to build on. Write the next steps into the handover as you would for any handover: what remains, in what order, and what to re-check first. What the successor produces from there is their work and their record; your record closes at the state you handed over, which is exactly the boundary that keeps a later failure in the finished job from being laid on your half.

How does a job record help when a client cancels mid project?

It turns the cancellation from an argument about memory into a check of a stated set. 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 the finished stages, the steps inside the part-done stage, and the gaps are already listed before the cancellation invoice is written, and the client accepts the closing handover on that same record. 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 your next job on one record from the first step, so a cancellation at any point is a sort, a price, and a handover instead of a reconstruction: 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