6 primary records-management, privacy, and tax sources reviewed
4 fields required on every retention-schedule entry
September 24, 2026 source verification date
Key Takeaways
- A retention schedule names each record type, how long it is kept, where it lives, and who is allowed to destroy it; without that schedule, delegation becomes guesswork.
- Retention is not the same as indefinite storage. Keeping records past the schedule increases breach exposure and discovery burden without adding legal protection.
- Destruction has two parts, the act and the proof; a disposal log that records what was destroyed, when, by whom, and how is the difference between a policy and a claim.
- Delegating destruction requires separation between the person who classifies a record and the person who erases it, plus a hold process that stops deletion when a dispute or audit begins.
- The assistant should be able to propose a record for disposal, but a named owner should approve it before anything is permanently removed.
Published September 24, 2026.
Why retention belongs in the delegation brief
Founders delegate document handling long before they write a records policy, and the result is a shared drive that grows without rules. Files are kept because deleting them feels risky, and the assistant has no basis for deciding what can go. That default is expensive. It enlarges the collection that a breach could expose, lengthens the material a dispute can reach, and turns a simple archive into a liability. A retention schedule is what lets a founder delegate records work with confidence.
This review sets out how to build a small-team retention schedule, how to hand destruction to an assistant without losing control, and how to prove that disposal happened. It is grounded in public records-management, privacy, and tax guidance and is written for founders and owner-operators. It is a general framework, not legal advice, and it does not replace advice from a qualified professional on the business's specific obligations.
What a retention schedule contains
A retention schedule is a table, not a narrative. Each row describes one record type and answers four questions: how long the record is kept, where it is stored, who owns the decision to destroy it, and what the trigger for the clock is. The trigger matters as much as the period. Some clocks start when the record is created, others when the relationship ends, and others when a tax year closes. A schedule that lists only a number of years is incomplete because nobody knows when to start counting.
Start by grouping records into a small number of families rather than listing every file. Common families for a small business include tax and accounting records, contracts and engagement letters, employment and contractor records, customer and client records, vendor records, insurance and corporate records, and marketing records. Each family gets a default period and a named destroyer. The grouping keeps the schedule short enough that an assistant will actually use it.
Retention is not indefinite storage
The instinct to keep everything is understandable and wrong. U.S. tax guidance describes how long records should be kept to support a return and notes that some records, such as those for property, are kept longer because they establish basis. It does not say to keep everything forever. Records-management guidance from the National Archives and Records Administration describes retention as a lifecycle with a disposition step, and privacy guidance from the Federal Trade Commission expects businesses to dispose of personal information they no longer need.
The practical rule is to keep what a stated obligation requires, keep what the business genuinely uses, and dispose of the rest on a schedule. Keeping records without a purpose is not neutral. It increases the cost of a breach and the scope of a legal hold. The security tradeoff is a recurring theme in delegated work, and the pattern is examined in our review of customer data protection in delegated support.
A minimal schedule for a small team
The table below is a starting point, not a legal standard. Periods should be confirmed against the business's jurisdiction, industry, and accountant's guidance.
| Record family | Typical clock | Common period | Destroyer |
|---|---|---|---|
| Tax returns and supporting schedules | Tax year close | 7 years | Named finance owner |
| Employment tax and payroll records | Tax year close | 4 to 7 years | Named finance owner |
| Contracts and engagement letters | Relationship end | 6 years plus current | Founder or counsel |
| Customer and client records | Relationship end | As needed, then dispose | Data owner |
| Vendor and procurement records | Relationship end | 7 years | Finance owner |
| Insurance and corporate records | Permanent or long | Life of entity | Founder |
| Marketing and lead lists | Consent expiry | Until consent withdrawn | Marketing owner |
Two design choices make the schedule usable. First, the destroyer column should name a role, not a person, so a change in staffing does not orphan the duty. Second, the schedule should include a hold column or a separate hold list, because litigation, audit, or an investigation freezes the clock. An assistant needs to know that a hold exists and that destruction is paused while it does.
Delegating destruction without losing control
Destruction is the step where delegation needs the most care. The person who decides a record may be destroyed should not be the only person who erases it. A simple two-step rule works: the assistant proposes a list of records that have reached the end of their retention period, and a named owner approves the list before any permanent deletion. The approval can be fast, but it should be explicit and recorded.
The mechanics of destruction matter too. Paper records should be shredded or delivered to a bonded destruction service. Digital records should be deleted from live systems, from backups where the retention schedule permits, and from personal devices and shared folders. Public guidance on media sanitation from the National Institute of Standards and Technology describes how the method should match the media, because overwriting a file is not the same as sanitizing a drive. The assistant can run the process, but the method and the vendors should be chosen by the owner.
The disposal log is the proof. For each destruction event, record what was destroyed, the date, the method, the approving owner, and where the confirmation lives. A log converts "we delete old files" into evidence that can be shown during a review. Because the log itself often contains sensitive information, it should be treated as a controlled record with its own access list.
Where retention meets confidentiality
Records often contain trade secrets, customer data, or contract terms, and the retention question cannot be separated from the confidentiality question. An assistant with access to a retention queue sees the shape of the business's records even if the contents are masked. That access should be governed by the same least-privilege and access-review discipline used elsewhere. The protection of confidential business information in delegated work is examined in our review of trade secret protection in delegated work.
One useful pattern is to let the assistant work from metadata and proposals rather than full content. The assistant can flag records that have reached the end of a period and route them for approval without opening every file. That keeps destruction efficient without multiplying the number of people who can read the archive.
Where the uncertainty sits
Retention periods are jurisdiction- and industry-specific, and the periods in this review are illustrative. A business in a regulated sector may face longer periods or specific disposal rules, and a business with a dispute pending may be required to preserve records that would otherwise be destroyed. The literature on digital disposal is also uneven, because deletion from backups and from cloud providers is not always under the business's direct control. A founder should confirm the specifics with a qualified professional and should not treat a general schedule as a substitute for local rules.
Methodology and limits
This review examined retention and disposition guidance from the National Archives and Records Administration, records-retention guidance from the Internal Revenue Service, the Federal Trade Commission's business guidance on data security and disposal, media-sanitation guidance from the National Institute of Standards and Technology, U.S. Small Business Administration guidance on managing a business, and the NIST Privacy Framework. Each source was checked on September 24, 2026. The review provides a general operating framework and does not provide legal advice.
Frequently asked questions
Can my assistant shred documents? Yes, if the method is defined and a named owner approves the list first. The approval is what keeps the decision with the business.
How long should I keep tax records? IRS guidance describes a baseline and longer periods for some records. Confirm the period with the business's accountant.
Do I have to delete records from backups too? The schedule should say so explicitly. If backups are outside the business's control, record that limitation rather than assuming deletion.
What if a dispute starts? The clock stops. A legal hold overrides the schedule, and destruction is paused until the hold is lifted.
References
- Records management, National Archives and Records Administration
- How long should I keep records, Internal Revenue Service
- Disposing of consumer report information, Federal Trade Commission
- Guidelines for media sanitation, National Institute of Standards and Technology
- Privacy Framework, National Institute of Standards and Technology
- Manage your business, U.S. Small Business Administration
Sources
External sources cited in this article. Follow each link to review the original publisher and context.
