VerifableStart a recordOpen app
Lifecycle

What the record is worth after the factory gate

A passport states what was made. Its value continues through the years afterwards: helping a technician prepare for a visit, supporting a warranty claim, giving a financier condition evidence to assess, or helping another project consider a reclaimed beam. Over those years, owners, service contractors, technicians and receiving projects each need part of that history. A continuing record helps them work from the same evidence.

The record these four jobs run on works today: issue a passport against its product group's shape at Create a product passport, resolve the identity it gets through the resolver, and issue or present its credentials in the sandbox. The four guided lifecycle workflows are not yet available as one public event log.

Why keep the record

Two reasons exist to keep a product record, and they attract different buyers. One is the obligation: Regulation (EU) 2024/1781 (Ecodesign for Sustainable Products, ESPR) and Regulation (EU) 2024/3110 (Construction Products) put a passport in front of one product group after another as their delegated acts and harmonised specifications arrive. Preparing the required evidence takes time; applicability and dates must be checked for the particular product.

The other reason is the work that the same record can support. A property owner wants the fault diagnosed before the van is dispatched. A manufacturer that retains title under a lease wants to know where its units are and what condition they are in. A deconstruction contractor wants to sell a component rather than pay to landfill it. None of those depend on a regulation, and all of them want exactly the payload a passport plus a logbook holds.

The four jobs after the gate

Each of these has its own page, with its own worked example.

Leasing and product-as-a-service

For a manufacturer offering a lease or service contract, location, condition and maintenance history help assess service needs and residual value. A passport and logbook can supply part of that evidence. Financing and insurance still depend on the counterparty's assessment, contract and wider risks.

Retaining ownership can give a manufacturer a stronger reason to maintain a product and recover it for another use. The record can support that business model; it does not establish durability, financial viability or regulatory compliance by itself.

The resolvable product identity a leased unit is tracked by runs today. Per-use billing against verified events, and the condition evidence a financier or an insurer underwrites, are later applications of that continuing record.

Who uses the record, and why

For whom
Anyone who owns the consequences of a product after the sale: property owners and facility managers, maintenance contractors and the technicians they send, manufacturers that retain title under a lease or a service contract, deconstruction contractors, and the projects that receive what those contractors remove.
Why
Maintenance and reuse decisions need specific answers: which unit is this, who last serviced it, is its warranty still valid, and who was authorised to work on it? Recording that information when the work happens gives later teams evidence to consult when assessing condition, responsibility and possible reuse.
What it costs
Nothing today. Passport issuance, the resolver, the sandbox and the wallet are published at no cost, with no card and no sales call; what is being prepared is stated on pricing.
What you gain
Resolvable asset identifiers, a linked product history and condition evidence that remains available through changes of custody. Together, these can support discussions about leasing, take-back and resale.

What you can use today

  • A passport issued against its product group's shape The battery group has a wired shape, and issuance is gated on it. Issue one.
  • A product identity third parties can resolve An issued product gets its own DID and a typed link-set of its credentials, reachable server-side through the resolver.
  • Credentials issued to and presented from a wallet Issuance and presentation run against the pre-seeded test tenant, whose keys reset on every restart, so credentials from it suit integration work. Run a round trip.

Each of these is on Facts with the URL or file that settles it. The event log, delegated mandates, reuse matching and per-use billing are not presented as public capabilities. The identity layer underneath all of it is described on digital product passports.