Every physical object deserves a permanent Digital Passport.
The object keeps its identity for life. Owners change. History never starts over.
- No account needed to start
- Documents read on your device
- Export everything, always
Apartment · Northgate Building
- Address
- 1420 Oak St, Unit 312
- Last repair
- 4 weeks ago
- Recorded spend
- $18,240
- Warranties
- 2 live
- Water heater replaced12 Mar 2026 · Calloway Plumbing$1,840Participant Confirmed
- HVAC annual service08 Nov 2025 · Meridian Mechanical$320Professional Verified
- Dishwasher repair22 Jun 2025 · Northgate Appliance$215Receipt Supported
34 records · 3 owners · evidence intact across all of them
- Acquired
- Used
- Maintained
- Upgraded
- Sold
- History persists
A building. A medical device. A piece of industrial equipment. The same story applies to anything physical.
- 54
- Asset types
- 30
- Trade taxonomies
- 10
- Work states
- 8
- Verification levels
- 8
- Evidence signals
- 3
- Never metered
A history is built from paperwork, or from work.
Most systems do the first and call the second somebody else's problem. Both doors lead to the same passport.
Documents you already have.
Nine years of invoices in a drawer, a folder, an inbox. Drop them in and the history assembles itself.
- Read on the device — images never upload
- Provider, date, amount and trade recovered per document
- Routed to the right asset, or parked rather than guessed
- Held as a draft until you confirm it
PDFs use their own text layer first, which is the single biggest accuracy win in the product.
Import an archiveWork as it happens.
A specialist finishes a job and records it at the asset. No document exists yet — the invoice is a consequence of this, not its source.
- Every value is first-hand, so nothing is guessed
- Parts and labour total themselves — no reconciling three numbers
- Classified automatically: no dropdowns to pick from
- Confirmed on creation, because testimony arrives already reviewed
Generate the invoice from the record afterwards. The passport fills itself in as a by-product.
Record workHow a verified record appears.
Six steps, five of which already happen without us.
Routing happens before classification, because the object biases the reader — the same words on an apartment invoice lean plumbing, on a truck invoice they lean auto. Extraction then runs twice: once for the universal fields, once for the trade it landed on.
- 01The work happensA repair, a service, an inspection.
- 02The invoice already existsNobody has to create anything new.
- 03Someone uploads itThe owner, or the provider. Either is enough.
- 04It is read on the deviceProvider, date, amount, trade.
- 05A draft record appearsNothing is filed until you confirm it.
- 06Evidence is weighedThe score comes from the document, not a claim.
- Verified TrooLink recordAdded to the passport permanently.
- Provider registration not required
- Mechanic registration not required
- Business registration not required
- Integration work not required
TrooLink works even if the provider has never heard of TrooLink.
- Buy new software
- Train employees
- Migrate data
- Replace the workflow
High adoption cost
- Keep existing software
- Keep existing workflow
- Upload existing documents
- The history builds itself
No operational changes
Ask for the work here, and the record writes itself.
A job is sent, taken on, timed, done and handed in. The passport entry is what falls out of that — not a form somebody remembers to fill in afterwards.
Every state below is somebody’s move, and the product knows whose. That is what makes the two questions a working day actually asks — what am I waiting on, and what is waiting on me — different questions with different answers.
- AssignedSent to a specialist, who has not answered yet.
- AcceptedThey have taken it on. A time may still need agreeing.
- ScheduledA time is agreed by both sides.
- In progressThey are at the asset and have started.
- SubmittedThe specialist has sent their result in.
- Waiting for acceptanceSitting with whoever has to accept it. Nothing is on the passport yet.
- Follow-up requiredNot accepted. More was asked for, and the original task stays linked to it.
- CompletedAccepted, and now part of the asset's permanent history.
- DeclinedThe specialist did not take it on.
- CancelledCalled off by whoever asked for it.
Nothing reaches the passport until you accept it
A specialist submits; the record waits. Accept it and it becomes permanent history with their name on it. Send it back and the original job stays linked to what was asked for.
Every state belongs to somebody
Submitted is the specialist's moment; waiting for acceptance is yours. One status for both would make “how many am I waiting on” and “how many are waiting on me” the same question, and they belong to different people.
Progress is derived, never stored
There is no column saying how far along a job is. A stored step is a claim about progress not backed by evidence, and it is wrong the moment somebody accepts a job on another device.
A refusal is part of the record
Declined and cancelled are states, not deletions. A specialist who was asked and said no, and an owner who called it off, both stay answerable for having done so.
Every figure is a filter.
A dashboard saying nine above a screen showing eight is worse than no dashboard. Each count here is the length of the list behind it, from the same definition — so pressing the number opens exactly what it counted.
Agreed for a time that has passed, and not started.
Somebody is at the asset.
Work handed in. Nothing reaches the passport until you accept it.
Assigned, and nobody has taken it on.
The leading four of 9, in the order a working day reads them: what has slipped, what is under way, and what is waiting on you — before anything that needs nothing.
- Every figure is a filter — click it and you get the very rows it counted, from one definition
- Pick a building and the work booked against its lifts, its units and their equipment counts as the building's
- The calendar takes the same filters, so a date opens what happened and what is still coming
- Contractor and specialist stay separate: a job goes to a firm first, and then to a person inside it
Not one opaque score. A source you can examine.
A single number answers “how much should I trust this?” with a number — the one answer nobody can check. A level answers it with who said so, and on what basis.
Recomputed from the evidence present, never stored and never set. Each rung is something found on the paperwork itself — a record cannot be promoted by asserting anything.
Levels are additive, never a ladder you climb off
A record accumulates claims, each naming its own source. The strongest is a summary of that list — never a substitute for it.
A higher level never erases a conflict
Authority-verified with contradictory evidence is authority-verified and conflicted. Nothing may overwrite a dispute.
Absence is shown as absence, not failure
A repair whose provider has not answered yet is the ordinary case. It must not read as a warning.
A shop that has never heard of us can still confirm the work.
Years later, without anything having been invented in the meantime.
- 01Day one
The work is recorded
The shop is named on the record as an unregistered provider. It holds no account and therefore no rights.
- 02Later
The shop is invited
Sent, opened, claimed, confirmed, declined — every state is nameable, and every exceptional one resolves somewhere.
- 03Years later
They confirm their part
The record gains a participant-confirmed claim, from them, dated then. Nothing is backdated and nothing is invented.
- An unregistered provider is never a user — email control alone proves nothing
- Claiming an identity opens a review queue, not a backdated endorsement
- Who named this business, and on which record, stays answerable
- A declined claim is preserved, because being refused is part of the record
Registration comes after the work, not before it.
A mechanic standing at a customer's car has no reason to create an account with a company they have never heard of — and every reason to record the job they just did.
- 01
Scan the asset
The sticker on the machine opens the passport. No account, no workspace, no search for which unit this is.
- 02
Record what you did
Parts, labour, readings, photos. It totals itself and files itself under the right trade.
- 03
Generate the invoice
Sequential per workspace, derived from what exists rather than a counter. Your paperwork, done here.
- 04
Keep it as your history
Registration is offered after the job, holding a finished record with your name on it — never before.
Claim work you recorded before you had an account
Matched to a verified phone or email, listed one at a time, nothing pre-ticked. Claiming attaches a record — it never confirms one.
The owner still decides
A submission is an assertion until it is accepted. Decline it and the claim is preserved, because a tradesperson who did the work and was refused deserves to have said so.
A plot of land does not have an odometer.
A universal card shows every field any type might have, so most rows read “—”. A dash asserts that something is missing rather than inapplicable, and a page of them teaches a reader that the software doesn't understand what they're looking at.
- 01Make and model
- 02Odometer
- 03Trim
- 04TrooLinked since
- 05Last service
- 06Next service due
- 07Warranties
Work here is called “service”
- 01Address
- 02Floor
- 03TrooLinked since
- 04Last repair
- 05Next repair due
- 06Warranties
- 07Recorded spend
Work here is called “repair”
- 01Manufacturer and model
- 02Location
- 03Serial Number
- 04Run time
- 05TrooLinked since
- 06Last maintenance
- 07Next maintenance due
- 08Warranties
Work here is called “maintenance”
- 01Parcel / cadastral number
- 02Address
- 03Plot size
- 04TrooLinked since
- 05Inside
Work here is called “record”
These are complete lists, not excerpts. A vehicle leads with its odometer because that is how vehicles are judged; land has no odometer, so the row does not exist there — it is not blank, and it is not a dash. Each type declares its own order, and a fact with no value is dropped rather than dashed.
One vehicle, or four hundred units across nine buildings.
The hierarchy is five levels named in real-world words, because nobody should have to learn what a parent passport is in order to file a plumbing invoice.
A fleet or group
A group of sites or assets under one owner — a property company, a fleet, a hospital network.
A building or location
A single building or location. Shared plant lives here — roof, boiler, lifts, grounds.
A unit or space inside one
One tenancy or space within a site — an apartment, a suite, a room.
On its own
Stands on its own, with its own identity and service life — a vehicle, a machine, a device.
A part or system inside something
A serviceable part inside something else — an HVAC unit, a fridge, a transmission.
Print the sheet, walk the floors
Avery 5160, 5163, L7159 and plain paper at real die-cut geometry, minted in bulk. This is the difference between a system somebody finishes and one they abandon on unit 40.
A QR that is a capability, not a name
128-bit tokens, many per passport, scoped and optionally expiring, revocable individually. The object's permanent UUID is never printed, because a UUID on a sticker can never be taken back.
A code a technician can read aloud
TL-7QK2-M4XPZ, Crockford base32 with a check character, for a camera that will not focus on a scratched sticker. Resolved only against labels already on the device, never by a server.
Bulk creation that infers what it is making
A run of air handlers is not named Apt 101. The pattern, the level and the type come from what is already there — a portfolio holding Vehicle 1 and Vehicle 2 proposes Vehicle 3.
Loose paperwork clusters itself
Documents that share an identifier or an address propose the asset they belong to, so an archive with no structure arrives with one.
The reader improves retroactively
Records are re-read against the text already stored — no OCR, no upload, works offline. Owner-entered values are never overwritten, and a disagreement is shown rather than swallowed.
Who owns the history?
Today it's scattered across everyone who ever touched the object — which means nobody has it. A passport puts it where it belongs.
- The repair shop
- The dealer
- The insurer
- The manufacturer
- You
- Every prior record survives, with its evidence and its score intact
- An era is appended rather than a copy made — the object is the same object
- It descends the tree, so a building carries its units and their equipment
- The seam is a record of its own: the history says where one owner ended
Said exactly, because the exact version is the only useful one.
“Nothing leaves your device” would be false, and shipping that sentence would be worse than shipping no sentence.
- Document images and scansNever leave the device. There is no server copy.
- Metadata — provider, date, amount, category, trustSyncs, so a passport survives a lost laptop.
- Recognised text from a documentSyncs only if you turn it on. Off by default.
- OCR runs in WebAssembly on the device, against assets served from our own origin — the library defaults to a CDN, which would leak that a scan is happening even though the content stays local.
- A share link carries its token in the URL fragment, which the browser never sends to a server and which never lands in an access log.
- Local storage is namespaced per account, so two people on one browser cannot see each other's passports.
- Anonymous use is first-class: no account is required to build a passport, and none is required to open one you were sent.
Your records are never the thing we ration.
More history in here makes this product better, so charging somebody to stop adding it would be charging them to make it worse. What can be metered is what genuinely costs something to run, and nothing else.
- Answering work sent to youReceive a task, open the passport, accept or decline, propose a time, scan the QR, start, submit and upload what was asked for.
- Recording historyCreating passports and Verified Records, in any number.
- Accumulating your own recordA specialist's accepted work counting towards their own professional history. §36.
- Reading documentsper use
- Storing document imagesstorage
- Working with colleaguesseats
- Dispatch toolstooling
- Invoice automationtooling
- Advanced reportingtooling
- Exportsper use
- Free participant — Somebody answering work sent to them, and keeping their own record of it. §36: never a paid requirement.
- Professional — One person running their own work.
- Service company — A firm with people, schedules and customers.
- Enterprise — A developer or organisation with large asset trees and many colleagues.
- The split is in the source, not in a policy page: every capability declares whether running it actually costs money, and the test suite refuses a limit on one that does not.
- No prices appear anywhere in this codebase. What a plan includes is data somebody configures, so changing it is a row in a table rather than a release.
- A plan decides what a workspace is offered. It never decides who may touch what — that is membership, checked on the server, and the two are not allowed to be confused.
Almost anything can have a TrooLink.
These are examples. Not a list. Not a limit.
Cars, trucks, boats, aircraft
- Vehicles
- Boats
- Aircraft
- Trucks
- Motorcycles
- Vans
- Buses
- Trailers
- RVs
Homes, apartments, buildings, land
- Houses
- Buildings
- Apartments
- Land
- Commercial Spaces
- Rental Properties
Pools, gyms, playgrounds, courts, parking, cinema
- Pools
- Spas & saunas
- Gyms
- Playgrounds
- Sport courts
- Parking garages
- Home cinemas
- Wine rooms
- Docks
HVAC, fire, electrical, plumbing, lifts, access, solar
- Elevators
- Gates & access control
- Security systems
- Fire systems
- EV chargers
- Solar systems
- Irrigation systems
- Smart home systems
- HVAC systems
- Electrical systems
- Plumbing systems
- Ventilation systems
Machines, HVAC, medical, tools
- Medical Equipment
- Industrial Equipment
- Construction Equipment
- Electronics
- Containers
- Heating & cooling units
- Generators
- Appliances
- Agricultural Equipment
- Office Equipment
Roads, bridges, utilities, networks
- Infrastructure
- Roads
- Bridges
- Utility Systems
- Water Systems
- Electrical Infrastructure
- Public Facilities
Anything with a serial number
- Anything else
If it exists physically, it can have a TrooLink.
Give everything you own a permanent history.
- No account needed to start
- Documents read on your device
- Export everything, always