Journal/Guide

A building issue reporting system needs a front door

Ten past ten, level three lift lobby, corridor light out and the fire door not latching. Whether the resident's scan becomes a record or a suggestion depends on the door: not bolted, not wide open, a doorman.

A two-colour risograph poster of a door standing slightly ajar in its frame with a small orange square label on the wall beside it
WP
Will PrinmanCo-founder
16 September 2026·5 min read

Ten past ten on a Tuesday night, level three lift lobby of an occupied residential building. A resident coming home notices the corridor light by the fire stair is out and the fire door beside it is not latching. There is a small printed label on the wall next to the lift call button. She scans it with her phone.

What happens in the next ninety seconds decides whether that building has an issue reporting system or a suggestion box.

Two ways to get it wrong

Most buildings do one of two things with that resident, and both are wrong.

The first is the bolted door. Report it to the building manager, by email, in business hours. The resident does not, because it is ten at night and she is tired, and the fire door stays unlatched until the annual fire safety inspection finds it. The report that never got made is the most expensive one in the building.

The second is the open door. A web form, or worse a shared inbox, that anyone can drop anything into with no name attached. That feels helpful right up until the first week, when it fills with three reports of the same light, two complaints about the neighbour's dog, and one about the light that is actually on level four. Nobody can ask a follow-up question because nobody knows who sent it. Nothing gets attributed, so nothing gets verified, so the manager stops reading it.

Here is the opinion: a building issue reporting system needs a front door with a doorman. Anyone can walk up. Nobody gets in without being let in. Once you are in, you are in for years.

What the label on the wall actually does

The label is a QR code scoped to a location. Not the building, the level three lift lobby. Scanning it opens the record for that spot and nothing else, which is why the report about the light cannot end up on level four.

Scanned by a stranger, it shows a read-only view or a sign-in prompt. It does not let them submit anything. What it offers instead is a short form: name, email, phone. That creates a pending request. The account exists, the login does not work yet, and nothing the person types goes anywhere until someone in the office approves them.

That is the doorman. It costs the manager one look at a request, once per resident. Approve, and the resident gets a set-password link and can report for as long as they live there. Deny, and the account is dead, along with any printed card they were holding.

There is a rough edge worth naming. Residents type their own apartment number into a phone form at ten at night, and they get it wrong. That is why the approve screen lets you correct the name, email and unit before you say yes. Do it there, because a resident attached to the wrong unit is a mess to unpick later.

What the resident sees afterwards

Once approved, the resident lives inside a surface built for one thing. Their own reports, with a photo on each one, and a status that moves. Not other residents' reports. Not what the repair cost. Not the name of the electrician who attended. They can raise an item and comment on it. They cannot change a status, because the person who reported the light out is not the person who decides it has been fixed.

At handover, or the day a new owner settles, a printed QR card does the same job without the pending step, because you already know who they are. The card logs them straight in and keeps working for years. Take it back by deactivating the user and the card dies with it.

What the manager sees

Every report lands on the same location tree the building was built on. Level three, lift lobby, common area. Unit 304, ensuite. That addressing is the quiet win. When the level three lobby light is reported for the fourth time in a year, the record shows four items hanging off one location, which is a different conversation with the electrical contractor than four separate emails ever were.

Assign the light to the electrician in a couple of taps. They get an email with a link that opens the work, no app to install. They attend, photograph the fix, mark it done. The manager looks at the photo and closes it. Every step stamped with who and when. Eighteen months later, when a committee member asks why the fire door on three was unlatched for a week, the answer is on the record instead of in someone's memory.

What it is not

It is not an anonymous hotline. If a building genuinely wants unattributed reporting, this is the wrong tool, and it is wrong on purpose. An issue nobody will put their name to is an issue nobody can ask a question about, and a report you cannot verify is a report you cannot act on with any confidence. The front door asks for a name.

And it does not run your maintenance calendar. There is no preventive schedule in it that says the fire doors get checked in March. That is a different product, and we would rather say so than pretend. What this one does is make sure that when a door fails between inspections, a resident can tell you at ten at night, and you have a record of exactly when she did.

The label on the wall, the pending request and the card at handover are laid out as one answer on how tenants report maintenance without calling the office. For a strata scheme, where the committee sits in the client seat and the register covers common property, the strata page has the rest.

IssuesId