# Paralegal Case File Management: Structuring Active Litigation Files

Paralegal case file management establishes uniform folder hierarchies, standardized naming conventions, and disciplined exhibit tracking across active litigation matters. Structuring files into distinct tiers for pleadings, discovery, transcripts, and work product prevents misplaced filings, accelerates document retrieval, and keeps case teams prepared for court deadlines.

Source: https://fast.io/resources/paralegal-case-file-management/
Author: [Tom Langridge](https://fast.io/authors/tom-langridge/)
Last reviewed: 2026-11-07

## Why Generic Storage Fails Active Litigation Case Files

When an emergency preliminary injunction hearing or summary judgment filing deadline lands on a litigation team, an ambiguous filename like `Brief_Final_v2.docx` or a misplaced deposition exhibit creates an immediate operational crisis. In active litigation, the difference between an orderly hearing and a blown filing deadline is rarely attorney argument; it is whether the litigation support team can locate, verify, and cite a decisive document in seconds.

Paralegal case file management is the structured practice of organizing, indexing, versioning, and securing all evidentiary documents, pleadings, discovery responses, and work product within a unified matter directory throughout active litigation.

Active litigation places unique operational demands on legal files that general corporate storage systems cannot accommodate. In corporate transactions or commercial contracting, files accumulate along a predictable schedule, culminating in closing binders where final executed agreements supersede earlier working drafts. Litigation files, by contrast, are adversarial, highly fragmented, and subject to strict court deadlines and procedural rules. A single dispute generates thousands of disparate records: court-stamped pleadings from the docket, contested motion bundles, formal discovery requests and objections, voluminous document productions from multiple parties, third-party subpoena returns, deposition transcripts with marked exhibits, and internal attorney strategy memoranda.

Generic cloud storage and shared network drives fail litigation practices because they treat legal documents as undifferentiated static data. On unmanaged file servers, paralegals and attorneys save documents across scattered local directories, desktop downloads folders, and personal email threads. This lack of architectural structure introduces severe operational risks:

* **Version Drift:** Attorneys co-authoring briefs across email attachments create competing revisions, increasing the likelihood that an outdated draft or unredacted work product is submitted to the court clerk.
* **Loss of Evidentiary Integrity:** Incoming productions saved directly into active working folders risk accidental modification, renaming, or deletion, compromising chain of custody.
* **Retrieval Latency:** Under hearing deadlines, legal assistants lose valuable billable time hunting for specific deposition exhibits or clerk filing receipts buried inside generic subdirectories.
* **Security and Boundary Failures:** When case files live in unstructured directories, sharing an exhibit set with an outside expert witness or co-counsel often exposes unrelated case files or internal attorney notes.

Solving these operational bottlenecks requires a standardized digital legal file structure built around matter-centric workspaces, consistent naming taxonomies, and disciplined version control protocols.

## How to Structure a Paralegal Case File Management Hierarchy

The foundation of reliable paralegal case file management is a uniform directory taxonomy applied across every active litigation matter in the firm. When every case file follows an identical organizational hierarchy, any legal assistant, paralegal, or covering associate can open an unfamiliar matter and immediately locate the required pleading, discovery response, or hearing exhibit.

To prevent folder sorting inconsistencies across operating systems, legal teams should employ two-digit zero-padded numerical prefixes (`01_`, `02_`, `03_`). Numerical prefixes enforce a consistent procedural order across Windows, macOS, Linux, and web interfaces, rather than allowing folders to rearrange based on alphabetical sorting.

Below is the production-tested six-tier directory schema recommended for active litigation matters:

```
Matter_2026-0142_Rodriguez_v_GlobalLogistics/
├── 01_Pleadings_and_Court_Filings/
│   ├── Filed_Court_Stamped/
│   ├── Working_Drafts/
│   ├── Summons_and_Service/
│   └── Docket_Entries_and_Notices/
├── 02_Orders_and_Judicial_Rulings/
│   ├── Scheduling_and_Case_Management_Orders/
│   ├── Discovery_Orders_and_Rulings/
│   ├── Motion_Decisions_and_Judgments/
│   └── Minute_Entries/
├── 03_Discovery_and_Written_Requests/
│   ├── Interrogatories/
│   │   ├── Propounded_to_Opposing_Party/
│   │   └── Received_from_Opposing_Party/
│   ├── Requests_for_Production/
│   │   ├── Served_Requests/
│   │   └── Received_Requests/
│   ├── Requests_for_Admission/
│   │   ├── Served_Requests/
│   │   └── Received_Requests/
│   └── Third_Party_Subpoenas/
│       ├── Subpoenas_Issued/
│       └── Subpoena_Returns_and_Objections/
├── 04_Document_Productions_and_Bates_Archives/
│   ├── Incoming_Productions/
│   │   ├── Def_Production_001_Bates_XYZ000001-XYZ000450/
│   │   └── ThirdParty_Bank_Bates_BK000001-BK000120/
│   ├── Outgoing_Productions/
│   │   ├── Plf_Production_001_Bates_PL000001-PL000850/
│   │   └── Plf_Production_002_Bates_PL000851-PL001500/
│   └── Privilege_Logs/
├── 05_Depositions_and_Transcripts/
│   ├── 2026-04-12_Doe_Jane/
│   │   ├── Transcripts_Certified/
│   │   ├── Marked_Deposition_Exhibits/
│   │   ├── Video_and_Audio_Recordings/
│   │   └── Deposition_Summary_PageLine/
│   └── 2026-05-18_Smith_John/
│       ├── Transcripts_Certified/
│       ├── Marked_Deposition_Exhibits/
│       └── Deposition_Summary_PageLine/
└── 06_Attorney_Work_Product_and_Trial_Prep/
    ├── Legal_Research_and_Authorities/
    ├── Case_Chronology_and_Timelines/
    ├── Witness_Kits_and_Outlines/
    ├── Master_Exhibit_List/
    └── Trial_Briefs_and_Motions_in_Limine/
```

### Isolating Contested Motions into Procedural Bundles

A common structural flaw in litigation file management is dumping all motion papers into the general pleadings folder. In complex commercial litigation, a contested motion to dismiss or motion for summary judgment generates a constellation of interconnected documents: the notice of motion, memorandum of law, attorney affidavits, dozens of documentary exhibits, the opposing party's responsive brief, counter-affidavits, reply memoranda, and the court's ultimate order.

When these filings are intermingled with ordinary pleadings, reconstructing the motion record months later for oral argument or appellate review becomes an operational burden. Paralegals should establish a dedicated subfolder within `01_Pleadings_and_Court_Filings/` for each major procedural event (for example, `01_Pleadings_and_Court_Filings/Motions/2026-06-15_Plf_Motion_for_Protective_Order/`). Inside this bundle, store every document tied to the motion in strict procedural sequence. This guarantees that the arguing attorney has the entire procedural record in one place without pulling disparate filings from the main docket index.

### Separating Document Productions from Source Evidence

Another frequent breakdown occurs when legal teams mix client source evidence with formalized document productions. Client business records, financial ledgers, and raw email exports must remain separate from Bates-stamped collections produced in litigation.

Incoming document productions received from opposing counsel or non-party witnesses must be saved in read-only condition within `04_Document_Productions_and_Bates_Archives/Incoming_Productions/`. Each production batch should reside in its own folder named by producing party, production volume, and Bates range. Maintaining this strict separation preserves chain of custody and prevents client evidence from being inadvertently reproduced during subsequent discovery rounds.

## How to Standardize File Naming Conventions and Version Control

Even the cleanest folder hierarchy collapses if documents inside carry ambiguous, unstandardized names. When a case folder contains files labeled `Response_Draft.docx`, `Response_Final.docx`, `Response_FINAL_v2.docx`, and `Response_Approved_by_Partner.docx`, identifying the authoritative filing requires opening each file individually. Under court deadlines, this ambiguity invites severe errors, such as serving an unedited draft or filing a document with active revision tracking.

To eliminate confusion, every document added to the litigation directory must adhere to a strict ISO 8601 date-based naming formula:

`YYYY-MM-DD_{DocType}_{Description}_{PartyOrFiler}_{StatusOrVersion}.{ext}`

Applying this convention ensures that documents automatically arrange themselves chronologically within each directory, regardless of whether a user sorts by filename or date modified.

### Core Components of the Standard Litigation Filename

Each element in the naming formula fulfills a distinct operational role:

* **Date (`YYYY-MM-DD`):** Represents the official date of filing, service, execution, or document creation. For historical evidentiary records (such as an underlying contract or historical email), use the date the original document was authored, rather than the date it was scanned or uploaded.
* **Document Type Code (`{DocType}`):** A standardized three- or four-letter identifier that instantly categorizes the procedural nature of the record.
* **Substantive Description (`{Description}`):** A concise, specific description of the document. Words are separated by hyphens rather than spaces to prevent file path truncation and broken links across legal technology platforms.
* **Party or Filer (`{PartyOrFiler}`):** Designates who drafted, filed, or produced the file (for example, `Plf-Rodriguez`, `Def-GlobalLogistics`, `NonParty-FirstBank`).
* **Status or Version Indicator (`{StatusOrVersion}`):** Explicitly marks the procedural status of the file, such as `Draft-v01`, `Served`, `Filed-Stamped`, or `Executed`.

The following table summarizes standard document type codes used across active litigation files:

| Code | Category | Typical Document Types |
| --- | --- | --- |
| `PLDG` | Pleadings | Complaints, Answers, Affirmative Defenses, Counterclaims |
| `ORD` | Judicial Orders | Case Management Orders, Preliminary Injunctions, Discovery Rulings |
| `MOT` | Motion Practice | Notices of Motion, Memoranda of Law, Supporting Affidavits |
| `DISC` | Discovery Requests | Interrogatories, Requests for Production, Requests for Admission |
| `RESP` | Discovery Responses | Formal Objections and Answers, Responses to RFPs, Responses to RFAs |
| `PROD` | Document Productions | Formal Bates-stamped document collections and production sets |
| `DEP` | Depositions | Certified Transcripts, Video Recordings, Page-Line Summaries |
| `EXH` | Evidentiary Exhibits | Marked Deposition Exhibits, Hearing Exhibits, Trial Exhibits |
| `CORR` | Correspondence | Letters to Court Clerk, Rule 26 Meet-and-Confer Letters, Transmittals |
| `MEMO` | Work Product | Legal Research Memos, Deposition Outlines, Witness Examination Kits |

Applying this convention creates transparent, self-indexing directories across every litigation phase:

* **Court Pleadings:**
  `2026-01-15_PLDG_Complaint-and-Jury-Demand_Plf-Rodriguez_Filed-Stamped.pdf`
  `2026-02-12_PLDG_Answer-and-Affirmative-Defenses_Def-GlobalLogistics_Filed-Stamped.pdf`
  `2026-03-01_PLDG_First-Amended-Complaint_Plf-Rodriguez_Draft-v02.docx`

* **Motion Filings:**
  `2026-03-20_MOT_Notice-of-Motion-to-Compel-Discovery_Plf-Rodriguez_Served.pdf`
  `2026-03-20_MOT_Brief-in-Support-Motion-to-Compel_Plf-Rodriguez_Filed-Stamped.pdf`
  `2026-04-05_MOT_Opposition-to-Motion-to-Compel_Def-GlobalLogistics_Filed-Stamped.pdf`
  `2026-04-22_ORD_Order-Granting-in-Part-Motion-to-Compel_Judge-Chen_Signed.pdf`

* **Written Discovery:**
  `2026-02-20_DISC_First-Set-Interrogatories_Plf-to-Def_Served.pdf`
  `2026-03-23_RESP_Responses-to-First-Set-Interrogatories_Def-GlobalLogistics_Served.pdf`
  `2026-03-23_RESP_Responses-to-First-Set-Requests-for-Production_Def-GlobalLogistics_Served.pdf`

* **Deposition Records:**
  `2026-05-10_DEP_Jane-Doe-Vol-01_Transcript-Certified.pdf`
  `2026-05-10_DEP_Jane-Doe-Vol-01_PageLine-Summary_Paralegal.docx`
  `2026-05-10_DEP_Jane-Doe-Exh-001_Employment-Contract_Bates-PL000102-000115.pdf`

### Maintaining Version History Without Filename Clutter

Manual version control saving iterative files as `v1`, `v2`, and `v3` inside the active directory creates visual clutter and raises the risk that an associate inadvertently works off an obsolete file.

Modern cloud workspaces resolve this problem through per-file version history. In [Fastio workspaces](/product/workspaces/), every file automatically maintains complete revision checkpoints. When attorneys and paralegals co-draft a motion brief or update case notes, the workspace preserves every revision checkpoint under the single, authoritative filename. Case team members can view who modified the document, compare earlier drafts, and restore prior versions with a single click. This keeps active litigation folders clean while preserving a dependable record of drafting revisions prior to court submission.

## How to Manage Discovery Productions, Bates Stamping, and Master Exhibit Logs

Discovery management and exhibit preparation represent the most labor-intensive operational responsibilities in paralegal litigation support. During active discovery, case teams exchange thousands of pages spanning corporate accounting records, emails, personnel files, and non-party subpoena returns. Without rigorous indexing protocols, retrieving a key document during a deposition or evidentiary hearing becomes an operational failure.

Litigation paralegals must establish systematic intake pipelines that verify production volumes, log Bates ranges, and stage exhibits for trial. A reliable discovery management system bridges raw evidentiary records with courtroom strategy, ensuring attorneys have immediate access to verified documents and corresponding admissibility records throughout active proceedings. Standardizing these procedures across the firm prevents evidentiary gaps and protects the record for trial.

### Incoming Production Verification Protocol

When opposing counsel or a non-party subpoena recipient delivers a document production, the paralegal should execute an immediate verification protocol:

1. **Verify Transmittal Letters and Bates Ranges:** Match the transmittal letter against the deliverable media. Confirm that starting and ending Bates stamps align with the transmittal notice and verify that no pagination gaps exist in the sequence. If the production includes native files (such as complex financial workbooks or proprietary schematics), confirm that accompanying load files (DAT or OPT) map accurately.
2. **Deposit in Read-Only Master Storage:** Immediately copy the received files into a designated incoming productions directory within `04_Document_Productions_and_Bates_Archives/Incoming_Productions/`. This folder must remain strictly read-only to preserve evidentiary integrity and chain of custody. Working copies should be created only when redaction or specialized analysis is required.
3. **Execute Full-Text Search Processing:** Verify that all received PDFs have undergone optical character recognition. Unsearchable scanned images prevent litigators from locating key terms during motion drafting and deposition preparation.

### Structuring the Master Exhibit Log

A live Master Exhibit Log serves as the operational bridge between raw discovery records and courtroom presentation. Rather than maintaining isolated exhibit lists for each deposition, paralegals should maintain a centralized exhibit register in the matter workspace.

A standardized Master Exhibit Log tracks the following core data fields:

| Exhibit # | Document Description | Document Date | Bates Begin | Bates End | Sponsoring Witness | Deposition Marked | Admissibility Status | Objections and Notes |
| --- | --- | --- | --- | --- | --- | --- | --- | --- |
| Exh 001 | Executive Employment Agreement | 2024-03-15 | PL000102 | PL000115 | Jane Doe | 2026-05-10 | Admitted | Authenticity stipulated |
| Exh 002 | Email re: Bonus Structure Review | 2024-11-04 | PL000340 | PL000342 | John Smith | 2026-05-18 | Pending | Hearsay objection preserved |
| Exh 003 | Q3 Corporate Financial Audit Ledger | 2024-09-30 | DEF002100 | DEF002145 | Robert Taylor | Unmarked | Pending | Business records certification attached |
| Exh 004 | Human Resources Policy Manual | 2023-01-10 | DEF004550 | DEF004580 | Jane Doe | 2026-05-10 | Admitted | Relevance objection overruled |
| Exh 005 | Third-Party Bank Confirmation Slip | 2025-02-14 | BK000045 | BK000046 | Custodian of Records | Unmarked | Pending | Subpoena return authentication pending |

Maintaining this table as a live document in the litigation workspace ensures that litigation partners, associates, and trial specialists share real-time visibility into marked exhibits and evidentiary statuses across multi-week deposition tracks.

### Extracting Discovery Data with Metadata Views

Reviewing hundreds of medical records, contract portfolios, or third-party invoices to compile summary indexes traditionally requires hours of manual data entry. Paralegals often spend entire days extracting contract dates, monetary values, and party names into standalone spreadsheets.

Legal teams can accelerate this process using [Metadata Views](/product/document-data-extraction/). Metadata Views turn unstructured documents into a live, queryable database directly within the workspace. Rather than configuring rigid templates or complex extraction rules, legal operations managers describe the fields they require in plain language, such as Document Date, Author, Counterparty, Bates Range, Monetary Amount, and Document Classification.

The system applies a typed schema across PDFs, scanned records, Word files, and spreadsheets, generating a structured, filterable table. Litigation teams can sort productions by date range, filter for specific counterparties, or search across extracted dollar thresholds without re-processing source files. This structured data layer allows paralegals to identify critical documents in discovery batches rapidly and verify disclosure completeness before court hearings.

## How Matter Workspaces Isolate Active Litigation Files

Managing litigation files across complex cases requires unambiguous organizational perimeters. A boutique litigation practice or mid-sized defense firm handling dozens of active matters cannot rely on sprawling, undifferentiated network shares where records from different clients intermingle. Without strict workspace boundaries, files risk cross-contamination, inadvertent disclosure, and permission sprawl.

Establishing dedicated, matter-centric workspaces isolates each litigation matter into its own secure environment. Within each workspace, litigation teams maintain pleadings, discovery productions, and internal work product while retaining full administrative control over external sharing, client intake, and team collaboration. This architecture protects sensitive litigation assets while providing legal teams with the structure needed to manage high-stakes disputes.

### Workspace Boundaries and Role-Based Permissions

The cleanest architecture for legal practices is to dedicate an isolated workspace to each active client matter (for example, `Matter-2026-0142_Rodriguez-v-GlobalLogistics`). Keeping each litigation matter in its own workspace establishes an unambiguous perimeter around client records, pleadings, transcripts, and attorney work product.

In Fastio, permissions are set per organization, workspace, and share through member roles. Every member assigned to a workspace accesses workspace files based on their assigned organizational role. When a legal team needs to provide access to only a specific subset of documents (such as delivering a deposition exhibit package to an expert witness or sharing hearing exhibits with co-counsel), they create a dedicated share.

Branded shares (Send, Receive, or Exchange) allow legal teams to distribute files with custom branding, set expiration dates, and apply recipient-specific access controls. Litigators can also disable file downloads on shares when they want external parties to review documents without saving local unmanaged copies.

### Client Document Intake and Large Evidence Delivery

Collecting evidentiary records from clients through email attachments frequently fails because standard email providers enforce strict attachment ceilings. For personal Gmail accounts, the limit is 25 MB, preventing clients from emailing bulk business records, exported mailboxes, or high-resolution documents.

Paralegals can replace email file collection with Receive shares. By generating a branded Receive link, legal assistants provide clients with a simple web interface to upload multi-gigabyte files directly into a designated staging folder within the matter workspace. Clients do not need to create accounts or install software, reducing friction during urgent discovery deadlines.

Furthermore, active litigation frequently involves massive digital files, including multi-hour high-definition deposition videography, forensic drive images, and multi-gigabyte electronic discovery archives. While consumer cloud services often stall or reject large uploads, Fastio accommodates files up to `25 GB` on Starter, `50 GB` on Business, and `100 GB` on Enterprise. High-definition deposition videos can be streamed directly in the browser via HLS streaming, allowing attorneys to review witness testimony without waiting for entire video files to download. For law firms evaluating matter workspace deployment, monthly plans start with a 14-day free trial, which requires a credit card. Plan tiers include Starter (`$9.99`/mo), Business (`$49.99`/mo), and Enterprise (`$199.99`/mo), detailed on the [pricing](/pricing/) page.

### Auditing Changes and Syncing Firm Repositories

Litigation support managers require reliable tracking of file modifications to maintain order during high-stakes filings. Fastio provides a detailed activity log that records changes across the organization and workspace, documenting every file upload, edit, rename, move, and deletion, along with member role adjustments and share creation events. This activity record allows practice managers to verify when a critical pleading draft was modified or when a paralegal uploaded an incoming production set.

For law firms that maintain existing file servers or document repositories, Cloud Sync connects Google Drive, Dropbox, Box, and OneDrive folders to a workspace. Synchronization runs one-way or two-way, on a schedule or on demand. This allows litigation teams to mirror incoming court downloads or synchronize archived case folders into the active matter workspace without disrupting established firm habits.

## Checklist for Maintaining Case Files Across the Litigation Lifecycle

Establishing a digital litigation file hierarchy is only the first step toward effective case management; the system requires continuous operational discipline to remain reliable. Without scheduled maintenance routines, matter directories degrade over time as court deadlines accelerate, depositions multiply, and discovery volumes expand.

Litigation paralegals must implement standard operating procedures across each phase of the case lifecycle, from initial complaint filing to post-judgment closing. Enforcing structured weekly reconciliation schedules, standardized deposition wrap-up checklists, and rigorous pre-trial audit protocols ensures that the case file remains complete, accurate, and trial-ready at all times. Adopting these structured habits protects the trial record and eliminates last-minute scrambles before critical hearings.

### Weekly Docket Reconciliation and Deposition Completion

To maintain total file accuracy, paralegals should implement a weekly docket reconciliation routine:

* **Docket Audit:** At the close of each week, the paralegal reviews the court's electronic docket (such as federal PACER or state e-filing systems) against the firm's `01_Pleadings_and_Court_Filings/Filed_Court_Stamped` directory. Any minute entries, clerk notices, or third-party appearances that arrived without formal notice are downloaded, formatted with standard naming conventions, and cataloged.
* **Deposition Wrap-Up Protocol:** Following each deposition, the legal assistant secures the rough ASCII transcript, cross-checks marked exhibits against the court reporter's exhibit index, and updates the Master Exhibit Log. Once the final certified transcript and video files arrive, they are filed in the witness subfolder, and the paralegal's page-line summary is posted beside the transcript for attorney review.

### Pre-Trial Preparation and Matter Archival Transition

As a case approaches trial, the value of disciplined file management becomes decisive. Trial preparation demands the rapid assembly of judge's courtesy binders, witness cross-examination folders, and trial exhibit volumes:

* **Witness Examination Kits:** Paralegals pull documents directly from the witness subfolders and exhibit registers to assemble witness binders containing the deposition transcript, marked exhibits, prior sworn statements, and key impeachment materials.
* **Court Exhibit Staging:** Trial exhibits are designated with official court trial exhibit numbers (for example, `Plf-Trial-Exh-001`), cross-referenced against the Master Exhibit Log, and staged in `06_Attorney_Work_Product_and_Trial_Prep/Trial_Briefs_and_Motions_in_Limine/`.

When litigation concludes through settlement or final judgment, the matter transitions to inactive archival status. The paralegal conducts a final file hygiene check:

1. Verify that all executed settlement agreements, releases, and dismissals with prejudice are filed in the permanent record.
2. If settlement agreements or client engagement terms require signature, [e-signature](/product/e-signature/) allows case teams to send documents for signature directly from the workspace with signers in sequence or parallel, generating a tamper-evident audit certificate and filing the executed document back into the workspace.
3. Remove unneeded scratch notes and duplicate working drafts, retaining only official court filings, certified transcripts, final discovery exchanges, and the Master Exhibit Log.
4. Archive the workspace according to the firm's document retention policy, ensuring the matter record remains intact and searchable should subsequent enforcement or post-judgment proceedings arise.

## Frequently asked questions

### How do paralegals organize litigation case files?

Litigation paralegals organize case files using standardized, matter-centric folder hierarchies structured by procedural phase. A production-ready litigation directory separates materials into six core tiers: pleadings, judicial orders, written discovery, document productions, depositions, and attorney work product. Every document follows an ISO date-based naming convention (YYYY-MM-DD), and active drafts maintain per-file version history so attorneys can retrieve court filings, discovery responses, and marked exhibits instantly.

### What should be included in a legal case file?

A complete litigation case file should contain all formal court pleadings (complaints, answers, affirmative defenses), judicial orders and scheduling directives, propounded and received discovery requests (interrogatories, requests for production, requests for admission), outgoing and incoming document productions with Bates stamps, certified deposition transcripts with marked exhibits, formal party correspondence, client intake documents, and internal attorney work product such as legal research memoranda, witness outlines, and exhibit logs.

### What is the best way to structure digital case files for law firms?

The most effective digital legal file structure uses zero-padded numerical folder prefixes (such as 01_Pleadings, 02_Orders, 03_Discovery) within an isolated matter workspace. This numerical prefix enforces an identical chronological and procedural order across all devices and operating systems. Within each primary folder, subdirectories separate drafts from court-stamped filings and keep incoming third-party productions distinct from client source files, preventing accidental data mixing and preserving evidentiary chain of custody.

### How should paralegals track and organize deposition exhibits?

Paralegals should track deposition exhibits by maintaining a centralized Master Exhibit Log and creating dedicated per-witness subdirectories inside the depositions folder. Each marked exhibit should be named with the deposition date, witness name, exhibit number, document description, and corresponding Bates range. The master log records the exhibit number, document date, sponsoring witness, whether the exhibit was marked or admitted, and any pending objections, providing trial attorneys with a live index during hearings.

### How do legal teams maintain version control during intensive brief drafting?

Legal teams maintain version control by avoiding manual filename suffixes such as 'Draft_Final_v2.docx'. Instead, teams use workspaces with automatic per-file version history, where the active file retains a clean, standardized filename while the system automatically records every edit, author checkpoint, and timestamp. If an attorney needs to compare revisions or roll back a modification prior to filing, any previous iteration can be restored without creating folder clutter.

### What is the proper procedure for organizing incoming discovery productions?

When receiving discovery productions from opposing counsel or third parties, paralegals should immediately verify the Bates number range against the transmittal letter to confirm no pages are missing. The received production must be archived in an untouched, read-only incoming productions folder to protect evidentiary authenticity. The paralegal then verifies that accompanying load files align with native files and ensures all PDF documents undergo optical character recognition for full-text searchability.

## Sources

- [Google: Gmail Help](https://support.google.com/mail/answer/6584): Google restricts attachment sizes in personal Gmail accounts to 25 MB.

## About Fast.io

Fast.io provides shared workspaces where people and AI agents work on the same files, with built-in semantic search and citation-backed chat over what they hold. Agents reach it through a remote MCP server, a REST API at https://api.fast.io/current/, and a command line client published on npm as @vividengine/fastio-cli. MCP setup is at https://mcp.fast.io/docs: Claude and most MCP clients connect to https://mcp.fast.io/mcp/tools, ChatGPT to https://mcp.fast.io/mcp/operations, and coding agents to https://mcp.fast.io/mcp/code.