The last week of a project is where freelancers quietly lose money. The work is done, the client has gone half-quiet, and you are already mentally on the next thing — so the final invoice slips, the file handoff happens across three scattered emails, and nobody asks for the testimonial. When you offboard a client without a written sequence, the damage is rarely dramatic. It is an unbilled change request, an admin password you still hold two years later, and a referral that never got requested.
Offboarding is a process, not a mood. Below is the sequence, the decision rule for access transfer, a worked week-by-week example, and an honest note about where a spreadsheet stops carrying the load.
The Four Ways Offboarding Goes Wrong
Almost every bad handoff is one of four failures. Name them before you build the checklist, because each one needs a different control.
- Revenue leak. Out-of-scope requests absorbed without a change order. A final invoice issued weeks late, or never. A retainer that auto-renews when the client thought it ended, or lapses when you assumed it continued.
- Asset loss. Layered source files, raw footage, tracked spreadsheets and prompt libraries that live only in your tools. The client gets the export and not the original, then pays someone else to rebuild it.
- Access risk. You still hold admin on their hosting, ad account, payment processor or CMS long after the engagement closed. That is a liability for both sides, and it is the item people forget first.
- Goodwill loss. No closing conversation. No written sign-off. No specific ask for a testimonial or referral while the client still remembers the outcome.
A checklist that only covers file delivery fixes one of four. You want all four in one pass.
Run Offboarding as Five Stages
1. Freeze and reconcile scope
Declare a scope freeze in writing the moment the last deliverable ships. List every requested item against the original agreement and mark each one delivered, descoped, or out of scope and billable. Anything ambiguous gets resolved now, while the client is still engaged, not at invoice time.
2. Package the assets
Build one folder with a flat, boring structure: 01-final-deliverables, 02-source-files, 03-credentials, 04-documentation, 05-contract-and-invoices. Include a one-page read-me that says what each folder holds and what software opens it. Export from your tools into formats the client can actually use without your subscription.
3. Transfer access and revoke your own
Every credential gets moved, removed, or explicitly retained. No fourth option. Details below.
4. Get approval in writing
Send a short acceptance email listing the deliverables and asking for a plain confirmation that the work is received and complete. One reply is enough. Without it, you are invoicing against your own opinion that the job is done.
5. Bill, then name the next engagement
Final invoice goes out within 48 hours of written approval. In the same week, propose the next logical piece of work with a date attached.
How to Offboard a Client in One Week: A Worked Example
Say you are a freelance designer finishing a $6,000 brand identity build, half paid up front. Two extra requests came in mid-project: a pitch deck template and a second logo lockup. Here is the week.
Monday. You send the scope freeze email. It lists eleven agreed deliverables as complete, plus the two extras logged at $450 and $300. The client agrees to one and asks you to drop the other. Your final invoice is now $3,000 plus $450, and you know that on day one instead of day twenty.
Tuesday. You package the folder. Final logo files in five formats, working source files, the font license documentation with the client’s own license key, and a two-page usage guide. Total time: ninety minutes, because you named files properly during the project.
Wednesday. Access transfer. Their cloud drive ownership moves to their account. You are removed from their brand asset tool. You keep read access to one shared folder for thirty days for warranty fixes, which you state in writing with the revocation date.
Thursday. Acceptance email goes out. The client replies confirming receipt, which is your sign-off record.
Friday. Invoice for $3,450 at net-15. Same email thread, separate message: a twenty-minute closing call booked, and a proposal for a brand rollout review in ninety days with a fixed fee. Three things closed, one thing opened.
The whole sequence is five short tasks spread over five days. What makes it work is that each one is triggered by the previous one, not by remembering.
The Access Transfer Decision Rule
Use one rule for every credential, tool and shared folder connected to the engagement. Ask: does the client need to own this, or do I still need it?
- Transfer anything the client will operate or pay for: hosting, domains, CMS admin, ad accounts, analytics, anything billed to their card.
- Revoke anything you no longer need. This is the default. If you cannot state a reason to keep access in one sentence, remove it today.
- Retain with written consent only when there is a defined support window. Name the systems, name the reason, name the end date. Put the revocation date in your calendar the same hour you write it.
Two practical constraints. Never move credentials by pasting them into an email thread; use the client’s password manager or a share link that expires. And check ownership, not just access — being an admin on an account someone else owns is not the same as the client owning it.
When something goes wrong here, it is usually a tool nobody claimed: a scheduling app, a stock media subscription, a form builder you set up on your own card. Cancel it or move billing on the same day you hand over, and tell the client which one you did.
Close the Money Before You Close the Relationship
Final invoices behave worse than mid-project invoices, because the client no longer needs anything from you. Shorten the window. Net-15 on a closing invoice is reasonable and easy to justify. Send one polite reminder at day ten and a direct one at day twenty, referencing the acceptance email the client already sent you.
Do not improvise leverage. Whether you can withhold files, access or licenses when payment is late depends entirely on what your contract says, so read it before the situation is live rather than after. If your agreement is silent on it, that is the clause to fix in your next one.
Then ask for goodwill while the outcome is still fresh. On the closing call, make three asks in order: confirm the work is complete, answer one specific testimonial question such as what changed since the project started, and name two people who have the same problem they had. Vague asks get vague answers. If you want more on the ethics and mechanics of that conversation, the Cursiqa blog covers referral requests that do not pressure the client.
Where a Spreadsheet Stops Being Enough
A single tracker tab with one row per closing project and columns for each stage will carry a solo freelancer a long way. It stops being enough at four predictable points.
- More than one person holds credentials, so revocation depends on someone else remembering.
- You are closing several engagements a month and the manual checks compete with delivery work.
- Subcontractors had access, which means your offboarding has to cascade to them.
- The client works in a regulated environment and needs an evidence trail, not your word.
At that point you need a password manager with an audit log, a ticket per closure, and contract templates that define the support window. Be honest about the limit: a spreadsheet records intent. It cannot enforce a revocation date or prove one happened.
If you would rather start from a built sequence than a blank sheet, the Client Offboarding, Handoff & Renewal Kit packages the stages, the access rules and the closing templates into something you can run this week. You can also browse the rest of the Cursiqa workbook shop if pricing or pipeline is the tighter constraint right now.