What to Keep, What to Shred: A Retention Calendar for Solo US Design Practices
Photo: Ggglover, CC BY-SA 4.0, via Wikimedia Commons
Records are an operational asset, and a liability
A design practice generates paper even when it feels paperless. Contracts, statements of work, invoices, payment records, client emails, revision approvals, tax filings, insurance policies, and portfolio releases accumulate in folders and cloud drives. For a solo studio, the absence of a records policy is rarely noticed until a dispute, an audit, or a move forces the issue.
A retention policy is not bureaucracy for its own sake. It serves two purposes. It preserves the records a studio needs to defend its work, collect payment, and satisfy tax and legal obligations. It also creates a defensible process for destroying records that no longer serve a purpose. Without that process, the studio carries unnecessary risk and unnecessary clutter.
This article offers a practical starting point for independent US designers. It is not legal advice. Retention requirements vary by state, contract, and circumstance, and a studio with unusual exposure should consult an attorney and accountant.
Start with the legal minimum, then add business need
In the United States, there is no single federal retention period for all business records. Tax rules, employment rules, contract statutes of limitations, and state requirements interact. The IRS generally recommends keeping tax records for three to seven years depending on the circumstances. Many business advisers suggest a seven-year default for financial records. Contracts may need to be kept for the period of the statute of limitations for breach, which varies by state.
The practical approach is to set a baseline schedule that satisfies the most common requirements, then add longer periods for records with continuing value. Intellectual property records, business formation documents, and insurance policies often deserve longer retention than ordinary correspondence.
A practical retention schedule
The following schedule is a reasonable default for a small US design studio. It should be adjusted for state law, contract terms, and the nature of the work.
| Record type | Suggested retention | Trigger |
|---|---|---|
| Business formation documents, licenses, EIN records | Permanent | Keep for life of business |
| Contracts, statements of work, amendments | 7 years after project completion or termination | Longer if a dispute or claim is open |
| Final deliverables and approved files | 7 years after project completion | Longer for portfolio or copyright evidence |
| Invoices, payment records, bank statements | 7 years | Align with tax and audit needs |
| Tax returns and supporting documents | 7 years | Keep longer if unfiled or disputed |
| Payroll and contractor records, including 1099s | 7 years | Check state and federal requirements |
| Client correspondence and approval emails | 3 to 7 years after project completion | Keep longer if it supports a contract or dispute |
| Insurance policies and claims | 10 years after expiration or final claim | Keep current policies indefinitely |
| Copyright registrations, trademarks, IP assignments | Permanent | Keep for life of rights |
| Portfolio releases and model releases | Life of use plus 3 years | Review at end of campaign or project |
| Employment records | 3 to 7 years after separation | Check state requirements |
| Legal hold records | Until hold is released | Never purge during litigation or audit |
A studio should also keep a simple retention log. The log does not need to list every file. It should record the policy, the date of the last purge, and any records placed on legal hold.
Format and storage
Retention is not only a question of time. It is also a question of format. Final contracts should be stored as searchable PDFs. Signed agreements should be retained in a format that preserves signatures and metadata. Working files may be kept in native format when they have ongoing value, but they should not be the only copy of a final deliverable.
A practical storage approach follows the familiar backup principle: keep at least three copies, on two types of media, with one off-site. For most solo studios, that means a local drive, a cloud backup, and a versioned archive. Access should be limited to the designer and any trusted collaborator who needs it. Sensitive client files should be encrypted at rest and in transit.
File naming matters more than many designers expect. A consistent pattern—client, project, document type, date—makes retrieval possible years later. A records policy that cannot be searched is only marginally better than no policy at all.
The annual purge ritual
Set one date each year for a records review. Many studios use the start of the calendar year or the end of the fiscal year. Block two hours. Review the retention schedule, identify records that have passed their retention period, and move them to a purge queue. Do not delete immediately. Allow a short review window in case a project, claim, or client relationship requires the file.
When the review window closes, destroy the records securely. Digital files should be deleted from all backups according to the studio's backup cycle. Paper should be shredded. Record the purge date and the categories destroyed in the retention log. The record of destruction is itself useful evidence that the studio follows a consistent policy.
The ritual should also include a check for legal holds. If the studio is in a dispute, under audit, or has received a preservation notice, do not purge any related records. Suspend the schedule for those files until the matter is resolved.
When to call counsel
A retention schedule is a default, not a substitute for advice. A studio should consult an attorney when it receives a demand letter, faces a contract dispute, receives a tax notice, or is unsure whether a record must be preserved. The cost of a short consultation is usually far lower than the cost of destroying a document that later proves relevant.
A lighter studio, with a clearer record
Records retention is not the most visible part of running a design practice, but it is part of the infrastructure that makes independent work sustainable. A modest policy reduces the risk of losing important documents, shortens the time spent searching for old files, and provides a defensible answer when someone asks why a record was kept or destroyed. For a solo US studio, that is a practical advantage worth the two hours it takes to set up.