One queue for every building request

It is the system a facilities team uses to take in requests, schedule preventive work on building systems, and keep the record of what was done to each asset. The part that decides whether it works is intake: most facilities work starts with somebody who is not on the maintenance team noticing a problem, so how easily they can report it determines whether the system reflects the building or a version of it.

Yes, and it costs you nothing to let them. The request form lives on a public link, so a tenant, a cleaner or a security guard can report a fault from a phone with no account and without using up a paid seat. They get a tracking link and can follow the job themselves rather than phoning you for an update.

Yes. Work and assets carry a site and a client, so you can look at one building on its own or the whole portfolio, with the same naming and the same checklists everywhere. Adding the second building reuses what you built for the first.

A CMMS. It maintains the equipment and the building — work orders, preventive schedules, inspections, assets, parts and costs. It does not do lease accounting, space planning or occupancy, so if you run a formal real-estate programme you will keep that system and use QAI where the work happens.

Partly, and it is worth being precise. Contractors are a vendor type in QAI with their own record, purchase orders and spend history. But a job is assigned to a person with a login, not to a contractor company, so a contractor either works under one of your users or you record their work against the asset yourself.

Per user per month, based on the people who create and close work — not on buildings, floor area or the number of assets. People who only report problems cost nothing, which is what makes it practical to open intake to everyone in the building. There is a free plan to start on.

The work continues. Checklists and job details are stored on the device, so a job runs the same in a basement plant room as it does in the office. Answers, photos and signatures queue on the phone and upload themselves when a connection returns, retrying on their own if it drops part way.

Every completed inspection keeps who did it, when it started and finished, how long it took, the GPS coordinates, the photos and the signature at the end. Checklists that need a second pair of eyes can require an approval signature, stored with the approver’s name and the time. Any inspection exports as a PDF.

Not directly. There is no one-click connector to an ERP or a CAFM platform today. What exists is import: meter readings come in from Excel or CSV with matching and an anomaly review before anything is written. If a live integration is a requirement, raise it early rather than late.

Weeks, not quarters, if you start with one building rather than all of them. Import the asset list, put preventive schedules on the systems that cause the most disruption when they fail, and open request intake to the occupants. The second building reuses the same checklists and the same intervals.