Courts deciding where exhibits should be submitted are choosing between an online evidence portal for court exhibits and the eFiling route they already run. eFiling systems were designed around a document. A pleading is a few hundred kilobytes, it renders as a page, it needs no playback, and nobody worries about whether it will still open in 2040.
Courts now receive four hours of body-worn camera footage, a phone extraction, and a folder of CCTV in a proprietary wrapper. Those arrive at a system built for pleadings, and the results are predictable: rejected uploads, files split across submissions, counsel couriering hard drives because the portal timed out, and exhibits that reach the court with no metadata attached.
The decision in front of most courts is whether to widen the eFiling route, stand up a separate online evidence portal for court exhibits, or run both with a defined split. The guide to court digital evidence management treats this as one of the two or three decisions that shape everything downstream, and this article works through it.
Why eFiling breaks on media
The failure modes are specific rather than general, which is useful because it means they can be tested for.
Size limits are the obvious one, and they are usually set by the platform rather than by policy. Format handling is the less obvious one: an eFiling system typically converts submissions to a standard format for the docket, and converting video either fails or silently degrades it. Neither outcome is acceptable when the file is evidence.
Playback matters more than it sounds. A judge reviewing an exhibit needs to watch it, at variable speed, possibly frame by frame. An eFiling system that stores video as an attachment to be downloaded pushes that problem onto whoever opens it, which means the reviewing experience depends on what software happens to be on that person's machine.
Then there is custody. Documents in an eFiling system have a filing record, which is not the same as a chain of custody. For evidence, a court may need to show that a file has not changed since submission, and that requires integrity verification the eFiling system was never asked to provide.
The three models
| Model |
What it does well |
What it costs you |
Fits a court that |
| eFiling only |
One route for parties to learn, one integration with the docket, simplest to administer |
Breaks on size, format conversion, playback and custody, in exactly the large cases where evidence matters most |
Has low media volume and modest file sizes, or no capacity to run a second system |
| Separate evidence portal |
Playback, integrity verification, real size limits, evidence-appropriate metadata |
Parties now have two systems, and the court must keep records in both pointing at the same case |
Receives substantial media and has the integration capacity to keep two routes aligned |
| Both, with a defined split |
Documents through eFiling, media through the portal; each route does what it was built for |
Requires a written allocation rule and working integration, or it becomes reconciliation work |
Is most courts, once volume passes the point where eFiling alone stops coping |
The third row is where most courts land, and the rule has to be written down, because "large files go to the portal" invites arguments about what counts as large.
There is no universally right answer. The variables that decide it are your eFiling platform's actual limits, your media volume by case type, whether your jurisdiction mandates a particular filing route, and how much integration capacity you have.
Keeping metadata and identity consistent across two routes
Running two submission paths creates a reconciliation problem that courts consistently underestimate.
The same case exists in both systems. The same party is filing into both. If the case identifier is entered independently in each, they will diverge, and an exhibit will end up associated with a case number that does not quite match the docket. Standardized naming, required metadata, and validation at the point of upload are what prevent this, and they have to be enforced by the system rather than requested in a practice note.
Identity is the other half. If a party authenticates separately to each route, the court has two records of who submitted what and no straightforward way to join them. Single sign-on across both, covered in integrating an evidence system with the court case management system, is what makes the split invisible to the person filing.
Whatever arrives also has to feed the exhibit list correctly, which is the subject of the digital exhibit lifecycle. A submission route that captures no exhibit metadata pushes that work back onto the clerk.
Access after submission, not just at it
Submission is the beginning. The portal also has to control what happens next.
Role-based access so parties see their own material and what they are entitled to receive. Time-limited sharing so access expires rather than persisting indefinitely, which is the same control set covered in the guide to securely sharing digital evidence with defense, applied here to submission rather than disclosure. Compliance with protective orders, which means the portal has to understand that some material is restricted to named individuals. And an automated audit trail for every upload, view, download, and change.
NCSC describes exactly this set for an online evidence portal, and adds a requirement worth quoting in spirit: the system should make it hard to share files that were not intended to be shared. That is a design property, not a training issue.
The filer nobody designs for
Both routes assume a competent professional filer. A growing share of submissions come from people without counsel, filing from a phone, with a video they recorded themselves and no idea what metadata means.
An evidence portal that works for a law firm and defeats a self-represented litigant has not solved the court's problem, it has moved it to the counter. Assisted submission, plain-language instruction, and format help belong in the design, which is covered in designing evidence submission for self-represented litigants.
How VIDIZMO DEMS handles submission
DEMS provides the portal side of this arrangement rather than replacing an eFiling system.
Relevant capabilities: ingestion across a wide range of media and document formats without forcing conversion, including proprietary CCTV wrappers that commonly defeat general-purpose systems; browser-based playback with variable speed and frame-by-frame review, so the reviewing experience does not depend on the viewer's local software; hash-based integrity verification from the point of submission, so the court can demonstrate a file has not changed; and time-limited, monitored access links with role-based permissions for what happens after submission.
Where it does not help: DEMS is not an eFiling system and does not file into a docket. Courts under a statutory obligation to accept filings through a designated platform should treat DEMS as the evidence route alongside it, not as a replacement.
Deciding
Three questions settle it for most courts.
What is your eFiling platform's real limit, tested with an actual four-hour video rather than quoted from documentation? What proportion of your docket by case type actually involves media of that scale? And do you have the integration capacity to keep two routes aligned, or will a split create a reconciliation problem worse than the one it solves?
A court with modest media volume and no integration capacity is often better served by pushing its eFiling vendor on limits than by standing up a second system it cannot keep synchronized.
Explore DEMS to test ingestion, playback, and access control against the file types your court actually receives.
