Stable hierarchy
Site → building → floor → area stays consistent.
Resources • floorplans • locations • reporting
Floorplans and door navigation for clean reporting
A practical guide to structuring properties, floors, and door navigation so repeat visits stay consistent and reporting doesn’t turn into a naming clean-up project.
- Floorplans
- Locations
- Door register
- Reporting
Click to enlarge
Guide summary
Navigation help
Floorplans improve site speed but don’t replace IDs.
Clean reporting
Exports don’t need location “translation” later.
Who this is for / when to use it
Use this when setting up a new property, importing a door list, or planning repeat visits where consistency matters.
- Inspectors: find doors quickly on site without guessing locations.
- Office ops: ensure reports/export naming is readable and stable.
- Admins: define a hierarchy rule once and keep teams aligned.
Location hierarchy model
A simple hierarchy makes reporting readable and repeat visits consistent.
- Site: the client site or estate.
- Building/block: separate structures within a site.
- Floor/level: 0/1/2, B1, Mezzanine, Roof.
- Area/zone: corridor, stair core, wing, riser, etc.
Example hierarchy (copy/paste)
- Site: “Riverside Estate”
- Building: “Block A”
- Floor: “Level 03”
- Area: “Stair Core A” / “East Wing Corridor”
Floorplans workflow (upload, navigation, pinning)
Floorplans are for speed and clarity on site — keep them aligned to your hierarchy.
- Upload per floor: keep files small and readable on mobile.
- Pin doors consistently: match pins to stable door IDs.
- Use the same names: floor names in the plan match the system hierarchy.
Naming conventions for clean reporting
A naming rule is how you prevent “location drift” across inspectors.
- Short and stable: “Level 03” not “Third floor near lifts”.
- Don’t rename: if a name changes, keep a mapping and document it.
- Use the same abbreviations: decide once (e.g. “Stair A”, not “Staircase A”).
Naming cheat sheet
- Floors: “B2 / B1 / G / 01 / 02 / 03” (pick a format and stick to it).
- Areas: “Wing / Corridor / Stair / Riser / Plant” (choose standard nouns).
- Duplicates: suffix with a stable qualifier: “(North) / (South)”, not “near lifts”.
Edge cases
Decide how you’ll handle tricky layouts before the first big rollout.
- Duplicate floors: “Level 02 (North)” and “Level 02 (South)” beats ad-hoc wording.
- Replacements: keep identity stable where possible; don’t reuse IDs for different openings.
- Unknowns: use a consistent “unknown location” process and fix it later.
Quick QA checks (before exporting)
Run these checks so your PDF/CSV outputs don’t need manual “cleaning”.
- No duplicate doors: repeat visits should open the existing door record.
- Locations consistent: floor and area names don’t vary by inspector.
- Door IDs stable: exports reference the same doors across time.
Common pitfalls (navigation and reporting)
Good structure makes everything else faster: inspections, exports, and close-out.
- Renaming floors mid-project: prefer stable names + documented mappings over constant edits.
- Deep hierarchies: too many levels makes navigation slow; keep it practical for field teams.
- Door ID reuse: don’t reuse IDs for different openings; it breaks history continuity.
- Plans without pin discipline: pins should map to stable door IDs, not temporary labels.
Common questions
Quick answers on layouts, estates, and stable reporting.
How do we handle basements, mezzanines, and odd layouts?
Choose a naming rule that stays stable (e.g. B1, MZ, Roof) and use it consistently across properties. The goal is repeatability, not perfection.
What about estates with multiple blocks?
Treat each block/building as its own top-level structure, then apply the same floor/area naming rules inside each one.
What breaks reporting most often?
Location drift (different wording per inspector), duplicate doors created on repeat visits, and IDs reused after replacements.
Do floorplans replace door IDs?
No. Floorplans help navigation, but stable door IDs keep history and audit trails consistent over time.
Next step
Structure one building cleanly.
Then run an inspection and export a report without location clean-up afterward.