Trial Preparation When the File Is Digital

The old way of preparing for trial was physical and therefore obvious. Somebody built the banker's boxes, somebody tabbed the exhibits, and when a document went into a box it was visibly gone from the general file. You could look at a conference room table and know exactly what was going to court. The whole system had an audit trail made of cardboard and sticky tabs, and its main weakness was that it took two weeks of paralegal time and could not be duplicated cheaply.

Digital files removed the two weeks and quietly removed the obviousness along with it. A trial set now lives as a folder tree on someone's laptop, a shared drive, or a tablet, and nothing about it announces which version of the file it came from. The document you dragged into the exhibit folder six weeks ago has no idea that the underlying agreement was superseded in a supplemental production, and neither does the associate who is going to hand it to a witness. The failure mode is no longer a missing box. It is a working copy that stopped matching the master file at some point nobody can identify.

That is the actual problem worth solving, and it is not solved by better folder naming. It is solved by treating the trial set as a filtered view of the live matter rather than a separate pile of files, by deciding deliberately what has to exist offline, and by having a rule for what happens when the two diverge. What follows is how to build that, aimed at firms that run litigation out of a practice management system rather than out of a shared drive and a spreadsheet.

Start From the Matter, Not From a Folder

The first decision determines everything downstream. If your trial set begins life as a new folder that people copy documents into, you have created a second file that will start drifting the moment anyone touches either side. If it begins life as a saved selection inside the matter, tagged and ordered but still pointing at the master documents, it inherits every correction, every replacement and every access rule automatically. The difference sounds academic until the week before trial, when a client sends a corrected version of a contract and you need to know instantly whether that document is in the set.

In Casely this works because documents live on the matter and carry a comment field recording what changed and why. When a document is replaced, the reason is written into the record rather than living in someone's memory of a phone call. Building the trial set as a labelled selection over those documents means the exhibit you pull on the third day of trial is the same object the rest of the team has been working on, not a snapshot of what it looked like in July. You still control what is in the set. You just stop maintaining two truths about what each document says.

The Exhibit List Is a Document With Its Own Life

An exhibit list is not a table of contents. It is a working document that gets exchanged with opposing counsel, argued over, amended by the court, and then relied on by everyone in the room for the duration of the trial. It has a numbering scheme that must survive additions and withdrawals, it carries objection status per item, and it usually needs to exist in at least two forms: the version filed or exchanged under the pretrial order, and the internal version with your own notes about which witness introduces what.

Keep both, and keep them attached to the matter rather than to a person. The exchanged version is a filed document with a date and a recipient, and it belongs in the file with that context recorded. The internal version is a live working document that changes daily as you refine the order of proof. What you must never do is maintain the internal version as the only version and then reconstruct what you exchanged from memory. Practice varies by jurisdiction on how exhibit lists are exchanged and amended, and the specific judge's standing orders often matter more than the general rule, so confirm the local requirements before you design your numbering scheme around an assumption.

Witness Folders Are Views, Not Copies

Every trial team eventually builds a folder per witness containing the documents that witness will be shown. The instinct is to copy the exhibits into it, which immediately creates the duplication problem again, and worse, creates it several times over because the same exhibit shows up in four witness folders. Now a correction has to be applied in five places and you will find the one you missed while the witness is on the stand.

The better structure is a witness folder that lists exhibit numbers and points back to the single stored document. Add the examination outline, the deposition or witness statement extracts, and the impeachment material as their own items in that folder, because those genuinely are separate documents rather than duplicates. When the witness order changes, and it always changes, you are reordering a list rather than reshuffling files. Casely's connected matters feature is useful here for the adjacent case that keeps producing relevant testimony, because it links the related matter with the reason stated instead of leaving a colleague to guess why two files keep referencing each other.

Demonstratives Need a Chain Back to Evidence

