Hierarchical Location Structure - Buildings, Floors, and Rooms

Overview

Hierarchical location structures organize your physical spaces in parent-child relationships, mirroring your actual facility layout. This creates a tree-like organization:

Campus
└── Building A
    ├── Floor 1
    │   ├── Room 101
    │   └── Room 102
    └── Floor 2
        ├── Conference Room A
        └── Server Room

Benefits of hierarchical locations:

Logical organization that matches your physical layout
Easier navigation when finding assets
Grouped reporting (see all assets in a building, even across floors)
Flexible auditing (audit an entire floor or just one room)
Scalable structure that grows with your organization

Understanding Location Hierarchy

Parent-Child Relationships

Each location can have:

One parent (the location it belongs to)
Multiple children (locations within it)
No parent (top-level locations like buildings or campuses)

Example:

Parent: Building A - Floor 1
  └── Children:
      - Room 101
      - Room 102
      - Room 103

Inheritance and Reporting

When you view assets in a parent location, you typically see:

Assets directly assigned to that location
Assets in all child locations beneath it

Example: Viewing "Building A" shows:

Assets in "Building A" (not assigned to specific floors)
Assets in "Floor 1"
Assets in "Floor 1 - Room 101"
Assets in "Floor 2"
Assets in all other child locations

Common Hierarchy Patterns

Campus > Building > Floor > Room

Ideal for universities, corporate campuses, or large facilities:

Main Campus
├── Building A (Administration)
│   ├── Ground Floor
│   │   ├── Reception
│   │   └── Mail Room
│   ├── Floor 1
│   │   ├── Room 101 - HR
│   │   └── Room 102 - Finance
│   └── Floor 2
│       └── Executive Offices
└── Building B (Operations)
    ├── Warehouse
    └── Loading Dock

City > Site > Building > Area

For multi-site organizations:

East Coast Operations
├── New York Office
│   ├── Headquarters Building
│   └── Data Center
└── Boston Office
    ├── Sales Floor
    └── Support Center

West Coast Operations
├── San Francisco Office
└── Los Angeles Distribution Center

Building > Department > Zone

Functional organization within a single facility:

Corporate HQ
├── IT Department
│   ├── Server Room
│   ├── Network Operations
│   └── Help Desk
├── Manufacturing
│   ├── Assembly Line 1
│   ├── Assembly Line 2
│   └── Quality Control
└── Warehouse
    ├── Receiving
    ├── Storage - Aisle A
    └── Shipping

Warehouse > Zone > Aisle > Shelf

Detailed inventory tracking:

Main Warehouse
├── Zone A (Electronics)
│   ├── Aisle A1
│   │   ├── Shelf 1
│   │   └── Shelf 2
│   └── Aisle A2
│       ├── Shelf 1
│       └── Shelf 2
└── Zone B (Office Supplies)
    ├── Aisle B1
    └── Aisle B2

Building a Hierarchy

Method 1: Top-Down Creation

Create parent locations first, then add children:

Step 1: Create Top-Level Locations

1. Dashboard > Settings > Locations
2. Create "Building A" (no parent)
3. Create "Building B" (no parent)

Step 2: Add Second-Level Children

1. Create "Floor 1"
   - Set Parent: "Building A"
2. Create "Floor 2"
   - Set Parent: "Building A"
3. Create "Warehouse"
   - Set Parent: "Building B"

Step 3: Add Third-Level Children

1. Create "Room 101"
   - Set Parent: "Floor 1"
2. Create "Room 102"
   - Set Parent: "Floor 1"

Method 2: Bottom-Up Creation

Create all locations first, organize later:

Create all locations without parents
Edit each location to assign its parent
The hierarchy forms automatically

When to use: If you have a list of all locations and want to enter them quickly.

Method 3: Hybrid Approach

Create major structures, add details as needed:

Create buildings (top-level)
Create floors as you deploy assets
Add rooms when you need granular tracking

When to use: Starting small and scaling up over time.

Reorganizing Hierarchies

Moving a Location to a New Parent

Go to Dashboard > Settings > Locations
Click Edit on the location to move
Change the Parent Location dropdown
Click Save

Effect: The location and all its children move together in the tree.

Example:

Before:
Building A
└── Floor 1
    └── Server Room

After (moving Server Room to Floor 2):
Building A
├── Floor 1
└── Floor 2
    └── Server Room

Removing a Location from Hierarchy

To make a location top-level:

Edit the location
Set Parent Location to "None"
Save

The location becomes a root node in the tree.

Deleting Parent Locations

You cannot delete a location that has children. First:

Option A: Move children to a different parent
Option B: Move children to top-level (no parent)
Then delete the original parent

Best Practices

Keep Hierarchy Depth Reasonable

3-5 levels is optimal:

