Proof attached to the thing it proves, not merely filed somewhere near it.
Photos attach at the exact place they belong: the finding, the job, the asset. They are captioned, tagged, and stripped of EXIF metadata on upload. Documents are typed and anchored to whatever they are about. Beyond that sits a general file library with an organisation-wide store, per-building libraries and folders up to five levels deep, with certificate PDFs pinned directly to their compliance cells.
Evidence is only useful if it can be found from the thing it proves. A photo in a shared drive folder called “site visits March” proves nothing in an audit. A photo attached to the finding, which is attached to the work order, which is attached to the certificate, is a chain somebody else can follow without your help. Scrubbing EXIF also removes location and device metadata you never intended to hand over.
How it works
Photos
EXIF-scrubbed, captioned, tagged, attached at the finding, the job or the asset.
Documents
Typed, with lifecycles and signatures, anchored to what they concern.
Signatures
Who must sign and who has, each with its eIDAS tier. A required signature is the gate between issued and executed.
File library
Org-wide and per-building libraries, folders five levels deep, evidence pinned to spend.
Comments
Threaded discussion with mentions, on the record rather than in an inbox.
In practice
An auditor asks to see proof that the Lyon Sud emergency lighting test was actually carried out last October.
Open the compliance cell for Lyon Sud, emergency lighting. The certificate PDF is pinned to it.
From the certificate, open the work order that produced it.
From the work order, the technician’s photographs: captioned, tagged, and stripped of EXIF metadata when they were uploaded.
From the same job, the comment thread where the site manager queried one fitting and the technician answered, on the record rather than in an inbox.
The whole chain is dated, and every step of it was created as a by-product of doing the work.
Four clicks, no email search, and nobody has to telephone a contractor who may no longer hold the file. Stripping the metadata matters too: a site photograph carries GPS coordinates and device details by default, and handing those to a third party is rarely what anyone intended.
Illustrative walkthrough. Not a customer record.
What we will show you in a demo
The chain from certificate to work order to finding to photo, followed without asking anyone for help.
EXIF stripped on upload, so location and device metadata do not travel with the image.
A document that cannot move from issued to executed without its required signature.
Each signature carries its eIDAS tier, and the tier required on a document type is yours to set.
Why does stripping EXIF matter?
A site photo carries GPS coordinates and device details by default. Scrubbing them removes metadata you never intended to hand to a third party.
Can we keep using our existing document store?
The library covers org-wide and per-building files, but the point is the pinning: evidence attached to the record it proves is what an auditor can follow.
Insurance, contracts and spending limits as live records with dates on them, not folders somebody forgot to open. Contractors and suppliers sit in one central register with their service agreements,…
Every euro attributed, and a changed number that leaves a trace. Costs attach to the work order as lines: invoices, labour and materials, approved, posted, and rolled up by building…
What you may do, and where you may do it. Roles grant permissions resource by resource and action by action, denied by default, with six starter roles for facility management…
To provide the best experiences, we use technologies like cookies to store and/or access device information. Consenting to these technologies will allow us to process data such as browsing behaviour or unique IDs on this site. Not consenting or withdrawing consent, may adversely affect certain features and functions.
Functional
Always active
The technical storage or access is strictly necessary for the legitimate purpose of enabling the use of a specific service explicitly requested by the subscriber or user, or for the sole purpose of carrying out the transmission of a communication over an electronic communications network.
Preferences
The technical storage or access is necessary for the legitimate purpose of storing preferences that are not requested by the subscriber or user.
Statistics
The technical storage or access that is used exclusively for statistical purposes.The technical storage or access that is used exclusively for anonymous statistical purposes. Without a subpoena, voluntary compliance on the part of your Internet Service Provider, or additional records from a third party, information stored or retrieved for this purpose alone cannot usually be used to identify you.
Marketing
The technical storage or access is required to create user profiles to send advertising, or to track the user on a website or across several websites for similar marketing purposes.
English (UK)