Demonstratives are the part of the trial set most likely to be built outside the file. Somebody makes a timeline in a slide deck on their own laptop, somebody else builds a chart from a spreadsheet, and neither of those artifacts records where its numbers came from. Then opposing counsel asks what the chart is based on, and the honest answer is that an associate built it in March from a production set that has since been supplemented.

Treat every demonstrative as a document in the matter with a source log attached. The comment field on the document is the natural place to record which exhibits the demonstrative draws from and what version of each was used. This is not bureaucratic caution, it is the difference between being able to defend the exhibit and having to withdraw it. Admissibility standards for demonstrative aids differ across US state and federal courts, and the position in England and Wales, Canada and Australia is not identical, so check what your court expects before you invest days in something that may only ever be a jury aid rather than an exhibit.

Decide What Goes Offline Before You Need It

Courthouse connectivity is not a thing you get to rely on. Basements, thick walls, guest networks that block everything, and buildings that will not let you carry in a personal hotspot are all normal. Assume the cloud is unavailable for the entire trial day and work backwards from there. That does not mean printing everything. It means deciding, deliberately and in advance, which subset must exist locally and in what form.

The practical answer for most trials is a local copy of the numbered exhibit set, the witness folders, the exhibit list in both forms, the pleadings and orders that govern the trial, and the demonstratives in a format that opens without a network call. Test that it opens on the actual device that is going to the courthouse, not on the machine that built it. A slide deck that pulls fonts or linked images from a server will look fine on the laptop that made it and fail in the courtroom, and the person who discovers that will be you, standing up.

Encryption and Loss Are Not Hypothetical for a Trial Bag

A laptop carrying the full trial set of a contested matter is the most sensitive object your firm will move around in a given month, and it travels through public buildings, hotels and taxis. The security question is not whether your cloud storage is encrypted, because it is. The question is what is on the local device and what happens if that device leaves your possession. Full disk encryption on the trial machine is the floor, not the ceiling.

This is where the underlying storage model matters. Casely encrypts documents with AES-256 using a per-firm key, so the copies at rest in the system are protected independently of any device. What that does not do is protect an unencrypted export sitting on a laptop desktop. Build the offline kit into an encrypted container, keep a written record of exactly what it contains, and delete it after trial rather than leaving it on the machine to be found in an audit two years later. Data breach notification duties differ significantly across jurisdictions, and the analysis of a lost device turns on what was actually on it, which is a good reason to know.

Access, Ethical Walls and the Team That Grows Overnight

Trial preparation is when firms bring in help. Contract attorneys, a second-chair from another office, a paralegal borrowed from a different practice group, sometimes an outside consultant. Every one of those people needs fast access to a large amount of material, which is exactly the moment when careful access control gets abandoned in favour of a shared folder link. That shortcut is how a walled-off user ends up reading a matter they were specifically screened from.

Ethical walls only work if they are enforced where the data is served rather than in the interface. Casely enforces them at the server and data-access layer, which means a walled user genuinely cannot reach a restricted matter through search, through the calendar, or through a link someone forwards them in good faith. That property is worth more during trial prep than at any other point in a matter's life, because trial prep is precisely when links get forwarded fast and nobody has time to think about who is on the thread. Screening obligations vary between jurisdictions, and some regimes require client notice, so confirm what applies to your firm before you rely on a technical control alone.

Keeping the Working Set in Sync With the Master File

Drift is inevitable if you do not have a named person and a named moment. The rule that works is simple: the master file is authoritative, the working set is refreshed on a schedule, and nothing enters the working set except through that refresh. Pick a daily time during the trial itself, usually the evening, and make one person responsible for reconciling what changed in the master against what is in the kit.

The reconciliation is short if the trial set is a view rather than a copy, because most of it happens automatically and you are only checking exports and offline material. It is long and error-prone if the set is a copy, because you are diffing folder trees by hand at nine in the evening. Whichever structure you have, write down what changed each day and why. Casely's document comment field is the obvious place for that, and the habit pays for itself the first time someone asks in open court why exhibit fourteen is dated differently from the version in the bundle.

