The Closing File: A Client Offboarding Protocol for Independent US Design Studios
The work after the work
Most independent US design studios have a kickoff ritual. There is a scope document, a schedule, a shared folder, and a first call with careful questions. The ending often receives less ceremony. Files are sent, an invoice goes out, and the relationship drifts into silence. That silence is not neutral. It leaves ambiguity about acceptance, access, records, and future work.
For a one-person studio, offboarding is not administrative cleanup. It is a risk control, a relationship practice, and a business development step. FNAD encourages members to treat the close of an engagement as a defined phase with its own deliverables. The protocol below is deliberately modest. It can be run in a solo practice without new software, and it scales from a two-week identity project to a multi-month advisory engagement.
Why a closing file matters
A closing file is the studio's record of how an engagement ended. It answers four questions: Was the work accepted? What did the client receive? What did the client learn? What happens next? When those answers are written down, the studio is better protected against late disputes, informal requests that arrive months later, and the slow erosion of a good working relationship.
The protocol also supports repeat work. A client who receives a clear handoff, a short feedback request, and a respectful referral ask is more likely to return than one who receives only a final invoice. The aim is not to manufacture goodwill. It is to close the loop with the same care that opened it.
Phase one: confirm the finish line
Before files move and final invoices are issued, confirm acceptance in writing. The goal is to distinguish delivery from approval. A simple completion note can prevent the common problem of a client treating an open file share as an ongoing invitation for revisions.
Checklist:
- Compare delivered items against the signed scope and any approved change orders.
- Confirm in writing that deliverables have been received and accepted.
- State the final invoice amount and payment terms.
- Identify any remaining obligations on either side, including credits, licenses, or scheduled training.
- Set a date after which the studio will close the active project folder.
Email template: Completion confirmation
Subject: Completion and acceptance — [Project name]
Hello [Client name],
This note confirms that the final deliverables for [project name] were sent on [date] and match the approved scope dated [date]. Please reply to confirm receipt and acceptance. The final invoice for [amount] is attached and is due under the terms in our agreement.
After [date], I will move the project into the handoff and archive phase. If you expect additional work, we can discuss a separate scope at that time.
Regards, [Studio name]
Phase two: transfer knowledge, not just files
A folder of source files is not a handoff. The client often needs to know which files are final, which are working files, how brand assets should be used, and which accounts or licenses require action. For solo studios, a short handoff memo is often more valuable than a longer file index.
Checklist:
- Provide final files in the formats named in the agreement.
- Include a one-page handoff memo with file names, version dates, font and image licensing notes, and any usage limits.
- Transfer ownership or administrative access where the contract requires it.
- List credentials or accounts created for the project and confirm the revocation schedule.
- Offer a short recorded walkthrough or a 30-minute handoff call for complex systems.
- Confirm that working files are not part of the deliverable unless the contract says otherwise.
Email template: Handoff package
Subject: Handoff package — [Project name]
Hello [Client name],
Attached is the handoff package for [project name]. It includes the final deliverables, a file guide, licensing notes, and the access schedule for project accounts. Please review it within five business days and let me know if any item is missing from the agreed scope.
Unless you request otherwise, I will close the active project folder on [date]. The archive will be retained under the studio's records policy.
Regards, [Studio name]
Phase three: ask for feedback without overburdening the client
Feedback is most useful when it is short and timed close to the work. A five-question form is sufficient for most independent studios. Avoid long satisfaction surveys at the end of a project; they tend to measure fatigue rather than experience.
A workable set of questions:
- Did the final deliverables meet the brief as you understood it?
- Which part of the process was most useful to you?
- What could the studio have communicated more clearly?
- Would you work with the studio again or refer it to a colleague?
- May we quote your feedback in studio materials, with or without attribution?
Record the responses in the closing file. If a client raises a concern, respond with a specific next step rather than a general apology. If the concern is outside the agreed scope, say so plainly and offer a separate conversation.
Phase four: archive with intent
Archival is where solo studios often improvise. A consistent naming convention and retention note make later reference possible without turning the studio into a storage facility for every draft. The archive should preserve the contract, change orders, final deliverables, acceptance confirmation, handoff memo, and feedback. Working files can be retained for a shorter period if the contract allows.
Checklist:
- Name the archive folder with client name, project name, and close date.
- Store the signed agreement, change orders, final invoice, and acceptance note together.
- Record the retention period and the destruction date.
- Remove or suspend client access to shared drives and project accounts.
- Note any legal hold, confidentiality obligation, or industry-specific recordkeeping rule.
Phase five: make a respectful referral request
A referral request should arrive after the work has been accepted and the invoice has been settled, not in the same message as the final delivery. The request should be easy to decline and specific enough to be useful.
Email template: Referral request
Subject: A note of thanks — [Project name]
Hello [Client name],
Thank you for the opportunity to work on [project name]. If a colleague needs [specific service], I would be glad to be considered. There is no obligation, and I am happy to send a short capability summary if that would help.
I have also attached the closing file summary for your records.
Regards, [Studio name]
A simple closing calendar
Day 0: final delivery. Day 2: acceptance confirmation. Day 5: handoff package and access schedule. Day 10: feedback request. Day 30: archive complete and active access closed. Day 45: referral request, if appropriate.
Not every engagement needs every step. A small advisory project may require only acceptance, handoff, and archive. A larger brand system may justify a walkthrough call. The point is to make the close visible and repeatable rather than leaving it to memory.
For independent US designers, the closing file is a form of professional development. It turns a finished project into a documented relationship, and it gives the next conversation a firmer place to begin. FNAD members can adapt these templates to their own studio voice, but the sequence is worth keeping: confirm, transfer, listen, archive, and invite the next chapter.
