Start by understanding what is changing
A client may cancel because priorities have shifted, a budget has changed or the project is no longer needed. Whatever the reason, respond to the decision before debating its consequences. A brief acknowledgment keeps the conversation constructive: confirm that you understand they want to stop the project, then ask when they expect work to cease and whether they need anything delivered before that point.
Clarify what “cancel” means in practice. Is the project ending immediately, pausing for an uncertain period or changing into a smaller assignment? These options can affect the work you do next. Until you have a clear answer, avoid continuing with substantial new work simply to finish what you started. If you are the one who needs to end the project, give the client the same clarity: explain what you can still complete, what you cannot and when your involvement will end.
Keep the first exchange focused on facts rather than fault. You can express disappointment without asking the client to defend their decision. A calm opening makes it easier to address the harder questions: what has been done, what remains unpaid and what happens to the files.
Prepare a clear record of work completed
Before discussing a final payment, make a concise inventory of the project. Compare the agreed scope with the work completed so far. Include milestones reached, drafts or concepts produced, meetings held, revisions made and materials awaiting client feedback. Distinguish finished deliverables from work in progress; treating every draft as a completed deliverable can create confusion.
Gather the relevant proposal, agreement, approved changes, invoices and key messages in one place. The goal is not to build a case against the client. It is to give both sides a shared account of what happened. A simple status summary might group items as completed and delivered, completed but not yet delivered, and not started. Note any expenses or outside services only where they are relevant to the project terms.
Be specific about value without overstating it. Instead of saying that a project was nearly done, identify the actual tasks and decisions that moved it forward. This helps a client understand why work completed before cancellation still needs to be discussed, even if the final product will not be used.
Discuss payment and handoff as separate decisions
Review the agreement before proposing a closeout amount. Look for payment milestones, deposits, cancellation terms, approved additional work and any conditions for delivering files. Then explain your proposed final invoice in plain language, connecting each amount to an agreed milestone or identifiable work. If the terms are unclear, say what you believe is reasonable and invite the client to identify anything they see differently. Avoid presenting an uncertain entitlement as a settled fact.
Payment and file handoff are related, but they are not the same conversation. List what you can provide: for example, approved exports, working files, research notes or an organized folder of project materials. State the condition of unfinished items so nobody mistakes an exploratory draft for production-ready work. Check the agreement before making promises about editable files, usage rights or ownership; these details can vary between projects.
A closeout can also include practical decisions that cost little but prevent frustration. Agree on where files will be sent, whether shared access will remain open and who will handle subscriptions or third-party assets connected to the work. If there is a disagreement about payment or rights, keep the handoff discussion precise rather than using access to files as an improvised bargaining tactic.
Put the outcome in writing
After a call, send a short recap that records the cancellation date, the last work to be done, the deliverables to be handed over, the proposed or agreed final payment and any outstanding questions. Separate confirmed decisions from items still under discussion. This gives both people a chance to correct misunderstandings while the conversation is fresh.
If the client disputes your account, ask which specific item they see differently. A focused question about a milestone, revision or invoice line is more useful than a long exchange about whether the project was worthwhile. You can update a factual mistake without dismissing the work you completed. When agreement is difficult, pause before sending a reactive reply and return to the scope and documented decisions.
Close the project once the remaining steps are complete. Confirm receipt of the final materials, send any agreed invoice and remove or transfer access as appropriate. An orderly ending protects your time and gives the client a usable record, whether or not the original project reached its intended finish.
Use the experience to improve the next agreement
Afterward, note where expectations were unclear. Did the agreement define what happens if a project stops between milestones? Was the distinction between final files and working files understood? Could shorter approval stages have made progress easier to verify? These questions are more useful than trying to design terms around one difficult conversation.
For future projects, consider describing cancellation and pause procedures alongside scope and payment terms. Define when work should stop, how completed work will be assessed, what a final handoff may include and how changes will be approved. Clear terms cannot prevent every disagreement, but they give both parties a starting point when plans change. The immediate goal is simpler: discuss this cancellation with care, document the work honestly and leave as little unresolved as possible.
