The document manager: uses you would not expect

A document manager inside a CMMS is perceived as a place to store manuals, and that is its least interesting use. What actually changes are four things you would not expect when you implement it.

For what to digitize and in what order, see digitizing documentation. This is about what you can do once it is there.

1. Attach the document to almost anything

Not just the asset. In GMAO Cloud a document attaches to the client, the vendor, the address, the machine, the system, the incident, the quote, the work order, the machine model, the family, the vehicle, the technician, the order, the project, the maintenance plan, the tool, and personal protective equipment.

The practical consequence is that the decision that causes nothing to be found later disappears: where do I file this. You file it where it will be looked for.

And there is one case that gets underused: attaching it to the machine model or the family. The manual for a type of equipment gets uploaded once and is available from all forty units of that model, without duplicating it.

2. Decide who sees it, once

Each document carries its own visibility: whether the client sees it, whether the technician sees it, whether the vendor sees it, and whether it requires approval.

That turns a decision that repeats every week — what do I show this person — into a configuration. And it has two effects that are noticeable right away.

Client access works without supervision: the client downloads their reports and certificates when they need them, without anyone having to filter anything.

And when a vendor stops working with you, their access is revoked: the documentation remains yours and they stop seeing it, without moving a single file.

3. Certificates, which are not just a PDF

When the document is proof that something was done in compliance with a regulation, the file alone is not enough.

Certificates carry their number, their scope, their issuer, their holder, and their hash. That lets you search for them by what matters and present them as what they are.

This is what lets the documentation support legal maintenance, which is not a separate module: it runs on the preventive maintenance mechanism, and the proof comes from the history of work orders, completed checklists, and these documents with their dates.

The system logs and proves; the one who complies with the regulation is the company.

4. Letting the document notify you

This is what separates an archive from a system, and the most appreciated use of all.

A document can carry an expiry date, and there is a daily check on what is about to expire that triggers the corresponding notification.

Official inspection certificates, contracts, insurance policies, authorizations, approvals, technical inspections. The same applies to staff personal protective equipment, which also expires and whose renewal gets discovered late with uncomfortable frequency.

The archive waits for you to check it. The system warns you a month ahead.

Where it gets consulted

Wherever it is needed, which is almost never an office.

In the technician app, the operator opens the work order and has the equipment’s history and documentation right in front of them. And those documents are stored on the device itself, so they remain available in a plant room without coverage.

It is worth being precise here, because it is the most common mix-up: that full offline mode belongs to the technician app. Client access installs on the device but does not work offline.

The documents the system generates on its own

A nuance worth understanding: not everything that ends up in the document manager comes in from outside. A good part of it is produced by the operation itself.

The report for each intervention, with its timing, its material, its completed checklist, its photos, and the client’s signature. It is the document most requested and the first one asked for.

Quotes, with their PDF and email templates, which originate from a work order and generate another one once accepted.

And before-and-after photos, which stop being stuck on someone’s phone camera roll.

That self-generated output is what makes the archive grow on its own and, above all, grow organized: every document is created already attached to the asset, the client, and the work order that produced it, without anyone having to decide where to put it.

What does not get lost

Deletion is logical, not physical. A document or folder deleted by mistake can be recovered.

There is a record of creation, modification, and deletion, with which user and when. In a dispute over whether a document was delivered or changed, that separates a fact from an opinion.

The use nobody anticipates: building the documentation that is missing

There is equipment whose documentation does not exist: bought secondhand from a company that closed, installations modified without updating the diagram, machines whose manufacturer is no longer around.

There is no retroactive fix, but there is a practical way out: build it from usage. Every intervention on that piece of equipment, with its photos, its measured values, and what was found, gradually forms its own documentation that, after a couple of years, describes the machine better than the lost manual.

That requires two habits: the technician attaching photos as routine, and checklists recording values. Without that, the history says something was done but not what was there.

The mistake that makes a document manager useless

Using it as just another shared folder: uploading files without attaching them to anything specific, with names only the person who uploaded them understands.

If the document is not linked to an asset, a client, or a work order, the system cannot surface it when needed, and it goes back to being an archive you have to dig through. All the value is in the link, not the storage.

The second way to break it is uploading several versions of the same document without retiring the older ones. On a shared drive that causes confusion; here it causes something worse, because the technician could end up working from the wrong diagram in front of the equipment.

Where to start

With what expires — certificates, contracts, and insurance with their dates — which is the cheapest to load and cuts the most risk. Then, documentation for critical assets. And the rest, as it is needed.

And a configuration tip that saves reviews later: decide the default visibility for each document type before you start uploading, not after. Changing the visibility of an entire type is immediate; reviewing it document by document once there are a thousand inside is not.

If you want to see it with your own documentation, you can request a demo.