The asset
The machine’s manual, diagram, spec sheet and certificates. What the technician has in front of them when they open its record or scan its QR code.
Feature
A document is only useful if it shows up when it’s needed
A manual in a shared folder is a manual nobody looks at. Attached to the equipment it belongs to, it’s right there for the technician standing in front of that machine at six in the morning.
What is a maintenance document manager?
It’s the system that stores the technical and administrative documentation tied to maintenance — manuals, diagrams, inspection certificates, inspection reports, safety data sheets, contracts — attached to the element it belongs to instead of sitting in a separate folder structure. The difference from a shared drive isn’t storage capacity, it’s the link: a document attached to a machine shows up automatically when someone opens that machine’s record, and a certificate with an expiry date gives you a warning before it lapses instead of you finding out it already has.
Where documentation ends up
Everywhere except where it’s needed.
- The equipment manual is in a filing cabinet at the office, forty kilometers away.
- The latest inspection certificate is sitting in someone’s inbox.
- Nobody knows whether that site’s inspection report is still valid.
- The shared folder has three versions of the same diagram, none of them dated.
- When an audit comes around, two people spend a week rounding up paperwork.
What a document can be attached to
Practically anything — and that’s the whole point.
The site or facility
Inspection reports, floor plans and contracts that apply to an entire site rather than to one specific piece of equipment.
The work order
The vendor’s delivery note, a photo of the replaced part, or the report handed to the customer — tied to that specific visit.
The model or the family
The manufacturer’s manual gets attached once to the model and every matching machine inherits it. A hundred units, one document.
The person
Technician certifications and credentials, with their scope and issuer. Lets you check who was qualified on the date of a given visit.
The vendor or the customer
Contracts, insurance and activity-coordination paperwork, where it belongs — not in an inbox.
Whatever expires, gives a warning
In maintenance, documentation has a shelf life: an inspection certificate is valid for a year, insurance lapses, a calibration expires, personal protective equipment has a service life. Every document can carry its own expiry date, and the system periodically checks what’s about to lapse so it can warn you beforehand, not after the fact. It’s an unglamorous feature that solves an expensive problem: most documentation non-compliance isn’t about negligence, it’s about nobody keeping the expiry calendar in their head.
Shall we look at it with your way of working?
Leave your details and we will get in touch to see whether we fit. No commitment, no lock-in period.
Who sees what
One shared repository doesn’t mean everyone sees the same thing.
Visible to the customer
The certificate you want them to be able to download themselves, instead of emailing you for it every time.
Visible to the technician
What they need in the field, available in the app. Everything else doesn’t clutter their screen.
Visible to the vendor
The subcontractor accesses what they need for their job, and nothing more.
Certificates with their own data
Number, scope, issuer and holder as proper fields, not a loose PDF you just have to trust.
Audit day
The real test of whether a document manager works is simple: how long it takes to answer "show me the documentation for this site." If the answer is "give me a couple of days," the system isn’t doing its job no matter how many files are stored somewhere. With documentation attached to each element, that answer comes instantly and without reconstructing anything: the site’s certificates, its equipment manuals, its inspection reports and its service reports are exactly where they should be, because they were never anywhere else.
Frequently asked questions
Can I stop a work order from closing without its document?
That’s a configuration choice, and it’s worth using carefully. On jobs where the deliverable is precisely the document — a report, a certificate, a photo of the final state — requiring it avoids having to chase it later, once nobody remembers the details. Applying it to everything, though, ends up generating filler documents uploaded just to close things out, which is worse than having none at all.
What happens to the documentation when a piece of equipment is replaced?
It stays with the equipment that’s decommissioned, and that’s how it should be. The temptation is to clean up the history when retiring a machine, and that’s exactly the wrong move: the documentation and service history of a retired unit is what lets you judge whether its replacement was a good choice, or justify to anyone who asks what was done during the years it was in service.
Which documents are worth uploading and which aren’t?
The ones someone will need at some specific moment: equipment manuals and diagrams, certificates and reports with their expiry dates, safety data sheets, and whatever documentation a customer or inspector might request. Dumping your entire hard drive has the opposite effect, because it turns the search into the exact problem you were trying to solve.
Where are the documents stored?
In object storage within the European Union, with replication, always linked to the element they belong to inside your installation. Files are stored under a generated name that prevents access by guessing URLs.
Can I control which documents my customer sees?
Yes, document by document. Visibility is set separately for the customer, the technician and the vendor, so one shared repository serves everyone without showing too much.
Does it warn me when a certificate is about to expire?
Yes. Every document can carry an expiry date and the system periodically checks the ones approaching that date. The same applies to personal protective equipment and tool inspections.
Do I have to upload the manual to every machine individually?
No. The document is attached to the model or the family and every unit of that type inherits it. You only upload to a specific machine whatever is particular to it.
Does it work for my technicians’ documentation?
Yes. Certifications and credentials are managed as technician documents, with number, scope, issuer and expiry, so you can check who was certified on the date of any given visit.
Try it with one of your sites
Bring the documentation for one location and we’ll show you how it would be organized, and what would warn you before expiring.