Resources • QR tags • scan logs • access
QR tagging for a door register: rollout checklist
A rollout checklist for QR tags so repeat visits are faster without losing traceability, access control, or audit evidence.
- QR tags
- Scan logs
- Access control
- Rollout
- Door IDs
Treat tags as pointers to a door record —
the value comes from what the scan opens
A rollout checklist for QR tags so repeat visits are faster without losing traceability, access control, or audit evidence. Design identity and access in from day one.
Goal 01
Outcome
Repeat visits open the right door record instantly — with history, evidence, and remedials attached. No searching, no duplicates, no guessing which door it was.
Goal 02
Access control
Decide staff vs client views before rollout, then apply login or PIN. Keep scan logs so every access event is attributed, time-stamped, and reviewable at audit.
Goal 03
Rollout discipline
Pilot one building, validate materials and scan speed, then scale with the same ID scheme and placement rules. Naming conventions locked before install — they don't change afterwards.
Choose QR
Use QR for easy rollout and a consistent scan habit across mixed devices — no proprietary reader needed, works on any smartphone.
Roll out with QA
Generate one label per door, install consistently, and spot-check scans so every tag opens the right record before the estate is fully tagged.
Control access + logs
Use PINs or logins where needed and keep scan logs — every scan is an access event that belongs in the audit record alongside the door history.
Five steps that reduce
the usual tag programme problems
Treat tags as pointers to a door record. The value comes from what the scan opens — not the tag itself. Each step keeps that link intact across every visit.
Five steps before tags go on doors
Choose a door ID strategy
Pick stable identifiers and naming conventions before printing labels. If IDs change after tags are installed, every scan becomes a broken link. Agree the format, agree the hierarchy, lock it.
Save labels to device
Generate Standard or Tape label images, save them to the device, and print through the label printer app your team already uses. One label per door — QA before installing.
Control access
Use token verification and optional PIN protection for non-staff views. Decide what a scan should show — staff view versus client view — before any tag goes on a door.
Log scans
Keep scan logs so you can answer who accessed a record and when. A scan is an access event — logs make that visible during audits and incident follow-up.
Keep tags tied to inspections
Each scan must open the correct door record with full history attached. Tags are most valuable when they link to a real audit trail — not a blank or placeholder record.
Most QR programmes fail because
the tag is treated as the system
It's only an identifier. The quality comes from what it links to. Four decisions to lock in before a single label is printed — changing them afterwards breaks every tag already on a door.
Four decisions before printing
Decide what a scan should show
Staff view vs client view, and what evidence should be visible. A scan that shows everything to everyone is a data policy problem waiting to happen.
Agree a naming convention
Door IDs, location strings, and building codes should not change after tags are installed. Every rename after install is a broken link across every scan from that door.
Define ownership
Who creates doors, who can edit, who can close remedials, who can issue PDFs. Ambiguous ownership means records get edited by the wrong person with no audit trail of the change.
Plan for exceptions
Missing doors, duplicate IDs, damaged tags, and "door replaced" scenarios. If you don't have a plan for these before rollout, each one becomes a support crisis mid-inspection.
Minimum data to lock in early
Four things that must be decided before any label is printed
01
Building / site list
Location hierarchy — blocks, floors, zones — agreed and applied consistently before tagging starts.
02
Door ID format
Unique within a building at minimum. Format defined, no free text that changes visit to visit.
03
Tag format + encoding
Short token or URL — not free text that changes. What's encoded must not require manual updates later.
04
Access policy
Public or private scan, PIN protection, expiring links if needed — decided before tags go on doors.
QR rollout tips
What to decide early — before the first door is tagged
Make scans predictable
Keep label placement consistent so teams don't hunt for the code. Same position per door type, agreed before rollout.
Plan for damaged tags
Keep a manual lookup route for replacements and "door replaced" scenarios — don't rely on the tag being the only way in.
Test before rollout
Try one building first to validate materials, readability, and scan speed before committing to a full estate.
Keep a tag register
Door ID ↔ tag ID ↔ install date ↔ installer — so replacements and spot checks stay traceable.
Tags should be consistent and durable —
but must not compromise the door assembly
The scan needs to be fast and predictable on every repeat visit. Four placement rules keep that true without interfering with seals, closers, certification labels, or manufacturer markings.
Four placement rules
Place consistently
Pick one position that site teams can repeat across every door type. Consistent placement means inspectors don't search for the code on repeat visits — it's always in the same corner, at the same height.
Avoid critical components
Do not obstruct intumescent seals, certification labels, hinges, closers, smoke seals, or any manufacturer markings. Labels on components may void certification or affect door function.
Use suitable materials
Choose label stock and adhesive that matches your environment — heat, cleaning agents, moisture, abrasion. A label that falls off after two cleans is worse than no label.
Test on one building first
Validate stickiness, readability, and scan speed before full rollout. One building of failed labels is recoverable — a full estate is not. Test materials in the actual conditions they will face.
Always follow manufacturer guidance and building owner policies for labels and attachments. When in doubt, avoid changing anything on the door and use a nearby approved location instead.
Practical rollout tips
Three things that protect the tag programme after install
Keep a tag register
Door ID ↔ tag ID ↔ install date ↔ installer. When a tag is damaged or replaced, the register keeps the history intact without detective work.
Build a replacement process
Lost or damaged tag → reprint → reassign → keep history intact. Teams need to know the process before the first tag falls off, not after.
Run spot checks
Randomly scan 10 doors per area to catch mis-tags early — a tag opening the wrong record is harder to fix at audit than it is during rollout.
Scanning a door record is an access event —
treat it like one
If you share links externally, you need a simple policy that balances usability with traceability. Decide who can see what, use tokenised links, and log every scan before tags go on doors.
Four access rules before rollout
Decide who can see what
Internal users typically need full evidence — outcomes, photos, notes. External users may only need approved outputs and status. Decide the split before any tag goes on a door — not after a client sees something sensitive.
Use tokenised links
Avoid embedding personal data in the tag itself. Keep the tag as a pointer to the record — the token is what connects the scan to the door, and it can be rotated without replacing every physical tag.
Protect where necessary
Use PIN protection for non-staff views when the building owner policy requires it. PINs add a layer without requiring a full login — practical for client access to approved outputs.
Keep scan logs
Log when a tag is scanned, by whom, and which record was accessed. A scan log lets you answer audit questions and investigate incidents without relying on memory or email threads.
Starter access policy
Simple and practical — four scan scenarios
Staff scans
Full door record + evidence
Typically requires login. Full outcomes, photos, notes, and history visible.
Client scans
Approved outputs only
PDFs and exports — not raw notes or unissued findings, unless policy allows it.
PIN protection
When policy requires it
Use for non-staff access when building owner policy mandates it. Not always needed.
Scan logs
Every scan is an access event
Review logs during audits and incident follow-up — not just when something goes wrong.
If a tag is copied or shared
Three steps to contain it without losing history
Rotate the access token
Invalidate the old token and issue a new one. The physical tag still points to the right door record — only the access credential changes. Old links stop working immediately.
Review scan logs
Use the access log to confirm when and where the link was accessed — how many times, from which device type or IP range, and whether anything sensitive was viewed.
Keep the door record history intact
Only replace the tag pointer. The door record, inspection history, and evidence are unaffected. Reprint and reassign the tag to the same door if the physical label needs replacing.
Quick answers on offline scanning, client access,
and where tags add real value
Four questions that come up most often during rollout planning and the first few weeks on site. Deeper guidance is in the related guides.
Connectivity & client access
Tags open a link to a record, so viewing the full door record in real time requires a connection. However, Fire Door App works offline-friendly — inspectors can keep capturing findings as drafts when signal drops and sync when they're back on a stable connection.
In practice, most teams scan to confirm they're on the right door, then capture findings in the app regardless of live connectivity. The scan opens the record; the draft captures the findings. Sync everything at the end of the day.
Sometimes — it depends on your client relationship and what the scan should show. Decide the staff vs client view split before rollout, then use access controls (login or PIN) so sensitive evidence isn't shared unintentionally.
A reasonable baseline: clients see approved outputs — PDFs, status, completed evidence — but not raw notes, unissued findings, or internal team comments. If client scans are out of scope entirely, use login-only access so unauthenticated scans show nothing.
Tags & value
Treat tags as pointers, not the system itself. If a tag is copied and shared, rotate the access token — the old link stops working immediately, and the physical tag still points to the right door. You don't need to replace the label to revoke access.
If the physical label needs replacing (damaged, fallen off), reprint and reassign it to the same door. Keep the door record history intact — only the tag pointer changes. Use scan logs to confirm what was accessed before the rotation.
Repeat visits. On a first inspection of a new estate, tags save minimal time because inspectors are building the register anyway. The value compounds on every subsequent visit — scan instead of search, open the right record instantly, and reduce the risk of creating a duplicate for a door that already has history.
Tags also add value for handovers between inspectors or when a different team takes over a building — the scan always opens the same door record regardless of who's holding the tablet, removing reliance on institutional memory or naming conventions.
Quick facts
QR tagging at a glance
What a tag is
A pointer to a door record — not the audit trail itself. Value comes from what the scan opens
Lock in first
Stable door IDs, naming convention, access policy, and ownership — before printing labels
Offline
Capture works offline — scan to confirm door, draft findings, sync at end of day
Scan logs
Every scan is an access event — who, when, which record — for audit and incident follow-up
Revoke access
Rotate token to invalidate — no need to replace the physical label. History stays intact
Most value
Repeat visits and team handovers — scan opens the right record instantly, no duplicate risk
Get started
Roll out tags on one building first
Generate labels, tag a small set of doors, and test the scan flow end-to-end before committing to a full estate.
Roll out tags on one building first.
Then test scan flow end-to-end before the full estate.
Generate labels, tag a small set of doors, and confirm every scan opens the right record with access rules and logs you can defend in an audit.