A single central model on a federal courthouse project can carry years of authorship stamps, worksharing logs, and milestone snapshots that nobody on the team meant to produce as testimony. Once a dispute turns criminal, those saved versions stop being design history and start being exhibits. Prosecutors reach for them because they answer the two questions investigators keep asking: who knew what, and when did they know it.
The risk isn’t that someone drew the wrong wall. It’s that the model remembers every revision, every overwritten element, and every owner who touched the file, and that record now moves through discovery the same way email does.
If you lead a design, construction, or owner’s rep team on anything federally funded, the file sitting in your worksharing environment is already a potential witness.
Before the Dispute: The Model Is Already a Business Record
Federal projects have required BIM for close to two decades. GSA’s Public Buildings Service launched its national BIM program in the early 2000s, and the agency’s current facilities standard treats BIM as an essential method of project delivery. That history matters. It sets a reasonable expectation, in the eyes of a court, that these models exist, that they are maintained, and that they can be produced.
Once a model is a required deliverable, it is a business record. It’s kept in the ordinary course, relied on by the parties, and carries the hallmarks courts look for when deciding whether something is admissible. The central file you check into every evening is already the kind of document a subpoena can reach, which is why federal defense firms like Chapman, Dowling & Mallek get called in before the first production letter even goes out.
A few things sit inside that record that teams rarely think about until a lawyer asks:
- Authorship history. Revit tracks who created and last edited the file, and the Collaborate tab’s Show History view surfaces date and time stamps for authors on the central model.
- Worksharing logs. Every sync writes a record of which user touched which worksets, visible to anyone who knows where to look.
- Milestone saves. Design development, construction document, and issued-for-construction models, plus every archived snapshot in between, live on somebody’s server.
- Linked models and shared parameters. The structural, MEP, and civil files, plus the clash reports generated against them, pull in a wider circle of authors than the architectural team alone.
During the Project: Every Save Is a Snapshot a Subpoena Can Reach
The model you ship at substantial completion isn’t the only one that matters. The intermediate versions do most of the work in a dispute, because comparing them is how an expert reconstructs who changed what and when. A milestone comparison can show the extent of design development between two dates, which elements moved, and which coordination issues were flagged and then quietly dropped.
That’s also why flattening a Revit file to PDF is not a preservation strategy. A DISCO explainer notes that BIM files are highly dynamic, with layers of metadata and embedded historical changes that cannot be reduced to a static page without losing context. The native file, with its versions intact, is the evidence.
When the Letter Arrives: Preservation Starts Immediately
A preservation obligation can attach well before anyone files a complaint. It triggers when litigation is reasonably anticipated, which in federal construction work can be as early as a serious owner complaint, an OIG inquiry, or a qui tam filing you haven’t yet seen. From that moment, routine deletions, auto-purges of old central file backups, and casual “cleanups” of the server all become dangerous.
If a court finds you failed to take reasonable steps to preserve electronically stored information and that the lost information can’t be restored, the next question is intent. Under Federal Rule 37(e), a court can impose the harshest sanctions, including adverse inference instructions or dismissal, only on a finding that a party acted with the intent to deprive another party of the use of that information. The deletion doesn’t have to be dramatic to meet that bar. It just has to look purposeful.
A sensible first-hour response usually includes:
- Freeze the central model. Suspend auto-purge, lock the project folder, and preserve all backups, journal files, and linked models in place.
- Issue a written litigation hold. Name the project, name the custodians, and tell people in writing to stop deleting anything connected to it.
- Capture the environment. Record Revit versions, add-ins, and shared parameter files so the model can later be opened as it existed on the key dates.
- Loop in counsel before producing anything. If the matter has any federal exposure, call a defense firm that handles white-collar and federal investigations before you hand files to the government or an owner’s forensic consultant.
Revit and BIM files can reveal far more than a project’s final design, making revision histories, metadata, and archived models valuable evidence when construction disputes or federal investigations arise. By establishing clear preservation procedures and understanding what these digital records contain, construction teams can protect critical information and avoid additional legal complications when their work comes under scrutiny.
