Consulting firm records retention: proposals, deliverables and working papers

What sets a consulting firm's retention periods?#

A consulting firm's retention periods are set by four inputs: client contracts, laws that apply to particular record types, the time within which claims could be brought against the firm, and the business value of keeping the record. No single statute sets a period for consulting records in general, so each record type needs its own analysis.

Professional liability insurers sometimes add expectations of their own, and clients in regulated industries may impose retention or destruction terms that flow down to their consultants. Collect these before writing the schedule, because they often conflict with each other and with what partners assume.

Do not borrow durations from a generic template. Have counsel and your accountant confirm the minimum for each record type in the states where you operate, then decide whether business value justifies keeping a record longer.

Retention table: client-owned versus firm-owned records#

The retention table separates who owns each record from what drives its period. Use it as the skeleton of your schedule and fill in the periods with your advisors once the drivers are confirmed.

Proposal archives: keep, trim or delete?#

Proposal archives are firm-owned records with long-term value, because they show how the firm framed problems, priced work and staffed teams over time. Won proposals double as evidence of the agreed scope, so they usually stay with the contract record for as long as claims are possible.

Lost proposals rarely have a legal minimum, which is why they are often deleted carelessly. Pair each one with its loss reason from the CRM before deciding, since a proposal linked to its outcome teaches far more than one without it. Remove or mask client names if the archive will be reused for staff training or internal AI tools.

Working papers: the hard case#

Working papers are the hard case because they blend the firm's analysis with the client's facts. Models, interview notes, survey data and draft slides often contain confidential client information even when the method behind them belongs to the firm.

Treat working papers as client-confidential by default. Keep them for the period your claims exposure and the contract require, restrict access during that period, and then destroy them unless an exception applies. If the firm wants to keep a method, extract it into a clean template without client data before the papers are destroyed.

Analytics workspaces deserve special care. Notebooks, BI files and scratch databases often escape the engagement folder, so name them explicitly in the closeout checklist rather than trusting a folder-level policy to catch them.

Turning the schedule into system settings#

A retention schedule only works when systems enforce it. Most of the effort goes into configuring tools the firm already pays for, not buying new ones.

• 1Apply retention labels or policies in Microsoft 365 or Google Workspace by site or folder type, separating engagement sites from firm knowledge sites.
• 2Set mailbox and chat retention to match the schedule, with exceptions for custodians under legal hold. Learn how each tool resolves conflicts: Slack, for example, states that a legal hold saves messages and files in covered conversations regardless of retention settings.
• 3Turn on automatic deletion for meeting recordings where the schedule allows it; Zoom lets admins delete cloud recordings after a set number of days, with exemptions for individual recordings.
• 4Add an engagement closeout task in the PSA that triggers return, destruction or archiving.
• 5Tag CRM records and attachments so proposal retention follows the opportunity outcome.
• 6Keep a destruction log listing what was deleted, when and under which rule.
• 7Give counsel a way to place and lift legal holds across every one of these systems.

Legal holds: when the schedule stops#

A legal hold stops scheduled deletion for every record relevant to an actual or reasonably anticipated dispute, audit or investigation, whatever the retention schedule says. For a consulting firm, the trigger is often a client complaint about advice, a fee dispute or a subpoena served on a client that reaches its advisors.

Holds fail in practice when they cover only the engagement folder. A sound hold names custodians, covers their mailboxes, chat, laptops and analytics workspaces, and pauses automated deletion in each system. Counsel issues it in writing, the custodians acknowledge it, and someone checks that the system settings actually changed.

Lift the hold formally when counsel releases it, then resume the schedule. Records that were kept only because of the hold should not quietly become part of the permanent archive.

Illustrative: an IT strategy firm splits its archive#

Illustrative: a fictional IT strategy consultancy finds client deliverables, proposals and internal playbooks mixed together in the same SharePoint sites, with no way to apply different rules to each. Its managing partner asks operations to separate engagement sites from firm knowledge sites before the next client audit.

Engagement sites receive a label tied to each contract's return or destroy terms. Firm sites holding proposals, staffing plans and reviews follow the firm's own schedule. Client names are masked in the review library, and a destruction log starts. When the next client asks how its data was handled, the answer comes from the log rather than from anyone's memory.

How SourceX views retained consulting records#

SourceX views retained consulting records through ownership first. Client-owned deliverables, client data and confidential working papers are excluded from licensing, while firm-owned process records such as proposals with outcomes, staffing plans, project reviews and playbooks may be considered after client details are removed.

A clear retention schedule helps the Supply step of the SourceX five-step transaction, because it shows what still exists and how far back it goes. In the SourceX Enterprise Data Value Framework, recency and data cleanliness increase value, while preparation cost and privacy burden reduce net value, so records kept deliberately are easier to assess than records kept by accident.