Introduction
A tenant reports a leak. The help desk logs the request against a suite, the engineer identifies a failed component above another tenant’s ceiling, and an outside contractor submits an invoice using a building nickname. By the time finance tries to match the invoice to the job, three people have recorded the same incident under different locations.
Facility management software can connect work to the physical places, assets, teams, and suppliers involved. Some products focus on requests and service coordination. Others cover space planning or combine real estate, facilities, and workplace processes in an integrated workplace management system, or IWMS. The scope you need depends on which records must stay connected for people to do their work.
Build a location model that survives a move
Start with a few buildings and write down how people describe them. Finance may use property codes. Occupants use addresses and floor names. Maintenance staff may refer to equipment rooms by a label painted on a door. The software needs a stable identifier and enough searchable names to help each team find the same place.
Distinguish a physical space from its current use. A room can change departments, become a storage area, or be split into two. Historical requests should retain meaningful location information after a reorganization. Ask how the platform represents a room that is no longer available and whether a floor-plan change can preserve references from old work orders.
Walk a sample floor with a technician. Confirm that the plan, room labels, and asset locations match what they encounter. If the drawing shows an air handler in an old location, trace the correction from the field back to the system responsible for drawings. A platform with excellent map features still needs a process for keeping those maps accurate.
Connect requests to the people who resolve them
Use a service request that crosses a boundary. A building occupant reports a temperature problem, the help desk routes it to a building engineer, and an outside contractor investigates the control equipment. Ask the vendor to demonstrate the initial request, the job assignment, the evidence collected, and the update returned to the occupant.
A service portal should make reporting easy. Ask occupants for information they can provide, such as a room number, an approximate time, and a plain-language description. Reserve technical classification for the person who evaluates the problem. Check whether several similar reports can be linked to one incident without losing the list of people who need an update.
For external vendors, use a restricted account in the trial. Give the contractor enough access to locate the job, record work, and upload the agreed evidence. Test whether other buildings, tenant details, or unrelated contracts remain outside that account’s access. Ask how the organization withdraws access at the end of a contract and what happens to the history of work the vendor completed.
Decide how much maintenance capability belongs in the platform
A facilities team coordinating repairs may need strong service routing, location records, and vendor management. A maintenance organization responsible for critical equipment may need deeper preventive schedules, labor and parts history, and asset-level analysis. A workplace team planning a consolidation may care most about floor plans, space assignments, and room inventory.
| Primary problem | Capability to prioritize | Demonstration to request |
|---|---|---|
| Requests disappear between teams | Routing, ownership, and status | Transfer a request and notify the original reporter |
| Asset failures are hard to explain | Maintenance history and asset hierarchy | Trace repeat repairs for the same equipment |
| Space records disagree | Floor plans and durable location IDs | Revise a floor without losing earlier assignments |
| Property decisions span many sites | Portfolio reporting and consistent records | Compare costs and services across dissimilar buildings |
An organization with an established maintenance system can keep that system as the owner of technical asset records while using a facilities portal for intake. If two systems work together, decide which one controls changes to location and completion. Ask what happens when a job is transferred, a vendor withdraws, or a work order is closed in one system while the other is unavailable.
Make reports reflect the work behind the numbers
A portfolio-wide report may compare response times, costs, or overdue jobs. Start by defining when the clock starts and what counts as closed. A request logged on Friday could be acknowledged immediately, scheduled for Tuesday, and physically resolved on Wednesday. Each interval answers a different question about performance.
Compare sites with the same definitions and enough context. A location that records every small request may appear busier than one where staff handle work informally. A high reported contractor cost may reflect a one-off project or a different allocation practice. Show managers the underlying records they need to explain differences, and give finance a way to reconcile cost data.
Plan a small migration before a portfolio rollout
Choose one building with a manageable number of rooms, vendors, and assets. Import active records and enough history to test reporting. Resolve duplicate asset IDs before they become the basis for dispatch or cost allocation. Ask staff who know the building to review a sample. Record who has authority to correct records once the platform is live.
Compare the full scope of the contract, including modules, external user access, floor-plan work, migration, integrations, and ongoing administration. Request sample exports of locations, assets, work history, and attachments. A system that stores records in a way your team can retrieve and interpret gives you more flexibility when the portfolio changes.
At the end of the pilot, return to the original incident. Ask the occupant, engineer, contractor, and finance analyst to find the information relevant to them. If they can trace the job back to the same building, understand what was done, and reconcile the outcome without rebuilding the story from email, the system is doing the work that matters.