Online service log: what it is and what it must contain

An online service log is a job history stored on a server and available from a browser, not a file on a disk. The practical difference is not that it is on the internet, but that several people can write in it at once, each under their own name, and the technician can reach it directly at the customer's. Simply moving it into a browser, however, fixes nothing.

• Online does not mean better. It means more writers, individual logins and availability from the field.
• A service report is the record of a single job. The log is the continuous history.
• The most valuable entry is the one made on site, not the one typed up in the office in the evening.
• Before rolling it out, check entry from a phone, photo storage and what the customer will see.
• From three people, technicians take turns with one customer and the log stops being optional.

What the word online does to a service log

Three specific things, and they are worth separating from the marketing impression.

Concurrent access. The office and the technicians write in the log at the same time without overwriting each other's lines. The step of merging two versions of a file goes away.

Individual logins. Every entry shows who wrote it. It is not just a matter of control: when a record is unclear, there is someone to ask, and no need to guess from handwriting or the date.

Availability from the site. The technician opens the history at the customer's, not after returning. That is the difference the log is kept for, because that is exactly where the information is needed.

What online does not bring by itself is order. Inconsistently named equipment stays untraceable even on a server, and an empty field stays empty.

A service log and a service report are not the same thing

A report is the record of a single job, usually signed by the customer, and serves as the basis for invoicing and for complaints. A service log is the continuous series of those jobs and serves the person who comes next time.

Companies merge them because they fill in the report anyway. The result is a set of records that contains everything but nothing can be read across time: a hundred signed sheets will not answer the question of how many times that unit has already been repaired. The report belongs in the log as an attachment, not in its place. What the record itself should look like is covered in the service report and its template.

What an online service log must contain

The last row is the one an online log can make the most of. In a spreadsheet nobody reads it, because nobody can get to it. An open history on the order shows it to whoever is going there right now.

How a field entry gets into the log

This is where it is decided whether the log will be complete or half empty. A procedure that works well:

1. The technician has the day open on their phone before leaving, including the history for the order in question.
2. On arrival they start the work, which records the actual start, not an estimate from memory.
3. They log the tasks done immediately after finishing, while they still have them in their head.
4. They attach a photo of the condition to the order, not to the phone's gallery.
5. In the note they write one sentence for whoever comes next time.
6. The office does not check the entry line by line, it only adds what is missing for invoicing.

In practice, the mobile for technicians is built on this: the technician opens a browser, sees their day, starts the work and logs the tasks. The entry is finished before they leave the site.

Points three and five are where it usually fails. When the entry is put off until the evening, it lacks the details, and when the recommendation is skipped, the log turns into a timesheet.

What to check before you roll out the log

Five questions worth asking during the trial, not after six months:

1. Can an entry be made on a phone with one hand, or is it a form with twenty fields?
2. Can the history be read at the customer's without knowing the order number?
3. Where are photos stored and how large a file will the tool accept?
4. Who sees internal notes and what would the customer see if they were given access?
5. What happens when the technician has no signal?

Question four is the one most often underestimated. An internal note such as "customer pays late" has its place in the log, but it must be clear that the customer will not see it. Decide that before you start writing in the log.

Where the history is created

In the orders and history module sit the attachments, internal notes and a record of every change on a specific order; the customer card then shows all their orders together and search works even without diacritics. So the history is not created as a second set of records alongside the first, but as a by-product of ordinary work.

Since September 2026 this also includes the equipment card. Every unit at a customer's (boiler, lift, fire extinguisher) has its own card with a serial number, a history of results and inspection deadlines that run from the inspection actually carried out. The list shows what is overdue, and the inspections at one address become an order for the whole site visit in a single action. The technician in the field records OK, Fault or Not done for each unit and the next deadline moves on its own.

Appointments are the other half of it. The appointment calendar distinguishes a proposed and a confirmed appointment and holds a multi-day installation as one continuous bar, so the plan shows which days are fully booked.

From how many people it makes sense

From three. Up to two people, the service log is largely the memory of whoever was there, and the entry serves mainly for invoicing. From three, technicians regularly take turns with one customer, so the one who arrives was not at the previous job and has no one to ask.

One could object that where every technician has their own regular customers, nobody takes turns. That holds only until the first holiday, sickness or two emergencies at once. On that day someone unfamiliar goes to the customer and the history has to be written down.

It applies sooner than elsewhere to companies in service and installation, where several people take turns on one order and the previous job is the input to the next.

What an online log will not solve

It will not write down for the technician what they did. The tool lowers the cost of an entry, but it does not decide whether a person writes a sentence that will help someone next time, or just ticks off that they were there.

Nor will it sort out a mess in equipment names. Text search can handle a typo and missing diacritics, but it will not join a unit named differently every time into one history.

What really goes away is the gap between the job and the record. The entry is made on site and is on the order straight away, not three days later and not in a second spreadsheet.

Frequently asked questions