Floorplans · navigation
● maps

Structure guide

Site → door without guesswork.

Client, building, floor and area model; floorplan pins that match the register; naming rules and duplicate handling before exports scale across a portfolio.

Hierarchy Pins Naming QA

Floorplans are optional until they are not — once pins exist, they must match the register or every visit wastes time.

Location model

Riverside House · portfolio
ClientContract boundary · billing entity
BuildingBlock A vs B split for large sites
FloorLevel 2 · matches drawing title block
AreaEast wing · ties to door list sort
ZonesCompartment lines · matches drawing zones
LegacyOld names aliased · not duplicated rows

Drift here splits reports silently — fix structure before you add more buildings.

Import building lists once from the client — do not let every inspector invent spelling.

Floorplan pins

Drawing · Level 2
Upload
Current revision · dated filename
Pin
Leaf side · readable door code
Match
Pin label = register ID
QA sample
Spot-check 10% per floor
Revision
Drawing ref in filename · P01
Scale
Check door swing matches reality

Inspectors should never guess which physical door is FD-088.

Wrong pin is worse than no pin — mark “unverified” until someone walks the route.

Governance

Naming · duplicates · renames
Prefix multi-block sites before IDs collide
Resolve duplicate IDs before CSV export
Bulk rename with client comms, not silent edits
Guide below + door ID checklist for detail
Renames broadcast to coordinators before export
Portfolio view: same rules per client

The long guide covers site workflow, pitfalls and FAQs end to end.

Guide below Door IDs →

QR rollout should wait until hierarchy and pins are trusted — tags cement mistakes too.