Closing a service business: what happens to the records?

1. Put one person in charge of the record decisions#

Name the person responsible for coordinating the archive before the closure project becomes a list of subscriptions to cancel. They need authority to obtain answers from finance, HR, client account owners, IT, and the advisers handling the closure. They do not need to make every decision themselves.

Write down who will hold that responsibility after employees leave, how the custodian can be contacted, and who pays storage and support bills. A folder owned by a departing administrator is not a completed handoff. Neither is an external drive that only the founder knows how to decrypt.

The IRS includes keeping records in its business closure process; closure does not itself establish a deletion date. Its guidance distinguishes record types and directs businesses to check state responsibilities. Have the adviser handling your closure translate applicable duties into a record-specific schedule. IRS: Closing a business.

2. Work backward from access loss, not just the closure date#

The following is a planning sequence, not a statutory timetable. Start earlier when a vendor needs notice, an archive is large, or the team cannot complete the checks before a contract ends. If time is short, escalate the access dependency and fund a scoped extension where needed.

Check identity-provider, email, domain, device-management, encryption-key, and backup dependencies. Canceling one service may remove the sign-in or recovery route for another. Ask the administrator to map these relationships before removing accounts.

3. Give each collection a decision and an approver#

Start from the business data inventory. Add a closure decision register with these fields. One software system can contain several collections with different outcomes.

• Collection and boundary: record type, date range, system, client or business unit, and known copies.
• Reason and instruction: applicable policy, contract, retention requirement, hold instruction, or documented business purpose, with a reference.
• Disposition: retain in archive, return or transfer to an authorized recipient, securely dispose, or await a named decision.
• Accountability: decision approver, executor, future custodian, and contact route.
• Timing and proof: trigger date, next review date, completion evidence, and any unresolved exception.

Avoid a universal “keep seven years” rule. The IRS describes different periods for different circumstances and warns that non-tax requirements may continue after tax retention ends. Ask finance and your adviser to record the applicable trigger and period for each category. IRS record retention guidance.

“Awaiting decision” needs an owner and review date. It should not become permission for permanent storage or a reason to cancel a system that still holds required material.

4. Resolve holds and client commitments before routine cleanup#

Give counsel the proposed cancellation and deletion list, including automated retention jobs, employee mailboxes, devices, and backups. Ask which material must be preserved and how the instructions should be implemented. In federal civil litigation, Rule 37(e) addresses loss of electronically stored information that should have been preserved for anticipated or ongoing litigation. U.S. Courts: Federal Rules of Civil Procedure, Rule 37(e).

Separately, have client owners locate the executed agreements, amendments, and relevant instructions. Record return or deletion terms, permitted recipients, confidentiality provisions, and any continuing responsibilities. If a client request conflicts with a preservation instruction, escalate the conflict rather than asking IT to interpret it.

Consider a hypothetical 45-person agency whose project platform contains final deliverables, client-uploaded research, invoices, and internal templates. These are four review categories, even if one “export all” button retrieves them. A return of client files, a finance archive, and any proposed reuse of agency-created templates need separate decisions.

5. Make the archive usable by the person who inherits it#

An export finishing successfully proves only that a process finished. Ask the future custodian to retrieve a small set of authorized records that exercises the archive: an older item, a recent item, an attachment, and a record whose meaning depends on another table or file. Keep the test inside approved access arrangements.

• Can the custodian locate the record from an ordinary business reference?
• Do attachments open, dates make sense, and identifiers still connect related records?
• Are field definitions, filters, omitted material, and export dates documented?
• Can access and decryption be recovered without a former employee’s personal account?
• Is there a documented backup and restoration approach for the retained archive?

Record the test result and exceptions. Where evidentiary integrity, auditability, or a specific format matters, obtain the required preservation instructions before converting files. Choose access restrictions and storage arrangements to match the material rather than putting every record in one broadly shared folder.

6. Treat licensing as a separate proposal#

A licensing inquiry can be evaluated during a closure, but “someone may want it” is not a complete archive policy. Define the proposed collection and use, identify the relevant rights and restrictions, and decide whether the review effort fits the closure budget. Start with a description rather than the records themselves.

Do not let an unconfirmed opportunity interrupt client handoffs or required recordkeeping. If no responsible person can complete a bounded review before system access ends, document that constraint. Any decision to keep the material longer still needs an appropriate basis, custodian, controls, and review date. Use the licensing agreement checklist if a concrete proposal develops.

7. Sign off on disposal and ongoing custody separately#

For approved disposal, record the collection, copies in scope, method, executor, date, and evidence. Have the administrator check vendor deletion behavior and backup schedules; distinguish a deletion request from confirmed completion. The FTC advises disposing of unneeded sensitive information appropriately and warns that ordinary file deletion may leave recoverable data on devices. FTC business data security guide.

For retained material, give the custodian the decision register, access instructions, adviser contacts, review calendar, and funded storage arrangement. Schedule a post-handoff access check. The closure file should explain both what remains and why, as well as what was returned or disposed of and who approved it.

Questions owners ask