Direct answer
A kill fee is not a penalty. It is the price of the exit, set by stage, before anyone needs it.
Your client is asking for a kill fee clause, which is a good sign: they want the exit priced while everyone is still friendly. Set it wrong and two failures wait. Too low and a cancellation in week three leaves finished work unpaid while you turn down other work for a slot that vanishes. Too high and flat, with no link to work done, and the clause reads as a penalty the client will fight exactly when you need it. The working shape is simple: work already done is never part of the kill fee at all, it is owed at its agreed price. The kill fee itself is a separate, stated amount for ending early, and it steps down as the project advances, because the harm of an early exit is largest at the start. This page gives you the tier table, the arithmetic, and the clause to copy.
Updated November 17, 2026. First published November 17, 2026. The records quoted below are real and public, read back from the live service on November 17, 2026.
Step 1. Separate three amounts that a cancellation mixes together
Every early cancellation produces three different amounts, and a clean kill fee clause keeps them apart. Amount one is work done to the cancellation date: finished stages at their agreed prices, and the stage in progress for the steps actually completed. That amount is not a fee and it is not negotiable downward because the project ended; it is payment for value the client keeps. Amount two is the kill fee itself: a stated amount for the act of ending early, covering the slot you held, the work you turned away, and the restart cost of filling the gap. Amount three is deposits already paid, credited against the total so nobody pays twice. When a clause lumps all three into one percentage of the project price, it fails in both directions: cancel late and the percentage overcharges for a nearly finished job, cancel early and it underpays for the stage already built. Write the three amounts as three lines in the clause and on the final invoice, each with its own basis.
Step 2. Set the kill fee as tiers by stage, not one flat percentage
Price the exit by how far the project has travelled. A practical table for a staged project: cancel before stage one starts, the kill fee is the deposit only, kept in full, because no build work exists yet but the slot was held. Cancel during the first half of the stages, the kill fee is 25 percent of the remaining project price, on top of work done. Cancel during the second half, it is 15 percent of the remaining price. Cancel after the final stage is delivered and awaiting acceptance, there is no kill fee at all: the project price is due, because the work is done and ending the relationship does not unmake it. Adjust the percentages to your trade, but keep the shape: the fee applies to the remaining price only, never to work already done, and it falls as completion rises. That shape is what makes the fee defensible in the conversation where it matters: you can walk the client through the table and show that the later they cancel, the less the exit itself costs.
Step 3. Make the stage count a fact on a record, so the tier is never argued from memory
A tier table only works if both sides agree which stage the project was in on the cancellation date. 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 staged job moves through:
Accepted: the decision is on the record
- Status: accepted, decided_by client, decided_at 2026-10-16T14:31:51.146Z, release_hint ok_to_release.
- Steps: 4 steps total, 4 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Pending: checked, and still waiting on a decision
- Status: pending, release_hint hold.
- Steps: 5 steps total, 5 checked.
- aer1_version: draft-zambo-aer1-26.
- Open the handover or read its acceptance.json.
Read the accepted record as a stage that has closed: 4 steps, all checked, a client decision with a date. A cancellation after that point starts from a settled fact, that stage is done and payable in full. The pending record is a stage still open: work checked, no decision yet, which is exactly where tier arguments breed, because one side remembers the stage as nearly done and the other as barely started. Run each stage to an acceptance, or at least a dated handover the client can open, before the next stage begins. Then the kill fee calculation is three lines anyone can check: stages accepted at full price, the open stage for its completed steps, and the tier percentage on what remains.
Step 4. Write the clause in plain words, with notice and payment dates
Copy this shape and fill the brackets. Either side may cancel this project in writing. On cancellation, stages completed and accepted are payable in full, the stage in progress is payable for the steps completed to the notice date, and a kill fee of [25] percent of the remaining project price applies if cancellation falls in the first half of the stages, or [15] percent in the second half. Deposits paid are credited against the total. The cancellation invoice is payable within [14] days of the notice date, and the listed work done to that date, with its gaps named, transfers on payment. Four things in that clause do quiet work: cancellation is in writing so the date is fixed, the fee basis is the remaining price only, deposits are credited in the open, and transfer follows payment so the exit does not create a second dispute about files. If the client proposes their own kill fee wording, check it against the three amounts in step 1: any wording that makes work done part of the fee, or silent about deposits, needs those lines restored before you sign.
Honest limits
This page is general information about setting a kill fee, not legal advice: enforceability of cancellation amounts varies by place and by contract type, and a large project deserves a local review of the clause once. A kill fee also cannot create money in a client who cancels because they have run out of it; tiers and notice dates improve your position, they do not remove credit risk, which is why deposits and stage payments still matter. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove a stage was worth its price, which is why the clause prices stages in advance instead of arguing value after a cancellation.
Step 5. Offer the clause before the client asks, on the next quote
The client in this question did you a favour by raising the exit early. Take the hint permanently: put the tier table in your standard quote, one short paragraph, so every future client meets the price of cancelling at the same calm moment they meet the price of the work. Clients who plan seriously read a stated kill fee as professionalism, because it tells them you have been cancelled on before and handled it without drama. Clients who push for a zero kill fee are telling you something useful too: they want a free option on your calendar, and the honest answer is a smaller first stage or a larger deposit, not a free exit. Either way, the conversation happens at signing, in numbers, while it is still a design question instead of a dispute.
Frequently asked questions
My client wants a kill fee if they cancel the project early. How do I set one?
Keep work done out of the fee entirely, then tier the fee on the remaining price. Finished and accepted stages are payable in full and the stage in progress is payable for its completed steps; those are payment for work, not a fee. The kill fee itself is a stated percentage of the remaining project price only, higher early and lower late: for example 25 percent of the remainder in the first half of the stages and 15 percent in the second half, with no kill fee once the final stage is delivered. Credit deposits already paid against the total, fix the cancellation date by requiring written notice, and state that the listed work transfers on payment of the cancellation invoice. That shape is defensible because the client can check every line against the stage record.
Should a kill fee be a flat amount or a percentage?
A percentage of the remaining price, tiered by stage, beats both common alternatives. A flat amount ignores project size and timing: the same figure is trivial on a large project and punitive on a small one, and it costs the same to cancel in week one as in the final week, which no client will accept as fair. A percentage of the full project price double counts, because it charges a fee on work already done and paid for. A percentage of what remains falls naturally as the project advances, tracks the real harm of the exit, which is the unfilled slot and the lost remainder, and can be calculated by either side in one line from the stage table.
Does the client still pay for work done if there is a kill fee?
Yes. The kill fee is the price of ending early; it sits on top of payment for work done, it never replaces it. Stages completed and accepted are payable at their agreed prices, and the stage in progress is payable for the steps completed to the written notice date, because the client keeps that work and can hand it to a successor. If a proposed clause treats the kill fee as the total amount owed on cancellation, it is underpaying for finished work by design, and it should be corrected before signing: three lines, work done, kill fee on the remainder, deposits credited. The final invoice on a cancellation should show all three lines separately so the arithmetic can be checked at a glance.
When does a kill fee stop applying?
When there is nothing left to kill. Once the final stage is delivered, the project price is due for the work itself and an exit amount on top has no basis; the relationship can end, but the completed job is simply payable. The fee also falls away stage by stage in a well drawn table: highest while most of the project remains, lower in the second half, zero at delivery. State that endpoint in the clause itself, because a fee with no stated end reads as open ended and invites the argument that it was a penalty all along. The clean sentence is: no kill fee applies after delivery of the final stage.
How does a job record help set and collect a kill fee?
It fixes the one fact the whole calculation turns on: which stage the project was in, and what inside it was done, on the cancellation date. 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, and each stage can be accepted by the client on that record, so work done, the open stage, and the remainder are a checkable list rather than two memories. 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 staged job on one record, so if a kill fee is ever invoked, the tiers calculate themselves from the record instead of from recollection: 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
- How do I invoice for work a client cancelled halfway through?
- How do I write a contract for AI work so delivery can be verified?
- What payment terms should I put on my invoices so clients pay on time?
- My client will not give feedback and my deadline is passing. Should I keep working or stop?
- Do unused retainer hours have to roll over to the next month?
- Start with your problem: every problem in this directory, routed to its page