6 min read · 2026-11-11
Choosing maintenance software for a building: 12 questions to ask
Twelve questions to ask before you choose maintenance software for a tower, compound or small hotel, and how to test the answers in a two-week trial.
Choose maintenance software by testing it on your own building's worst week, not by reading feature lists: a resident reporting a leak at night, a technician on a phone in Arabic or Urdu, an owner abroad approving a quote, and a month-end report. The twelve questions below turn that into a checklist, and each one can be tested in a trial before you pay.
First, the four approaches
| Approach | Works well when | Stops working when |
|---|---|---|
| Group chat | A few units, one technician, residents who know each other | Requests sink, nobody owns them, proof leaves with the phone |
| Spreadsheet | One person logs everything and the team is small | Jobs need an owner, a deadline, photos and the resident's confirmation |
| General help desk tool | You already run one for other work | It knows tickets, not units, shifts, rounds or owners |
| Property maintenance tool | Requests, technicians, owners and residents all need to meet | You need deep accounting or leasing in the same place |
If you are deciding between the first two and a tool, UnitVO vs a building WhatsApp group and UnitVO vs spreadsheets go through it step by step.
The 12 questions
For residents
- Can a resident report without installing anything or creating an account? Every extra step loses reports.
- Does the resident get a way to follow the request, and confirm or reopen it when it is "done"?
- What happens with a dangerous report at night? Is it recognised without waiting for a person or an AI, and who is alerted? (Our triage table shows what should count as urgent.)
For the team
- Does every job get exactly one owner, and what happens if nobody takes it?
- Does it respect shifts, skills and certificates, or does it ping everyone?
- Can technicians work from their own phones, in the language they read most easily?
- Can rounds and checklists require a photo, and turn a failed check into a job?
For owners and money
- Can contractors send quotes without an account, and can owners approve above a limit?
- What does the owner receive each month, and in which language?
For you
- How is it priced: per staff seat, per unit, or per feature tier? What happens as you grow?
- Can you import your current sheet and export everything, any time, without asking?
- Where is the data hosted, who on your team sees what, and how is setup done?
Test it in two weeks
A feature list cannot answer the questions above; a short, realistic test can.
- Day 1-2: set up one building or a few units, import your units, add two technicians.
- Day 3: print QR stickers for five units and one common area; ask real residents to try them.
- Day 4-10: run real jobs through it, including one at night and one with a contractor quote.
- Day 11: walk a round with a required photo.
- Day 14: ask the team and two residents what was easier and what was harder than before.
How UnitVO answers them
UnitVO is built around these questions, so here are its answers, with the pages that show them.
- Residents scan a QR code with no app and no password, get a tracking link, and confirm or reopen the fix (QR codes).
- Danger words are matched by fixed rules before any AI, the local emergency numbers are shown, and the duty manager is alerted.
- Each job is offered to one qualified person on shift at a time, for two minutes, and escalates if nobody accepts.
- Technicians use the phone's browser in English, Arabic or Urdu.
- Rounds can require photos; Not OK becomes a job. Contractors quote by link; owners approve above a limit, and the manager sends them a monthly PDF summary.
- Plans are priced by units, every plan has every feature, and residents, guests, owners and contractor links are free.
- CSV import with a row-by-row preview, and a full export as CSV files in one ZIP (import and export).
- Data is hosted on Amazon Web Services in the European Union, in Milan; setup is online, by calls and online demos (security).
The fairest test is your own building: the 30-day trial has Team features for up to 50 units, which is enough for the two-week plan above. To see what good numbers look like at the end of it, read six building maintenance KPIs.
When this is not for you
Be clear about what you need on day one. WhatsApp on your own number is being connected in UnitVO; the QR page and web chat work today. The listed plans go up to 300 units. Setup is online only, with no visits. And UnitVO does not pay contractors or keep your books. If any of those decides it for you, read who UnitVO is not for first.
What it costs
In the International region: Free (5 units and 2 staff, USD 0), Pro USD 49, Team USD 75 and Portfolio USD 199 a month, billed yearly. Each region has its own price list in its own currency; prices are before tax, and UAE customers pay 5 % VAT at checkout. The 30-day trial has Team features for up to 50 units and needs no card. See pricing.
Questions and answers
What matters most when choosing maintenance software for a building?
Whether residents can report without an app, whether every job gets one owner, and whether technicians can work from their own phones in their language.
Should software be priced per user or per unit?
Per unit keeps costs predictable when you add technicians, cleaners or contractors; per user can grow quickly with a field team. Compare both on your own numbers.
How long should a trial be?
Long enough to run real jobs, including a night request and a contractor quote. Two weeks of real use tells you more than any demo.
Can I leave later with my data?
Ask before you start. In UnitVO the whole organisation can be exported as CSV files in one ZIP at any time.