The Bundle Question, and Why Terminology Matters Here

If you practise in England and Wales, the trial bundle is a formally regulated object with rules about pagination, indexing, timing and who prepares it, and electronic bundles have their own requirements that have been the subject of repeated practice guidance. If you practise in a US court, you are working from the pretrial order and the judge's standing orders, and the expectations about format can differ from courtroom to courtroom within the same building. Canadian and Australian courts each have their own conventions again.

The mistake is assuming your habits travel. A team that has built US-style exhibit sets for a decade will produce something that is technically complete and procedurally wrong for a jurisdiction that expects a paginated, indexed, hyperlinked bundle delivered in a particular way. If your firm handles work across jurisdictions, keep a short internal note per court about what the trial set has to look like, store it on the matter or as a firm reference, and read it at the start of prep rather than the week of trial. Confirm the current requirements locally, because practice directions and standing orders change.

Trial Weeks Are Also Billing Weeks

Nobody enters time during trial. That is understandable and it is expensive, because trial weeks are the highest-volume billable weeks a litigator has and reconstructing them a fortnight later loses hours in every direction. The team is exhausted, the days blur, and the memory of Tuesday afternoon is genuinely gone by the following Monday. The fix is not discipline, it is reducing the entry to something that takes seconds at the end of the day.

Capture time against the matter as you go, even roughly, and clean it up in the evening reconciliation you are already doing. Because Casely turns every unbilled hour into one itemised draft with a single click, the cleanup step produces something billable immediately rather than starting another project. For firms handling institutional or insurer clients, LEDES 1998B export means the trial's time entries land in the client's e-billing system in the format it expects rather than being retyped. If the matter is running against a retainer, the trust ledger enforcement matters too, since Casely blocks any disbursement exceeding the matter's actual trust balance at the database transaction level, which is a useful property during a week when expert fees and transcript costs are flying around.

After the Verdict, Collapse the Set Back Into the File

The last step is the one that never gets scheduled. When trial ends, the working set exists on several devices, the exhibit list has been amended by the court, demonstratives were modified overnight during the trial, and none of that has been reflected in the matter. Somebody has to reconcile it, and if it does not happen in the first week it will not happen at all. Book that time before trial starts, because you will not volunteer for it afterwards.

Collapsing the set means updating the master file with what actually happened, recording the final admitted exhibit list, noting which demonstratives went in and which were excluded, and then destroying the offline copies with a written record that they were destroyed. Casely's conflict checking searches the full contact and matter history including closed matters, which only works properly if the closed matter reflects reality, so a sloppy post-trial file quietly degrades a control you will rely on years later. The same is true of the deadline diary, since post-trial deadlines for appeals and costs applications attach to the matter and need next-date tracking from the moment the verdict lands.

The Structure Is the Preparation

The firms that handle digital trial preparation well are not the ones with the best folder conventions. They are the ones that decided early that the matter file is authoritative, that the trial set is a view over it, and that anything living outside that structure has a named owner and an expiry date. Everything else in this article follows from those three decisions, and no amount of careful naming makes up for getting them wrong.

If your current setup means the trial set only exists as copies on laptops, the fix starts with where the documents live and who can reach them. Getting legal document management right is what makes the rest of it possible, because a trial set built over a properly permissioned, versioned, encrypted document store is a filter you can rebuild in an afternoon, while a trial set built over a shared drive is an artifact you can only maintain by hand. Casely is cloud-native with no local install and a Free plan to start, which means you can test the structure on a single matter before committing a live trial to it.

Do that on the next case, not the next trial. Build the set the disciplined way while the stakes are ordinary, find out where your process leaks, and fix it in a month where nobody is waiting on you in a courtroom. The point of preparation was never the boxes. It was knowing, with certainty, that what you are about to hand a witness is the document you think it is.