Use Cases

QR Codes for Property Management

Selling a property and running one are different jobs. Once someone lives or works in a building, the useful codes stop being marketing and start being infrastructure — the fastest route from "something is wrong here" to a ticket with the right unit number already on it.

The short version

The best use is maintenance reporting: a code on the asset carries the asset's identity, so the ticket arrives already knowing what and where.
Make them dynamic. These codes outlive the systems behind them — portals get replaced, contractors change.
Most of these live in corridors, plant rooms and car parks, so durability and low light matter more than density.
Print the fallback next to every code. A resident with a dead phone battery still needs the number.
A code in a shared building is publicly scannable. Never put one in front of something that assumes only residents can reach it.

Maintenance and work orders

This is the case that justifies the whole exercise. The expensive part of a maintenance request is rarely the fix — it is the round trip establishing what is broken and where. "The heating's not working" turns into two phone calls and a visit before anyone knows which unit, which system, which floor.

A code fixed to the asset removes that entirely, because the code is the identifier. Scanning the one on a specific boiler, lift, laundry machine or corridor light opens a report form that already knows which one it is. The resident describes the symptom; everything else is already filled in.

What that changes in practice:

Tickets arrive unambiguous. No unit-number typos, no "the one by the stairs".
Duplicate reports collapse. Five people reporting the same lift produce five tickets against the same asset ID rather than five descriptions that have to be matched by hand.
History accumulates per asset. Over a year you can see which machine keeps failing, which is an argument for replacement that nobody has to assemble from memory.

Contractors benefit from the same code from the other side — scanning on arrival to reach the manual, the service record, or the isolation procedure for that specific unit.

Directories, wayfinding and access

Large or multi-tenant buildings have a permanent orientation problem, and printed directory boards are wrong within weeks of being made. A code at the entrance pointing at a maintained directory page stays current at no printing cost, which is the entire argument for dynamic codes stated in physical form.

It works for deliveries and contractors too: a code at a service entrance can carry loading-bay hours, which lift takes pallets, and who to call — the information that otherwise arrives as a phone call to whoever is nearest.

Access instructions are the one to be careful with. A code that reaches gate codes, key-safe locations or alarm procedures is readable by anyone who can stand in front of it, and in a shared lobby or an external gatepost that is the public. Encoding an entry code into something bolted to a wall outdoors is the same as writing it on the wall. If access details are genuinely needed, put them behind a login and let the code point at the door, not through it — and see QR codes and security for why the opacity of a code offers no protection at all.

Amenities and shared equipment

Gyms, laundry rooms, meeting rooms, bike stores, parcel rooms, EV chargers. Two jobs here, and it is worth being clear which one a given code is doing:

Booking — the code opens whatever reservation system already exists. Most of the value is removing the "what was the URL again" step for something used occasionally.
Instructions — how to work the machine, what to do when it jams, who to call. This is where the fallback matters most: someone standing in front of a broken dryer is exactly the person whose patience is lowest.

Community noticeboards are a decent fit as well, since the content changes constantly and the board does not.

These codes have to survive the building

Marketing codes live on a board for six weeks. These live on a wall for years, in the conditions the wall is in — and the failures are environmental rather than about density.

UV and weather. Anything outdoors fades, and a faded code is a contrast failure. Laminate, use UV-stable ink, and re-check after a summer and a winter rather than assuming.
Low light. Plant rooms, bin stores, car parks and stairwells are dim. Phone cameras compensate with longer exposures, which blurs a handheld shot — so print larger than the reading distance suggests. See the sizing guide.
Curved and awkward surfaces. Pipes, handrails, machine housings. The code distorts as it wraps; see curved surfaces.
Physical damage. Codes at hand height get scuffed, stickered over and picked at. Error correction absorbs some of that, and a plate survives better than a sticker.
No signal. Basements and lift lobbies frequently have none. This is the single most common reason a well-made code fails here, and no amount of print quality fixes it — which is why the printed phone number next to it is not optional.

Plan for the systems changing

Buildings outlast software. Over the life of a code installed today you can expect the maintenance portal to be replaced, the managing agent to change, and the contractor list to turn over at least once. A dynamic code means each of those is an afternoon of repointing rather than a re-labelling project across every floor.

Two habits make that survivable:

Keep a register mapping each printed code to its asset and location. When you migrate systems, that register is the difference between a bulk repoint and a walk round the building with a clipboard.
Name codes by asset, not by destination. "Boiler — Block C plant room" stays true through three portal migrations. "Old portal ticket form" does not.

Frequently asked questions

Do we need a special system for this, or will any form do?

Any form works. The code just opens a URL, so a per-asset link to whatever ticketing or forms tool you already use is enough to get most of the benefit. Dedicated facilities platforms add asset history and contractor dispatch, but the "the ticket knows which boiler" win does not require one.

What if a resident scans a code and there's no signal?

Nothing happens, which is why every code in a building should have a printed phone number or email beside it. Basements, plant rooms and lift lobbies are exactly where both the problems and the dead spots are. Treat the code as the fast path, never the only path.

Can we put access codes or key-safe details behind one?

Not on anything publicly reachable. A QR code is an encoding, not a lock — anyone who can photograph it can read it, including from a distance. If the information is sensitive, put it behind authentication and let the code link to the login.

How many codes is too many?

The limit is maintenance, not scanning. Every code is a thing that can point somewhere stale, so a hundred codes with no register is worse than twenty with one. Start with the assets that actually generate tickets — heating, lifts, laundry, lighting — and add only where a real question keeps being asked.

Should each unit have its own code?

For maintenance reporting on shared assets, no — code the asset, not the flat. Per-unit codes are worth it for things genuinely specific to that unit, like an appliance manual pack or a move-in guide, and those usually belong inside the unit rather than in a corridor.