Document Version Control Without Any Special Software

Every version control disaster starts the same way: someone saves proposal_final.pdf, then proposal_final_v2.pdf, then proposal_final_REAL.pdf, and two weeks later nobody can tell which one the client actually signed. The fix is not software. It is a two-digit counter. Name versions v01, v02, v03, padded so they sort correctly past version nine, and append them at the end of the filename: 2026-08-10_Contract_Acme-Supply_v03.pdf. The counter only ever goes up. It never resets, and no word ever replaces it.

The word final should appear exactly once in your entire system, and not as a version number. When a document is genuinely settled, rename that one file to end in _FINAL and, more importantly, move it out of the working folder into wherever finished documents live. Physical separation does what naming alone cannot: it removes the wrong file from the place you look. If a later change is unavoidable, do not edit the FINAL file. Start v04 back in the working folder and repeat the ritual, so there is always exactly one FINAL and it is always the newest one.

Drafts leak. Somebody attaches the wrong file to an email, or prints a working copy and it ends up in a client meeting. The cheap insurance is a visual marker that survives printing, forwarding, and screenshots. Put a DRAFT watermark across every version that is not final, using PdfWill watermark, and remove it only when you produce the FINAL. A reviewer who sees the diagonal grey word across the page cannot mistake it for the signed agreement, no matter how confusing the filename got in transit. Page numbers help too, since a mixed-up printed stack reassembles instantly when the pages are numbered.

Keep exactly one current copy per document, in one place. The most common cause of lost work is not a deleted file but a good edit made to a copy that later got overwritten by an older one from another folder. If you must have the file in two places, make one of them clearly an archive: a folder named _archive inside the project folder, holding old versions, that you never open to edit. Anything outside _archive is live. That single boundary removes most of the ambiguity without any tooling at all.

This habit does slip, so define the minimum viable version of it: increment the number and keep only the newest file in the working folder. Even if you skip watermarks and archives entirely, that alone prevents the final_final spiral. When you need to send a version out, PdfWill runs entirely in your browser with nothing uploaded, so you can compress the file to a mailable size, add a watermark or page numbers, and use protect with AES encryption before it leaves your machine. There is no cloud sync and no batch mode, so handle documents one at a time, in a single focused sitting.