How do QR maintenance requests work?

Each unit gets a permanent QR code. Scanning it opens a web page tied to that exact unit, where the person picks a request type and describes the problem. The request arrives already located and timestamped, so nobody has to ask "which shop is this?"

Do tenants need an app to report a problem?

No. The code opens a web page in the phone’s browser. Guests need no login at all; tenants use a PIN for their own unit; staff use personal codes that a manager can revoke.

What happens if a QR sticker is damaged or the unit changes hands?

Print a replacement from the dashboard and scan it in place — the code is bound to the unit, not to the tenant, so a new tenant inherits the same code and the unit keeps its history.

How many codes does a property need?

One per unit you want reports about — shops, suites, rooms — plus the shared places people complain about: restrooms, lifts, corridors, car park levels and the food court.

Maawa FM › Guides › QR maintenance requests: how a code on every door replaces the phone calls

// Guide · requests

QR maintenance requests: how a code on every door replaces the phone calls

A phone call tells you something is broken. A scan tells you what is broken, exactly where, at what time, and who reported it — without anyone installing anything.

Most properties collect maintenance requests the same way: a phone call to a manager, or a photo in a WhatsApp group. It works until it does not. Nothing is written down in a form anyone can search, the location is described rather than known, and by the end of the month there is no honest answer to "how long do we take to fix things?"

What a QR workflow actually is

Give every unit a permanent code and print it on a sticker or plate. When someone scans it, the page that opens already knows the building, the floor and the unit. They pick a request type — AC, plumbing, electrical, cleaning, lift, parking, access — write a line, and send it. The ticket lands on your board located and timestamped.

Print a code for every unit, straight from the dashboard, in a batch.
Stick and scan. The first scan in the field pins that code to that unit, so the map matches reality rather than a spreadsheet.
People report. Tenants, visitors and your own staff all scan the same sticker and get a different door.
Your team resolves. The ticket moves from new, to acknowledged, to in progress, to resolved — each step timestamped.

One sticker, three doors

Who scans	What they get	How they are identified
Tenant	Report an issue, see their own rent, charges and contract, update contact details	PIN for their unit
Visitor	Report a problem at the spot where they are standing, in Arabic or English	Nothing — no login, no account
Staff	Log and resolve operational work, with photos and notes	Personal code, revocable

Where to put the codes

Every lettable unit — inside, near the door, at eye level. Outside-facing stickers get peeled.
The places people complain about — restrooms, lifts, stairwells, corridors, car park levels, the food court. These generate more reports than the shops do.
Plant and back-of-house — chillers, pumps, generators, roof access. Staff report far more when the code is on the equipment.
Print on durable vinyl or an acrylic plate for wet and outdoor areas. Paper survives an office, not a car park.

The questions everyone asks

What if someone abuses an anonymous code?

Guest reporting is deliberately frictionless, so keep the guest door to reporting only — anything that touches money or contracts sits behind the tenant PIN. In practice the volume problem is the opposite one: getting people to report at all.

What about people who do not use smartphones?

They still call. The difference is that your team logs the call in the same place from the staff portal, so the record and the response time exist either way.

Does it need Wi-Fi or an app store?

Neither. A scan opens a normal web page on mobile data. Admins who want an app-like experience can install the dashboard to their home screen.

What happens when a unit changes tenant?

Nothing to reprint. The code belongs to the unit; the tenancy changes underneath it and the unit keeps its history of scans, requests and payments.

What to measure once it is running

Requests per unit per month — which shops and which shared areas actually consume your team
Time to acknowledge and time to resolve, by category
Repeat reports on the same unit — the sign of a fix that did not hold
Where reports come from: tenants, visitors or staff

None of this needs a data project. It falls out of the tickets, provided every ticket knows its unit — which is the entire point of putting a code on the door.

In Maawa FM the codes, the portals, the map and the ticket board are one system: print the batch, stick them up, and every scan lands on the floor plan you already uploaded. Request types come from a template — commercial, residential or hospitality — and you can edit the list to match what your building actually has.

See it on your own property

Maawa FM is live software, not a mock-up. Open the sandbox and click through a demo property, or send us your buildings and we will set one up.

Book a demo Try the sandbox

Written by the Maawa team · Last updated 2026-09-12 · Questions: [email protected]