Multi-site operations with one maintenance standard for every site and building

Apply the same plans, checklists and response times at every location, with one dashboard for the whole portfolio or a single site.

Book a demo
Updated 16 Oct 2026
FieldEx scheduling board on desktop with a technician's inspection checklist open on the mobile app, as used by multi-site maintenance teams

FieldEx is a field service and asset management (FSM+CMMS) application for organizations that maintain many sites, branches or buildings. Every site has its own assets, contacts and service zone. One maintenance plan can apply across all of them. Each site gets a QR code for fault reports, and each client gets a portal. FieldEx reports compliance and workload by site, region or portfolio.

What FieldEx does across a portfolio of sites

Running maintenance across many locations is a consistency problem. You need the same standard at every site and the same evidence from every technician. You also need one place to see which site is falling behind. FieldEx builds that from the site record up. One plan, one checklist and one response target can cover a hundred sites, while each site keeps its own history. Book a demo to see it with your own sites.

Every location as its own site

  • A site record for each branch, store, building or plant.
  • Each site holds its address, map pin and primary and extra contacts, plus its classification, geofence and service zone.
  • Sites linked to their customer and project, with the assets, jobs, tasks and maintenance plans that belong to each one.
  • Site photos, drawings and documents kept on the site record.
  • Site lists filtered and sorted by type, service zone, category, geofence or project.
  • Saved list views for each team.

One plan across many sites

  • Site maintenance plans applied to many sites at once, in Preventive Maintenance. Each site shows its last and next maintenance dates.
  • Asset maintenance plans that pick up every matching asset automatically, including assets added at new sites later.
  • Plans cloned to start a new region or client from a proven plan, with or without its assets.
  • A site removed from a plan without deleting the site record when a location closes.

Fault reporting at every location

  • An automatic QR code for each site that opens a fault-report form without logging in.
  • Each report carries the location, a description, contact details and photos or video.
  • Every report arriving as a job in the backlog with the site already filled in, using a shared default job template.
  • A branded portal for each client on its own subdomain, in the Customer Portal. Clients raise requests and follow every site's jobs there.
  • Service-level agreements per customer or asset, with at-risk and violation alerts.

The right technician for each location

  • Automatic assignment by skill, availability, shift, leave and service zone. Scheduling and Dispatch uses live location to rank the nearest eligible technician.
  • Technician groups tried in the order you set, such as the regional team first and a backup group next. A fallback applies when nobody qualifies.
  • Task journeys that record location, distance and duration between sites, viewable on a map.
  • Manager views of their team's tasks on a calendar, table or map.

Who sees which sites

  • An organizational hierarchy, so a regional manager sees their own sites' records while head office sees everything.
  • Permission profiles that limit users to their own records or open all records, and control web and mobile access.
  • Contractors set up as their own user group, assigned only the jobs and sites they work on.
  • Default list views by profile, so each role opens the sites and jobs that matter to them.

Parts and equipment across locations

  • Stock held by location, zone and store, with each technician's own stock tracked separately, in Spare Parts Inventory.
  • Transfers of parts and equipment between sites and people, with approvals routed to the groups responsible for each zone.
  • Reorder and low-stock alerts per location, and a movement history of every transfer and part used.
  • Arrival and departure times and watermarked photos on every job.
  • Parts from van stock and the client's sign-off on every job.
  • Jobs and tasks can be downloaded and worked offline, with check-in, check-out and travel synced later.

The FieldEx mobile app at any site

  • Each technician's jobs across all their sites, on the FieldEx Mobile App. Each job shows the site's location on a map and the asset's history.
  • QR or barcode scanning to open an asset and its checklist at whichever site the technician is standing in.
  • Check-in and check-out, watermarked photos, parts used and the customer's signature on every job.
  • Jobs and tasks can be downloaded and worked offline, with check-in, check-out and travel synced later.
  • The app in English, Bahasa Malaysia, Chinese, German or Spanish, so teams in different countries work in their own language.

