A service log in Excel: what belongs in it and when it stops being enough

A service log in Excel is a spreadsheet in which a company keeps the history of jobs at customers and on their equipment. As long as one person fills it in, it is usually enough. Technically, Excel can handle it. What decides is how much work it takes to keep such a spreadsheet in order once more people write into it, some of them from the field.

• A service log and a list of orders are two views of the same data, not two sets of records.
• A record should contain the equipment identification, the type of job, a fault description and the condition on leaving.
• Excel can handle it, but you have to design an equipment list and then maintain it.
• The most expensive point is not the writing, but the gap between the job and its being recorded.
• An equipment register with inspection deadlines is a different task from history on the customer.

What a service log is and why it gets confused with a list of orders

A list of orders is sorted by time. You open it and see what happened last week, what is in progress and what is waiting to be invoiced. It is an operational view and the company needs it every day.

A service log is a view of the same data from the customer's or the equipment's side. You ask what was last done on this unit, boiler or switchboard and what was left unfinished. The chronology is still there, it is just not what you search by. The company needs that view only occasionally, but at the worst possible moment: when the technician is standing on site and has nobody to ask.

Many companies keep only the first view and believe they have the second as well. The data really is there, but scattered across the rows of several sheets and without a common equipment identifier. Finding it means reading through, not searching.

What a record should contain

A record that cannot be found, or from which it is not clear who wrote it, is useless to a future technician. The minimum looks like this:

The last row is the one most often missing from spreadsheets, yet it has the greatest value. The sentence "the fan is getting noisy, plan on replacing it next time" gives whoever comes next a chance to bring the part with them.

What Excel can handle and at what cost

Most objections to Excel are phrased as technical impossibility and in that form they do not hold.

A workbook stored in OneDrive or SharePoint handles co-authoring and version history, so two people can write into it. But finding out who overwrote a specific row means comparing versions of the workbook; it is not a change log on the record. Consistent equipment names can be enforced with a list on a separate sheet, data validation and a drop-down list. Photos can be inserted into the workbook or linked to a folder. Excel has a mobile app too.

If you are staying with a spreadsheet, the minimum that keeps it alive looks like this:

1. Create a separate sheet with an equipment list: asset number, customer, location, type.
2. In the equipment column, set data validation with a drop-down list from that sheet and lock the sheet, so it can only be bypassed deliberately.
3. Add a job type column with a fixed selection, so checks can be filtered separately from repairs.
4. Save photos in a folder named by the asset number, not the date, and put a link in the row.
5. Appoint one person who extends the equipment list, and one place where new equipment is reported.
6. Once a quarter, go through the rows outside the list and tidy them up.

The cost of that is not in the licence, it is in the design and maintenance. In a small company it is usually done by the person with the least time, alongside their main job. As soon as that person is out for a month, discipline falls apart and the first manually typed row bypasses the drop-down list.

The second part of the cost is recording from the field. A row of twenty columns is hard to fill in on a phone even in the mobile app. Most companies solve it by having the technician send a message or say it over the phone in the evening, and someone in the office copies it in. That creates a gap of several days between the job and the record, and it is in that gap that exactly the details the log is kept for get lost. The same gap arises in planning too, where it shows in technician utilisation; the comparison of ServisBook with Excel goes into it.

How to tell the spreadsheet has stopped being enough

It is not about the number of rows, but about how many people work with the log and how often it is read from. You can tell by these symptoms:

1. A technician calls the office to find out what was done at the customer last time.
2. There are two rows for the same piece of equipment with different identifiers and nobody knows which is valid.
3. The photo from the job is on the technician's phone, not on the record.
4. Field records are copied into the spreadsheet by someone in the office several days later.
5. During a complaint, people search for who was there.
6. The column with recommendations for next time is empty.

What they have in common is that the information is in the log, but is not available at the moment someone needs it.

Where history is created when it is not a spreadsheet

A service log does not have to be a separate document. The record can be created directly on the order it belongs to, which takes the copying in the office out of the chain.

In the orders and history module, attachments, internal notes and a record of every change sit on the specific order. The customer card shows all their orders together, full-text search works even without diacritics, and labels can be named your own way in customisation without a programmer. History is therefore not created as a second set of records alongside the first, but as a by-product of everyday work.

Recording from the field is handled by mobile for technicians: the technician opens their day, starts the work and logs the tasks done while still on site. That closes the gap of several days that hurts a spreadsheet the most.

This also covers what history kept this way cannot do. It lacks a separate equipment card with a serial number and the date of the next inspection; in it, equipment is a field on the order, not a registered item. For anyone who only needs to know what happened at a given customer and who was there, that fits. Anyone who needs a register of registered equipment with deadline tracking needs additional records on top, which this module does not replace. The companies that most often run into this are those doing inspections and regular checks, where the deadline determines the date of the next job.

From how many people it starts to hurt

From three people. That threshold comes from one thing: from three, technicians regularly take turns at the same customer, so whoever comes was not at the previous job. Mandatory documentation for jobs and a high number of jobs per month push it even lower.

With one person, the service log is their memory and the spreadsheet serves more as a basis for invoicing. With two it usually still holds: both know who goes where, and when they are not sure, they ask across the street.

From three it starts to break, because someone other than the person who was there last time goes to the site. The question of what was done there no longer has anyone to ask, and the answer has to be written down, otherwise people go out again to find out what could have been read. One could object that where every technician has their own regular customers, nobody takes turns. That holds only until the first holiday, illness or two emergencies at once. On that day someone unfamiliar goes to the customer and the history has to be written down, because there is nobody to ask.

What stays the same

Switching from a spreadsheet does not relieve anyone of the duty to record. All that changes is where and when things are recorded and who can get to the record.

Nor does the need to keep equipment identification in order go away. Software searches better than a spreadsheet filter, but even it only finds what has been written down. A unit named differently every time remains unfindable in any system.

What goes away is copying and waiting. The record is created in the field and is on the order immediately, not in three days and not in a second spreadsheet.

Frequently asked questions