THE SHORT ANSWER
Ending a contract can stop future work while leaving payment, confidentiality, intellectual-property permissions, return duties and dispute terms in place. Read the survival clause together with each obligation and the termination provisions. Record who must do what, when it starts, when it ends and what evidence will show completion.
The project is over. You have sent the goodbye email, archived the folder and mentally buried the agreement. Then someone asks you to delete files, keep a secret, help the replacement supplier or stop using a logo.
Welcome to the contract afterlife. A survival clause identifies terms intended to keep operating after termination or expiry. The useful question is less theatrical: which duties and rights continue, for whom, and until when?
Download the one-page Contract Zombie Checklist (PDF). It works on paper without an account, upload or purchase. The worksheet records obligations; it is not a determination that every listed term is enforceable.
Three things that are easy to confuse
| Event | What it tells you | What it does not settle by itself |
|---|---|---|
| You stop doing new work | Work has paused or ended in practice | Whether the agreement was validly terminated |
| The term expires or termination takes effect | A contractual ending event has occurred | Whether outstanding invoices, licences or other duties end too |
| You finish an exit task | One identified obligation is complete | Whether every continuing obligation has expired |
If you still need to calculate the closing bill, start with the cancellation-invoice guide. This page is about what remains after the ending decision, rather than repeating that calculation.
Search beyond the paragraph called “Survival”
Read the ending clause, the survival list, the underlying clauses, definitions and any linked schedules. Search for words such as survive, after termination, accrued, expiry, return, retain and perpetual. A search is a locator, not a substitute for reading the surrounding text.
The UK government's Short Form Contract, version 1.5A, checked on 23 October 2026, gives a concrete example. It lists continuing clauses and also includes terms intended to continue expressly or by implication. Its exit provisions separately address assistance with handover and repayment of certain advance charges for undelivered work.
That is one public-procurement template, not a universal rule for every agreement. It shows why a numbered list may not answer the entire question. Conversely, a missing survival paragraph does not prove every debt, right or duty disappears; the actual term and applicable law still matter.
Meet a fictional contract's survivors
Imagine a fictional website project ends on 30 November. Assume its validly agreed terms provide the following. These are invented terms for the exercise, not recommended default drafting.
| Survivor | Fictional wording in practical terms | What the exit record should say |
|---|---|---|
| Final payment | Approved completed work remains payable, due 15 December | Freelancer sends final itemized invoice; client confirms any dispute separately |
| Confidentiality | Defined confidential information stays protected for two years after termination | Record the covered information and 30 November two years later as the stated end date |
| Background-code licence | A licence for incorporated pre-existing code continues with the delivered site | Keep the licence and its conditions with the handover pack |
| Return and deletion | Client material must be returned or deleted within 14 days, subject to stated lawful-retention exceptions | Identify systems, responsible person, due date and what must be retained separately |
| Exit assistance | Up to four hours of paid handover help on request within 30 days | Record request window, rate, contact and actual time used |
“Everything survives forever” would lose the distinctions that make this useful. The confidentiality duty has a duration. The deletion task has a deadline. The licence is permission subject to conditions. The invoice is a debt with its own due date.
For portfolio use, a continuing licence to run a website is not necessarily permission to publish private client material. Check the NDA and portfolio guide.
Fill out the Contract Zombie Checklist
Use one row per obligation or right. If a clause contains two different time limits, split it into two rows.
- Exact reference and duty: clause, schedule, document version and a plain-language description.
- Owner: who owes the duty, and who will actually carry out the task.
- Trigger and timing: termination, expiry, disclosure, payment or another event; then the deadline or duration.
- Action and evidence: return receipt, paid invoice, access-transfer confirmation or retained licence copy.
- Open question: missing date, unclear definition, conflicting clause or disputed legal effect.
Use “unclear” when the text is unclear. An invented expiry date makes a neat spreadsheet and a poor decision.
Do not run a blanket deletion ritual
Before deleting, reconcile return/deletion wording with retention exceptions, legal record-keeping, backups and any dispute-preservation duties. Document what is kept, why, who can access it and when it can be reviewed for deletion. Do not assume keeping a copy for your convenience is authorized, or that a deletion instruction overrides every legal requirement.
Also check access separately: removing a login does not prove every copy was deleted, and deleting a local folder does not transfer ownership of the client's accounts. The website handover checklist can help with that practical distinction.
Send an exit confirmation with the remaining tasks
We understand [agreement] ends on [date] under [clause]. Our remaining-task record lists [payment], [handover], [return/deletion with stated exceptions] and [other continuing duties]. Please confirm the responsible contacts, deadlines and any differences from your understanding. Please also clarify [specific unresolved wording]. This list is intended to organize the exit, rather than change or waive the agreement's terms.
Do not label the message a mutual release unless that is the agreement you actually intend to make. A routine handover record and a negotiated settlement have different jobs.
When an AI first pass helps
Ask it to produce an obligation register with exact passages, owners, triggers and durations, and to mark uncertainty rather than fill gaps. Verify every row against the complete document. An AI review cannot carry out the exit, guarantee that it found every survivor, or decide a contested enforceability question.
The goal is pleasantly boring: a closed project with a short, accurate list of what is still alive.
Put your own contract in context.
Starting notes from this guide are included; edit them before submitting.
Review my contract · $1