Your own vans, tools and test equipment at every site

  • Service vans, access equipment, power tools and test meters kept as assets, each with its registration or serial number and home site.
  • Track recurring certifications on each asset, with reminders before due dates and certificates attached when records are marked complete.
  • Maintenance plans for vans by date or odometer reading, and workshop machines on their own plans.
  • Exports as CSV, Excel or PDF, or reports emailed on a timetable to each state office or client.

One dashboard for the portfolio

  • Overdue work, work due in the next 7 days and work completed in the last 7 days.
  • Dashboard filters for service zone, group, asset type and time range.
  • Site reports by status, customer, service zone, type and category. Reporting and Analytics also shows the last visit to each site.
  • Reports exported as CSV, Excel or PDF, or emailed on a schedule to each region or client.

FieldEx also runs this kind of work for Multi-Trade Operations, Planned Maintenance & Reactive Repairs and First-Time Fix.

How do you keep preventive maintenance consistent across multiple sites?

Set one standard, apply it everywhere, and check every site against it. The UK's Facilities Management Standard 001, under GovS 004 Property, says it is particularly important to avoid variations in service delivery standards across an estate. It also requires a thorough estate compliance plan that includes every property. The UK government's fire safety guide for offices and shops makes the same point from the other end. Regular checks, servicing and maintenance must be carried out whatever the size of the premises, and defects put right quickly.

What FieldEx does about it

  • One plan, every site: a site maintenance plan covers many sites at once. Asset plans add every matching asset across the portfolio, including new ones.
  • The same checklist everywhere: each plan uses one job template and checklist. Every site's visit asks the same questions and collects the same evidence.
  • Laggards shown by site: each plan lists every site's last and next maintenance dates. The dashboard filters overdue work by service zone or group.
  • Defects fixed quickly: a failed checklist answer creates the corrective job straight away, at whichever site it was found.

Who is responsible for fire safety maintenance at each site in a multi-site business?

The responsible person for each premises, usually the manager with overall control of it. Article 17 of the UK's Regulatory Reform (Fire Safety) Order 2005 sets the maintenance duty. The premises and its fire equipment must be subject to a suitable system of maintenance, and kept in efficient working order and good repair. The government's fire safety guide for offices and shops covers organizations with several premises. Each should decide who the responsible person is for each one.

What FieldEx does about it

  • A named contact on every site: each site holds its primary contact and additional contacts, so the responsible person is on the record.
  • Their own sites, their own view: each site or regional manager sees their own sites' jobs and plans in the hierarchy. Head office sees all of them.
  • Alerts to the right owner: reminders and service-level alerts go to the users or groups you choose for each site's work.
  • Maintenance on schedule at each site: fire equipment runs on recurring inspections per asset type. Each site shows due, overdue and completed status.

Who is responsible for maintenance when several businesses share one building?

Each of them, for their part, and they must coordinate. Article 22 of the Regulatory Reform (Fire Safety) Order 2005 covers two or more responsible persons who share premises. Each must cooperate with the others and coordinate their fire safety measures. Since 1 October 2023, each must also tell the others which part of the premises they consider themselves responsible for, and keep a record of it. Article 17 adds that occupiers of other parts must cooperate with the maintenance arrangements.

What FieldEx does about it

  • The building and its occupiers on one site: the shared building is one site, with each occupier's contacts on the record. Their areas are noted in the site's classification and reference fields.
  • Shared assets, one history: common fire alarms, sprinklers and emergency lighting sit on the building's site record. Every party sees the same maintenance history.
  • Records of who covers what: the written split of responsibilities is attached to the site record, next to the risk assessment.
  • Each client sees its own work: through the customer portal, each occupier sees the jobs and equipment linked to its own account.

How do you run the same weekly, monthly and annual fire checks at every branch?

Set one weekly, monthly and annual rhythm and roll it out to every site. The UK government's fire safety guide for offices and shops sets a common pattern. Each week, test the fire detection and warning systems, following the installer's instructions. Each month, test all emergency lighting and safety torches for charge and illumination. Each year, a competent person tests and maintains the emergency lighting, firefighting equipment, fire alarms and other installed systems.

