Engineer Scheduling Software: A Plain UK Guide for Field Service Firms (5–30 Engineers)

Engineer scheduling software puts every job, engineer, site and contract on one board, warns you before you double-book someone, and pushes the assigned job straight to the engineer's phone. For a UK field service firm running 5 to 30 engineers, the board itself is the easy bit. Every vendor can demo a drag-and-drop planner. The question that decides whether the system earns its licence fee is what happens in the 30 seconds after you assign the job: does the engineer see it on a phone in a plant room with one bar of signal, and does the certificate come back the same day, attached to the job, ready to invoice.

This guide judges scheduling software by that test.

Two different products are called "engineer scheduling software". Make sure you're looking at the right one

Search that phrase and you get two completely different categories fighting over the same words.

The first is project and resource scheduling for design, software and manufacturing teams: tasks, dependencies, Gantt charts and capacity planning. Microsoft Project sits here, as do work management tools like Teamhood, which markets itself for project and portfolio planning. These are built for people at desks.

The second is field service dispatch: assigning engineers to postcodes, against SLAs, with certificates coming back off a phone.

The two-line test: if you are scheduling people to sites with response times, tickets and paperwork, you want field service software. If you are scheduling tasks to a timeline for a team in an office, you want project software. Getting this straight before you book demos saves you three wasted hours.

The rest of this article is about the second kind.

What UK field service firms are actually running today (and where it breaks)

The typical setup at this size is not chaos, it is a working system held together by one person's memory. A wall planner or a shared Outlook calendar. A WhatsApp group per engineer or one for the whole team. Paper job sheets. Word certificate templates saved on the office PC. A spreadsheet tracking which PPM visits are due.

It works until it does not, and it always breaks in the same five places.

• Double bookings. Two jobs, one engineer, nobody spotted it because the calendar entry said "Smith" and not where he actually was at 2pm.
• The forgotten PPM. The contract says quarterly. The spreadsheet says overdue. The customer says something less polite.
• The reactive that eats the afternoon. An urgent breakdown gets slotted in and three planned jobs quietly slide, with nobody telling the customers.
• The job sheet that stayed in the van. Work done, paperwork lost, invoice never raised.
• The certificate chase. A week of emails to get a signed test sheet out of an engineer who has already moved on to five other jobs.

None of those are scheduling problems on their own. They are what happens when the schedule lives in one place and the evidence of work lives somewhere else.

The scheduling board: what good actually looks like

A usable board for a firm this size has:

• Day, week and multi-week views with one column or lane per engineer, so a Monday morning is a glance not an audit.
• Clash and double-booking warnings that fire when you drop the job, not after.
• Travel time and postcode clustering, so you can see that sending the Croydon van to Watford at 3pm was optimistic.
• Skills and tickets on the engineer record, including Gas Safe, F-Gas, BS 7671 18th Edition and fire industry qualifications, with a warning when you assign work to someone who does not hold the right one. This is not administration for its own sake: gas work must be carried out by a Gas Safe registered business under the Gas Safety (Installation and Use) Regulations 1998, and handling fluorinated gases requires certification under UK F-gas rules.
• Holiday, sickness and training visible on the same board, not in a separate HR tab.
• Recurring PPM generation from the contract, with the year's visits laid out and adjustable.
• A way to slot an emergency in without rebuilding the week, ideally by dragging one job and seeing exactly what moves.

That is the whole list. Anything else on the board is decoration.

What happens after you assign the job. The part nobody demos

Here is the sequence that matters, and the one you should insist on seeing live.

You drop the job on Dave's Tuesday. Within seconds his phone buzzes. He opens the job and gets the job pack: site address and access notes, the asset list, the last three visits, the previous certificate, the customer's site contact. All of that needs to be on the device already, because the moment he walks into a basement plant room the signal is gone.

He marks himself travelling, then on site. He works. He fills in the form on the phone, takes photos of the panel and the fault, completes the certificate, and gets a signature on the screen from whoever is there. He marks the job complete.

None of that requires a connection if the app is offline-first, meaning it stores the job locally and queues everything to sync later. Plenty of apps are online-only with a thin cache. They look identical in a demo held in an office with full wifi, and they fall over in a rural site, a lift motor room, a retail basement or a car park.

