What it means to rename legal contracts by content
To rename legal contracts by content is to read the agreement inside a file and use what it says to name the file. The OCR layer opens the contract, finds the title, the parties, the effective date, and the contract type, and writes a filename like nda_mutual_brightline-partners_terraforma-inc_2025-04-10.pdf from what it found. The contract itself is untouched. No clause is edited, no term is restated, no party is added or removed. The only thing that changes is the filename on disk.
This is the difference between content-based renaming and a rule or template. A rule says "if the file came from the legal folder, prefix it with LEGAL_." A template says "fill in the parties and date by hand, then save." Neither one knows what is inside the file. Content-based renaming reads the agreement and names the file from it, so a scanned NDA and a typed SOW land with names that actually tell you what they are. It is a naming layer, not a contract lifecycle management system. Renamer.ai does not track obligations, send renewal alerts, route approvals, handle e-signature, or replace your CLM. It reads the contract and names the file.
The fields renamer.ai reads inside your contracts to name the file
When renamer.ai opens a contract, it pulls a set of fields from the content and uses them to build the filename. The fields it reads:
- Contract type - NDA, MSA, SOW, amendment, letter agreement, or another agreement class, read from the title and opening clauses
- Agreement title - the named title of the agreement, such as "Mutual Non-Disclosure Agreement" or "Master Services Agreement"
- Party A - the first named party to the agreement, read from the preamble
- Party B - the counterparty, read from the preamble or signature block
- Effective date - the date the agreement takes effect, read from the effective-date clause
- Execution date - the date the last signature was added, read from the signature block
- Contract number - any reference or contract number printed on the agreement
- Jurisdiction - the governing law or jurisdiction named in the agreement
- Term length - the duration of the agreement, read from the term clause
- Renewal type - whether the agreement auto-renews, renews on notice, or terminates, read from the renewal clause
- Document status - draft, executed, countersigned, or amended, inferred from signature and watermark signals
- Amendment reference - for amendments, the parent agreement the amendment modifies, read from the amendment's recitals
Twelve fields, pulled from the content, combined into a filename. Not every field appears in every contract, and the naming template decides which ones surface in the final name.
How to rename legal contracts by content
Step 1 - Drop or import your contract files
Pull your contract files into renamer.ai. A batch can be mixed: NDAs, SOWs, amendments, master services agreements, scanned PDFs, and typed Word files in the same import. There is no need to sort by type first, because the content-reading step does the sorting for you. A folder of two hundred contracts from a closing or a vendor onboarding batch goes in as one drop.
Step 2 - AI reads each contract's content with OCR
Renamer.ai opens each file and reads the agreement inside. For typed contracts it reads the text layer directly. For scanned contracts and phone photos of signed pages it runs OCR to recover the text, then reads the title, parties, dates, and contract type from the recovered content. Each file gets a proposed filename built from the fields the AI found. A scanned NDA with no text layer still gets named from the parties and effective date the OCR recovered off the page.
Step 3 - Review and apply the content-based file names
Every proposed filename is shown next to the original before anything is renamed. You scan the list, confirm the names that read right, fix any the OCR misread, and apply. A batch of two hundred contracts is reviewed and renamed in a few minutes. The files keep their original extensions and the content inside them is never touched. Only the filenames change.
Before and after
The table below shows how contract files look before and after content-based renaming. Every after-name is built from what the AI read inside the file.
| Before | After |
|---|
| contract_final.pdf | nda_mutual_brightline-partners_terraforma-inc_2025-04-10.pdf |
| scan_20250422.pdf | statement_of_work_halcyon-bio_northgate-logistics_2025-04-22.pdf |
| Document(8).pdf | amendment_msa_sundial-media_olu-adeyemi_2025-05-03.pdf |
| IMG_20250415_130000.jpg | service_agreement_northgate-logistics_marta-kowalski_2025-04-15.jpg |
| email_attachment(2).pdf | master_services_agreement_brightline_ravi-subramaniam_2025-05-12.pdf |
The first column is what you have today: filenames that tell you nothing. The second column is what the file becomes once the AI reads the agreement inside it. A name like nda_mutual_brightline-partners_terraforma-inc_2025-04-10.pdf tells you the type, both parties, and the effective date before you open the file.
Copy-ready naming templates for legal contracts
These templates are the patterns renamer.ai fills from the content it reads. Pick the one that matches how your team files contracts, and the AI populates it from the fields inside each agreement.
- {doctype}_{partyA}_{partyB}_{effectivedate}.pdf - the content-derived template. Both parties and the effective date, straight from the preamble and the effective-date clause. Best for agreements where the counterparty matters most, like NDAs and MSAs. Example: nda_mutual_brightline-partners_terraforma-inc_2025-04-10.pdf.
- {doctype}_{contract#}_{date}.pdf - the reference-number template. The contract or reference number printed on the agreement, plus the execution date. Best for teams that file by reference number, like vendor contracts and procurement files. Example: statement_of_work_SOW-2207_2025-04-22.pdf.
- {doctype}_{partyA}_{jurisdiction}_{effectivedate}.pdf - the jurisdiction template. The governing law named in the agreement, plus the first party and effective date. Best for cross-border contracts where the jurisdiction is the filing key. Example: msa_halcyon-bio_delaware_2025-04-10.pdf.
Three templates, each filled from fields the AI read inside the contract. The first two are the load-bearing pair; the third is for teams that file by jurisdiction.
Contract-file naming is one layer of how legal document management fits together. It makes sure every NDA, SOW, and amendment lands already named by what is inside it, so the matter and case-file context around it stays findable.