Open a customer and see the whole picture: every building, every unit in it, the make, model, serial, install date, warranty status, and every visit that unit has ever had. The technician walking in tomorrow knows the equipment history before opening the door.
A live Taskade Genesis app is embedded on this page. Expand a branch, follow how sites, units, and service history connect, then use it and you own a running copy in about ten seconds. Trying the finished structure beats imagining it from a description.
That app is the Maintenance Tracker Dashboard, a live Taskade Genesis app you can click through and clone in about ten seconds. It is not a site equipment history map out of the box, so treat it as the starting point: clone it, then carry its equipment records across and describe the rest of this build to Taskade Genesis.
The build is a real asset register. A customer holds sites, a site holds units, and a unit holds its service history, its parts, and its documents. Each unit carries make, model, serial number, install date, warranty end date, location within the building, access notes, and the filter or belt sizes a technician always has to look up. Service visits attach to the unit, so failure patterns become visible: the rooftop unit that needs a capacitor every summer is obvious in one glance rather than buried across four years of separate job records.
Read the register in whichever layout answers the question:
- Mind Map view to see the whole customer as a tree of sites and units at a glance
- Table view for the full equipment list with age, warranty status, and last service in columns
- List view to read one unit complete history in order
- Calendar view for what is due on which unit and when
- Plus Board, Gantt, and Org Chart across the 7 project views
Automations keep the register current instead of letting it rot. With Taskade automations, a completed visit writes to the unit history automatically, a photographed data plate creates the unit record on first visit, and a unit crossing its expected life gets flagged for a replacement conversation. Across 100+ bidirectional integrations, forms and phone uploads pull field data in while Slack and email push replacement opportunities to the sales side. See document intake and projects as databases.
The AI agents in the app carry 34 built-in tools including persistent memory, file analysis, web search, custom slash commands, and multi-agent collaboration, on 15+ frontier models from OpenAI, Anthropic, Google, and open-weight providers. The Asset agent reads the history of a unit and tells you plainly when the repair spend has passed the point where replacement is the better recommendation.
Use the app, invite technicians and sales, and the register, the histories, and the documents are yours.
Explore live asset trackers in the Community Gallery, start a build at Taskade Genesis, or learn mind map view. Unit intervals drive preventive maintenance scheduling, and serialized parts on each unit feed warranty claims.
The register builds itself if you capture at the door. Asking a crew to spend a weekend cataloging equipment produces a spreadsheet that is out of date within a quarter, while asking them to photograph a data plate on the first visit to each unit produces a register that is accurate because it is created by the people who are actually standing in front of the equipment. After a full service cycle the coverage is close to complete. The payoff shows up on the day a technician is sent to a site nobody on the current crew has ever visited and they still arrive knowing what is on the roof.
Frequently Asked Questions
How do units get into the register in the first place?
The fastest way is capture on the first visit: the technician photographs the data plate and the app reads the make, model, and serial into fields. Beyond that, you can load an existing equipment spreadsheet with the convert vertical and let the field crew correct it as they go.
What if a customer has forty units at one site?
That is exactly the case the tree structure handles. Sites can hold any number of units, and units can be grouped by building, floor, or system so a technician finds the right one without walking the roof twice.
Can it tell me which units are out of warranty?
Yes. Warranty end dates are fields, so the out-of-warranty list is a saved filter, and units approaching expiry can trigger an outreach task while the coverage still means something.
Does it help sell replacements?
It gives you the evidence. Repair spend per unit against age and expected life is visible per site, so the replacement conversation is grounded in that customer own numbers rather than a generic pitch.
Can customers see their own equipment list?
Yes. Publish a read-only view per customer, which is particularly valuable for multi-site facilities managers. On Business plans and above that portal can sit on your own domain with sign-in, covered in multi-site account portals.
What documents can I attach to a unit?
Manuals, warranty certificates, commissioning reports, photos of the install, and permits. Everything a technician might otherwise search for lives on the unit record, and words inside uploaded documents are readable rather than locked in a file.
Does the history survive a technician leaving?
That is the main point. The knowledge that used to live in one veteran head lives on the unit record, so the person covering that route next week has the same context.
How do we stop it becoming a second system nobody updates?
By making the unit record the place work is done rather than a place work is copied to. Visits attach to units, photos attach to units, and history is written by completing jobs. A register that requires separate maintenance always rots, so it should not require any.