When Dave gets back to the van and picks up a bar of signal, everything syncs. The office sees the completed job, the photos and the signed certificate without phoning anyone.

That is the difference between a scheduling tool and a system that actually runs the work. If you want the detail on how the whole day looks from the engineer's side, we have written that up separately in job management for engineers on a van and a phone, and the paperwork side in engineering forms UK field service firms actually need on site.

Scheduling is only useful if it reaches the invoice

Follow the chain: job scheduled, job completed, paperwork attached, job marked ready to invoice, invoice out.

Most scheduling-only tools stop dead at "completed". Everything after that is a second data entry job for the office: retype the labour, retype the parts, find the certificate, email it separately, raise the invoice in the accounts package.

The systems worth paying for carry the job data forward, so the person raising invoices sees a queue of completed jobs with the evidence attached and the parts already listed. Add an unbilled work report, which lists completed jobs with no invoice against them, and most firms this size find money in the first month that they had genuinely lost. We go deeper on that chain in billing software for engineers.

Features that matter for 5–30 engineers vs features that are enterprise theatre

| Matters at your size | Enterprise theatre at your size | |---|---| | Clash and double-booking detection | AI route optimisation across 200 vans | | Offline-first mobile app | Dynamic re-optimisation every 15 minutes | | Certificates and forms built for your trade | Multi-region workforce forecasting | | Recurring PPM scheduling with asset registers | Multi-stage approval workflows | | Timesheets generated from job data | Custom BI dashboards and data warehouses | | Six reports you will actually open | Sixty reports nobody opens |

Nothing in the right-hand column is fake. It is genuinely useful if you run 300 engineers across five depots. When you run 12, you are paying for the build cost, the training cost and the complexity of features designed for someone else's problem. That is the honest reason older systems can cost more than they earn: not that they are bad, but that they were priced and designed for a bigger company than yours.

What it costs, and how to work out whether it pays

UK pricing in this market is usually per user per month, and the details are where the number moves:

• Separate office and engineer licences, often at different rates.
• One-off implementation and data migration fees.
• Minimum contract terms, commonly 12 months, sometimes longer.
• Charges for custom certificate and form templates, which is where a lot of firms get caught, because the templates are the whole point.

Some vendors publish plans openly, such as Joblogic and Commusoft. Others quote only after a demo. Either way, ask for total first-year cost, not the headline per-user figure. For a worked example of how these quotes stack up, see EngineerOffice pricing explained.

Then run this arithmetic with your own numbers. No estimates from us, because your figures are the only ones that count.

1. Office hours per week spent rescheduling, chasing job sheets and re-keying paperwork, multiplied by loaded hourly cost, multiplied by 4.3.
2. Plus the value of jobs lost or re-attended in a typical month because of double bookings and missed PPMs.
3. Plus your monthly unbilled work: completed jobs with no invoice raised. Check the last three months properly.
4. Minus the total monthly cost of the software, including the setup fee spread over 12 months.

If line 4 is comfortably negative, stop deliberating.

Why engineers reject scheduling apps (and how to stop it happening again)

Engineers do not reject software because they are technophobes. They reject apps that:

• need a signal to do anything useful
• take twelve taps to record a two-minute job
• log them out daily and lose part-filled forms
• flatten the phone battery by lunchtime
• feel like surveillance rather than support

The last one deserves care. If tracking arrives as an announcement, it lands as an accusation. If it arrives as a conversation about proving attendance for SLA disputes and getting people home quicker, it usually lands fine. The ICO's guidance on monitoring workers sets out what you need to tell staff and why, and it is short enough to read before you roll anything out. We have covered the practical side in how firms track engineers without starting a fight.

Before you sign anything, run the one job, one phone, one plant room test. Take the app to your worst-signal site, with your most sceptical engineer, and complete a full job including certificate and photos. If that works, adoption is a training problem. If it does not, no amount of training fixes it.

How to run a fair trial in two weeks

