The location tree

Locations are the backbone of MaintenanceOps. Work orders happen at a location, assets live at one, parts are stored at one, and requests are routed by one.

Why location setup matters

A clean location tree improves request routing, technician directions, asset history, inventory, PM setup, and reporting all at once. It is one of the highest-leverage setup tasks in MaintenanceOps.

Build the tree top-down

Level	What it represents	Example
Site	Campus, property, or top-level address	Main Campus
Building	A building inside the site	Elementary School
Room	A room or specific space	Room 204

Main Campus → Elementary School → Room 204

Add detail only where it helps operations. You do not need to model every closet or hallway unless you want work, assets, or inventory tied to that space.

Add sites, buildings, and rooms

• Select + New site to create the top level.
• Open a site and select + Building.
• Open a building and select + Room.

Use names people recognize

A technician should be able to read a work-order location and know where to go. Match signs, room numbers, or the names staff already use instead of inventing codes the team must decode.

Decide what each room is used for

Room setting	Turn it on when
Work-order location	Someone may realistically report or perform maintenance in the space
Storage location	Technicians physically keep stocked parts there

A room can be both, either one, or neither.

See Storage and stock for inventory setup.

Assign managers for request routing

Sites and buildings have a Managers panel. Managers assigned at a higher level cover locations beneath them, so assignments usually do not need to be repeated room by room.

When a request is submitted, MaintenanceOps routes it according to the selected location. If no manager is assigned, the request escalates to a Super Admin.

Check manager coverage before opening requests to staff

A requestable location without the intended manager may still route, but it can land with a Super Admin instead of the person who normally owns that building. Verify coverage before broadly sharing the request process.

See Requests and approvals for the full request workflow.

Control what requestors can select

Use Show to requestors for spaces people should be allowed to choose on a request form. Hide operational spaces that would confuse general staff, such as internal storage rooms or mechanical areas.

A smaller, familiar list makes requests faster and reduces incorrectly located work.

Choose the right view

View	Best for
Panel	Understanding one site, building, or room together with its connected assets, parts, PMs, procedures, and work history
Table	Scanning and sorting many locations and comparing counts such as assets, parts, and open work orders

Higher-level locations roll up information from the spaces beneath them.

Before you move on

A good location setup should pass these four checks:

1. Recognizable names — staff and technicians understand them.
2. Work-order rooms marked — requestable/workable rooms are enabled correctly.
3. Storage rooms marked — inventory locations appear where they should.
4. Manager coverage set — requests reach the right person.

Next step

For property contacts, lease dates, insurance renewals, square footage, and site-level maintenance cost, continue with Building details and renewals.