Level 1: Campus/Building
Level 2: Floor/Department
Level 3: Room/Area
Level 4: Zone (optional)
Level 5: Specific rack/shelf (optional)

Avoid excessive nesting:

❌ Too deep: Campus > Region > City > Building > Wing > Floor > Section > Room > Zone > Sub-zone > Rack > Shelf
✅ Better: Building > Floor > Room > Rack

Use Consistent Levels Across Branches

Keep similar structures at the same level:

Consistent:

Building A
├── Floor 1
│   └── Room 101
└── Floor 2
    └── Room 201

Building B
├── Floor 1
│   └── Room 101
└── Floor 2
    └── Room 201

Inconsistent (avoid):

Building A
└── Room 101  (skipped Floor level)

Building B
└── Floor 1
    └── Room 101

Name Locations to Show Hierarchy

Even though hierarchy is built-in, clear names help:

Good:

Building A
└── Building A - Floor 1
    └── Building A - Floor 1 - Room 101

Also Good (codes):

HQ
└── HQ-F1
    └── HQ-F1-R101

This makes locations identifiable even when viewed in a flat list (like asset edit forms).

Match Your Physical Layout

Your digital hierarchy should mirror reality:

If your building has 5 floors, create 5 floor locations
If you have open-plan offices, don't create individual desk locations
Match how your team talks about spaces

Viewing and Navigating Hierarchies

In Location Settings

The Locations management page shows the hierarchy:

Top-level locations appear first
Children are indented beneath parents
Expand/collapse sections to navigate

In Asset Filters

When filtering assets by location:

Select a parent to see all assets in that location and its children
Select a child to see only assets in that specific location

In Reports

Location reports can:

Show asset counts per location
Roll up child location data to parents
Display the full hierarchy path for each asset

See Location Reports for details.

Use Cases

University Campus Management

North Campus
├── Science Building
│   ├── Biology Lab (Floor 1)
│   ├── Chemistry Lab (Floor 2)
│   └── Physics Lab (Floor 3)
└── Library
    ├── Main Reading Room
    └── Computer Lab

South Campus
├── Student Center
└── Athletic Facility

Benefits:

Audit entire buildings at once
Report on asset distribution by campus
Track equipment moves between labs

Multi-Site Retail Chain

Region: Northeast
├── Store #101 - Boston
│   ├── Sales Floor
│   ├── Stockroom
│   └── Office
└── Store #102 - New York
    ├── Sales Floor
    ├── Stockroom
    └── Office

Region: Southeast
├── Store #201 - Miami
└── Store #202 - Atlanta

Benefits:

Compare asset allocation across stores
Audit by region or individual store
Track regional vs store-specific equipment

Manufacturing Facility

Plant 1
├── Production Floor
│   ├── Assembly Line A
│   ├── Assembly Line B
│   └── Quality Control Station
├── Warehouse
│   ├── Raw Materials
│   ├── Finished Goods
│   └── Shipping Dock
└── Maintenance Shop
    ├── Tool Crib
    └── Repair Bay

Benefits:

Track equipment by production line
Analyze maintenance costs per area
Manage warehouse inventory separately from production assets

Quick Tips

Start with Major Divisions
Create your top-level locations first (buildings, sites, campuses). Add detail later as needed.

Don't Over-Structure Initially
Begin with 2-3 levels. Add more depth only when you have enough assets to justify it.

Test with Real Assets
Create a few assets in different locations to see if your hierarchy makes sense for finding and reporting.

Use Hierarchy for Delegation
Assign location managers or auditors to specific branches of the tree.

Plan for Growth
Leave room in your naming scheme for new buildings, floors, or areas.

Next Steps

Creating and Managing Locations - Add new locations to your hierarchy
Moving Assets Between Locations - Track transfers within your hierarchy
Location Reports - Analyze assets by hierarchy level
Location-Based Asset Audits - Audit by branch of the tree

Common Questions

Can I have multiple top-level locations?
Yes. Each building, campus, or site can be a separate root in the hierarchy.

What's the maximum hierarchy depth?
There's no hard limit, but 5-7 levels is the practical maximum before navigation becomes cumbersome.

Can a location have multiple parents?
No. Each location has exactly one parent (or none for top-level locations). This keeps the tree structure clean.

What happens to child locations if I delete a parent?
You can't delete a parent that has children. Move the children to a new parent or remove their parent first.

Should I use hierarchy or departments for organizing assets?
Use both! Hierarchy reflects physical location (where assets are), while departments reflect organizational ownership (who owns them). An asset can be in "Building A - Floor 2" (location) and owned by "IT Department" (department).

Can I export the full hierarchy path for each asset?
Yes. CSV exports can include the full location path (e.g., "Building A > Floor 1 > Room 101").

Need Help?

If you have questions not covered in this article, our support team is here to help.

Contact Support