A Records Retention Baseline for Executive Support Teams

Retention is an operating control, not a storage decision

Executive support teams accumulate records that look routine until someone asks for them. A signed vendor agreement, a payroll correction, a leave request, a reference check, and a board packet each carry a different retention obligation. Keeping everything forever creates privacy and discovery risk. Deleting too early can violate pay, tax, or leave laws. A retention schedule is the bridge between those two failures, and it belongs in the operating documentation of the team rather than in a filing cabinet nobody reviews.

The schedule should identify the record type, the owner, the retention period, the trigger that starts the clock, and the method of disposal. It should also state which records are subject to a legal hold, because a hold overrides the normal schedule. The goal is not to create a perfect archive. It is to make routine decisions consistently so that the team is not improvising when a client, auditor, or regulator asks a question. The retention compliance research explores how those decisions can be tested rather than assumed.

Tax and payroll records

The Internal Revenue Service publishes guidance on how long to keep records. The general rule for supporting tax returns is three years, with longer periods in cases such as underreported income or unfiled returns. Employment tax records should generally be kept for at least four years after the tax is due or paid, whichever is later. An executive assistant agency that runs payroll should treat those records as part of its core compliance file, not as a finance-only concern. The IRS's recordkeeping page is the appropriate starting point.

Payroll records include pay rates, hours worked, overtime calculations, deductions, and proof of payment. They also include the records that explain a correction, such as a retroactive raise or a reimbursed expense. Keep the audit trail, not just the final payslip. If the agency uses a professional employer organization or a staffing platform, confirm which party holds the underlying records and how the agency can obtain them. A vendor's retention policy does not automatically satisfy the agency's obligation.

Hours and pay records

The Fair Labor Standards Act requires employers to keep payroll records for covered employees. Department of Labor guidance describes the specific data that must be recorded, including employee information, hours worked, amounts paid, and deductions. The regulations generally require payroll records to be preserved for three years and time and pay records that support them for two years. Those periods are minimums, and state law may require longer retention. The Department's recordkeeping fact sheet lists the required fields.

Email, messaging, and working files

Email and chat are where many of the most important approvals actually happen. A message that authorizes a payment, approves a contract change, or directs a confidential disclosure is a business record even though it does not look like a formal document. Apply retention by function rather than by format. If the message is the only evidence of a decision, it belongs in the same retention category as the decision record. If it is a scheduling confirmation, it can follow a short administrative schedule.

Working files create a different problem. Drafts, spreadsheets, and local copies may contain personal or client data that is not captured by the central system. Define where working files may be stored, how long they may remain, and who is responsible for deleting them. Link the retention rule to the document expiry review so that old versions do not survive simply because nobody remembered they existed. A short, enforced rule is better than a broad instruction to clean up eventually.

Legal holds and preservation

A legal hold suspends normal disposal when litigation, an investigation, or a government request is reasonably anticipated. The hold should be issued in writing, scoped to specific custodians and record types, and acknowledged by each custodian. The team should stop deleting relevant material immediately, including messages and working files that would normally expire. The hold remains in effect until counsel releases it in writing.

The practical challenge is that executive support teams often hold the records without controlling the legal strategy. Build a clear escalation path: if the assistant receives a preservation request, a subpoena, or a credible threat of litigation, notify the appropriate legal contact before deleting anything. Document the notification and the steps taken. Do not attempt to decide the scope of the hold without counsel. The retention schedule is designed for ordinary operations, and the hold is the mechanism that overrides it when ordinary operations are no longer appropriate.

Executive assistants often work across time zones and may be classified as exempt or non-exempt depending on duties and pay. The classification decision should be documented, and the records supporting it should be retained with the payroll file. If the role changes, update the classification analysis and keep the earlier version. A record that shows why a decision was made at the time is far more useful than a reconstructed explanation written after a complaint.

Leave and accommodation records

The Family and Medical Leave Act imposes recordkeeping obligations on covered employers, including basic payroll data, dates of leave, and health insurance contributions. The Department of Labor's FMLA guidance is the appropriate starting point for the specific requirements. Leave records should be kept separately from the general personnel file where possible, because they contain medical information that should not be shared with routine hiring or scheduling decisions. That separation also limits who can answer a question about the leave without exposing the underlying medical reason.

Accommodation requests and medical documentation deserve additional care. Limit access to the people who need it, log who viewed the file, and avoid storing the information in a shared drive that the whole support team can browse. The retention period should follow the applicable employment and civil rights rules, and the file should be reviewed when the employment relationship ends. Privacy is not a reason to destroy a record early, but it is a reason to restrict it.

Hiring, reference, and performance records

An agency that screens executive assistants should keep the records that explain its decisions: the job description, the application, the interview notes, the assessment results, and the reference check. Retention periods vary by jurisdiction and by the type of record. A practical baseline is to keep hiring records for the period in which a discrimination claim could be filed, plus a margin for state and local rules. The agency's counsel should confirm the applicable period.

Performance records should distinguish between routine feedback and formal warnings. Routine notes can be brief and time-limited. Formal discipline that could support a termination decision should be retained longer and stored with the personnel file. The same logic applies to client complaints about an assistant. Keep the complaint, the investigation, the response, and the corrective action together. A file that contains only the complaint tells a misleading story.

Contracts, client records, and correspondence

Signed contracts should be kept for the term of the agreement plus the period in which a breach or tax issue could be raised. That usually means several years after expiration, and longer for agreements with indemnity, confidentiality, or recordkeeping clauses. Amendments, statements of work, and renewal notices belong with the contract, not in a separate email folder. The renewal calendar described elsewhere on this site should link to the contract file rather than duplicate it.

Client correspondence and executive inbox records are the hardest category because they mix business records with incidental messages. Apply retention by function, not by sender. A message that approves a payment, changes a contract, or authorizes travel is a business record. A message that confirms a lunch is not. Write the rule in plain language and give the team examples. When a legal hold is issued, suspend deletion for the relevant custodians and document the hold.

Building a schedule the team will follow

Start with a small inventory of the records the team actually creates. Group them into payroll, employment, contracts, client service, and general administration. For each group, assign an owner and a retention period supported by a source. Publish the schedule where the team works, not in a policy folder nobody opens. Add a quarterly check that samples a few files and confirms they match the schedule.

Disposal should be deliberate. Record what was destroyed, when, and under which schedule, then confirm that no legal hold applies. If a record is ambiguous, keep it and ask for a decision rather than deleting it silently. The schedule is a tool for consistent judgment, and its value depends on the team's ability to explain a decision later. This report is an operational baseline, not legal advice. Employment counsel and a tax professional should review the final schedule for the agency's jurisdictions and client contracts. If you need help drafting a retention schedule, contact our team.