Start a recordOpen app

Real-estate maintenance with a trusted history

A maintenance record identifies who reported a fault, who was authorised to act, what work was done, what was measured afterwards and which agreement covered the work. Verifable's aim is to link those details to the asset so later teams can inspect its maintenance history.

The wallet credentials, passport and identity foundations this runs on work today — issue and present a credential in the sandbox. The combined maintenance record and authority decision are not yet a guided public workflow.

Illustrative workflow: from fault to recognised work

  1. Fault reported. A fault against a tagged asset is reported, with whatever evidence is on hand at the time.
  2. Responsible organisation identified. The asset's responsible organisation is looked up from its logbook record.
  3. Technician's credential checked. Before work starts, check the technician's relevant qualification and their current permission to carry out this job. A qualification alone is not a mandate.
  4. Work done and logged. The work performed is logged against the asset, with the technician's identity attached.
  5. Measurement recorded. A post-work measurement is taken and logged, evidencing the state the work left the asset in.
  6. Both logbooks updated. The event is carried into both the building's logbook and the equipment's own product logbook — one event, two places it belongs.
  7. Agreement recognises it. The agreement that governs the maintenance relationship recognises the completed work against its terms.

Tagged assets and maintenance routes

Maintenance starts from the same tagged assets the building logbook already tracks. A maintenance route is the recurring path a technician follows through a set of assets — an inspection round, a seasonal service schedule — and each stop on that route reads and writes against the asset's own record rather than a separate maintenance-only database.

The products used to maintain a product matter too

A cleaner, coating, sealant or replacement part is not absorbed into the asset it helps maintain. Its own model or batch record stays distinct and is linked as an input to the work event. That lets someone later ask what was used, by whom and with what result without pretending every input is a construction product or governed by the same instrument.

Regulation (EU) 2026/405 introduces model-level passports for detergents and end-user surfactants from 23 September 2029. Other cleaners, coatings and sealants require their own classification. See the one-wet-day reference and product-group boundaries.

Responsibilities and delegated authority

The target is to make who may act on an asset a Wallet-verifiable fact rather than a paper assumption. A responsible organisation will be able to delegate authority to a named technician or contracted firm, scoped to a mandate checked before work starts. Portable mandates and this maintenance-policy check are still in development. See wallets for how these credentials and mandates are held and presented.

Inspection and fault evidence

Inspections and faults both produce evidence — photographs, measurements, technician notes — that is kept attached to the event it belongs to rather than summarised away. Later questions about an asset's history are answered from that evidence directly.

Connection to agreements

Maintenance does not happen outside a relationship — it happens under a service agreement, a lease obligation, or a warranty term. See agreements and receivables for how the agreement side of that relationship is represented alongside the work it governs.

What you can use today

  • Wallet credentials
  • Digital product passports

See Facts for the available record and identity foundations.

Related: the building logbook this work writes into, and Veritas for how the underlying evidence is kept.