What FieldEx does about it

  • Set weekly, monthly and annual inspections on each asset that needs them.
  • Site staff do the weekly test: branch staff get mobile access to complete the weekly checklist. A permission profile limits what they can see and change.
  • Contractors do the annual service: the annual job goes to the contractor's group. The certificate is attached to the completed record.
  • Every branch in one view: the dashboard and inspection list filter overdue checks by service zone, asset type or group.

What maintenance records should each site keep, and for how long?

Keep a log book of every test, audit and repair at each site, and keep water-system records for at least 2 to 5 years. The UK government's fire safety guide for offices and shops suggests keeping a log book of all maintenance and testing. The Health and Safety Executive's (HSE) legionella record guidance set the retention periods. Most records are kept while current and for at least 2 years after. Records of monitoring inspections are kept for at least 5 years.

What FieldEx does about it

  • A log book per site, built automatically: every inspection, job, certificate and reading is saved on the site and its assets as the work is done.
  • Available on the premises: the site manager opens the site's records on the web or the phone. The client downloads job reports through the portal.
  • Kept for as long as you need: records stay on the site and asset for as long as you keep them, well past 2 or 5 years.
  • Pulled by site when asked: inspection and job reports filter by site, asset type and period. They export as CSV, Excel or PDF.

How should staff at many locations report faults?

Through one front door that works the same at every site. The UK's Facilities Management Standard 001 says building users should have a single point of access to facilities management (FM) services. That might be a helpdesk for larger portfolios or a building manager for smaller ones. The methods of access must give all users a consistent experience.

What FieldEx does about it

  • A QR code on every site: each site gets its own QR code automatically. Staff scan it and report a fault without logging in, with photos or video.
  • The site is already known: each QR report creates a job with the site filled in and a default job template applied.
  • One backlog for the helpdesk: reports from every site, the portal and the office land in the same scheduler backlog. They are ready to assign.
  • The same experience for every client: each client's branded portal shows their own sites' jobs and lets them raise requests the same way.

How do you manage contractors working across many locations?

Agree how the work will be done, coordinate it, and keep checking it against what was agreed. HSE's guide to using contractors (INDG368) sets these two duties. The client and contractor must work together so the work can be done safely. The client also keeps a check on how the work is going, doing more the greater the risk. HSE's lone working guidance adds that when a lone worker will be at someone else's workplace, the employer must ask that employer about risks and controls.

What FieldEx does about it

  • Contractors as their own group: each contractor's team is a user group. Jobs can be assigned to the group, and its members see only the work given to them.
  • Progress against what was agreed: jobs show their status, check-in and check-out times, photos and checklist answers. Service-level agreements alert you before a target is missed.
  • Site hazards in the job: the contractor opens the job on the phone and sees the site's notes and attachments, such as access rules and risk assessments.
  • Contractor work in reports: jobs and service-level data report by contractor group, site and period.

How do you keep track of technicians working alone at remote sites?

Know where each lone worker is, keep in touch, and be ready to respond if something goes wrong. HSE's lone working guidance applies the Management of Health and Safety at Work Regulations. Employers must manage the risk to lone workers, and must train, supervise and monitor them. They must also keep in touch with them and respond to any incident.

What FieldEx does about it

  • Check-in and check-out on every task: technicians check in and out of each task. A supervisor sees who is on which site and since when.
  • Journeys on a map: task journeys record location, distance and duration, with pause and resume. Managers see their team's tasks on a map view.
  • Live location for dispatch: FieldEx uses technicians' live location to match them to jobs. Outside the live-location window, it uses a predicted location.
  • Offline and still logged: jobs and tasks can be downloaded and worked offline, with check-in, check-out and travel synced later.

How often must a multi-site team's service vans and trucks be inspected?

Inspect commercial vehicles on a set schedule, and give each one a full periodic inspection at least once every 12 months. In the United States, the Federal Motor Carrier Safety Administration's rules in 49 CFR Part 396 set this for motor carriers. Every carrier must systematically inspect, repair and maintain the vehicles it controls. Its records show each vehicle, the due dates of its inspections and the work done. They are kept for 1 year, and for 6 months after the vehicle leaves the fleet. The annual inspection report is kept for 14 months.

  1. Receive and record the complaint, then register it.
  2. Verify and investigate.
  3. Assign it to in-house maintenance or the facilities management (FM) contract.
  4. Update the complaint register and the mySPATA database.

