Decide what is shared and what stays local
A multi-site evaluation begins with an operating model. Decide which definitions should be common across the organization and which choices belong to each location. Asset naming, work categories and reporting definitions may benefit from shared standards. Assignment queues, local suppliers and storeroom balances may need their own rules.
Write down the exceptions before selecting a product. Two facilities may use the same type of equipment but have different schedules or staffing. The system should support those differences deliberately rather than forcing staff to create unexplained duplicate categories.
Demonstrate roles at two different locations
Use at least two sample sites and distinct user roles. Ask a local technician, site planner, regional manager and central administrator to complete appropriate tasks. Demonstrate both what each person can access and what they cannot. Avoid evaluating only with an unrestricted administrator account.
- A technician finds assigned work and the correct local asset history.
- A planner changes local priorities without altering another site’s queue.
- A regional manager compares sites using the intended report definitions.
- A contractor receives access limited to the authorized work.
- An administrator changes shared templates without overwriting necessary local details.
- A transferred employee gains the right access and loses access that is no longer needed.
Check the operational boundaries
Follow a part, an asset and a work order through the processes that cross locations. Ask how stock transfers, moved equipment and shared vendors are represented. Confirm whether a record keeps its history when it moves and how the receiving site can find that history.
| Boundary | Question to test |
|---|---|
| Time | Which time zone controls due dates, notifications and reports? |
| Parts | Are balances separate, and how is a transfer recorded? |
| Assets | Can equipment move while retaining its identity and history? |
| Templates | Which changes propagate, and which stay site-specific? |
| Reporting | Can authorized managers compare sites without manual merging? |
| Integration | Which system owns shared records and resolves update conflicts? |
Compare the actual proposed configuration
Multi-site capabilities can depend on plan or implementation. Fiix lists multi-site management in Professional; MaintainX lists multi-site tools in Enterprise. Ask vendors to demonstrate the required scope in the configuration being quoted rather than relying on the phrase “multi-site.”
Include a realistic expansion case in the proposal. Check whether adding a location changes licence counts, plan eligibility, integrations, onboarding or support. Ask who will configure the additional site and which tasks your own administrator is expected to complete.
Make portfolio reporting comparable
Agree on definitions before comparing backlog, completion rates or costs. If one site closes a job when physical work ends and another waits for managerial approval, their completion reports may describe different events. A shared dashboard does not automatically solve inconsistent data entry.
Use the pilot to trace a small sample from source record to portfolio report. Check filters, date boundaries and excluded statuses. Keep required exports usable outside the platform. The final decision should explain how local work remains practical while regional reporting stays understandable, along with the operational effort needed to maintain that arrangement.