Company Documents: Avoiding Wrong Versions and Scattered Attachments

The cost of disorganized documents isn't the disorder itself: it's the quote sent with last year's price list, the procedure carried out in a version that had already been replaced, the attachment searched for across four mailboxes while the customer waits on the phone. An archive exists to make these things hard to do, not to create order for its own sake. This guide will help you decide who is responsible for each document, which version is valid, and where to find it.

Not All Documents Have the Same Problem

Putting everything in a shared folder and calling it an archive doesn't solve anything, because documents have different uses and therefore different failure points.

• Documents that describe how work is done: procedures, instructions, forms. The problem is the version.
• Documents tied to a job: quote, order confirmation, delivery note, report, photos from a job. The problem is the link: they need to stay attached to the job order, not to the folder of whoever created them.
• Documents that come from outside: data sheets, certificates, manuals, vendor price lists. The problem is knowing whether they're still current.
• Documents that expire: policies, permits, contracts. The problem is noticing in time, not after the fact.

Four different problems call for four different rules. Applying just one rule to everything means, in the end, applying none.

The Current Version Is the One Someone Has Approved

"The latest" and "the right one" aren't the same thing. The most recently edited file might be someone's draft. Until there's an approval step, whoever is looking has to guess, and sometimes guesses wrong.

• One single place for the current version, separate from where drafts are kept.
• A role that approves, defined by role rather than by person, with a named backup.
• Superseded versions aren't deleted: they're moved and marked as superseded, with the date and a note of which document replaces them.
• Every document carries its own version number, even when printed or sent by email.

A Procedure Sheet, in Full

The example below is illustrative and shows which fields make a document manageable.

Finding It: Depends on How the Document Is Linked

Searching by file name works as long as one person alone chooses the names. With more people, something else is needed.

• Every document tied to a job should be linked to the job order, the customer, or the visit: that way you search starting from the job, which is how the question actually arises.
• A few labels agreed on in advance — document type, year, customer — are worth more than a deep folder structure that everyone interprets their own way.
• The file name states type, reference, and date, always in the same order.
• Full-text search only helps if the documents are actually text: a PDF that's a photo of a page contains no searchable words.

Who Can View and Who Can Change

The most useful permission isn't the one that hides things: it's the one that prevents changes. Most damage doesn't come from someone reading a document that isn't theirs to read, but from someone changing one that affects everyone.

• Four distinct roles: who reads, who uploads, who approves, who can delete.
• Documents containing personal data — employment contracts, certificates, evaluations — are accessible only to those who need them to do their job.
• Access for someone leaving the company is removed the same day, and along with it, any documents that existed only on their device need to be recovered.
• When a document needs to go out, a link with an expiration date is preferable to an attachment that will sit forever in someone else's inbox.

Retention and Deletion

Some documents must be kept by obligation, others should be deleted once the reason for keeping them has ended. Both are decided together, type by type, and written down alongside the definition of that type: how long it's kept, where the unmodifiable copy lives, who carries out the deletion, and when.

When Much Less Than a System Is Enough

If the documents that matter are few and only two or three people touch them, a dedicated system is a burden: a folder for the current version, one for history, a file-naming approach agreed on together, and one person who approves are enough. You can recognize the moment something more is needed by three signs: documents need to be linked to jobs, permissions need to differ by role, or you need to be able to say who has seen and changed what.

What This Guide Doesn't Cover

This guide covers document organization: ownership, versions, access, findability. What needs to be fixed in the documents before feeding them to an assistant that answers people's questions — formats, readable text, withdrawal of superseded documents — is a later step, with its own dedicated guide.