Maintenance AI

Read the work order notes the way an owner would.

QTR reads the problem text, technician notes and descriptions on every Yardi work order, then groups tickets by what is actually happening in the building. Single-unit appliance and fixture repairs stay out of the review, so what reaches the owner is the condition that needs a decision.

Reads Yardi Voyager Financial · operating · maintenance Works with your AI agent Owner-controlled
Recurring Issues · TTM · AI-tagged
1,247 WOs analyzed
high
Signal House · Call box / intercom failure pattern
access_control · intercom
vs portfolio
9.3×
"call box not working""intercom broken""buzzer dead"
WOs
7
Active
6mo
Spend
$2,340
medium
Everfield Commons · Building-wide kitchen drain cleanings
plumbing · drain
vs portfolio
2.1×
"slow drain""backed up sink""dishwasher backup"
WOs
11
Active
4mo
Spend
$1,890
medium
Marlowe Park · Garbage disposal end-of-life cluster
appliance · disposal
vs portfolio
1.8×
"disposal jammed""won't run""leaking under sink"
WOs
14
Active
9mo
Spend
$980
Grouped by AI from problem text + technician notes, not the dropdown category
Building conditions

Roofs, risers and water, not every slow drain.

The review looks for live building conditions: water intrusion, loss of heat or hot water across units, electrical and structural problems, and the same issue coming back. Routine ticket handling and close-out notes are not findings.

Reads
Every ticket’s text
Description, problem text and technician notes
Daily
Serious items only
Emergency and escalating conditions
Weekly
Short review
Up to 10 conditions per company
Evidence
Every cited ticket
Units, dates, cost and hours
How it works

From ticket text to a decision.

Work orders stay in Yardi. QTR reads them every morning.

01 /
Recurring conditions

Tickets grouped by what is happening in the building.

Grouping uses the words in the ticket and the technician’s notes, not the category someone picked, so five tickets filed five ways still read as one problem.

  • Repeat conditions across units and buildings
  • Reopened work and issues that return after completion
  • Spend and hours compared with the portfolio
  • Evidence phrases shown beside each condition
Recurring conditions · Last 90 days
3 conditions
Building
Condition
Tickets
Units
Since
Signal House B
Water through top-floor ceilings after storms
7
5
Jul 14
Everfield C
Kitchen drains backing up on one stack
11
6
Jun 2
Marlowe Park A
No hot water, same riser
4
4
Sep 9
Grouped from ticket text and technician notesOpen WO Analysis →
02 /
Daily review

Serious items the day they appear.

Each morning QTR reviews new, reopened and changed open tickets. Only emergency and escalating building conditions raise an alert. A leaking faucet in one unit does not.

  • Emergency and emerging levels, each with its evidence
  • Unchanged tickets stay quiet
  • Personal alert switches for each level
  • Opens straight to the work order
Daily work order review · Oct 21
1 emergency
Building
Ticket
Condition
Level
Signal House B
48211
Water coming through ceilings on two floors
Emergency
Marlowe Park A
48230
Third no-hot-water call on the same riser
Emerging
Single-unit repairs stay out of the alertOpen ticket →
03 /
Ask your assistant

Ask what is going on in a building.

Your assistant reads the same work order findings and can summarize a building’s tickets, then file the condition to Action Center when you ask.

  • Searches open and completed tickets
  • Answers with ticket numbers and dates
  • Links to the work order in QTR
  • Files the condition with its tickets attached
ChatGPT · QTR connectorRead
Is the roof at Signal House B getting worse?
QTR toolswork_order_findingswork_order_detail

Yes. Seven water-intrusion tickets since July 14 across five top-floor units, three of them after the Oct 10 storm. Two were reopened after a patch. Ticket 48211 this morning reports water on two floors.

7 tickets citedOpen WO Analysis
Questions

Questions owners ask

How do I identify capex needs from work order data?
Group tickets by the building condition described in the problem text and technician notes. The same condition across units, work reopened after completion and rising cost on one system point to a repair-or-replace decision.
How do I review maintenance across a large portfolio without reading every ticket?
Surface only live building conditions: water intrusion, loss of heat or hot water across units, electrical and structural issues, and repeats. QTR raises serious conditions daily and caps the weekly review at 10 per company.
Why are Yardi work order categories unreliable for analysis?
The category is whatever the person filing picked, so one problem gets filed several ways. The description and technician notes are the reliable record of what is actually happening.
Onboarding Now

Spend your time buying deals. Automate your asset management.

QTR is invite-only and tuned for mid-market multifamily owners working out of legacy PM and accounting systems. Tell us about the portfolio and the reporting cadence. We will follow up with access and onboarding.

Onboarding
One day
First signal scan
Next morning
Sweet spot
750–10,000+ units
Access
Invite-only
Existing user? Sign in
Request Workspace Access
TLS 1.3 Role-based access