Small business outsourcing workflow guide
Set a document retention sweep for a small-business assistant
A retention sweep that names what to keep, what to delete, who approves the deletion, and how to prove the record was handled.

Start from the retention schedule
A document retention sweep needs a written schedule that names each record type and how long it must be kept. Do not ask the assistant to decide from memory. Include invoices, payroll records, customer contracts, tax filings, and correspondence that supports a legal obligation. For each type, state the trigger that starts the retention period, such as the end of the tax year or the end of a contract.
Separate a legal minimum from a business preference. A record may be kept longer for customer service or dispute history, but the schedule should say why. A schedule that keeps everything forever is not a retention policy, and it increases the cost and risk of a breach. Review the schedule with the business's accountant or legal adviser before the first sweep.
Write the schedule in the same language the team uses. If the staff call a document a packing slip, the schedule should use that term and explain the record type. Link each row to the folder where the records live. A schedule that cannot be mapped to a real location will not be used.
Inventory before deleting anything
The first sweep should be an inventory, not a deletion. List the folders, the record types, the date range, and the estimated volume. Identify duplicates, personal data, and records that are past the retention date. Do not open every file; sample each folder and record the pattern. The inventory gives the owner the evidence to approve a deletion plan.
Flag records that are under a legal hold, an open dispute, or a pending audit. Those records must not be deleted even if the schedule says they are old. Keep the hold list beside the inventory and check it before every sweep. A deletion that destroys evidence is far more costly than keeping a file too long.
Record the system of origin for each folder. A copy in a shared drive may not be the official record, and deleting the copy may not satisfy the retention rule. Identify the authoritative system before deciding what can go. The assistant should not guess which copy matters.
Give the assistant a reviewable deletion list
Prepare a deletion list with the record type, the date range, the location, the count, and the schedule rule that allows deletion. The owner should be able to approve or reject the list without opening every file. Keep the list with the sweep record. A deletion that cannot be traced to a rule is a risk the business cannot defend.
Delete in small batches so a mistake can be stopped. Start with the least sensitive records and verify the result before moving on. Do not empty the recycle bin or the backup in the same step. The first sweep should prove the process, not maximize the volume removed.
Record who deleted the files, when, and with what approval. If the tool keeps an audit log, export it with the sweep record. If it does not, write a short manual log. The evidence matters if a customer or a regulator later asks why a record is missing.
Protect personal and financial data
The assistant should handle only the records the task requires and should not copy personal data into a personal drive or a chat message. Use the approved storage location and the approved sharing method. If a document contains a customer's identity document, redact it before sharing with anyone who does not need it. The retention sweep is a good time to remove unnecessary copies.
Check the access list for the folders being reviewed. Remove access for people who have left or changed roles. Do not leave a shared link open after the sweep. A retention policy that deletes the official record but leaves an open copy elsewhere has not reduced the risk.
If a deletion includes financial records, confirm the accounting system has the official copy before removing the working file. Do not delete a record that the accountant still needs for a tax filing. Ask the accountant to confirm the retention period in writing. Keep that confirmation with the schedule.
Handle the exceptions with a named owner
Some records will not fit the schedule, such as a contract with an unusual clause or a file with unclear ownership. Put those in an exception list with the reason and the owner. Do not let the assistant make a legal judgment. The owner should decide whether to keep, delete, or seek advice.
Review the exception list at the next sweep. If the same type appears repeatedly, update the schedule or the folder structure. An exception that is never resolved becomes a permanent collection of mystery files. A short note on the decision is enough to close it.
Close the sweep with a short report
The report should state the folders reviewed, the records deleted, the records kept, the exceptions, and the approver. Keep it with the retention schedule. The report is the evidence that the business followed its own process. It should be short enough that the owner will actually read it.
Schedule the next sweep before closing this one. A quarterly or annual cadence is easier to maintain than an ad hoc cleanup. Put the date on the calendar and assign the owner. A retention program that depends on someone remembering is not a program.
Use the report to improve the folder structure. If the assistant had to open five places to find one record type, the structure is costing time. Fix one folder or one naming rule and check the effect at the next sweep. Small structural changes are more durable than a large annual cleanup.
Sources and next steps
- U.S. National Archives, records management
- Federal Trade Commission, data security guidance
- U.S. Small Business Administration, manage your business
Compare this workflow with the small-business outsourcing service guides and bring a redacted source record to the scoping call.