EngineerOS: What It Is, Who It's For, and What It Costs (UK Field Service)

Engineer OS in one paragraph

Engineer OS (engineeros.uk) is a UK-built, mobile-first job management platform for independent field service companies running roughly 5 to 30 engineers: fire and security, electrical and M&E, HVAC and refrigeration, plumbing, heating and gas. Jobs, mobile forms, certificates and photos live in one place, and the engineer app is built to work on a phone in a plant room with one bar of signal. If you were looking for job management for a firm that sends vans and engineers to site in the UK, you are in the right place.

If you were looking for a different EngineerOS

The name is not unique, and the search results are a mess. Three things get mixed up with us regularly.

• engineeros.app, a paid, local-first desktop dashboard for software engineering managers tracking sprints, incidents and architecture decision records. Nothing to do with vans.
• Open-source projects called EngineerOS on GitHub, generally AI developer workspaces for notes, tasks and semantic search. You can see the range of them via a GitHub search for the name.
• EngineerOffice, a US-origin practice management product for design and engineering consultancies, built around timesheets, projects and professional-services billing. This is the one people mean when they type "engineers office", and it is the most common mix-up we see. If you are comparing the two commercially, we have written up EngineerOffice pricing explained.

None of those is this. If you manage software teams or run a consultancy billing by the hour, one of the above is probably what you want, and you can stop reading here with our blessing. If you dispatch engineers to site and your biggest daily problem is where the job sheet went, carry on.

Why the name: an operating system for the way engineers actually work

Most firms this size do not have one system. They have WhatsApp for dispatch, paper job sheets in the van, Word templates for certificates, a spreadsheet for who is where this week, and an accounts package that never hears about any of it until someone types it in on a Friday afternoon. Each part works. The joins are where the money leaks.

"OS" is not a claim to be clever. It just means the single layer all of that runs on, so a job created on Monday morning still has its photos, its certificate and its signature attached in eighteen months when a customer disputes the visit.

For the record, people arrive here having typed eng os, engineero, engineo, engineeo, engineering os, os engineer and os engineering. Same product.

What Engineer OS actually does

Rather than a feature grid, here is the capability, in the order a job moves through the business.

Getting work to the right engineer. Jobs are created once, with the site, the asset and the customer attached, then scheduled to an engineer's day. Reactive work slots in around planned work without rebuilding the week. More on the thinking behind that in our piece on engineer scheduling software.

The engineer app. Built offline-first. The engineer opens the job, does the work, completes the paperwork and moves on. If there is no signal, nothing is lost. It syncs when the phone finds a connection.

Forms and certificates on site. Your existing Word and PDF templates get rebuilt as mobile forms, so the output looks like what your customers already accept. Completed on site, signed on the phone, attached to the job. We have written separately about getting engineering forms on site right rather than just digitising a bad form.

Photos, signatures and evidence. Before and after photos, asset plates, meter readings and customer signatures live on the job record, not in someone's camera roll.

Assets and site history. The next engineer to attend can see what was done last time, what was replaced and what was flagged. That is the difference between a first-time fix and a second visit.

Quotes, invoicing and the accounts handoff. Work done becomes work invoiced, without retyping. Our view on that is in billing software for engineers.

Recurring PPM and service contracts. Planned visits generate themselves on schedule, so contract work does not depend on somebody remembering.

Reporting an owner will actually open. Jobs open, jobs overdue, certificates outstanding, engineer utilisation. Including the parts that make people twitchy, which we cover honestly in tracking engineers without starting a fight.

Who it is built for, and who it is not

Built for: UK limited companies, roughly £500k to £5m turnover, five to thirty engineers, an owner or operations manager who still knows every job on the board, one or two office staff, and engineers whose entire working kit is a van and a phone.

Not built for: sole traders who want a free invoicing app (you do not need this yet), national contractors needing deep ERP or CAFM integration across dozens of divisions, or software engineering teams, who want one of the products in the disambiguation section above.

Saying that out loud saves everyone a wasted demo.

How it compares to what you are probably on now

Versus WhatsApp, paper and spreadsheets. You do not gain speed on day one. Your team is already fast. What you gain is an audit trail and a certificate that does not get lost, which matters most on the day a customer challenges an invoice or an insurer asks for records. Gas work is a good example: only a Gas Safe registered engineer may legally carry it out, and the paperwork proving what was done should not depend on a photo in a group chat.

