How to offboard a client cleanly
A good closeout protects both sides by making the final state of the project explicit.
Confirm that delivery is actually complete
Offboarding should begin only when the agreed work has reached the point defined in the proposal, statement of work or contract. Record what has been delivered and what the client has approved. If a small item is still open, list it instead of silently treating the engagement as complete. This keeps the closeout document aligned with the real project rather than an idealized version of it.
Resolve the commercial side
Check whether the final invoice has been issued, whether a balance is still due and whether credits, expenses or approved change orders remain unresolved. The checklist is not an accounting system, but it prevents a common operational mistake: closing the project folder while money is still outstanding. For projects with milestone billing, the Deposit & Progress Payment Schedule Calculator can help structure payments earlier in the engagement.
Transfer files and ownership deliberately
Identify the final deliverables, source files, documentation and account ownership that the client should receive. A website project may include design sources, code repositories, domain ownership and analytics access. A photography engagement may include galleries, usage licences and archived originals. A clean handover tells the client where each item lives and which party is responsible for keeping it after closeout.
Review access as a security task
Temporary access should not become permanent by accident. Review shared accounts, collaborator seats, cloud folders, project-management tools, hosting systems and any other service used during delivery. Remove access that is no longer required, but do not revoke something the client still needs to complete acceptance or download deliverables. Never copy passwords or recovery codes into this checklist. Use secure delegated access or credential-management methods instead.
Archive enough context for the future
The provider should retain the records required by its normal business, tax, warranty and backup policies. That can include the signed scope, approvals, final files, invoices and a concise note explaining the final state. Good archiving makes future support easier because the next person does not have to reconstruct the engagement from email history.
Plan the relationship after delivery
Offboarding does not have to mean disappearing. Decide whether a testimonial request, maintenance offer, renewal reminder or simple check-in is appropriate. A future date turns “we should follow up sometime” into an operational action. The Follow-up Assistant is designed for recurring lead, quote, invoice, review and reconnect reminders.
Use the checklist as a repeatable process
This generator keeps working inputs locally in the browser and produces a portable checklist that can be copied, printed or downloaded as standalone HTML. Example mode is isolated from saved real inputs. Print uses the site-wide output-only print standard, so the browser should print the generated checklist rather than navigation, SEO text or form fields. Keep confidential credentials outside the tool and maintain authoritative records in your own backup system.
Frequently asked questions
What belongs in a client offboarding checklist?
Typical closeout steps include final deliverables, approval, final billing, source files, access review, ownership transfer, archiving and a future follow-up date.
Should passwords be included in the checklist?
No. Use secure account invitations or credential-management methods and keep passwords, recovery codes and secrets out of the generated document.
Does this tool revoke access automatically?
No. It creates a local checklist only. Access changes must be completed in the relevant service or account.