Organize contracts, agreements, and legal files with clear naming that includes document type, parties involved, and execution date for easy retrieval and compliance.
{date}-{doc_type}-{party1}-{party2}-{subject}| Field | Description | Example |
|---|---|---|
| {date}AI | Document or execution date | 2024-03-15 |
| {doc_type}AI | Type of legal document | contract, nda, agreement |
| {party1}AI | First party (usually your company/name) | acme-corp |
| {party2}AIOptional | Second party or counterparty | techstart-inc |
| {subject}AI | Brief subject or matter description | software-license |
Organize client contracts and case files
Manage vendor and client agreements
Track property documents and leases
Maintain audit-ready documentation
Legal documents are time-sensitive to locate. When a counterparty requests a signed copy of a 2022 NDA or an auditor asks for the vendor contract executed in January, the ability to search 2022-nda-acme-* and immediately retrieve it — versus opening a folder labeled "Contracts" and scrolling through 200 files — is the difference between a two-minute task and a two-hour one.
Date-first naming means contracts sort chronologically in any file manager without any special tooling. Every sorted view is automatically a timeline of your legal history. You can glance at the folder and see whether you have a current agreement in place, when it expires, and what amendments have been made.
For compliance and audit purposes, a consistent naming convention creates an implicit index. Auditors and regulators can verify document completeness by scanning filenames alone. A folder of well-named contracts communicates professionalism and preparedness before a single file is opened.
The default pattern suits general business contracts. These variants fit specialized practice areas:
Matter-based (law firms)
{matter_id}-{date}-{doc_type}-{party}-{subject}e.g. M2024-001-2024-03-15-contract-smith-retainer.pdf
Real estate
{property}-{date}-{doc_type}-{party}e.g. 123-main-st-2024-03-15-lease-jones.pdf
Employment
{date}-{doc_type}-{employee_id}-{subject}e.g. 2024-03-15-nda-emp-007-confidentiality.pdf
2024-06-01-amendment-acme-techstart-software-license-v2.pdf. This creates a clear link between the original agreement and its modifications without renaming the original.acme-techstart-deal_closed-2024-06). Individual file names remain intact for reference.It defaults to agreement as the doc_type. You can correct it in the rename preview before confirming — the preview shows the proposed filename for every file so nothing is renamed without your review.
Only for drafts. Final executed documents should not carry version numbers — use the execution date as the definitive identifier. Adding a version number to an executed contract implies it could be superseded, which can create legal ambiguity.
With the self-managed AI key (BYOK) or local Ollama mode, document content is sent only to your chosen provider under your own API key. No data passes through FilesDesk servers. For highly confidential matters, Ollama local mode means content never leaves your machine.
Yes — use the matter-based alternate pattern and include the case number in {matter_id}. For example: CV2024-12345-2024-03-15-motion-plaintiff-summary-judgment.pdf. The case number at the front makes the filing instantly locatable by docket number.
Download FilesDesk for professional legal document management.
Download FilesDesk