QR tags on penetrations, so the next visit finds them.

Section 01How to do it

1. 01

   Agree the penetration IDs first

   As with doors, the label is only as good as the identity under it. Print after the register is settled, never before.

2. 02

   Check the print before you commit a roll

   Print one, scan it, in the light you will actually have. A riser at eight in the morning is not a desk.

3. 03

   Place them where they survive

   Adjacent to the penetration, on a surface that will not be painted over, re-boarded or wiped weekly. Consistency beats optimal placement.

4. 04

   Set the access rules

   Decide what a scan reveals. Where the record holds sensitive detail, gate it rather than assuming nobody will scan it.

5. 05

   Verify the whole run once

   Scan every tag on the day it is fitted. A mis-mapped tag found later undermines the register it was meant to serve.

Section 02What the app actually does here

• Each penetration can carry its own QR tag, generated from the record
• Penetration labels are produced as PNG images — only fire-door labels print as a PDF sheet
• Scanning opens the penetration record, its photographs and the tested system used
• A tag can be removed and regenerated if a label is damaged or replaced
• The scan link carries a signed token, so a tag resolves to exactly one penetration and cannot be guessed at
• Labels are produced one at a time from the penetration record — preview it, then save or download
• The tag survives re-survey: new findings attach to the same penetration, so its history builds visit on visit

Section 03What goes wrong

Every one of these has cost somebody real time. They are cheap to avoid and expensive to unwind.

Section 04Questions

Section 05Related