The signed version is the copy that carries every required signature, and for an e-signed document a good first place to find it is the completion message from the signing platform, not the file with "final" in its name. Confirm it by reading the signature page, then check its text against the last draft both sides agreed, and file every other version in an archive instead of deleting it.
A pile like contract_v2, contract_final and contract_FINAL_signed is a naming problem first and a records problem second. Below: a two-minute triage, a text check, a naming rule, and ways to compare versions without tracked changes. Which version is legally binding is a question for the parties or a lawyer, and the rules can differ by country, state and contract.
Why a File Called "Final" Proves Nothing
A file name is a label somebody typed. It cannot tell you whether a later edit arrived. Filestage, a maker of online proofing software, tells readers of its guide to document version control to never, ever, ever use the suffix _final, and calls it cursed. Its example of a naming scheme gone wrong is Legal_Policy_final_final_maybethistimeitisfinal_v9. Every extra round of edits makes the previous "final" untrue.
The cost is not only confusion. The contract-management vendor fynk opens its guide with a story in which a file called MSA_final_v4_clean.pdf comes back signed and the liability cap has changed, with nothing marked to show it.
The stakes sit in what happens when copies differ. Rocket Lawyer's legal-information answer says a contract is generally strongest when everyone signs the same final version, and that the outcome often depends on the differences between versions, the parties' intent and what happened after signing. That is general information, not a ruling, and it can change by place and by case.
Two jobs hide in this question. Finding and verifying the signed copy is a records task. Deciding what a contract means if versions disagree is a legal task. This guide covers the first.
The Two-Minute Triage: Find the Signed Copy First
Work from the outside in: signing platform first, signature page second, body text third. That puts the records created at signing ahead of a file name anyone could have typed.
Step 1: Find the completion message (about 30 seconds)
If the document went through an e-signature service, search the inbox for the completion notice and open the platform account. Dropbox's help page for its DocSend e-signature feature says that once every signer finishes, all parties receive a signed copy, and the certificate lists each event with a UTC timestamp. Adobe's learning pages say Acrobat Sign records every transaction's milestones in an audit report. A DocuSign community moderator says to request the Certificate of Completion from the sender or account administrator. What arrives differs by service, so download the completed file as soon as it lands.
Step 2: If it was signed on paper or sent as a scan
Search the photo library, the scans folder and email attachments by the other party's name and by the weeks around signing, not by the word "final". Then ask the other side for their copy. Australia's business.gov.au advises you to always keep a copy of any contract you sign, says it is best if both parties sign two copies so each keeps an original, and adds that otherwise you should ask for a photocopy and check that it is an exact copy. Rules can differ elsewhere.
Step 3: Read the signature page
A signature page answers who signed, when, and whether everyone required has signed. Bind, a workspace product for in-house legal teams, says in its guide that a contract carrying only your signature is signed but not yet executed. It advises checking the signature blocks against the parties named in the preamble, and recording both the execution date, when the last required signature is added, and the effective date, when obligations start. The two can differ.
- Every party named at the start has a signature block, and every block is signed.
- Names on the signature page match the opening paragraph, including company suffixes.
- Each signature is dated. The latest date is the execution date, when the last required signature was added.
- Every schedule or attachment the contract mentions is present.
Signature pages signed separately from the body add risk. Sprintlaw's New Zealand guide says to make sure everyone knows exactly which version those pages relate to. A version number or date in both footers makes that checkable.
Set a two-minute timer. If the parties, signatures and date line up, move to the text check. If anything is missing, ask the sender or the other party for the completed copy first.
Check the Signed Text Against What Was Agreed
A signed file can still hold the wrong text. Compare its body with the last draft both sides approved before filing it as the record. Sprintlaw's pre-signing checklist asks you to confirm that the version number or date is the latest one agreed and that there are no hidden tracked changes or comments. Check these items first.
- Names, addresses and company details of each party.
- Amounts, payment terms and due dates.
- The term, the renewal rule and the notice period.
- Limits on liability.
- The version number or date in the header or footer.
The fynk guide recommends comparing the exact draft you sent with the file you received, even when the returned file shows tracked changes, because the sender may have made edits that were not marked. It also describes a failure it calls approval attached to the wrong text: finance approves one draft, someone makes another edit, and a different version goes out for signature.
Bind warns that if a counterparty signs a version that differs from yours, you have a dispute about what was agreed rather than an executed contract. Whether a mismatch matters depends on the contract and the law that applies, which is a lawyer's territory.
Archive the Rest, Do Not Delete It
Keep exactly one file as the record and move every other version into a labelled archive. Bind says to store only the fully signed copy as the record, and calls a partially executed PDF beside the fully executed one a classic source of audit headaches. The fynk guide adds that the signed document belongs with its approved draft, negotiation history and approval record. Two folder levels fit both: record on top, history underneath.
- Top level: one signed PDF, for example Acme_MSA_v3_signed_2026-11-09.pdf.
- A subfolder named history: Acme_MSA_v1.docx, Acme_MSA_v2.docx, Acme_MSA_v3.docx and any partially signed copy.
- The email thread behind the negotiation, saved as a PDF, plus the platform's certificate or audit report.
- A one-line note on who signed, when, and where the record sits, as Sprintlaw's guide suggests.
Do not delete drafts to tidy up, because a deleted draft cannot be compared with the signed copy later. Retention rules for business records can differ by country and industry.
A Naming Rule That Ends the "Final" Mess
Use one stable file name, add a v1, v2, v3 suffix for each round, never use _final, and label the signed copy once, with its date.
- Keep one base name for the life of the document, such as Acme_MSA. Filestage lists this as one of three features of a good convention.
- Add a consistent version suffix and save a copy each review round: Acme_MSA_v1, Acme_MSA_v2, Acme_MSA_v3.
- Pick one separator and keep it. Filestage says underscores, hyphens and spaces all work.
- Never use _final. If a status label is wanted, fynk advises changing it only when the document reaches that stage.
- Label the signed copy with its version, the word signed and the date of the last signature: Acme_MSA_v3_signed_2026-11-09.pdf.
The UK Data Service recommends a systematic convention such as version numbers or dates, and shows a date in year-first order inside a file name: HealthTest-2008-04-06. Year first also keeps an alphabetical file list in date order. The same page advises a version table inside the file recording versions, dates, authors and changes.
Do not rename the old pile. Rename only the signed copy, move the rest into the history folder, and apply the rule to new documents from today.
How to Compare Two Versions Without Track Changes
Use your word processor's compare function if you have one, and ask the same questions of both files if you do not. Work on copies, never on the signed file itself.
Compare functions in common tools
In Word for Windows, open both documents, go to Review, then Compare, and choose the legal blackline option. Microsoft's page says the result appears in a third, new document, and the compared documents are not changed unless you choose to show the changes inside one of them. If either document has tracked changes, Word asks you to accept them to continue. On Word 2019 for Mac, the page lists Review, Compare, Compare Documents.
In Google Docs, choose Tools, then Compare documents, and pick the other file. Google creates a third document showing the differences as suggested edits. A Word file must be stored in Google Drive, and column layout and table column width are not compared. For PDFs, Adobe lists a feature that detects differences between two PDF files, available only in Acrobat Pro, Premium or Studio.
| Method | What you get | Limit | Best for |
|---|---|---|---|
| Word: legal blackline | A third document showing the differences | Word asks you to accept existing tracked changes | Two Word drafts |
| Google Docs: Compare documents | A third Google Doc of suggested edits | Word files must sit in Google Drive; column layout is not compared | Drafts in Google Docs or Drive |
| Acrobat: compare two PDFs | A check for differences between two PDFs | Acrobat Pro, Premium or Studio only | Signed PDF against the last PDF draft |
| Same questions, both files | Side-by-side answers on payment, notice and liability | Finds only what you thought to ask about | No compare tool, or a photo or scan |
| File hash (Get-FileHash) | Whether two files hold identical content, whatever their names | A different hash says the files differ, not where | Spotting renamed duplicates |
Ask the same questions of each version
When no compare tool is available, or a file is a photo or scan, read both versions for the same short list of terms and write the answers side by side. Keep the questions identical so the answers line up. Starter questions:
- "What is the payment term?"
- "What is the notice period?"
- "What is the liability cap?"
- "When does it renew?"
- "Who are the parties, and who signed for each?"
This finds only differences in the terms you asked about. A compare tool catches changes you did not think to ask about, like the changed liability cap in fynk's opening story. Treat the questions as a fast first pass.
Check whether two files are identical
Two files with different names may be the same file. Microsoft's documentation for the PowerShell command Get-FileHash says file names can change without altering the content or the hash, changing even a single character changes the hash, and identical hash values mean identical contents. It uses SHA256 by default. A different hash only says the files differ, so follow it with a compare.
Why You Still Confirm With the Other Party
A file you trust is still only your copy. Ask the other side to confirm in writing that the signed copy matches theirs, and keep the reply. The Australian guidance above points the same way: each side keeps a copy, and any copy is checked as exact. Rocket Lawyer notes that outcomes can turn on what happened after signing, so a record of what each side said afterwards is worth having.
A confirmation can be one line: "Attached is the signed copy dated 9 November. Please confirm it matches the copy you hold." Send it to the contact who handled the deal, and keep these together:
- The signed PDF, and the platform's certificate or audit report if there is one.
- The approved draft and the version sent for signature.
- The email thread behind the final text, including the confirmation reply.
If the two sides hold different texts, stop and take advice. The fynk guide says to start by preserving the signed document, the approved draft and the negotiation record, and that which terms bind the parties depends on the facts and the applicable law. A DocuSign community moderator adds that DocuSign Support cannot determine which version of a contract is legally valid.
Asking Two Saved Versions the Same Question
MemX can help with one part of this job: asking the same question of two saved versions. MemX Upload accepts photos, PDFs, text files, Word documents and audio, up to 20 MB each, and MemX reads the dates, amounts and names in them. With Chat With Documents you ask in plain English, and answers include source thumbnails and dates so you can open the original and check it.
The method matches the one the MemX employment-contracts page describes for two job offers: save both, ask the same question about each, and compare the answers. For two contract versions, upload both and ask "what is the payment term?" and "what is the notice period?" of each. If the answers differ, open both sources and read the clause itself.
The upload page also says MemX spots duplicates by file content, not file name, so the same file is not saved twice and a renamed copy is caught. A version with changed wording is a different file, not a duplicate of the version it replaced. MemX is private by architecture: encrypted at rest with a key per account, every read logged.
The honest limits: MemX does not show tracked changes or a line-by-line comparison, so it does not replace Word, Google Docs or Acrobat for a full compare. It does not decide which version is binding, and its answers are not legal advice. It works from files you add yourself, or that MemX Smart Scanner files from folders you allow, and does not fetch the completed copy from a signing platform or an inbox. The Free plan lists up to 50 photos and files, so keep the signed copy and last agreed draft in MemX and the rest of the pile in the history folder.
01How do I find the signed version of a contract?
Search the inbox and signing platform for the completion notice first, since Dropbox DocSend, for one, emails a signed copy and a signature certificate. For paper, ask the other side for their copy. Then read the signature page for parties, signatures and dates, and compare the text with the last agreed draft.
02Which version of a contract is legally binding?
That depends on the facts, the contract and the law where it applies, so it is a question for the parties or a lawyer. Rocket Lawyer's legal-information answer notes the outcome often depends on how the versions differ, what the parties intended and what happened after signing. The signed copy is where the conversation starts.
03Should I put "final" in a file name?
Filestage advises never using the suffix _final and shows how names can pile up, such as Legal_Policy_final_final_maybethistimeitisfinal_v9. Keep one stable base name, add v1, v2, v3 for each round, and label the signed copy once with the word signed and the date of the last signature.
04How can I compare two versions of a document without track changes?
Use the compare tool in your software: Word's Review, Compare option, Google Docs' Tools, Compare documents, or Acrobat's PDF compare (Pro, Premium or Studio). Without one, read both files for the same terms, such as payment, notice and liability, and write the answers side by side.
05Can MemX tell me which version I signed?
No. MemX can answer the same question from each version you upload and show the source, so you can compare the answers. It does not show tracked changes or a line-by-line comparison, does not decide which version is binding, and gives no legal advice. Confirm with the other party.
