Build a file retention routine for a virtual assistant's downloads

Inventory where downloads land

Start by listing every place an assistant saves a client file during a normal week. Include the browser download folder, the desktop, personal cloud drives, chat attachments, and the shared client folder. Walk through one real task and watch where each file goes. A retention rule that ignores the download folder will miss most of the copies.

Ask the assistant which folders they use because the approved path is slow or confusing. The workaround is often the real location of client data. Fix the approved path before writing a rule that forbids the workaround. The inventory should describe the current habit, not the intended one.

Classify files by retention

Group files into a few categories, such as working copies, client deliverables, financial records, and personal notes. Give each category a retention period and a deletion owner. Keep the list short enough to remember and specific enough to act on. A category that says keep as needed will never produce a deletion.

Check the client contract and the applicable recordkeeping duty before setting a period. Some records must be kept for a fixed time, while working copies can be removed once the deliverable is saved. Write the reason beside each period so the assistant understands the rule. The classification should match the client's obligations rather than the provider's convenience.

Set a daily cleanup habit

Add a five-minute cleanup at the end of each shift. The assistant moves the day's working files into the approved folder, deletes duplicates, and empties the download folder. Keep the action in the task card so it appears in the queue. A daily habit prevents a month of files from becoming a cleanup project.

Make the cleanup easy by naming one destination for current work and one for archived work. Remove folders that are no longer approved so the assistant does not have to guess. Check the download folder at the start of the next shift and note anything that was missed. The habit is working when the folder is empty most mornings.

Handle sensitive files separately

Treat files with personal, financial, health, or authentication data as a separate category with a shorter retention period. Store them only in the approved system and never in a personal download folder. Use the client's secure transfer method rather than email attachments. The sensitivity of the file should determine the path, not the speed of the task.

Give the assistant a clear instruction for a file that arrives through an unapproved channel. The instruction should include where to move it, who to notify, and how to confirm deletion. Do not ask the assistant to decide whether the data is sensitive without a definition. A short list of examples makes the rule usable under pressure.

Verify deletion and evidence

Deleting a file from one folder does not remove it from a synced drive, a backup, or a chat attachment. Check each location that the classification covers and record the deletion date. For sensitive files, record the person who confirmed the removal. Evidence turns a claim of deletion into a fact the client can review.

Use a simple log with the file name, category, location, deletion date, and reviewer. Do not include the file contents in the log. Keep the log with the task record rather than in a personal note. A log that takes more than a minute to update will be skipped during a busy week.

Review the routine monthly

Once a month, sample ten files from the download folder and the shared drive. Check whether each file has a category, a retention date, and an owner. Look for files that were kept past their date or deleted too early. The sample shows whether the routine works in practice rather than only on paper.

Ask the assistant which part of the cleanup feels unnecessary or confusing. A rule that creates busywork without reducing risk should be simplified. Change one part of the routine and test it for a month. The goal is a habit the team can sustain, not a perfect policy.

Write the rule into onboarding

Give the retention routine to a new assistant on the first day, before they download a client file. Explain where files go, how long they stay, and who confirms deletion. Add the routine to the first-week checklist so it is not treated as an optional extra. A new assistant should learn the path before they learn the workaround.

Review the first week's folders with the assistant and correct any file that is in the wrong place. Keep the correction beside the rule so the next person sees the example. Update the onboarding checklist when the approved path changes. The routine becomes part of the role instead of a periodic cleanup campaign.

Add one exception path for a file that arrives outside the approved system. The path should name the secure destination, the person to notify, and the deletion confirmation. Test the path with a harmless sample file before a real one arrives. An exception path that has never been used is only a hope.

Name the records owner

Give the retention routine a named owner who can answer questions and approve an exception. The owner does not need to inspect every file, but they should review the monthly sample and the deletion log. Write the owner's name and backup beside the routine. A rule with no owner is enforced only when someone remembers it.

Separate the records owner from the assistant who does the cleanup. The assistant should not approve their own exception or confirm their own sensitive deletion. The split gives the client a second pair of eyes on the files that carry the most risk. It also makes the routine easier to defend during a client audit.