One site, four services, four different dates
A small office customer has a fire alarm system you service twice a year, extinguishers serviced annually, and fire doors inspected on a frequency the customer agreed with their own adviser. A multi-site retailer has the same mix across forty branches, with visits that must fit around trading hours. A care home wants visits booked weeks ahead and confirmed with the manager.
Your office runs this on a spreadsheet with a tab per customer, or a calendar that shows the alarm visit but not that the extinguishers at the same site are due next month. Engineers go to a site for the alarm service and leave, and three weeks later someone else drives back out for the extinguishers.
Why the schedule keeps slipping
Service frequencies for fire safety systems are agreed per customer and per system, and they rarely line up. The spreadsheet holds dates but does not think about them.
- Due dates are typed in by hand after each visit, if the visit is recorded.
- Different systems at the same site are scheduled separately.
- Missed or partial visits, such as a floor that could not be accessed, are not carried forward.
- Customers who add or remove sites tell the account manager, not the planner.
- Nobody has a view of everything overdue across the whole customer base.
How often each system should be serviced is for your customers and their advisers to decide, with your technical input. The schedule's job is to follow what has been agreed.
The cost of a slipping schedule
A missed service visit puts the customer relationship at risk and can leave a customer asking why their certificate is out of date. Separate visits for systems at the same site waste engineer time and fuel, and customers are irritated by repeated disruption. At contract renewal, a customer who has had to chase you for visits will look elsewhere.
A schedule held per system, planned per site
We build a scheduling layer that holds each system at each site with its own service frequency, and plans visits so engineers do as much as possible in one trip.
- Each customer site has its systems listed: alarm system, extinguishers, emergency lighting, fire doors, dry risers or whatever you service, each with its agreed frequency and last service date.
- Due dates are calculated automatically from the last completed service.
- Each week the planner sees sites with anything due in the coming window, and the tool suggests combining systems due close together into one visit where the customer allows.
- Visits are confirmed with the site contact by email or text, with a link to accept or suggest another date.
- Engineers complete each system separately on their phone, so a partial visit leaves the unfinished system still due, with a reason.
- A dashboard shows all systems as due, booked, done or overdue, filterable by customer, area and system type.
| Situation | Spreadsheet today | System schedule |
|---|---|---|
| Alarm and extinguishers due a month apart | Two separate trips | Combined visit suggested |
| One floor not accessed | Visit marked done | That system stays partly due |
| Customer adds a branch | Told to the account manager | Site added with its systems |
| Overdue services | Found when the customer asks | Listed on the dashboard |
If you already use a job management platform such as Simpro or a fire-specific package, we start by checking whether it can hold schedules this way, and extend it rather than replace it where we can.
The planner's week afterwards
On Monday the planner opens a list of sites with systems due over the next few weeks, already grouped. They send confirmations, handle the replies, and release the week to engineers. Engineers arrive at a site knowing everything due there. The overdue list is short and visible, so it gets dealt with rather than discovered.
Is your schedule like this?
- Service dates are kept in a spreadsheet or calendar by hand.
- Engineers visit the same site twice for different systems.
- Partial visits are recorded as complete.
- Customers have chased you for an overdue service.
- You could not quickly list every overdue system across all customers.