JKR's client charter commits to acknowledging complaints within 1 to 3 days and responding within 7 days. JKR.PK(O)07 gives an example target of 15 minutes for urgent (segera) breakdowns.

What FieldEx does about it

  • Each vehicle as an asset: every van and truck has its own record, with registration, make, serial number and the site it is based at.
  • Due dates on every vehicle: the annual inspection runs as a recurring certification, with reminders before it falls due and the report attached.
  • Servicing by date or mileage: each vehicle's servicing runs on a maintenance plan by date or odometer reading.
  • Repairs on the vehicle's history: defects found on the road become jobs on the vehicle, so its inspection and repair record is complete.

How detailed should an asset register be across a property portfolio?

Detailed in proportion to the building's importance. The UK's Facilities Management Standard 001 requires a complete FM asset register. Its granularity depends on building criticality, and asset condition is reviewed regularly. The standard also asks for a forward maintenance register at least 5 years ahead. It covers short-term needs of 1 to 2 years, medium-term needs of 3 to 5 years and long-term needs beyond 5 years.

What FieldEx does about it

  • Depth chosen per site: register assets with parent and component levels where a site needs them, and as single assets where it doesn't.
  • A consistent structure: asset types, categories and subcategories are shared across every site. The register reads the same everywhere.
  • Condition and status kept current: inspections update each asset's status and meter readings. The change history shows who changed what.
  • Lifecycle data for the forward register: asset reports on age, cost and reliability filter by site. They support the 1-2, 3-5 and 5-plus year plans.
Customer story

A large American facility services company with a regional presence in Singapore runs its field teams across many buildings on one FieldEx system. Before FieldEx, staff emailed service requests to field teams by hand, and managers had no live view. Now more than 100 technicians and contractors work from one schedule. The company groups maintenance by equipment type and location. Every job ends with a digital checklist and a PDF report. Its buildings share the pattern of any multi-site portfolio: one schedule, many locations and a record for each.

Read the Facility Services Case Study

Chubb, an integrated security provider, runs security operations from 18 branches across Malaysia on FieldEx. Its story describes a central dashboard of active, pending and completed jobs. Tasks are assigned automatically by skill, availability and location, and SLA reminders help avoid penalties. Jobs can't be closed until every SOP step is done. Chubb saw a 50% increase in daily completed tasks. Its branches share the pattern of any multi-site operation: one standard, local teams and a central view.

Read the Chubb Story

Questions multi-site operators ask about FieldEx

What is the best maintenance software for multiple sites?

It needs a record for every site and plans that apply across all of them. It also needs a way for each site to report faults and a single view of who is behind. FieldEx does all of these in one system. Field service and maintenance management share the same site and asset records. Compare approaches in our guide to CMMS Software.

Can one maintenance plan cover all our sites?

Yes. A site plan can apply to many sites. Asset plans pick up every matching asset automatically, including assets at sites added later.

Can regional managers see only their own sites?

Yes. The organizational hierarchy scopes what each user sees. Regional managers see their own teams' records, and head office sees everything.

Does each site get its own fault-reporting QR code?

Yes. FieldEx creates a QR code for every site automatically. Reports made through it arrive as jobs with the site already filled in.

Can each client have its own portal?

Yes. The customer portal carries your logo, colors and font, and can run on a branded subdomain. It shows each client only its own jobs, equipment and reports.

Can we compare maintenance performance between sites?

Yes. Reports group jobs, inspections and service-level data by site, service zone, customer or period. Site reports show the last visit to every site.

Can parts be moved between sites?

Yes. Parts and equipment transfer between stores, sites and technicians, with approvals by zone and a movement history of every transfer.

How long does it take to set up FieldEx across many sites?

There's no setup fee. Once we know your requirements and your data is ready, FieldEx can be implemented in as little as a week with standard features for small businesses. Larger setups and custom work take longer. Sites, assets and past jobs can be uploaded. FieldEx helps with setup, and training is included. See Setup and Training.

Run every site to the same standard, from one system

Book a Demo