Available On: Essential, Premium, Professional, Enterprise
📋 Overview
Locations are the foundation of organized maintenance in UpKeep. They define where your assets live and where maintenance work takes place — making it easy to assign tasks, track history, and run location-specific reports.
UpKeep supports a multi-level location hierarchy so you can mirror your real-world facility structure, from a single building down to individual rooms, floors, or zones.
🏗️ Location Hierarchy by Plan
The depth of your location hierarchy depends on your UpKeep plan:
Plan | Hierarchy Depth | Example |
Essential, Premium, Professional | 2 levels | Building → Floor |
Enterprise | Up to 6 levels | Campus → Building → Wing → Floor → Zone → Room |
💡 Enterprise customers can nest sub-locations up to 6 levels deep, enabling detailed facility mapping for complex multi-site operations.
🔧 Key Capabilities
Multi-level nesting — Create parent locations with sub-locations up to 6 levels deep (Enterprise)
Address & map coordinates — Pin exact GPS coordinates for each location
Team assignments — Assign workers, teams, vendors, or customers to specific locations
Work order association — Link work orders directly to the exact location where work is needed
Bulk import — Upload multiple locations at once via CSV import
Location-based permissions — Control who can see and manage specific locations
📍 How to Add a Location
Navigate to the Locations section in the left sidebar.
Click Create Location in the upper right.
Enter the required details:
Location Name — A clear, descriptive name (e.g., "Warehouse A" or "Main Office - Building 2")
Street Address — The full street address for the location
(Optional) Add map coordinates to pin the exact GPS position.
(Optional) Assign workers, teams, vendors, or customers to this location.
Click Create Location to save.
You'll see the new location appear in your Locations list immediately.
📂 How to Add a Sub-Location
Sub-locations let you nest locations within a parent — for example, adding "Floor 1" and "Floor 2" under "Building A."
Option 1: From the Locations List
Navigate to the Locations section.
Find the parent location in the list.
Click the Options Menu (three-dot icon) next to the parent location.
Select Add Sublocation.
Enter a descriptive name for the sub-location.
Click Create Location to save.
Option 2: From a New Location
Click Create Location as usual.
In the location details, set the Parent Location field to the desired parent.
Click Create Location to save as a sub-location.
🏢 Enterprise: Building a 6-Level Hierarchy
Enterprise customers can nest sub-locations up to 6 levels deep. Here's how to build out a deep hierarchy:
Plan your structure first. Map out your hierarchy on paper before creating locations. Example:
Level 1: Campus (e.g., "West Coast Campus")
Level 2: Building (e.g., "Building A")
Level 3: Wing (e.g., "North Wing")
Level 4: Floor (e.g., "Floor 3")
Level 5: Zone (e.g., "Zone B")
Level 6: Room (e.g., "Server Room 3B")
Create top-level locations first, then add sub-locations at each level using the steps above.
Repeat the sub-location process at each level — each sub-location can itself have sub-locations, down to 6 levels.
💡 Tip: Use the bulk import feature to set up large hierarchies efficiently. Include parent location references in your CSV to auto-nest locations.
📤 Bulk Import Locations
If you have many locations to add, use UpKeep's bulk import to save time:
Go to the Location Import Page.
Download the CSV template.
Fill in your location data, including parent location references to establish hierarchy.
Upload the completed CSV.
Review the import preview and confirm.
✅ Best Practices
Use consistent naming conventions — Include identifiers in location names (e.g., "Kitchen - W1" instead of just "Kitchen") so team members know exactly which location is which.
Plan your hierarchy before building it — Restructuring later can affect existing work orders and reports. Take time to map out levels before creating locations.
Start broad, then go specific — Create top-level locations first, then drill down into sub-locations. This keeps your structure clean and logical.
Use addresses and coordinates — Adding street addresses and GPS coordinates makes it easier for field technicians to find locations, especially across multiple sites.
Assign teams at the right level — Assign workers and teams to the most specific location level relevant to their work area.
💼 Common Use Cases
Multi-site facility management — A company with 10 warehouses uses Level 1 for each warehouse, Level 2 for zones within each warehouse, and Level 3 for specific bays or docks.
Campus management — A university maps Campus → Building → Floor → Department → Room to route maintenance requests to the right team.
Fleet & yard tracking — A logistics company uses locations to track vehicle maintenance by region, depot, and parking zone.
Healthcare facilities — A hospital group nests locations by Hospital → Wing → Floor → Department → Room for precise equipment tracking.
❓ FAQ
Can I create work orders for a location without an asset?
Yes. Many customers use location-based work orders for site-specific maintenance — for example, "ceiling light damage in Main Office" without attaching a specific asset.
If I assign a work order to a sub-location, will it appear under the parent location in reports?
No. Work orders are tied to the exact location selected. A work order assigned to "Floor 3" will only appear under Floor 3 in reports — not under the parent building. To see work orders across all levels, adjust your report filters to include sub-locations.
Can I move a location to a different parent?
Yes. Edit the location and change the Parent Location field. Note that any existing sub-locations under it will move along with it.
How many locations can I create?
There's no hard limit on the number of locations. The hierarchy depth limit (2 or 6 levels) depends on your plan, but you can create as many locations at each level as needed.
Can I import sub-locations via CSV?
Yes. Include the parent location reference in your CSV file, and UpKeep will automatically nest the imported locations under the correct parent.