Your files stay in Drive. DilloLex puts the finished work product back where it belongs.
Most Nevada firms already keep their matter files in Google Drive. They do not need a new document management system; they need the documents that come out of a process to end up in the same place they started. DilloLex reads the folder the firm already has, does its work on hardware the firm owns, and writes the finished, named, approved document back into that same folder when the attorney says so. The original is never touched. No portal. No migration. No new login for staff to manage.
General information for Nevada legal professionals. This is not legal advice. Read the full disclaimer.
The problem with every other approach
There is a standard failure mode in legal technology adoption: the tool works well, but it produces output in its own portal. The finished demand letter, the stamped production set, the draft motion, the redacted medical record, all of it lives in a vendor dashboard the firm has to log in to separately. Staff develop a habit of working in two places. The attorney asks for the file and learns it is in the tool, not in the matter folder. A few months in, someone emails the PDF out of the portal and drops it into Drive by hand, which is where it should have been in the first place.
DilloLex is designed to avoid that loop. The firm's storage is the starting point and the ending point. The tool works in the middle.
How the connection works
The DilloLex appliance connects to the firm's Google Drive using credentials the firm controls. The connection is read-write: the appliance reads the matter folder to do its work, and it can write a finished document back to a designated review subfolder within that same matter structure when the attorney approves it.
The appliance reads document content locally after syncing from Drive. All AI reasoning runs on the appliance. No client content goes to an outside AI during that process. The connection to Drive is a storage connection, not an AI connection; files move between the firm's appliance and the firm's cloud account.
The write-back step is gated. Nothing is written back to Drive automatically. The attorney reviews the proposed output in DilloLex, approves it, and the appliance then copies the finished file to the review folder the firm designates. The firm controls the folder structure, the naming convention, and the approval step.
What the firm keeps control of
The firm keeps full ownership of its storage. Drive folders, sharing permissions, and folder structure remain exactly as the firm has them today. DilloLex reads from and writes to the locations the firm points it at; it does not restructure the firm's files, rename folders, or change permissions. The appliance works within the structure the firm already runs.
The firm also controls the review folder. When DilloLex writes a finished document back, it goes to a subfolder the firm designates, named for attorney review, not directly into the active matter folder alongside originals. The attorney moves it, renames it, or discards it. The originals stay exactly as they were.
Non-destructive output: the source file is never overwritten
This is the rule the appliance enforces without exception: a produced or processed document is always saved as a new file. A redacted version of a record is saved alongside the original with a distinct name, for example, the original medical record alongside a sibling file labeled with the date and the word redacted. The source file is never overwritten, never moved, and never deleted. If the attorney discards the output, the original is untouched. If the output is approved and written back, both files exist in Drive, and the source is still there to check against.
The same principle applies to Bates stamped productions, assembled appendices, and any other work product the appliance generates. The appliance creates; the firm decides what to keep. Read more about how the Bates numbering and production tools work within this same pipeline.
Named, ordered, and ready for the attorney's review
When a document comes out of the appliance, it arrives in Drive named and organized according to the firm's conventions. A draft motion is named for the matter and the filing type. A stamped production set arrives in the production subfolder with a Bates index alongside it. A redacted medical record arrives next to the original with a consistent naming suffix. The attorney opens Drive, finds what was proposed, and reviews it where the rest of the matter already lives.
This matters for workflow. The alternative is a finished document that lives in a tool the attorney has to remember to check, followed by a manual download-and-save step that someone may or may not complete before the deadline. When the output lands in Drive automatically after approval, the matter stays current without a separate filing step.
What happens at approval
Approval is always a human step. The attorney or supervising staff member reviews the proposed output in DilloLex, confirms it is ready, and triggers the write-back. The appliance then copies the file to Drive, names it per the firm's conventions, and logs the action. Nothing moves to Drive without that explicit step.
If the attorney does not approve, nothing changes in Drive. The proposed output remains in DilloLex pending a revision or discard. The matter folder in Drive reflects only what the attorney signed off on.
How DilloLex helps
DilloLex is software that assists a firm's staff. It does not practice law and does not replace the attorney's judgment. What it does is read the matter folder the firm already maintains, run its work on the firm's own hardware, and deliver the finished output back to that same folder after the attorney approves it. The source files are never overwritten. No client content goes to an outside AI. The attorney reviews every proposed output before it lands in Drive, and nothing is final until the attorney says so.
For a firm already running Google Drive, the change is not what storage to use. It is what the storage contains at the end of the day: not just the intake documents and correspondence, but the finished motion drafts, production sets, and processed records the firm's attorney actually approved, already named and filed where the rest of the matter lives.
To see how the integration works on a real matter folder, book a demo. You can also read more about how DilloLex handles the full matter workflow, the firm's security architecture, and what the appliance costs.
Common questions
Does DilloLex change the firm's existing folder structure in Google Drive?
No. The appliance reads from and writes to the folders the firm points it at. It does not restructure folders, rename existing files, change sharing permissions, or move content. The firm retains full control of its Drive structure. DilloLex works within whatever organization the firm already runs.
Can a produced or redacted document overwrite the original?
No. The appliance always saves output as a new file alongside the original. A redacted record, a Bates stamped production, or any other processed file is written with a distinct name. The source file remains untouched in Drive. Both the original and the output exist after approval, and the original cannot be overwritten by the appliance.
Who authorizes the write-back to Drive?
The supervising attorney or the staff member the firm designates reviews the proposed output in DilloLex and explicitly approves it before anything is written to Drive. The appliance does not push files to Drive automatically. The approval step is a human action, and the appliance logs what was written, when, and by whose authorization.
Does client content go to Google's servers when DilloLex reads from Drive?
Files move between the firm's Drive account and the firm's appliance over a secure connection. All AI reasoning runs on the appliance. No client content goes to an outside AI as part of that process. Google stores the files the firm stores there; that is an existing relationship the firm already has with Google. DilloLex does not route client content through any additional outside AI service.
What if a staff member forgets to approve before a deadline?
Nothing goes to Drive, and nothing is filed, without the approval step. DilloLex does not interact with courts or filing systems. The firm's staff is responsible for filing deadlines under the applicable Nevada rules, including NRCP, NRAP, and local court rules. DilloLex assists with document preparation; the attorney remains responsible for all professional obligations. Confirm current Nevada procedural rules before relying on any general information in this guide.
A note on accuracy
This guide is general information for Nevada legal professionals. It is not legal advice, it does not create an attorney-client relationship, and it does not address the requirements of any specific matter, court order, or applicable rule. Nevada NRCP, NRAP, EDCR, and local court rules are amended from time to time; confirm current rules and applicable bar guidance before relying on anything described here. Cloud storage providers, including Google Drive and Microsoft OneDrive, have their own terms of service, data handling practices, and security policies; the firm remains responsible for confirming that its use of any storage service is consistent with its confidentiality obligations under Nevada RPC 1.6 and applicable court rules. This is general information, not legal advice; consult the current Nevada RPC and relevant bar guidance before relying on any specific interpretation.