🚪 One Tag Per Door: Building Owners, Units and Tenant Requests That Know Which Flat They Came From

The first version of tenant requests gave a building one code. It worked, and within a week of using it on a real property the limitation was obvious: a request would arrive saying the heat was out, and the first thing anybody had to do was ring round to find out whose heat.

A forty-door building with one code is a suggestion box. What a maintenance team needs is the door number, and asking the resident to type it is not the answer — they get it wrong, they leave it blank, or they put the building number in the unit box. A job for 4B arrives labelled 12C and somebody drives across town twice.

So the tag now belongs to the unit rather than the building, and everything the request needs to be actionable is attached to the tag rather than asked for on the form.

A building now records three different people

Before any of this works, the app has to be able to tell three parties apart, because they are routinely confused and the consequences of confusing them are not symmetric.

The site contact is who a vendor calls. That is the one that can appear on a public check-in page, because it is a business line and the whole point of publishing it is that a contractor standing at a locked door can reach somebody.

The building owner is the person or company that owns the property. That is a commercial relationship and it is never published anywhere.

The tenant is whoever is in a particular unit right now. That is somebody's home address and phone number, and it is the one that must never leave your account — which is why the tenant page publishes a unit LABEL and never a tenant name.

• ▸ Owner — recorded per building, never published, changed only by an account owner or manager.
• ▸ Site contact — recorded per building, may appear on a vendor check-in page, and can be switched off per building.
• ▸ Tenant — recorded per unit, never published, read privately when a request arrives so the office knows who to call back.

Every unit, including the empty ones

Suites & Tenants lists every unit at a property. A unit is whatever the door says — 4B, Suite 200, North Wing, Unit 12 — and it exists whether or not there is any equipment in it. A vacant suite says "vacant, nothing installed" instead of quietly not being there, because a vacancy is a fact you want on the list when you are planning a turnover.

A unit carries the tenant's name, phone, email and free-text notes: access instructions, the alarm code, who to call first. Only an account owner or manager can write the tenant fields — the same rule the app already applied to the site contact, since who is in a property is a customer relationship rather than a job detail.

Renaming a unit does the thing you would expect and the thing you would not. Rename 4B to 402 and every piece of equipment labelled 4B follows it. Work orders do not: a job that was done in 4B stays recorded as 4B, because an invoice has to keep matching the paperwork it was raised against.

What the resident actually sees

They point a camera at the tag and a page opens. No app, no account, no password, and the page says so in as many words — the line about never asking you to pay or sign in is there so that a spoofed sticker has something to contradict.

The first thing on the page is the way out, not the way in. An emergency number sits above the form as a tap-to-call button, because somebody reading it may be walking down a staircase.

Then a short set of questions. If any of them is answered yes — a gas smell, in particular — the form is removed and replaced by that phone number. This is deliberate and it is the one piece of the page that is not a preference: every gas utility gives the same instruction, which is to leave and not use a phone, a light switch or any electrical device indoors. Filling in a web form is the dangerous act, so the page refuses to accept one rather than flagging it as urgent and sending it.

If nothing is tripped, they describe what is wrong and can attach up to three photos. They are not asked for a unit — it came from the tag. They are not asked for a phone number or an email — those are read from the unit's own record when the request arrives. Their name is optional, because a roommate or a guest cannot honestly answer it.

The page behind the tag, written once and then adjusted

Under the form is whatever the property manager chose to publish: office name, phone, email and hours; an out-of-hours number; what counts as an emergency; shutoff locations; fire safety; utilities; bins, parking and quiet hours; current notices; and links to documents.

That is written once for the building, and every unit shows it. Then a unit changes only the parts that are different — because the shutoffs are behind the pantry in one flat and in the hall closet in another, and the ground-floor suite puts its bins in the side alley. A unit stores only its difference, so changing the office number changes it everywhere rather than in forty places.

A button on the unit copies the building's text in so it can be edited rather than retyped. It fills only the blanks, so pressing it twice never overwrites a sentence already written for that unit.

Two of the fields are deliberately dumb. Fire safety is free text only — nothing generates it, templates it or suggests a default, because stay-put versus evacuate depends on how the building is constructed and in some cities an official notice is already required on that door. And the document links carry a warning at the point you paste one: anyone who scans the tag can open it, there is no sign-in, so a lease does not belong there.

From a scan to a job

Requests arrive in their own tab and stay there. They never become a work order on their own — a report from a resident is a claim that something is wrong, not an instruction to dispatch, and the two should not be the same object.

When you do turn one into work, it asks who to assign it to from your team, the same as any other work order, and the unit travels with it. Photos stay private throughout: readable only by you and your active team after signing in, never by the public and never in the notification email.

Alerts go to a notify list kept deliberately separate from your vendor check-in contacts, because a contractor should not be told what is broken inside somebody's home. That list takes emails and text numbers, and each number shows whether it has actually registered SMS consent — carriers block the message otherwise, and a number that has not registered is accepted and then silently never texted, which is worse than a visible failure.

Printing them

A tag prints as a letter-size door tag, or on 4 × 6, 4 × 2 or 2 × 2 label stock, with the unit already printed on it in large type — the point of a per-unit tag is that nobody has to work out which unit it belongs to, including whoever sticks it up.

Choosing a label size sets the page size, so a label printer is told 4 × 6 rather than handed a letter sheet with a small drawing in the corner. Both the phone and the web dashboard print the same thing from the same generator.

If a card goes missing, replace it. Replacing mints a new code and retires the old one immediately, so the card in somebody's bin stops working.

And you can find one unit again

A building's equipment list filters by unit, on the phone and on the dashboard, including a "no unit set" option for the machines nobody has labelled yet — which is the filter you actually want first, because it is the list of work to do before any of this is useful.

Work orders carry the unit they were done in, so "what has been done in 4B" is a question with an answer.

Does the tenant need the app or an account?

No. They point a phone camera at the tag and a web page opens. There is no app to install, no account to create and no password. The page states that it will never ask you to pay or sign in, so a fake sticker has something to contradict.

How does the request know which unit it came from?

The unit is encoded in the tag itself, which is minted for one unit. The resident is never shown a unit field to fill in, so there is no way for the request to carry a unit that disagrees with the door it was scanned on.

Is the tenant's name or phone number published on the page?

No. The tag publishes the building name and the unit label and nothing else about who lives there. The callback contact is read from the unit's private record when a request arrives, so it never travels through the public page.

What happens if a printed tag goes missing?

Replace it on that unit. Replacing mints a new code and retires the old one straight away, so a card that has gone astray stops working immediately rather than staying live.

Can two units say different things on their page?

Yes. The building page is the base every unit shows, and a unit overrides only the parts that differ — a shutoff location, a bin day, a parking rule. Text replaces; lists like house rules and documents add to the building's rather than replacing them.

Does a tenant request create a work order automatically?

No. Requests land in a Tenant Requests tab for review and never become work on their own. Turning one into a work order is a deliberate step, and it asks who to assign it to from your team.

What happens if someone reports a gas smell?

The form is removed and replaced with a phone number and the instruction to leave first and call from outside. Filling in a form indoors is the dangerous act, so the page refuses to take one rather than accepting it and marking it urgent.

Does this work on the web dashboard as well as the app?

Yes. Units, owners, tenant pages, per-unit overrides and tag printing all work the same on the phone and on the web dashboard.

Jonathan Curtis

HVAC Technician & Founder · Equipment Tracker Pro

Jonathan Curtis is an HVAC technician and the founder of Equipment Tracker Pro. He built the app to solve real problems he encountered in the field, including the daily frustration of faded nameplates and administrative double-entry.