Which version is final: keeping one master of a shared document, version names and the step when it is sent

On Tuesday a proposal goes to the customer. On Thursday the customer asks about a figure on page three. One colleague opens "proposal_final.docx" from an email, another opens "proposal_final2.docx" from the shared folder, and the third remembers changing that figure last week. Nobody is sure which file the customer holds, and the first ten minutes of the call go to finding out.

This happens in every small company that works with documents: quotes, contracts, offers, reports, handbooks. The cause is rarely carelessness. It is the lack of one agreed place and one agreed rule. This article describes a light routine for a team of two to twenty people.

One master in one place

Every document has exactly one master. It lives in a shared folder that the whole team can reach, for example the customer's folder in your shared drive. An email attachment is a copy, never the master.

When a colleague needs the document, send a link, not a file. The link always leads to the current master, and nobody has to ask "is this the latest?" If an external person needs an editable file, send it once, say plainly that it is a copy, and name the date when their changes will be merged back.

Version names that tell the truth

The word "final" is a promise that is broken the next day. Use a name that carries a date and a status instead:

• 2026-10-24 proposal Novak draft
• 2026-10-26 proposal Novak sent
• 2026-11-02 proposal Novak signed

The date sorts the files in the right order. The status tells the reader what the file is. Keep the customer or topic in the same position every time so the list stays readable. If your tool keeps a version history, use it for small edits, and create a new named file only when the document changes its status.

One pen at a time

Two people editing the same paragraph produce a conflict, and a conflict produces a copy. Agree a simple rule:

1. One person is the author and holds the pen. The name is written at the top of the document or in the folder.
2. Others comment, suggest changes or write their remarks in a short list. They do not edit the text itself.
3. When the author has taken in the remarks, the author says so in one line: "Version of 26 October is ready for a last look."

For a quick change of a typo, anyone may edit. For a figure, a date, a price or a clause, only the author edits, because these are the places where a silent change costs money.

The step when it goes out

The moment a document leaves the company is the moment the versions must stop. Before sending, do three things:

1. Do a final read-through by a second person.
2. Save the exact file you send, as a PDF where the customer does not need to edit, with the status "sent" in the name.
3. Write the date and the recipient in the customer's record or in a short recap.

From then on, if the customer asks about page three, the answer comes from the sent file, not from the working draft. If you need to change something after sending, create a new version with a new date and tell the customer which one replaces the old one.

Cleaning up

Drafts pile up quickly. Once a quarter, the owner of the folder spends fifteen minutes on this: keep the sent and signed versions, delete or move the drafts that no longer matter, and check that nothing important lives only on one laptop. When a job is finished, move the folder as described in archiving a finished project.

What to avoid

• Final, final2, final-really. The name should say the status and the date, not the hope.
• Sending attachments inside the team. A link is shorter and cannot go out of date.
• Everyone editing everything. It feels fast and creates the copies you wanted to avoid.
• Overwriting the sent version. Once a document went out, it is a record. Changes go into a new version.
• A rule only in someone's head. Write the three rules on one page and put it at the top of the shared folder.

A simple start

1. Choose the shared place for the masters and tell the team that attachments are copies.
2. Agree the name pattern: date, customer or topic, document, status.
3. For each important document, write the name of the author at the top.
4. Add the "save the sent file" step to your checklist for sending quotes and contracts.
5. After a month, ask the team one question: "How many times did we not know which file was the right one?" and adjust.

Sources

• This article describes a working routine and makes no statistical claims. The related WVI articles linked above cover shared folders, final checks of customer documents and archiving.