Versus an older system such as JobLogic. The firms who come to us from established platforms rarely complain about the feature list. They complain about two things: the engineers will not use the app, so the office ends up retyping job sheets anyway, and the annual bill has grown past what the tool visibly earns. Both are fixable, and both are the point of Engineer OS.

Versus ServiceM8 and generic trades apps. ServiceM8 and similar tools are capable, but they are built for a general trades market and, in ServiceM8's case, from Australia. UK compliance paperwork is not a plug-in. Gas, fire alarm and electrical certification, the wording your customers expect, and support in your own working hours are the practical differences.

Pricing and what you are committed to

Engineer OS is priced per engineer, per month. Office and admin users are not charged.

The logic is simple: you pay for the people generating revenue on site, not the people typing. A firm with twelve engineers and two office staff pays for twelve, not fourteen.

There is no long lock-in. Taking on a seasonal engineer for three months should not commit you to twelve months of licence, so seats can go up and down as your team does. Current figures are on the pricing page at engineeros.uk rather than in this article, so you are never reading a number that went out of date last quarter.

Onboarding: what the first week looks like

Day one and two: data in. Customers, sites, assets and any open jobs. If you have a spreadsheet, that is usually enough to work from. If you are coming off another system, we will look at what can be exported.

Day two and three: forms and certificates. We rebuild the templates you already use, starting with the three or four that carry most of your volume, not all forty.

Day four: engineer phones. This is the bit everyone worries about. The honest position is that if an engineer needs more than about ten minutes of training to open a job, complete a form and finish it, the app is wrong, not the engineer. That is the standard we hold ourselves to.

Day five: one real job, run end to end, with someone from your team watching it happen. Then the next ten. Most firms of this size are running live within a week and have stopped printing job sheets inside a month.

Common questions before you book a demo

No signal? The app works offline and syncs later. That is a design decision, not a workaround.

Accounts? Job and invoice data is designed to hand off to your accounts package rather than replace it. Ask us on the call which integrations are live for Xero, QuickBooks or Sage today, and we will tell you straight rather than promise a roadmap.

Import? Customers, sites and assets, yes, if you can export them. Historic job photos from a decade of WhatsApp, realistically no.

Data location and ownership? Your data is yours. If you ever leave, you get it out. We will confirm hosting arrangements in writing before you sign anything.

Next steps

Two sensible routes. If you want to see it against your own jobs, book a demo and bring one messy live job with you, ideally a contract site with history. If you are still deciding, read the longer explainer, What Is Engineer OS?, or the practical case for job management that works on a van and a phone.

FAQ

Is EngineerOS the same as EngineerOffice? No. EngineerOffice is a practice management product aimed at design and engineering consultancies, built around time, projects and professional-services billing. Engineer OS is UK field service job management for firms sending engineers to site. If you were searching for "engineers office", see EngineerOffice pricing explained above.

What does Engineer OS cost per engineer? It is priced per engineer, per month, with office and admin users free. Current figures are on the pricing page at engineeros.uk so you are always reading a live number.

Does the engineer app work with no phone signal? Yes. Jobs, forms, certificates, photos and signatures all work offline and sync when the phone reconnects. A basement plant room does not stop the paperwork.

Can Engineer OS replace JobLogic or ServiceM8? For most independent UK firms running five to thirty engineers, yes. It covers scheduling, the engineer app, forms and certificates, assets and site history, quotes and invoicing, and recurring PPM. Firms needing deep ERP integration are usually better served elsewhere, and we will say so.

How many engineers do you need before Engineer OS makes sense? Around five. Below that, the owner usually still holds the whole board in their head. From five upwards, the cost of lost certificates, repeat visits and chased job sheets is bigger than the software.

Does Engineer OS handle gas, fire and electrical certificates? Yes. They are built as mobile forms from your existing templates, completed and signed on site, and attached to the job and asset record so they can be found years later.

How long does it take to move off spreadsheets and paper job sheets? Most firms this size are running live jobs within a week: data in, key forms rebuilt, phones set up, then one job end to end with someone watching. Full paper elimination typically takes a month.