1. Pick one real week of jobs. Not a sandbox. At least one reactive callout and one PPM visit.
2. Pick two engineers, one of whom thinks this is a waste of time. He is your best tester.
3. Run in parallel with the existing system for those two weeks. Yes, it is double work. It is two weeks.
4. Test in a bad-signal site deliberately. Aeroplane mode counts as a first pass, a real basement counts as the real test.
5. Check the certificate output against what your fussiest customer currently accepts. Print it. Look at it.
6. Test your exit. Ask them to export your data mid-trial and see what you actually get back.

Five questions for every vendor, in writing:

• Is the mobile app offline-first, and can a full job be completed with no connection?
• What is the real total monthly cost, including setup, spread over year one?
• Who builds our certificate templates, how long does it take, and what does it cost?
• How long is the minimum contract and what is the notice period?
• Can we export all our jobs, customers, certificates and photos, in what format, at no charge?

Choosing between engineer scheduling solutions: a short shortlist logic

The UK market splits into three groups.

The big incumbents. Feature-rich, mature, genuinely capable, and built and priced with larger teams in mind. If you need multi-depot stock control and complex approvals, they earn their money. If you need a board and a working mobile app, you will pay for a lot of shelf.

The lightweight scheduling and timesheet apps. Cheap, quick to start, fine for allocating time. They generally cannot do trade certificates, asset registers or PPM contracts, so the spreadsheet survives and you now run two systems.

The middle ground built for 5 to 30 engineers. Scheduling board, mobile forms, certificates and photos in one place, priced for a firm doing £500k to £5m rather than £50m.

That is where Engineer OS sits. Jobs on a board, pushed to the engineer's phone, forms and certificates completed on site whether or not there is signal, photos and signatures attached to the job, and the completed work sitting ready to invoice rather than in a van door pocket. If you want the plain version of the scope, here is what Engineer OS is.

Next step, if you want one: take your worst-signal site, your most sceptical engineer and one real job, and test whichever three systems make your shortlist against exactly that. The one that survives is the one to buy.

FAQ

What is engineer scheduling software and how does it differ from a shared calendar?

A shared calendar records that someone is busy. Engineer scheduling software records the job: site, asset, fault, access notes, SLA, skill required and paperwork due. It pushes that job to the engineer's phone, takes status updates back, and carries the completed certificate and photos through to invoicing. A calendar tells you where someone should be. Scheduling software tells you what actually happened.

How much does engineer scheduling software cost in the UK for a team of 5–30 engineers?

Almost always per user per month, frequently with separate office and engineer licences, plus one-off setup, data migration and certificate template fees, on a minimum term. Some vendors publish plans, including Joblogic and Commusoft; others quote after a demo. Ask for the total first-year figure, then compare it against office hours lost to rescheduling and your unbilled work over the last three months.

Does engineer scheduling software work offline when engineers have no signal?

Only if it is offline-first. That means the job pack downloads in advance, and forms, photos and signatures can be completed with no connection and sync when signal returns. Many apps are online-only with a small cache and will stall in a plant room, basement or rural site. Ask whether a full job, certificate included, can be completed in aeroplane mode, then test it on a real site before signing.

Can it handle planned maintenance (PPM) contracts as well as reactive callouts?

Proper field service systems generate recurring PPM visits from the contract, tie them to an asset register per site, and show them on the same board as reactive work so you see collisions before customers do. Lightweight scheduling and timesheet apps usually cannot, which is why the PPM spreadsheet survives. Ask to see a 12-month PPM schedule generated live during the demo, not a screenshot.

Will it schedule based on engineer skills and certifications like Gas Safe or F-Gas?

Most credible systems let you tag engineers with tickets and warn you when you assign work to someone who does not hold the right one, and the better ones track expiry dates. This matters legally as well as operationally: gas work must be carried out by a Gas Safe registered business, and handling fluorinated gases requires certification under UK F-gas rules.

How long does it take to move off spreadsheets and WhatsApp onto a scheduling system?

Budget two weeks of parallel running with two engineers and a live week of jobs, then two to four weeks to bring the rest of the team across. The software is rarely the bottleneck. Cleaning your customer and site list, building asset registers for PPM contracts and getting certificate templates to match what your customers already accept is the real work. Do it first and the switch itself is short.