Keep the records. Put ERPNext around the work.

Fire-safety shops already have a system, even when it grew from paper books and spreadsheets. The work-order pad matches the technician’s day. Excel holds receivables, Word makes quotes, and email carries finished documents to the customer. Years of folders contain the proof behind every site visit.

We build the missing workflow around those tools. ERPNext connects the first call with field work and payment, and keeps the old files available by client and year instead of buried in a folder tree only one person understands.

What the paper was costing them

The paper work order carries the full visit. Arrival and departure, break time, travel, regular and overtime rates for one or two technicians. The same sheet holds the safety checklist, the completed work, the materials used and a signature.

A job like that usually produces two or three carbon copies. The customer keeps one, the office files another, and the technician holds one for pay records. Somebody in the office then retypes their copy into billing, line by line, days after the visit happened.

Excel and Word carry the rest. Quotes get written per site, invoices come from a spreadsheet template, and the numbering has grown by hand for years. A number gets reused, a row gets deleted instead of marked void, and the sheet that says an account is paid disagrees with the one that says it’s still owed.

We rebuild that numbering and reconciliation logic once, in ERPNext, so a quote or invoice number never repeats and an outstanding balance means the same thing everywhere staff look for it.

Digital work orders, done once, on the technician’s own phone

ERPNext now holds the technician flow. The job opens on the technician’s phone, where they record the visit and complete the safety checklist. Work performed and used materials stay on that record. A customer can sign before the technician leaves, and a completion photo can join the file.

Clock events can capture location where the phone has a signal. The field work continues inside a mechanical room with poor reception. If a clock event appears physically impossible, ERPNext flags it for office review. Staff see the flag while the technician keeps the job moving.

The office reviews a finished work order before billing. An accepted quote supplies the billing details and tax gets calculated from the approved record. ERPNext makes a locked PDF, sends it by email and records whether delivery succeeded. Payment closes the job after reconciliation.

This is a Missing Piece because one workflow joins tools the shop already uses. A job like this takes 3 to 6 weeks. It ends with a handoff document, and the shop owns the finished system.

Recurring contracts are the business, so the schedule treats them that way

Monthly and quarterly contracts already define the service cycle. ERPNext reads the interval from the agreement and places the next job on the schedule. Office staff can see due work without maintaining a second reminder sheet.

The schedule uses the shop’s existing customer and site language. A recurring record can carry the site access details, service scope and the agreement behind the visit. The next technician opens the same history used by the office.

Annual certificate dates and contract renewals can land in crowded weeks. A due view shows them before dispatch fills the calendar. Staff still choose the technician and date because contract rules cannot know who is off sick or which urgent call arrived that morning.

Roles that keep money away from the people who don’t need to see it

A small office often puts call intake close to billing. ERPNext can keep those jobs in one system while its permission layer separates the records. The admin has full access, including invoices and payments. A coordinator can schedule work and prepare quotes without opening the money screens.

Technicians use the mobile flow for assigned jobs. Their access ends when a job reaches invoicing, since the field record has completed its purpose. That boundary lives in ERPNext’s own permission layer, not just a hidden button. Removing a button from a screen leaves a direct route to the data, so the underlying role has to refuse the request too.

The roles follow the shop’s actual duties. We map who answers calls, who approves prices and which person reconciles payment before the build starts. That map becomes part of the handoff document for the owner.

An archive that stays searchable, not just stored

The old archive still matters after the phone work order ships. Past invoices can settle a dispute, and an inspection report can explain why the next visit has a specific scope. Email threads also carry access notes that never reached the spreadsheet.

Decades of files move into the same client and year structure the office already knows. Staff can browse familiar folders, while ERPNext links current work to the same customer history instead of starting the shop’s records over from zero.

Archive work starts with an inventory. We identify duplicate names, unsupported file types and records whose customer cannot be proven. Staff decide any uncertain match. The import keeps that choice recorded so an old invoice never lands under a site because software guessed.

GPS auditing that flags, never blocks

A fire-safety visit can need location evidence. The building can also block a phone signal exactly where the technician must work. A hard location gate can stop a valid visit in the field.

The workflow records location at clock events when the phone can provide it. ERPNext flags a suspicious distance for office review. It does not reject the technician’s work order. The rest of the day remains outside the location flow.

That rule sits in the handoff material with the other field rules, so the owner can see what the system records and what causes a flag.

Where the honest answer is a lighter tool

A general field service product can cover a shop with standard work orders and a clean customer list. It can already provide a calendar and mobile forms for less than a custom build. Use that route when its process matches yours and the old archive can remain separate.

Missing Piece work fits when ERPNext must follow the shop’s own work order, carry recurring contract rules and bring a difficult archive across. We build one custom workflow, then hand over the system and its operating document. Hosting is billed at cost up to the monthly cap. Any later change has a flat per-feature price, with no retainer.