Every design team has a folder called final, and right next to it a folder called final-2. Two months later the wrong file goes to print, or a client opens a version a colleague replaced last week. The design is rarely the problem. The problem is that nobody can tell which file is the true one.
Versioning is not software you buy. It is a small set of habits about names, changes, approvals and old files, and it costs a few minutes a week.
Most losses come from three habits: saving over the same file, naming by feeling (new, last, edited), and keeping the working copy on one person's laptop. When that person takes leave, the project stops.
The second cause is silent change. A small request is applied, the file is overwritten, and the version the client liked disappears with no way back.
Pick one pattern and apply it without exception. A date at the front means the folder sorts itself by time, which is exactly what you need when you open it six months later.
For example, q8dm-brochure-approved-2026-10-30-v03.ai states the project, its state, its date and its round in one line. Nobody has to open it to know what it is.
Keep one short text file in the project folder, with a line per change: date, who, what changed, and which file is now current. Four columns, no software required.
The log answers the question that eats meetings: is this the version we agreed on? It also protects the designer, because a request that was never written down is a request that never happened.
Decide in advance who may mark a file as approved. In most small teams it is one person, and everyone else requests changes. The approved file moves into a locked folder, and any later edit becomes a new version instead of an overwrite.
Keep the source file, not only the exported PDF. An export cannot be edited, so a client asking for one line of text a year later otherwise costs you a full rebuild.
Not everyone needs write access. Editors change files, reviewers comment, clients view. Setting that up on a shared drive prevents the most common accident: a well-meaning colleague saving over the approved copy.
At project close, move the whole folder to an archive area, keep it read-only, and write the closing date in the log. Read-only files cost nothing and answer questions years later. At Q8DM we see this clearly when a client returns after two years asking for a print file that was delivered once.
Take one active project, rename the current files to the pattern above, write the first five lines of the log, and move everything older into an archive folder. That is the whole system, and it holds.
If you would rather have it set up properly, with permissions and a storage structure that fits your team, talk to us at https://q8dm.com and we will build it around the way you already work.